The website vs webapp debate is at least as old as my career. And it keeps coming up. One camp says "React is too complex you don't need any of that", the other camp goes "I don't understand how you live like this". Both are right.

The trick, then, is to keep related code close together to reduce context boundaries and to limit the amount of relevant detail so it fits in your working memory.

I guess if AI is what it takes to finally get people to care about architecture and team structure then mission accomplished?

The best part about writing is that you get to learn new and exciting ways you were wrong. Databases are smarter than I thought!

You've heard that array or list columns in a database are bad. But why? Yesterday it clicked for me

Here it is: 20+ years of programming experience distilled into 378 words. From the book I'm writing.

5 common themes

Been thinking about what needs to be in place for engineers to ship with confidence

Never underestimate the power of good marketing for bad products. NoSQL was fun but SQL is here to stay.

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".

Solve the problem at hand, not the one you imagine might come next. A simple fix now often beats a complex one later.

Shared state in programming isn't the enemy, it's unclear dependencies that tangle your code. Keep it clean with explicit state dependencies and strict access guidelines

Detangling a Big Ball of Mud is hard. You have to find domain boundaries where none exist. Looks like AI can help 🤩

Why are utility files bad? How do you recognize architectural complexity? What the hell is a transitive dependency?

Clean code matters, but it's the architectural complexity that truly impacts your productivity and bug count. Focus on simplifying the system, not just the code.

Unravel the hidden costs of architectural complexity in software engineering and learn practical strategies to tackle it. Boost productivity, reduce defects, and improve staff retention with insights from an MIT PhD thesis.

Complicated code slows down junior devs, while complex systems impact senior devs more. Focus on managing system complexity & dependencies, not just simplifying code.

Unlock the secrets to combating architectural complexity in software development and learn to identify and fix the wrong abstraction. Boost productivity, reduce bugs, and retain more staff.

a little case study from an upcoming book I'm writing with Manning about software rewrites

Efficient problem-solving in engineering with a shift in perspective – focusing on user outcomes can lead to innovative solutions and change your approach to system design.

A simple change in perspective can help you overcome complex technical challenges and save time on future projects.

Microservices are a pain in the ass. They turn every system into a byzantine mess of complexity. But this week ... they saved my butt.

Write functions, mostly magic.