(no title)
vaidhy | 9 months ago
I will take the last one first. When I was managing large teams, my assumption is that a developer spends about 25% of the time actually coding. Let us say, AI makes them 50% more productive. So, you got a real gain of 12.5%. It is nowhere as huge as you put on your chart.
AI coding seems really great for one-off prototypes or some small, well-defined pieces, but they are not ready for production code. Multiple research papers have found AI code to be less secure, more buggy etc and they hinder rather than help experienced developers. So, you are going to lose even more of the hypothetical 12.5% gain here.
Finally, your post seems to say that the developers are not prioritizing your work, not that they are not working. Even if they are more productive, there is still no guarantee your feature will get prioritized.
The solution to your stated problem seem to be inability to get your work prioritized and nothing to do with AI or developer productivity.
paolop|9 months ago
If what you are saying it's true, i.e. AI is borderline useless, it should not be used as a reason to justify layoffs, right?
Finally, I was lucky enough to get a lot of my work prioritized - that paragraph was just trying to be the usual funny interaction between PMs and devs. I guess it didn't work. The main point remains - products today are not that polished or complete, so clearly some code is not being written or fixed.