6 ms·

> Hearing so many people say that AI-generated code is unusable and fixing it takes longer than writing it by hand, makes me wonder if they are working on a ver

> Hearing so many people say that AI-generated code is unusable and fixing it takes longer than writing it by hand, makes me wonder if they are working on a very specific field or I just have skill issues. In my work, there are people everywhere in the "AI adoption" spectrum. On one hand, a certain Senior engineer spent a month having an AI write him thousands of lines of code for a feature. The AI wrote a million tests, tools to visualize data, everything. But he still has not delivered the code to the main repository since he knows nobody will ever review the mess the AI wrote, and he can't even properly understand it to defend it in review. We have human reviews as part of our process, the coworker is 100% stuck on it. I, on the other hand, don't ask AI to write code for me, but I have AI explain me concepts, track down bugs, review my patches, etc. Sometimes it shows me patch format, but I prefer it doesn't touch my filesystem. I treat it as a senior employee whose task is to be there and help me. It's been going great. I am definitely more productive, I am coding faster, and the future is sustainable for me. Having it write shit for me would definitely be faster, but I want to use AI as a tool to teach me what to do, not do it for me. There are also employees who are still working on the pre-AI model. Whenever AI is mentioned, they automatically assume it could be hallucinating and whatnot. To these, I never mention AI, because it simply derails the conversation to a useless point.

pydry 1mo ago
From what I see around me the first is by far and away the most common use case. * Everybody thinks theyre more productive. * Some devs do boost their productivity a bit. * But nowhere near enough to counter the slop merchants. On average if I measure productivity by pull requests, productivity has gone up. If I measure by bugs and incidents and value delivered, I think mostly it's gone down, often significantly due to the side effects of AI abuse and slop. To be fair pull requests are a lot more measurable than the trust lost because of a series of critical bugs and incidents but if you work on the ground floor of a product you get a good sense of the relative trade offs. If I look at open source as a whole ive noticed a rhyming pattern - established products aren't moving any faster these days (despite a flood of PRs) but there is a sudden new deluge of vibe coded projects you can wade through, none of which are really gaining traction.

pydry 1mo ago

From what I see around me the first is by far and away the most common use case. * Everybody thinks theyre more productive. * Some devs do boost their productivity a bit. * But nowhere near enough to counter the slop merchants. On average if I measure productivity by pull requests, productivity has gone up. If I measure by bugs and incidents and value delivered, I think mostly it's gone down, often significantly due to the side effects of AI abuse and slop. To be fair pull requests are a lot more measurable than the trust lost because of a series of critical bugs and incidents but if you work on the ground floor of a product you get a good sense of the relative trade offs. If I look at open source as a whole ive noticed a rhyming pattern - established products aren't moving any faster these days (despite a flood of PRs) but there is a sudden new deluge of vibe coded projects you can wade through, none of which are really gaining traction.