I like what unison are up to - the code has one canonical reputation that's stored in a database, not a file, thus the formatting of it becomes a display concern only

...if I accentuate my prompts towards what I think makes code better than that, and double down on engineering practice around making changes when I'm using an agent (even smaller changes, watch the test fail first, etc.) I can go marginally faster

My experience has been that AI writes median quality internet code unless explicitly instructed otherwise...

Oh come on, a Premier Inn, surely, the breakfast is superior

Other: it makes _more_ software.

Or even Fortingall, thanks autocorrect

Fortingale?

I reckon all this apple stuff is really only fit to go in the canal nowadays

Seek out fast feedback; act on it

Watched this (Across the Spider-Verse, for complete context) for maybe the tenth time over Christmas, and it remains an absolute masterpiece.

This is why I always use my squirrel rather than someone else's

I mean this one is soluble with a well factored dependency tree and a good build tool, no? Or are you wanting something that lets you edit a root node in an ABI incompatible way and still have a fast build?

I suspect getting the message out with modern build systems is probably possible, and we'll then discover that the test system hasn't got a bloody clue what to do with it...

I feel like the build tool here rightfully says "hey, I built it, over to you now test system" and there's a missing message of "oh btw it was an incremental build and the artifacts that changed were [...]" and then the test system can traverse a different graph to do its work