54
Computer programming provided numerous technical puzzles to solve. I can still recall
coming into
the office, starting work on a particular section of code in the morning, and not
leaving my desk for hours. I could get lost in the puzzle-solving feedback
loop of thinking about
a problem, writing some code, testing that code until it worked, and then moving on to the next
problem. Those were wonderful learning experiences for me; however, I began
to seek out
different, larger problems. I transitioned from a technical role to that of a project manager and
later a business analyst. Where my technical roles were more about solving problems on my
own, my project manager and business analyst roles were more about solving problems with and
across larger teams. My aspirations grew to manage a team, but I had my first professional
experience with rejection when I was turned down for a manager promotion. It was a valuable
lesson. I had gone into
the interview over-confident, even cocksure, that I would get the job. In
reality, I was underqualified for the position, not yet mature enough for the responsibilities, and
came across as arrogant during the interview. I eventually earned
my first manager assignment
leading a large team of twenty-five highly tenured and technical engineers and entered the next
significant phase of my career.
Do'stlaringiz bilan baham: