Syndicated StrictMark pages
Some say intelligence is a commodity now. We have intelligence on tap. What is the bottleneck then? Tokens? Lately, my work has been token-constrained more often. Given some context and hints, LLMs can endlessly reproduce known engineering practices and tricks. Then we get some legit-looking codebase that works most of the time. Still, to get beyond that prototype-quality code (slop), we likely…
Beagle is a git-compatible SCM for modern workflows. Fundamentally, it is the same commit-tree-blob model, but the higher order constructs are tuned and rebalanced to make it a useful tool in coordinating a swarm of LLMs and steering their activity towards an objective.
A. Karpathy once said that OpenAI researchers are effectively "automating themselves away" by improving their AI. Right now I develop Beagle SCM with Anthropic's Fable and it is of course a brilliant model able to spot nits in a mountain of code, file tickets, make fixes. Still, yesterday it managed to commit the build/ dir into a project, twice. It is brilliant, but clumsy.
I have worked with revision control and on revision control systems for quite some time now and I had every opportunity to develop strong opinions. Many of those opinions have changed as parallel LLM development became the norm. Tomorrow, the process will likely evolve even further. So, how do I see modern revision control? Can I really have any stable opinion here?