|
|
|
|
|
by Stehfyn
45 days ago
|
|
I use a multimodal approach to defining my spec: different layers of criteria for how the software looks, behaves, what it produces, and under what constraints. For the literal code: • A healthy cocktail of /WX + /Wall, plus clang-tidy with very few suppressions • An extremely opinionated mix of clang-format and LLM-generated bespoke formatting that AST-based tools cant express • Hungarian notation; all stack locals pre-hoisted, declared in order of appearance, and separated from subsequent assignments • Enforced dataflow: all memory accesses are bounded independent of branch resolution, with only data-oblivious indexing • Functions have a single point of return In a C89 workflow, this pushes agents to produce code where wrong business/domain decisions are unmistakably obvious, while eliminating the vast majority of bug classes before I ever read it. So yeah, Ill reassert 80%, if not more. |
|