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 other nonsense. - HN / What I’ve Learned in 45 Years in the Software Industry

• 68 Bits of Unsolicited Advice
• 39 pieces of unsolicited advice for Software Engineering Managers
• Drunk Post: Things I’ve learned as a Sr Engineer / HN
• An incomplete list of skills senior engineers need, beyond coding

Focus on the Fundamentals

Technology constantly changes, but some fundamental approaches to software development transcend these trends. Here are six fundamentals that will continue to be relevant for a long time.

• Teamwork — Great teams build great software. Don’t take teamwork for granted.
• Trust — Teams move at the speed of trust. Be the kind of dependable person you would want to work with.
• Communication — Communicate honestly and proactively. Avoid the curse of knowledge.
• Seek Consensus — Take the time to bring your whole team along. Let discussion and disagreement bring you to the best solution.
• Automated Testing — Well-tested code allows your team to move fast with confidence.
• Clean, understandable, and navigable code and design — Think of the next engineer that will take over your code as your customer. Build code that your successor won’t have any trouble reading, maintaining, and updating.

Simplicity

Fighting complexity is a never-ending cause. Solutions should be as simple as possible. Assume the next person to maintain your code won’t be as smart as you. When you can use fewer technologies, do so.