dan @danabra.mov · 31/12/2025not sure this makes sense but it tickled my brain, yall should read itChad Fowler@chadfowler.comaicoding.leaflet.pubImmutable Infrastructure, Immutable CodeWhy "Never Upgrade in Place" Now Applies to Software 14596
a bezoar @a-bezoar.bsky.social · 31/12/2025If you want your program to fully meet its specification you have to precisely write the spec. You could write it in LEAN which proves spec compliance but doing that is highly non trivial. 000
CodeMonument @codemonument.com · 31/12/2025I understand your interest around this. Tickles my brain too. One thing I wonder: he wants specification over coding and generate the runtime code in CI or something. Then evaluate that code against the spec to see if it is doing the stuff it is supposed to. 100
Nick Williams @wicky.nillia.ms · 31/12/2025Any sufficiently precise specification is effectively an ad-hoc, informally specified, bug-ridden, slow implementation of half of a programming language 080
Sam Rose @samwho.dev · 31/12/2025I interviewed at a company that are sort of doing this to great effect. 020
Arnaud Barré @arnaud-barre.bsky.social · 31/12/2025It remind me of this. AI creates a new high level coding language which is english. But all the mutations problem will exist in the spec/code written in english. You will have merge conflicts, need to factorize specs parts, exception in the middle a shared part, optimization that are not needed, ... 1141
casperstr.bsky.social @casperstr.bsky.social · 31/12/2025Isn’t declarative code meant to be a structured way to express a specification? 000
rich harris @rich-harris.dev · 31/12/2025Fascinating but deeply wrong IMHO. If you want software to behave deterministically, which I assume we do, then there can be no _gaps_ between the specification and the implementation. Eventually they will sort of... converge? 1180
Steven Cowles @brit-tiggs.bsky.social · 31/12/2025Can't see how you avoid the "two devs touching the same file requires a merge somewhere" issue. That said - I'm also currently shipping code in a trinity - module, unit test and module spec. LLM's can recreate the original module from the other two files - and also quickly understand intent. 000
Georges Boris @georgesboris.com · 31/12/2025when I take "specification" as docs and tests, I have the feeling AI could end up cheating a lot to pass specs with brute force. Maybe adding property based tests + strongly typed APIs (w. proper invariants) could help? idk if you have all this for everything, the implementation is a detail. 000
Julian @juliangaramendy.dev · 31/12/2025what do they mean by "In-place modification" ("In-place modification has a hidden cost profile. Incremental edits entangle intent with the sequence of changes that produced them.") IMHO, the smaller the module, the more similar a modification will be to a full module rewrite. Right? 000
Adi Ginting @adipginting.bsky.social · 01/01/2026Hey, Dan. Sorry, I just opened bsky. Did you get a job in Japan finally? 100
fabienbeaulieu.bsky.social @fabienbeaulieu.bsky.social · 31/12/2025Definitely worth reading, resonate a lot with my own perspective on this whole AI-engineering-era we’re all in… Code has been meant to express our intention to other developers and to let computers figuring out what to do. Well, it’s no longer true. Prompts are now the new “programming language”. 100
@chadfowler.com
@chadfowler.com@chadfowler.com@chadfowler.com
