1. Integration tests are a pain to setup, not anymore!
Also, code reviews before PRs.
2. AI doing production triage work
3. AI code reviews before submittng work to my team to review.
4. The workers that haven't embraced AI assistance work at a slower pace, which bottlenecks teams when you rely on them. This is particularly noticeable when it comes to PRs and there are a (human usual) number of defects requiring more time to fix and/or refactor.
Using AI doesn't mean it has to take your job, it means like an intelligent IDE, it can correct your code and instead of templates (e.g. implement this interface and you get stubs) you have entire classes written.
1. Integration tests are a pain to setup, not anymore! Also, code reviews before PRs.
2. AI doing production triage work
3. AI code reviews before submittng work to my team to review.
4. The workers that haven't embraced AI assistance work at a slower pace, which bottlenecks teams when you rely on them. This is particularly noticeable when it comes to PRs and there are a (human usual) number of defects requiring more time to fix and/or refactor.
Using AI doesn't mean it has to take your job, it means like an intelligent IDE, it can correct your code and instead of templates (e.g. implement this interface and you get stubs) you have entire classes written.
Curious what type of production triage are you using AI for? Incidents or bugs or both?