> now that we have the compute and proper AI, not just IKBS, we can focus on generating a specification and not the code. A specification that can persist acros

> now that we have the compute and proper AI, not just IKBS, we can focus on generating a specification and not the code. A specification that can persist across the entire SDLC. All a bit like all the other branches of engineering that have drawings, specifications and circuit diagrams and things. I'm not clear what this is supposed to achieve; if engineers can use AI to generate good specs, what's the issue with using llm in tdd/codegen cycle. currently, for complex projects with big teams the strategy seems to let llm loose and shoot for impossible deadlines which will likely backfire as llm could generate good code for a small subsystem, it fails frequently in brownfield, large projects resulting in engineering rework; by considering human effort to code in the release schedule, and then using llm to generate/refactor/tdd a good quality software could be built, without frustrating engineers having to deal with ai slop.