· Brittany Ellich · illustration  · 1 min read

Project success vs architecture diagram complexity

A line graph comparing the expectation vs reality of the likelihood of project success vs the architecture diagram complexity. Expectation is that lower complexity has lower success, higher complexity has higher success. Reality is the opposite.

Everyone knows writing a more complex architecture diagram is the key to success!

Share:
Back to Blog

Related Posts

View All Posts »
Why I'm betting on ATProto (and why you should, too)

Why I'm betting on ATProto (and why you should, too)

Social media was supposed to connect us, but most of it has turned into ads, division, and loneliness. I'm betting on ATProto as a way to fix that, and not just for developers. Whether you're a scientist, journalist, or just someone who wants the internet to feel human again, I think ATProto matters for you too.

Embrace the uncertainty

Embrace the uncertainty

Nobody knows what the future of software engineering looks like, and that's incredibly uncomfortable. But instead of waiting for someone to hand us the answer, I think the move is to embrace the uncertainty, because these moments of deep uncertainty have historically been moments of extraordinary opportunity.

Start where you are: A practical guide to building with AI

Start where you are: A practical guide to building with AI

The best practices for building with AI haven't been written yet, and that's actually exciting. This post breaks down a layered approach to AI-assisted development, from chat to coding agents to agent fleets, with practical tips for getting started no matter where you are.

Living in the inflection point

Living in the inflection point

I'm scared, I'm excited, and I'm exhausted by the pace of change. All of those things can be true at the same time. This blog post is a (hopefully) grounded take on living through AI's inflection point, why the backlash is valid, and why human connection matters more now than ever.