Agentic coding is just a convention you maintain by reading every diff, the kind that decays when you're tired. So vibe coding is the failure mode you have to plan for, not a separate practice.
A checkpoint on the Eignex rewrite, three months in: the libraries have converged on one config shape, and combo is the next domino.
How to give library users typed schemas humans, refactor tools, and AI assistants can all reason about. Three Kotlin designs, one I shipped as skema.
I keep seeing the 'AI is making us dumber' argument. It replays past tool panics, but the engagement loop AI is landing inside is the new variable.
I've hit the same "pack state into a tiny string" problem four times now. Here's the library that came out of it, and a detour on why kotlinx.serialization is so cool to build on.
Progress update on kencode and kumulant, plus a first pass at what I'm actually trying to build with Eignex.
A quick who-am-I and what-is-this. PhD in continuous optimization, left academia, now building Eignex in the open.