The best engineering books aren't those you read at the start of your career. It's the ones you appreciate 5 years in.

The Buxton Index measures an entity's planning period and explains many of your work dynamics.

Do Hard Things is a recent book from an author of my favorite book about burnout (Peak Performance). It talks about why our traditional view of toughness is wrong.

Overtraining won't always get you to the finish line faster. Growth comes in cycles - rest, push hard, recover. Less can be more when it comes to achieving your goals

Dive into this engaging exploration of hands-on learning from pottery to programming. Discover how embracing new experiences can enhance personal growth and improve your coding skills.

Great question. Common concern. *What if I get stuck in a technology that isn't hot??* Or worse, burn out re-learning every new thing 😱

Chatting about teaching and learning complex technical skills with an engineer I'm mentoring. She's a former chef. We shared the same frustration with online resources.

A critical look at a conference talk that went great but felt a little off.

Boo meetings, yay code, right? There comes a time in your career when coding is no longer your highest impact contribution. Might even be holding you back. 🙊

Earlier in my career when I thought I was god's gift to engineering but wasn't, I failed one of those stupid interview questions that "have nothing to do with the work". It was a great question.

The opposite of folks who follow every FAANG trend and over-engineer their companies to death, are the folks who *never* take advice from the big boys.

When I dropped out of college to focus on freelancing back in 2012, I set 3 ground rules:

When I first picked up Software Engineering at Google I thought it was another one of those FAANG books full of lessons that make no sense at human scale. I was surprised, lessons apply to teams as small as 5.

In his book, The Art of Science and Engineering, Richard Hamming says the key to a great career is vision. What does that really look like?

I've been computering daily for 24 years, since I was 9, and managing RSI since high school. People often ask how it never gets bad. This is the article I always wish I had written.

Next time you finish a project, ask yourself: *"Might this work be important?"*. Add the polish.

What slows you down most while coding? It's not lack of skill. It's not lack of ideas. It's uncertainty. Fear.

The year that felt like a drag and ended in the blink of an eye.

Productivity porn shows you how to pack more into your day. Productivity porn is wrong my friend. You need to remove things to grow.

Would you take some % of your salary in bitcoin? The joke is that compared to pre-IPO equity, bitcoin is predictable and has a known value.

Wow, college was such a waste of time ... when did you ever invert a binary tree outside of an interview? Honestly I never inverted a binary tree in college either ☹️

You start a new job and it's amazing. Code all day, clear objectives, easy guidelines, ship a bunch of features be a hero. Then something happens and suddenly you get nothing done. 🤔

Understanding beats knowledge every day. To have a strong career, learn to understand, not just to know.