Quote:
Originally Posted by Tervuren
svandamme, I'm curious if you would share how you think you arrived at your problem solving skills, it would seem from what you say that how you approach/think is a rarity.
|
I think it's because i never learn in the classic way, i tend to learn on the job by trial and error. So chances are I'll have seen the problem already before when learning it.
If you run into a wall once, you'll remember it, maybe not the details of wat type of brick it was.. but you'll know where the wall is.
Also as a kid I was much into Lego, i was alone a lot and would spend ages building stuff. Also spent a lot of time dimantling anything i could get my hands on.. radio's tvs, computers my bike, my motocycle.
I was a high school dropout, and wiggled my way in IT.
In the beginning of my career that was though, because i'de get stressed out and get locked in on a problem, like a writers block thing... the more i focussed the less ideas i got.
So i learned to distract myself from the problem, by doing something else.
Sometimes you have to ignore a problem a bit first to get an idea on how to fix it.
Obviously that don't work for urgent things. But for some reason I do better with urgent things because well, they tend to be clearly defined problems.
So the systematic approach on things for the most part has become instinctive.
It's sort of my thing..
It doesn't work on everything, like I can't do vbscript for the life of me..I'm not a programmer.
We have some really clever folks in our company, more clever then I am.
And those never escalate much to us, or when they do , it's a clear bug for R&D.
But some, they just never seem to progress or learn from previous encounters.
If you have somebody that escalated and issue, and you fixed it, with feedback to them that the prereq's weren't ok.
You'de think they would remember.
Maybe a second time they miss something.
But not 5 times in a row, within 6 months, right?