view the rest of the comments
Unpopular Opinion
Welcome to the Unpopular Opinion community!
How voting works:
Vote the opposite of the norm.
If you agree that the opinion is unpopular give it an arrow up. If it's something that's widely accepted, give it an arrow down.
Guidelines:
Tag your post, if possible (not required)
- If your post is a "General" unpopular opinion, start the subject with [GENERAL].
- If it is a Lemmy-specific unpopular opinion, start it with [LEMMY].
Rules:
1. NO POLITICS
Politics is everywhere. Let's make this about [general] and [lemmy] - specific topics, and keep politics out of it.
2. Be civil.
Disagreements happen, but that doesn’t provide the right to personally attack others. No racism/sexism/bigotry. Please also refrain from gatekeeping others' opinions.
3. No bots, spam or self-promotion.
Only approved bots, which follow the guidelines for bots set by the instance, are allowed.
4. Shitposts and memes are allowed but...
Only until they prove to be a problem. They can and will be removed at moderator discretion.
5. No trolling.
This shouldn't need an explanation. If your post or comment is made just to get a rise with no real value, it will be removed. You do this too often, you will get a vacation to touch grass, away from this community for 1 or more days. Repeat offenses will result in a perma-ban.
6. Defend your opinion
This is a bit of a mix of rules 4 and 5 to help foster higher quality posts. You are expected to defend your unpopular opinion in the post body. We don't expect a whole manifesto (please, no manifestos), but you should at least provide some details as to why you hold the position you do.
Instance-wide rules always apply. https://legal.lemmy.world/tos/
My professional experience so far has been that "faster" doesn't actually work unless you abandon the whole concept of responsibility entirely and just blindly trust the AI. Writing code has never been the long tail of software engineering. It has always been code review, software management and debugging, and so far AI has actually made that significantly slower in my experience.
Just this week my colleague and I pointed out a very laughably obvious flaw in a "true believer's" code, and he just... argued about it, not because the AI can't be wrong, but because of the implication of him submitting code he clearly did not understand. So far, that's the norm, not the exception.
Obviously it's not going anywhere, but the pendulum is so far past the equilibrium it's going to settle into eventually, that the loudest evangelists might as well just be wrong.
This all or nothing extreems aren't reality.
You can have AI help you add unit-tests you wouldn't have thought of.
Once you are "Done" writing tests, and can't think of more scenarios, AI more often than not can. And can help you add better test coverage.
I've heard many people say this, what is the downside here?
A unit test you don't understand is worse than useless.
You understand you can... Just read up and learn on the thing the slop machine suggests right?
You don't have to trust it. And you shouldn't.
But dude is right, the slop machine will 110% come up with legit suggestions because it's the stolen collective knowledge of the internet.
Your job is to exercise that thinking thing between your ears and validate information before implementing it. Regardless of the source.
Then read the extra tests it came up with and make sure you understand it.
It catches things like a null check you might have forgotten, trivially easy to understand.
You don't even have to have it write any tests if you want, you can ask it "what Unit-Test scenarios did I miss?" And write them yourself.
That last scenario is the correct usage IMO, and largely how I've been using it. However, in my experience the actual result in actual organizations is that every software engineering taboo just falls to some combination of ego, laziness, and whip cracking, one by one, until something gets properly fucked, and only then are strict rules established.
My major beef is that it is too tempting to abuse it, and the abuse inevitably becomes too voluminous to properly inspect, and something inevitably breaks. The same thing happens with humans, but humans moving at human speed make it exponentially easier for humans to comprehend. For bullshit slopware, code nobody actually has time to understand is honestly fine, but for serious systems it is absolutely not ok.