Respite from the AI mania

There’s so much fear going around about how AI will take over the world and subjugate humanity with its impending superhuman powers.

Two essays that I read last week cut through the drivel with thoughtful analysis and reasoning, pushing back on the hyperbole peddled by those whose valuations depend on keeping everyone on edge.

Pause your notifications for half an hour, settle in with warm beverage and have a read. It’ll be worth it.

Sent from my Claude

Someone on HN pointed out how clever it is, as an advertising strategy, for Claude Code to claim co-authorship over commits that it generates, given the exposure it would garner on GitHub and the like.

It reminded me of the Sent from my iPhone sign-off that Apple’s mobile Mail app would eagerly tack on to emails that you send.

Back when smartphones were first emerging, emailing from one meant that you were on the bleeding edge. But with a screen and keyboard no larger than a humble postcard, the writing rarely surpassed the courtesy or the polish found on one.

The solution we collectively settled on was to apologise for these shortcomings with signatures ranging from please excuse any typos and the brevity of this message to iPhone. iTypos. iApologize. Apple’s was an adaptation of Sent from my Blackberry. Characteristically restrained and implicit, it rode the iPhone’s dominance to cement itself as the cultural shorthand that we know and love.

While Co-authored-by: Claude Sonnet 5 almost certainly takes a page out of Apple’s branding playbook, we’re still discovering the breadth of concessions that it implicitly demands of its human collaborators.

Don’t credit the LLM

Lately, an odd habit seems to have caught on among my peers when they’ve done something with an LLM.

When asked “how many support requests have we received about the new Feature X?”, they answer “according to [LLM tool], we’ve received 17 requests since it was released.” When posting a pitch document or a pull request, they volunteer “I asked [LLM tool] to write this for me” or “[LLM tool] wrote the unit tests”.

Odd. Like a writer disclosing the spellchecker they used alongside every piece, or a pilot announcing their version of avionics software over the PA while taxiing to the runway.

Why did I need to know that?

At first, I put it down to a bit of novelty and excitement. But as this wore on, I started to wonder why someone might feel the need to declare their use of an LLM.

Perhaps:

  1. You believe in ascribing credit where credit is due. Using an LLM feels like cheating so disclosing it makes you feel less like an imposter for having produced something amazing.
  2. The LLM’s performance exceeded your wildest expectations, ergo the work is impressive by association. Never mind that it is only 80 percent complete and no one knows which 20 percent is missing.
  3. You outsourced the work to an LLM and didn’t bother to review it before hitting send. There may be mistakes but spotting them is left as an exercise for your recipients.
  4. LLM use has been mandated by Up Above. Claiming you’ve used one (even if you haven’t) buys you a higher tolerance for sloppiness since you are presumably facilitating your own eventual redundancy.

For 2 to 4, all I can say is I’m sorry and I hope things work out for you.

But for the first reason, I’d challenge the notion of sharing credit with a tool, let alone feeling like a cheat for using one. Credit and accountability are two sides of the same coin. A tool can only take as much credit as it can be held accountable for, so crediting it inadvertently dilutes your own accountability for the work.

If you’ve created something profound or remarkable, take complete credit for it. If it misses the mark or turns out to be utter slop, also take full responsibility and improve from there. This is how every meaningful or valuable thing was ever created long before the advent of “AI can make mistakes” and will remain so long after, with or without LLMs.

HN discussion

Toast button approximation

Instead of writing tonight, I added ❤️ buttons to the end of my posts that mimic the neat little toast buttons that Bear blogs have. It’s Solid Post Likes but with six inches of CSS overrides because I’m dangerous like that. I also turned off comments because it’s 2026 and email (from 1971) is cool again.

If you’re just passing through, test the button out for me so I know it works?

Re: What do you think?

Robert blogged about the power of asking “what do you think?”

It brought up memories from my formative years when grown-ups had also given me the gift of this question. I don’t know how children elsewhere had it, but these were rare departures from the “grown-ups know best” norm that prevailed in my corner of the world at the time.

Mind you, these weren’t the “let’s see what the silly kids think” routines that inevitably come up at family gatherings. We would have been discussing a topic in earnest, or solving a problem, or mulling over a decision. The stakes may not have been high, but they were real, and that made all the difference.

“What do you think?” invited me to participate rather than to merely observe. It showed me that I could contribute meaningfully. Instead of striving to be heard, the challenge was to form an opinion that was worthy of the hearing. Imagine what a rush it would have been, as a child, for your view to be acknowledged; more so, for it to be tested and sharpened on its merits; to say nothing of seeing a sliver of it in the final outcome, however small.

Every one of these interactions built my confidence and shaped the life I have today. I’m grateful to the people who gave me these gifts, and take this as a reminder to pass it on to those around me.