Brian LeRoux

Building a Home in the Age of Exponential Change Discover the critical difference between building a house and a home in tech. Learn to focus on outcomes, not just tools.

fullhoffman.com/2026/03/10/t...

The hammer problem..

"The people who built close to the runtime — who used the primitives, kept dependencies thin, and focused on their application — shipped faster and maintained less. The people who built elaborate tooling spent their time maintaining elaborate tooling."

Oh look, we've rediscovered why regions and availability zones exist

ol willy bob we called him

I see no reason why large orgs would no longer exist. Even if we achieve levels of super intelligence to rival the very best sci-fi/fantasy the Culture there are large collectives organized around particular interests and pursuits. Do intelligent entities (humans or otherwise) have interests?

we can replace the glaciers with comet ice once we industrialize the Lagrange points (this is a bull signal for solana btw)

keep up? I've already mapped you newbs. I'm engaged with you through my metaverse avatar running on my custom rust fork as we speak. (Also this is not meat space Brian but a personal LLM trained on all his data)

totally brand new. an uncarved block!

or I might get left behind? lol. LMAO even

hahaha yes what could go wrong

idk how tf we get out... dystopic sci fi where corporations are effectively the government increasingly seem likely alas

speaks to me very much. we have such an abundance of infrastructure riches locked behind private interests in a constant spiral of enshittification.

yeah exactly, we tend to overestimate the short term and underestimate the long term which is endearing testimony to our optimism as a species

it's cool we can prompt a thing into existence today. but just like we could copy paste a thing before that doesn't necessarily account for running and maintaining said thing over the fullness of time.

The JSDoc compiler is insanely fast. It takes 0.00000s to compile my JavaScript app.

the main reason LLMs won't replace a lot of software-as-a-services is governance and compliance. what works for a small team won't work at scale.

project hail mary next week! fist my bump!

hard to know without being inside but pretty clear to me AI wasn't a catalyst for efficiency so much as a nicer narrative

I mean..

love textmate and homesite and others too

felco hand pruners are to gardening as vim is to editing text

AI Didn't Break the Senior Engineer Pipeline. It Showed That One Never Existed. Most organizations never had a model for developing engineers. They had an environment that produced growth by accident. AI just made the luck run out.

If coding is your favorite part of software engineering, keep coding. AI doesn't stop you. But if coding was the only part you were good at, that's a different conversation. The job was always bigger than the code. #bransoncognac blog.bryanl.dev/posts/ai-sen...

So anyhow, why use an abstraction? Generating code isn't really the hard part about developing software. Knowing what code to generate and making it easy to modify or throw away is the tricky part. Which means we still need to quickly understand, debug, iterate, verify & deploy code.

That being said, verbose things, can be helpful to have a higher level dialect that hides complexity. And browser and aws certainly both have a bit of that going on in particular cases (web components api and Cloudformation for example).

Think as always 'it depends'. Stable software (browsers, AWS apis, etc) don't really need abstraction. Unstable things probably benefit from shared conventions and api surfaces. Funny how ppl tend to put the heavy abstractions on top of stable stuff with breaky semantics.

reason #37362562 why I need a 3d printer

Cool internet rabbit holes still exist 🖖🏻

www.wixiban.com/toys/galoob-...

“I must create a system, or be enslaved by another man's. I will not reason and compare: my business is to create.”
- William Blake

"What I cannot create, I do not understand"
- Richard Feynman