We’re deep into 3D printing over here after getting a Bambu Lab P2S for Christmas.

Mostly so far it’s been Everett and I finding models on the web and printing in different colors. Learning the basics of the slicer software and parameters, tweaking print settings. I’ve only just started dabbling back in CAD (and the skills are rusted all the way through). Fusion 360 is powerful, though. Planning to get Everett in there and learning some basics like I did when I was young — but back then it was like AutoCAD 5.0 or something.

One thing I wanted to do with this was create organization containers for drawers around the house. I discovered the Gridfinity system, which is an open source spec for printing modular trays and bins.

Then I found this Gridfinity Generator tool by Marcus Svensson. A slick web-based CAD for quickly creating custom grids and bins.

Software builders already spent quite a bit of time on the terminal. AI coding (especially Claude Code) has made the terminal not only an I/O mechanism for working with a system, but also an IDE and complete interface for building software.

Brian Lovin posted on X this site he built to explain the underlying tech of terminals.

We’re only seeing the very beginnings of the cool stuff that’s now possible — or rather worthwhile — to build when it only costs you a few prompts.

I ran across this documentary about the making of a Steinway grand piano.

The process of constructing one of these takes a year or more. It’s a great example of handmade craftsmanship in a world where we’ve mechanized every step, and oriented so much manufacturing to mass production. A Steinway is still made by a hundred masters, each honing a skillset for decades.

In a world where most everything is mass-produced, it’s no surprise that hand craftsmanship becomes a luxury good. As costs drop on manufactured versions, demand for the art form of hand tooling falls, skilled artisans begin to disappear.

I hope in more domains we’ll have a renaissance of handcrafted things. Not just on the demand side — with more people interested in buying them — but also in the supply: more kids interested in becoming furniture makers instead of financiers, artisans instead of attorneys.

One note I love on the Steinway process (and would be the same for many other crafts) is how many of its makers are working class locals, people with the nugget of a talent or a knack for craft that found a calling, showing up to the factory every day and filing that skill to a razor sharp point.

One day I’ll find a spare $100K for my own 9 foot ebony grand.

As I was reading this article from Ted Gioia the other day, I noticed in this image he used a logo I recognized:

This is Hollywood Boulevard from the 1930s. Notice the Kress Building on the far side of the street.

It reminded me of our own Kress Building in downtown St. Petersburg, FL:

And the one in Tampa:

SH Kress & Co was a five-and-dime store chain that’s been defunct for over 20 years. Though you’d think there’s nothing noteworthy about a chain of the dollar stores of their day, they’ve left a legacy of interesting preservation-worthy architecture in cities across the United States.

Many of these still stand as beautiful specimens of historical architectural styles. The St. Pete one in Beaux-Arts style, Tampa in a Renaissance Revival. Or this gorgeous Art Deco example from Fort Worth, Texas:

In our modern culture of thrifty, modern, utilitarian design, there’s no way a corporation would invest in this kind of general public good.

In their day, these buildings functioned as stores: places to sell cheap things people needed. But they doubled as beautiful additions to the cityscape.

Are there any going concerns today about which we could say the same? What generic commercial building erected in the 2000s or beyond will be worthy of preservation and reuse in the 2100s?

Jonah Goldberg with one of his classic broadsides against our broken primary system:

People hate on “smoke-filled rooms” because they think such venues give the rich and powerful undue influence over the nominating process. That is surely the case, though it did produce some pretty good presidents. It also produced some bad ones, though the blame for their failures can rarely be put at the feet of Fat Cats and Robber Barons. But the brief against smoke-filled rooms leaves out the fact that primaries are steamy garbage dumps for the same forces. The “money primary” and the “media primary” aren’t pristine processes either. Indeed, the primaries provide a form of “democracy washing” the influence of big money and rampant demagoguery—by the candidates and their donors and media boosters. What the primary system does is cut out the gatekeepers, the institutionalists, the small-r republican figures who care about the integrity of the party, the salience of various unsexy issues, and this thing called “governance.” When the party is in control, it still cares a lot about winning, but it also cares about the long-term viability of the party, its issues, and down-ballot candidates. Congressmen who want to get reelected might want a more boring presidential candidate that will put the party above his own ego and self-interest.

When some, like Jonah, want a return to smoke-filled rooms, the democracy-above-all crowd screams that with elites and gatekeepers between The People and their choices, it’s some kind of tyranny. What they fail to appreciate is how patently undemocratic the existing primary system is.

“Democracy washing” is such a great term to describe the current system. Pure, popular-democracy primaries give us a simulacrum of choice, without the underlying reality. If we don’t slog through the messy horse-trading and argumentation of the old 1880 style Jonah writes about during Garfield’s time, we trade better results for the ability to pretend The People are in the driver’s seat.

The patient slog through debate and argument is the process of better results simmering in the oven. Sure, we can bake the ribs in the toaster, but let me know how those turn out compared to giving them time to braise.

Like many things in our immature culture, we get so preoccupied with processes looking the way we want them to that we never do the mental trade-offs to determine if we’re getting better or worse results. Or if the thing we think is happening is even happening in the first place.

(The link to the article might be paywalled. But take that as tip to subscribe to The Dispatch.)

OpenAI launched a major update to Sora yesterday.

There’s something about AI video that just doesn’t get me excited.

Sound on. pic.twitter.com/QHDxq6ubGt

— OpenAI (@OpenAI) September 30, 2025

Sure, it’s impressive: we’ve created black magic-levels of technology that can summon real-looking images from the ether. We can type a request and generate whatever movie we want.

But one of the things that makes film exciting is not only its quality or entertainment value, but the knowledge that a human produced it. There’s an aesthetic to the depth of human involvement in the process that Sora can’t substitute for. The more we close the uncanny valley visually, the more repulsed we are when we do find out it was “just AI.” We assumed human achievement, but we’ve been lied to.

I know, I know. We’ve had CGI in film for years. What’s the difference between Sora or Veo and the machine-assisted CGI from Transformers or something? This actually admits to the problem. People have disliked the overuse of CGI for years. The practical filmmaking of Christopher Nolan or George Miller or Ridley Scott stands out in a field full of CGI slop. CGI was once simply the seasoning on the meal, now it’s become the meal itself.

There Will Be Blood is impressive as a human feat of planning and executing on a vision, creating a collection of ideas and making them real – from script writing to performance to location selection to cinematography. The oil derrick explosion scene is impressive not just for what it is to look at, but because wow, humans made that happen.

Or think about music. Bach’s compositions aren’t merely impressive for their technical complexity or because they sound beautiful; what sits with you after hearing the Well-Tempered Clavier is that a human came up with that out of thin eighteenth-century air. The idea itself that a regular person could create something so original, textured, and interesting is an essential part if its value.

AI-generated media is stripped of this humanity. If we know a server farm generated those pixels or sound waves, we find ourselves disconnected from the impressiveness of human achievement. We have no way to relate to it. I know that playing a guitar is hard, but typing a prompt to get the computer to do it? I have no idea. Definitely sounds a lot less hard to me.

The AI bulls will claim the creativity is in the prompting, that talent will emerge able to steer these models toward genius originality. There’s something to this, for sure. All creators and craftsmen leverage the tools at their disposal. Modern woodworkers have power tools to assist in furniture making. Musicians have precision instruments and recording gear that allow them to realize a closer representation of their vision. Every advance inserts a new layer of abstraction between human imagination and a realized idea.

But as we move up the abstraction ladder of creativity, I’m less impressed by the human aspects of the achievement. Our hand is further removed from the output. Am I impressed by a song composition piped into a computer for a computer to play back? Sure, maybe. But I’m all the more impressed when the composer sits at the piano and plays it with their own hands.

I can simultaneously believe a CNC-sculpted statue is impressive to look at, while I consider the David to be both an impressive sight and impressive employment of human craftsmanship. Both require skills, but one requires more skills.

There will always be a market for authenticity. We have an appreciation for the humanity conveyed by a Van Gogh that simply isn’t there and can’t be there in a Midjourney image. No matter how fancy the prompt engineering.

Iain McGilchrist:

Who does not now find themselves constantly busy? The young, the middle-aged and the old feel it alike. We are all time-poor; and time is not worth nothing. Time is life. Everything now is freighted with so much bureaucracy; and the bureaucracy is in an unholy alliance with AI. Together they massively, colossally, waste our time.

As he reminds us in this piece, we’ve got to stay vigilant here. Bureaucracy + AI is a dangerous combination for all our sanity (and likely worse).

We’ve already seen the enshittification of everything powered by financialization and dehumanization and “optimizations” for efficiencies, or for economies of scale. AI is superfuel for this nonsense.

I’m bullish on free markets and humans selecting against this world, as long as we have options. Let’s build and maintain those options.

I’ve been diving back into Alexander’s A Pattern Language the past few days.

As I was making notes in Obsidian, it occurred to me that APL, with its interlinked system of patterns, could be an interesting medium for building a relationship graph around. Patterns connected to patterns.

Then looking around I ran across essentially this exact thing: a web-published version of an Obsidian graph of patterns.

Browsing to any pattern shows you the subgraph of adjacent patterns, with backlinks to each one. A neat way to traverse the relationships of Alexander’s system.

My latest post on the importance of remembering what makes the American flavor of independence unique:

Something unique about the American Founders’ flavor of revolution was that it was the first (only?) of the revolutionary movements of the past 300 years that took human nature into account. Many of the revolutions in the time since — the French Revolution, those of the 1840s, the Russian Revolution — had toppling despotic authoritarian regimes in mind.

In that respect the American Revolution shared a causal relationship in what brought it about.

Where the American version differed, though, was not in its origins, but its ends. It sought to replace an oppressive monarchy with something rooted in bottom-up individualism. A republican (small r) system of government that accepted human fallibility: one designed around the unchangeable essence of the “crooked timber of humanity.”

In the latest issue of Building Blocks, I dove into Shape Up and its idea of setting the appetite for a project.

Fundamentally, appetite inverts the question we begin with when planning a project.

Instead of starting with “Here’s a spec. How long will it take?”, we start with a time window we’re comfortable spending on the problem and ask “What can we get done inside this box?”

Rather than define a richly-detailed design of what we want, appetite requires us to start with a problem definition, and refine that first. If we narrow the problem down, we also narrow the solution space. Solutions are allowed to be smaller and more focused.

The appetite starts with time boundary and works backward to a design that fits inside.

Appetites define sound and acceptable constraints up front. And constraints are wonderful tools for generating creativity.

Julian Lehr wrote an interesting post recently on the problems with conversational interfaces, with the fitting title “The case against conversational interfaces”. Here’s Julian:

We keep telling ourselves that previous voice interfaces like Alexa or Siri didn’t succeed because the underlying AI wasn’t smart enough, but that’s only half of the story. The core problem was never the quality of the output function, but the inconvenience of the input function: A natural language prompt like “Hey Google, what’s the weather in San Francisco today?” just takes 10x longer than simply tapping the weather app on your homescreen.

Voice works so well in human-to-human communication because it’s enormously flexible on both ends — for speaker and listener. Through speech we can both communicate and understand just about any idea using the same framework of 26 letters and a couple thousand words.

The speaker can walk up to anyone fluent in the language and fairly effectively communicate just about anything — commands, requests, thoughts, ideas, emotions — and have the listener comprehend.

But conversation is slow. The “bitrate” for conversational speech is peanuts compared to what you can do with hand signals or ideograms or jpegs. A set of hand signals could convey a message much faster, but at the expense of loss of range, and easier misinterpretation. Spoken language trades bandwidth and information density for flexibility, nuance, and error tolerance. All major utilities when talking with a stranger, but not with our computers.

We keep chasing conversational interfaces in computing because of ease-of-access and the promise of flexibility. But in commanding the computer, the loss of compression, low bandwidth, and ambiguity are annoyances rather than assets. When we have a conversation with a clerk at the store, these are features. When it’s with our computers, they feel like bugs.

Julian goes on to talk about how we might think more creatively with fitting LLMs into this picture:

We spend too much time thinking about AI as a substitute (for interfaces, workflows, and jobs) and too little time about AI as a complement. Progress rarely follows a simple path of replacement. It unlocks new, previously unimaginable things rather than merely displacing what came before.

As AI seeps in everywhere, we need to think positive-sum in how it helps the human-computer interaction problem. It holds the potential to generate background threads of activity as we’re using our slow-but-flexible inputs like speech or typing: retrieving information and summarizing and performing interstitial actions while we’re in the middle of other tasks.

Will Manidis:

The demonic recognizes in our shortcuts the perfect opportunity: tempt humans away from the difficult labor of making, growing, and building with our own hands and minds. Instead, offer an endless stream of effortless consumption—images without artists, music without musicians, stories without storytellers. The devil’s oldest strategy is, of course, promising godlike creation without godlike effort.

Every feed, every product shelf, every book rack, even restaurant and menu, now overflowing with slop. If we’re being honest, the slop movement — mass produced, carbon-copied, no connection to humans — predates AI. But AI turbocharges the ability to churn this stuff out.

When we think about brain-computer interfaces, why do we always jump to the chip-in-the-head? Or the wire dongle with an antenna behind our ear? The Larry Niven “wirehead”?

Maybe it’s just a bandwidth thing.

Aren’t our phones a low-bandwidth version of a BCI? Certainly phones and social media and other modern tech modify our brains in similar ways.

Or perhaps it’s both the high-bandwidth abilities enabling so much more combined with the idea that they’re uncontrollable in some way. A piece of hardware pinging electrical signals inside our heads that we can’t be consciously aware of. We don’t know what they’re doing, and “unplugging” doesn’t give the airgap of leaving your phone at home when going for a walk.

There’s probably also a visceral feeling it gives us of an inhuman piece of inorganic matter being embedded in our heads. And our heads are our “selves”. The brain barrier is a special one to us, even though it’s technically no different than another organ, in terms of its make-up.

I just watched this excellent interview with Michael Dean on the How I Write podcast.

Michael is an architect and writer, and his writing project is fascinating.

He’s built a framework for thinking about writing that adapts Christopher Alexander’s concept of pattern languages to writing.

If you’re unfamiliar, Alexander created a way of thinking about design and functionality that gave us a modular, nested framework for how to build spaces — from whole cities down to features within rooms. A “pattern” is a loose and modifiable guideline for how a component of a system should work. More defined than a rule-of-thumb, but less rigid than a rule. So patterns can be refined and adjusted to adapt to different settings.

Thinking about writing this way is interesting. Language has similarities to other complex systems: letters, words, sentences, phrases, paragraphs, stories, narratives. It’s made of modular components that nest together in a hierarchy, where ideas (“wholes”) emerge from the interactions between parts, even at different levels in the hierarchy.

Michael’s system gets more abstract than the simple physical form of the words and sentences, into things like voice and tone, cohesion, motifs, stakes, rhythm, and repetition.

Need to spend some more time with these ideas.

I recently wrote about the tendency of creators to keep messy versus clean workspaces.

While sometimes the mess is a certifiable inefficient disaster resulting from laziness, the “organized chaoos” messy space acts like a mental buffer.

Here’s computer scientist Jim Gray on the purpose of buffering in a programming context, from his book Transaction Processing:

The main idea behind buffering is to exploit locality. Everybody employs it without even thinking about it. A desk should serve as a buffer of the things one needs to perform the current tasks.

Keeping things “in the buffer” redounds to productivity (and ideally, creativity). If something is closer at hand, it lowers the transaction costs of retrieval.

Memorization works this way, too. People question the benefits of rote memorization in school, but this is a useful metaphor for understanding its value. Memorizing reusable data keeps it “in RAM” for faster retrieval.

Faster retrieval reduces friction, which means faster feedback loops, faster learning.

Saw this from John Carmack today on X:

Feedback beats planning.

My plea at Meta was “No grand plans, follow the gradient of user value”.

I love this. If you just keep persistently pushing up the gradient toward more value, it’s winning in the long term. Durable and sustainable success is that which happens gradually.

This reminds of a conversation I was just having earlier today about Fulcrum and our positive net retention. Our product fit was good enough that no one ever left. That didn’t mean infinite growth or hockey-stick revenue, but it created a durable foundation from which to grow gradually.

With the bottom-up adoption model, the continuous shipping of new features, and modest evolution of pricing and packaging with time, that combo enabled a gradual climb up the gradient.

You don’t always need that comprehensive 5-year strategy doc or holistic product redesign or earth-shaking press release. You just need that next nugget of feedback on the adjacent missing links in the value chain that you can iterate toward solving.

Keep climbing the gradient, and success will follow.

Here’s a useful way of thinking about the domains of our three branches of government, from Yuval Levin’s American Covenant:

It is only a slight exaggeration to say that the Congress is expected to frame for the future, the president is expected to act in the present, and the courts are expected to assess the past. These boundaries are not perfectly clean, of course.

How distinct this delineation of roles is between the branches of government is up for debate, but this is a useful way to think about the Framers’ intention in designing the balanced separation of powers.

• Legislators frame laws for the future
• The president acts on them today
• Judges compare what’s happening today and planned for tomorrow against precedents set in the past

We tend to run into trouble when any of the branches strays outside its primary domain.

When the executive is designing Big Plans for the future, or when the judiciary is issuing punishments in the present, or (in what I’d say is our worst problem today) the legislative isn’t doing anything, we get into fraught territory.

While each of these has its primary focus on a particular time horizon, they aren’t the sole arbiters of decision making with respect to their domain. Our complex array of checks allows each to assert influence over other areas. I just find this a useful compression of the general model of the system.