Why do some projects ship and others seem to drag on forever? You need 3 people to get this right.

You can't prevent bugs. You'll burn out. Instead focus on making them quick to fix.

Manny Lehman was one of the first to notice that software is never done. It just continues to evolve forever.

The Series A inflection point is the most fun time in a startup, if you ask me. Here's what it looks like

When yaks aren't procrastination, they might be tunnel vision. You're so focused on the right solution, you miss the good enough solution

A small improvement that lands is better than a large improvement stuck in review

A long design phase without shipping kills many software projects. Here's a story from production I haven't shared before.

5 common themes

You can't fix everything. Focus on the next big thing and let the small fires burn.

Removing a single line of code slashed database CPU usage by 66% 🤘

Swizec reveals the hidden pitfalls of overusing the DRY principle in coding, leading to bad abstractions. Discover how to write adaptable, efficient code that avoids these common traps.

This talk from C3Fest summarizes the key lessons I've learned in the past ~15 years of working in tech startups. It's a high level overview of a new book I'm writing (60% done).

Here's a trap that talented engineers fall into all the time. It creates frustration, burnout, and the genre of tweets that read like "Why don't people care about the amazing work I'm doing".

Discover the potential pitfalls of spurious automation and learn a foolproof three-step process to automate any task effectively. Don't miss out on understanding when automation is truly beneficial and when it can become a hindrance.

Not everything needs to work forever. Start by solving the problem

Decided to publish my notes because they look pretty useful on their own. Although I hope my stage presence adds a little something something. Enjoy :)

All the hard lessons learned using feature flags in production. Skips the why and gets to the how.

here's war story from last summer. I've talked about it in workshops but haven't written it down before. It's for a book I'm working on.

Many engineering challenges start with your roadmap

effective engineering teams should work *with* their product owner/manager, not *for* them

When working: sync first *then* async

A shift in your code review process can boost your team's productivity. Empower authors to make the call.

Don't get stuck being a critical member of the team.

Team dysfunction where everyone's a soloist? Try this fix: Force the team to work on ONE story at a time.

Ever felt like your software team is just soloists in a trench coat? You may be right!

No amount of growth hacking, investor money, or a/b testing will save you, if people don't want what you have.

Agile is something you are, not something you do.

Talk about today, not yesterday

Books start with a detailed outline that's easy to change. That's when they're easy to change and where you can help.

Swizec is writing "Scaling Fast", a book about his journey in a 20x hyper-growth startup. Questions?