You're the Broker, Not the Builder
AI coding assistants are good enough to do the building. Your job is to be the broker between the problem and a scalable, resilient solution. Here's what that looks like in practice.
We can't find the internet
Attempting to reconnect
Something went wrong!
Hang in there while we get back on track
Thoughts on software, consulting, and building things that matter
AI coding assistants are good enough to do the building. Your job is to be the broker between the problem and a scalable, resilient solution. Here's what that looks like in practice.
Software used to be something only tech companies could justify building. That's not true anymore. If you run a business and haven't talked through which problems are solvable with software, now is the time.
How building Winnow Labs' blog and research atlas as a passion project turned into a real partnership, and why the best thing you can do between jobs is build something.
A former Amazon robotics engineer breaks down why the Rivr acquisition faces the same cost and scale challenges that every robotics effort at Amazon eventually hits.
Most Phoenix apps don't need GraphQL. Here's how to know when PostgreSQL and Ecto are enough, and when Absinthe actually earns its complexity.
Erlang was designed for isolated processes with their own state, communicating over unreliable networks. That's exactly what agentic AI looks like.
Engineering is a partnership, not a transaction. The companies that move fastest are the ones whose engineers actually understand the business.
From MVP to millions of users, Elixir and Phoenix handle it all. In the age of AI, that flexibility matters more than ever.
For a year I said AI tools only added 20% efficiency. I was measuring the wrong thing.
After 8 years building software at companies like Amazon and GridPoint, I'm starting something new.