4 ms·
Probably looks like this: - teams blitz through Jira tickets - developers figure out they can't keep up with reviewing the code - too many new features pushe
by varispeed 4mo ago
Probably looks like this:
- teams blitz through Jira tickets
- developers figure out they can't keep up with reviewing the code
- too many new features pushed at once, rushed work to develop training materials
- features don't work as good, many edge cases come out in support tickets
- tickers return to Jira board
- teams spend time triaging and fixing with less AI
- some features turned out to be mistake, but now have to stay
- once mess is cleared, return to "normal" pace, no AI agents, Cursor allowed with budget cap.