- cross-posted to:
- lobsters@lemmy.bestiver.se
I don’t get it, it’s just a markdown file, which is how llm specs already get written. I’m supposed to trust that the llm will “compile” it correctly every time without touching the code output? What happens when the code gets huge and complex, a “recompile” entails waiting for ages to get something similar to what others compiled? What am I missing?
It looks like something you could run
makeagainst, building and testing one module at a time based on per-module specs.Cool, I guess. Except for the environment whenever someone runs make, as that’ll get slightly warmer… which might be nice in winter, if localized to my dungeon home office.
edit: An interesting aspect seems to be the change cycle… it must detect when a spec change has occured (git diff?), and generates targeted changes so the code matches the spec. No spec change, no LLM calls, no code change. Problem in the generated code? Fix the spec instead…

