4 ms·
I read that as you have never been debugging a production issue at 3am while losing data and/or revenue.
by JanneVee 7mo ago
I read that as you have never been debugging a production issue at 3am while losing data and/or revenue.
- esafak 7mo agoI don't. I did those things before AI so what's new?
- vinceguidry 7mo agoThe Googling you do to get an understanding of something you've never seen before can be done in a fraction of the time by AI.
- JanneVee 7mo agoA feature wasn't 10000 loc written by a AI before that no one except the AI with the context understands. If you review all that to understand it fully your productivity gain diminishes, the gain might not go away fully but it is much less when you can be woken up at 3am because of an incident and start reviewing everything.
- esafak 7mo agoIf I'm the responder it makes no difference to me if an AI wrote it or another worker; it's alien either way.
- JanneVee 7mo agoWell, for me it makes a difference. I often get in a sense a "theory of mind" of the other developers when I read other code. I don't get the same thing with AI code.
- simianwords 7mo agoAI helps in both, so not sure what your point is? its like saying "don't write code because we will have to debug it later".
- JanneVee 7mo agoWell you aren't writing the code, the AI is and you are letting the AI debug that created it in the first place and it doesn't learn from the experience in the same way. Hopefully you understand the problem in such a degree that you can spec away the problem in the next iteration. I'm seeing that issue now, people just forget to learn what the issue is and keep repeating mistakes that are regurgitated from the training material.