You make a fair point about git blame—we've always forgotten our old code.
But there's a crucial difference between forgetting the "what" (the specific lines of code) and forgetting the "why" (the architectural trade-offs and business reasons). My concern is that AI-driven development accelerates the forgetting of the "why."
I couldn't agree more with your breakdown! These three categories perfectly capture the landscape of most tech roles today.
Your point about the early-stage company experience particularly resonates with me. Like you, I don't have a prestigious university background, and what you said about finding true peers/mentors really hits home. I think most of us in tech struggle to find mentors who can provide genuine strategic guidance rather than just technical advice.
I'm also drawn to startups and the prospect of working with brilliant teammates. The energy and growth potential in such environments is unmatched. But finding these 'small but mighty' companies feels like searching for needles in a haystack - they're rare gems where everything aligns: smart people, exciting work, and good culture.
Just curious - when searching for these early-stage roles, did you have any specific strategies for identifying truly promising opportunities? And the trickier question... how did you assess whether you'd be working with genuinely smart people versus just well-practiced interviewers?
Wow, thank you for sharing such a detailed and honest career journey! I really resonate with what you're saying about shifting focus to becoming an expert rather than trying to stay sharp in everything. The pressure to 'know it all' can be overwhelming, but as you've shown, doubling down in one area can actually open new doors and create opportunities.
I'm on the fence about the certification learning approach you mentioned - not sure if it would work the same way for me, but it's interesting to hear how you used it.
Your point about building financial runway is incredibly helpful - definitely something I'll keep in mind when planning long-term career moves.
Thanks again for sharing your insights and perspective!
I'm curious - how do you maintain the energy to learn new technologies while keeping your existing skills sharp?
Don't you ever feel burnout or fatigue from the constant need to stay current? Would love to hear your strategies for sustainable learning in this field.
I appreciate your advice about certification and specialization.
However, from my experience in software engineering, I've observed that certificates seem to carry less weight compared to previous employers and actual work experience. Companies tend to focus more on demonstrated skills and project history. Nevertheless, thank you for sharing your perspective!
Thank you for your insights! I'd love to hear your thoughts on choosing between companies/industries.
While I'm naturally drawn to smaller companies despite the higher job security risks (risk/reward ratio makes sense to me), I've found that many startups lack the interesting work and open culture they advertise, and sometimes their business prospects are questionable.
As for larger companies, they often seek technical leads with management experience, which creates a barrier for someone like me.
How did you navigate this dynamic in your search?
But there's a crucial difference between forgetting the "what" (the specific lines of code) and forgetting the "why" (the architectural trade-offs and business reasons). My concern is that AI-driven development accelerates the forgetting of the "why."