There is a typo in your recap section "The quantity of experience you get is much more important then its quantity.", you must have meant "The quality of.."
Great tips Peter. Some of these tips made me think about my experience in a growth engineering team where we worked with so many teams and various stakeholders. If you ask the right questions you can try to find teams that allow you to see the forest for the trees instead of just one piece. I definitely learned a lot that way (eg: working with sales on lead scoring pipeline and understanding how a sales team operates)
Also strongly resonate with writing on substack as a way to gain experience. Reading yours and other engineer's articles motivated me to start Karthik's Newsletter to share my learnings in the engineering journey and make it accessible + actionable
Some great tips Petar.
Personal projects are my favorite of the list. They can help so much when work projects are not up to par.
This are really awesome tips to grow.
There is a typo in your recap section "The quantity of experience you get is much more important then its quantity.", you must have meant "The quality of.."
thank you for the feedback, much appreciated
Personal projects are my favorite playgrounds to explore new techs, excellent article my friend!
Great tips Peter. Some of these tips made me think about my experience in a growth engineering team where we worked with so many teams and various stakeholders. If you ask the right questions you can try to find teams that allow you to see the forest for the trees instead of just one piece. I definitely learned a lot that way (eg: working with sales on lead scoring pipeline and understanding how a sales team operates)
Also strongly resonate with writing on substack as a way to gain experience. Reading yours and other engineer's articles motivated me to start Karthik's Newsletter to share my learnings in the engineering journey and make it accessible + actionable