What I’ve Learned in 45 Years in the Software Industry
This is the opposite of what you get from new hires/juniors: they tend to focus on which stacks matter, what to learn, how to develop, deploy and maintain. Not much real advice on the behavioral side, to the point that people often take trainings for behavioral interviews and memorize “leadership principles” and other nonsense.
Something that I find interesting is that career advice coming from professionals having many years of experience focuses almost exclusively on the people aspects and not the technology: communication, trust, teamwork, documentation, clarity. The advice is clear, precise and honest. This is the opposite of what you get from new hires/juniors: they tend to focus on which stacks matter, what to learn, how to develop, deploy and maintain. Not much real advice on the behavioral side, to the point that people often take trainings for behavioral interviews and memorize “leadership principles” and…
related reading
- Don't Call Yourself A Programmer, And Other Career Advice | Kalzumeus Softwarekalzumeus.com
- What to learndanluu.com
- Don't Call Yourself A Programmer, And Other Career Advice | Kalzumeus Softwarekalzumeus.com
- Stuff you should have been taught in college but weren’t – Casey Handmer's blogcaseyhandmer.wordpress.com
- Don't Call Yourself A Programmer, And Other Career Advice | Kalzumeus Softwarekalzumeus.com
- Things they didn't teach you about Software Engineeringvadimkravcenko.com
- Lessons learned in 35 years of making software – Jim Grey on software managementdev.jimgrey.net
- Advice for new software devs who've read all those other advice essays • Buttondownbuttondown.email
- I felt obliged to comment because I feel I know what you are talking about and I... | Hacker Newsnews.ycombinator.com
- One lesson from 19 years at Microsoft.linkedin.com
- Drunk Post: Things I’ve Learned as a Senior Engineerluminousmen.substack.com
- How I Hire Programmers (Aaron Swartz's Raw Thought)aaronsw.com