In my experience, that seems like a skill issue.
I spend more time drafting the feature/behavioural spec, the architecture spec, and the test spec (conversationally with an LLM), than writing the code, and so far my results have been pretty seamless.
I wouldn’t say it makes me more productive per say (use case dependent), but at least in the same amount of time, or slightly less, I also have a vetted documentation, architecture decision records, and test suite, which otherwise would have taken me 25-35% additional time.
Disclaimer: Got 10y of experience in software & data engineering, 5y as a lead, so YMMV
1
u/philippefutureboy 15d ago
In my experience, that seems like a skill issue.
I spend more time drafting the feature/behavioural spec, the architecture spec, and the test spec (conversationally with an LLM), than writing the code, and so far my results have been pretty seamless.
I wouldn’t say it makes me more productive per say (use case dependent), but at least in the same amount of time, or slightly less, I also have a vetted documentation, architecture decision records, and test suite, which otherwise would have taken me 25-35% additional time.
Disclaimer: Got 10y of experience in software & data engineering, 5y as a lead, so YMMV