The first step in my career was learning how to do things, but it took understanding why I was doing them for my career to take off. I went from completing tasks to asking why, then understanding the impact of my work, and eventually gained the ability to find the most impactful things to work on.
Comments
Sometimes the impact of the work is not visible until later. And the impact doesn't pan out like I had imagined. Do you have any suggestions to minimize such instances?
Once I started focusing on the "why" behind my work, it helped me prioritize better and create more impact. It’s a big step from just completing tasks to truly making a difference.
The most "impactful" may not be the coolest geekery. It does deliver on business goals.
Good teams reward asking why.
What’s the job of what I’m building? Pushed me to ask the whys
Interested in hearing Kelsey’s thoughts on this
You also need to understand the business purpose of every piece of code you write.