One thing I learned from working with experienced engineers is that solving a problem and approaching a problem are two different skills.
During one of my projects, I had the opportunity to work closely with Microsoft engineers.
Since I was working independently, whenever I faced an issue, I would first spend time exploring it myself. I would check the data, logs, code, test different possibilities, and eventually figure out a solution.
But sometimes, when I discussed the same issue with them, I was surprised by how differently they approached it.
Instead of immediately looking for a fix, they would pause and ask a few simple but thoughtful questions. Those questions often narrowed the scope of the problem quickly and helped uncover the root cause much faster than trial and error.
Over time, I started adopting that mindset.
I learned that spending more time understanding why something is happening often leads to a better outcome than rushing into how to fix it. I also picked up many small but valuable engineering habits from everyday discussions, habits that continue to help me in my work today.
Courses and certifications definitely help us learn new technologies.
But some of the best learning in my career has simply come from working with skilled people, observing how they think, and applying those learnings in my own way.
Grateful for the experiences, mentorship, and the people who generously shared their knowledge along the way.
Top comments (1)
dev.to is also great source for learning ๐