u/Alternative_Win_6638

Devs were saying like "Why should I bother about docs, I'll write code comments". Today, in the AI Assistants age classical SW engineering documentation is gold. AI strives for well structured requirements & design specs, plans and testing docs, he navigates them effectively and derives excelent context.

Once you get it you'll never write a single line of code again and your speed and quality will rock

3 Years ago - reading ticket, writing code manually, using debugger to track bugs, learning new language features.
Today - Feeding story to AI assistant, generating product requirements doc, generating implementaton plan doc, generating code, running tests, defining error description, generating corrective actions, managing context, learning new llm models features. sprint velocity and quality 5-10 times higher.

Follow up Clarification: Because some responders are skeptical, I'm not working for Anthropic, No tokenmaxing, no vibe coding. Following structured engineering procesess and getting QA approvals for my deliveries. No magics

We all know that AI code generation can be tricky and not expected. Developrs often say that it is not predictable as other tools, test runners, compilers etc... were results are always the same for the same input. So if the AI can give different answers for the same questions how can we know for sure it is right ?
My answer to that: It is completely OK to provide different responses for the same input. This is no different than Human devs, doesn't it ? The key is how we provide the AI a mean to 'close the loop', a test it can run to validate the correctnes of solution can help the AI assitant debug and find errors iteratively and ensure the final solution meets our requirements. I see it as a key concept when working with AI assistant especially for complex tasks. How about you ?

We tend to call a backend machine a 'Server' and this might be confusing when it comes to the client server model. Because a 'Server' isn't always necessarily a 'Server' in the client server model. In a transaction between two microservices, for example, the machine who send the request is the 'Client' and the one providing the response is the 'Server'. So the distinction between Client and Server is per transaction and not absolute. Did this confuse you as well ?

It used to be the standard method to build software before Agile took over. Do you think it still relevant today ?