What I Wish I Knew 20 Years Ago as a Software Engineer
Key lessons I wish I had known earlier in my career—focusing on problem-solving, collaboration, and lasting impact.
When I started out, I thought being a good engineer was all about writing complex, elegant code. I spent hours optimizing for performance, thinking that shaving off milliseconds was the key to building great software. But over the years, I’ve realized that none of that matters if your code can’t be maintained or scaled.
Here’s what I’ve learned:
Solve the
Keep reading with a 7-day free trial
Subscribe to Building Better to keep reading this post and get 7 days of free access to the full post archives.