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
- On becoming competitive when joining a new company – Ludwigludwigabap.bearblog.dev
- What to learndanluu.com
- Things unlearnedscattered-thoughts.net
- Things they didn't teach you about Software Engineeringvadimkravcenko.com
- Advice for new software devs who've read all those other advice essays • Buttondownbuttondown.email
- Stuff you should have been taught in college but weren’t – Casey Handmer's blogcaseyhandmer.wordpress.com
- Habits of great software engineersvadimkravcenko.com
- AddyOsmani.com - 21 Lessons From 14 Years at Googleaddyosmani.com
- Don't Call Yourself A Programmer, And Other Career Advice | Kalzumeus Softwarekalzumeus.com
- Thoughts on the software industry | linus.coffeelinus.coffee
- Four lessons I learned after my first full-time job after collegehuyenchip.com