134 karma · joined March 8, 2026
however, unit labor costs has also been increasing (although they remain variable): https://www.bls.gov/opub/ted/2026/productivity-up-0-3-percen...
https://www.choiceofgames.com/make-your-own-games/choicescri...
how do you figure?
It will certainly be a cutthroat landscape for engineers, but companies will be building _more_ capacity, not less. In other words, the demand won't disappear for skilled technical labor, it will just move higher up the value chain.
I've been finding enforcing integrations and behavior structurally (e.g., through codegen/schemagen, e2e tests, etc) more reliable than simply instructing the models to write tests. oftentimes these tests are pretty low quality anyway, and results in its own form of tech debt.
TLDR; it found test-writing volume only weakly correlates with success and that encoding test-writing principles did not move resolution rates but _did_ materially change cost. Encouraging tests cost +19.8% output tokens for 0% gain; discouraging them saved 33–49% input tokens for ≤2.6pp accuracy loss. Separately, imposing the TDD procedure specifically seems like it can backfire: it actually _increased_ regressions from 6.08% to 9.94%.
IMO, where tests clearly help is primarily as an "oracle" applied after generation. It gives the models a signal that enables them to verify and self-correct if necessary.
also, use-case for massively concurrent writes is pretty narrow, and SQLite is not optimizing for that anyway.
you seem like the inexperienced one to me..
It's an SDLC workflow harness for agents. Instead of using skills to encode my typical workflows (e.g., create PRD, then create plan using TDD, then dispatch subagents, etc) I've built a concurrent event-sourced process manager to handle it.
> If AI displaces human workers faster than the economy can reabsorb them
Big if.
I think it's clear a self-describing CLI is optimal for local-first tooling and portability. I personally view remote MCP servers as complementary in the space.