Version Change in Dev Processes
Ai is changing everything and that’s old news. The question for us before we start fresh round of hiring was — how do we want ai enabled development processes going forward and this would mean hiring what kind of engineers.
The very first attempt was creation of product roadmap given product vision, that lead to more granular — hey can you make the product vision into exact JIRA break up of tickets into Epic-Feature-Requirements hierarchy and then we tried generating product cases. It all was going fast so we said ok given this wireframe sketch and this context write me all the product cases. That went well so we said write us engineering test cases which are much more granular than product and cover validations and constraints.
From that point we arrived at that it’s the QA & Code review that needs to go Ai. Write an Ai agent to QA by only giving prompts that are converted into test cases. If a prompt leads to new cases they be stored in the E-F-R hierarchy and given a paper & pencile sketch & PRD ask cursor to give the first version code. Test the code against prompt tool to spot if a new case arrives and add code for that if it does , add the case to the case repository.
When the PR arrives with new code, the automation testing framework is becoming code review where hit the code against the test cases to spot if the code for any piece is missing. If not pass the PR for deployment.
We’re aiming to building ai agents and integrations with dev tools to work out this process flow. Will report how fast it goes.