#ai

36 articles

Where Does The Experience Come From?

Proton’s CTO wrote a memo that nearly eulogized writing code by hand. Lars Faye points out that expertise comes from experience, and the memo doesn’t say where the next generation gets any. Here’s what used to teach it, and three ways to keep teaching it.

Learn to Imagine

Compute power can reproduce almost anything; it can't imagine anything. "Learn to code" pointed people at what AI is able to automate, and we should have been asking for imagination, not lines of code.

Nate Meyvis: Where is all the new, good software?

Nate Meyvis takes up a question AI skeptics keep raising: if AI-assisted coding is so powerful, where is the wave of new, good software? Several of his answers hold up well, particularly that approval chains don’t speed up and that much new software is private. What he doesn’t address is the question itself.

Four Horsemen, or Four Decisions?

Alex Martsinovich argues that agentic coding causes four unavoidable harms - slop, alienation, deskilling, and team breakdown β€” but these aren't technological inevitabilities, they're the results of specific choices about how to use AI coding tools.

Am I better because of AI?

A recent discussion on how AI was used effectively made me wonder what "effective" or "better" meant, because there's no way to test the alternative any more to compare. I still don't know how to characterize my own results, but I think it makes me better because it gives me a chance to work out who I am and what I mean to say, but not really how to say it.

User Submission: AI is a Bad Tool

Reader Hideki Idoru argues that AI is a decent information distiller and a bad tool for nearly everything else in software, because no one can cheaply verify that generated code is correct. The deeper claim is that most programming was already trivial, unabstracted busywork, and AI has only torn the mask off. It's worth reading and thinking about.

Ray Myers on Bun's Rewrite: Heat, but More Light

Ray Myers wrote up the Bun rewrite and the fight around it. It's emotional in places, but there's real signal in it about how agentic work is sold versus how it's done, and one review technique worth stealing.

What's Old is Old Again

A Reddit user on r/SaaS is looking forward to the consulting rates he'll command once the wave of projects trying to dig out from under AI slop hits. He's not wrong, but he's dated the pattern to 2010 offshoring when it's older than that, and the lesson never sticks: coding was never typing.

Bun Has Been Converted to Rust. Now What?

Bun was ported from Zig to Rust by an LLM and passed nearly all its tests - while shipping more than ten thousand unsafe blocks. Memory safety is the main reason you'd pick Rust. So what did the rewrite actually accomplish?

The Tacit Dimension

Christian Ekrem's 'The Tacit Dimension' carries Polanyi's 'we can know more than we can tell' into software engineering. He's right that experience works that way. Knowledge doesn't, and the essay never separates the two.

Being Wrong in the Same Direction

This is a working example of using red/green testing to fix a bug - one that starts in the issue description and lives in the code. You can fix the issue, but the bug remains because it's part of an unexamined specification. Testing - and caring - are the fix.