146 points drogus 4 hours ago 53 comments
Ozzie_osman 1 hour ago | parent
In some cases you can get away with not reading the code. And maybe in the future that will be more common. But for now, I personally prefer to read (or skim) the code, and not abdicate to AI.
tomrod 1 hour ago | parent
rob74 36 minutes ago | parent
...which is a bit disappointing, actually. I mean, if you give an AI agent the complete code for a working application (ideally including tests), it should be able to translate it into an equivalent application in another language. I can understand if it makes mistakes because of ambiguous or incomplete prompts etc., but for this task you shouldn't even need a prompt, any information it might need is right there in the code?
CoolestBeans 12 minutes ago | parent
So porting should be perfect conditions for an AI agent. It has the testing suite. It has the original implementation. Hell, it can A/B the original with its working copy and attach the original to a debugger.
So yeah I dunno. I guess despite some people's rhetoric on this site we shouldn't underestimate how difficult these tasks are "in the real world" (as opposed to like a game port which doesn't have real money on the line so far). And it is kind of a miracle these tools can even get in the ballpark and fool a lot of people.
IshKebab 1 hour ago | parent
It definitely improves the results if you do think but I don't think "you still have to think" is a safe space that's going to save us from unemployment.
B56c 54 minutes ago | parent
skydhash 8 minutes ago | parent
catlifeonmars 7 minutes ago | parent
as1mov 53 minutes ago | parent
rubyfan 52 minutes ago | parent
yuhmahp 49 minutes ago | parent
remember this timeless Agent Smith quote
zelphirkalt 44 minutes ago | parent
pixl97 40 minutes ago | parent
deadbabe 37 minutes ago | parent
If you are not using AI agents for everything, you're doing something wrong, and wasting company time. It has been emphasized that no one should be writing code by hand and if you think an AI has implemented something wrong you need solid reasoning to show why or else people just label you as some anti-AI troublemaker, who just becomes an obstacle standing in the way of things getting done.
If your human generated opinion is in any way wrong or simply not a true homerun then you get snubbed in future reviews, people stop listening to you.
ThunderSizzle 32 minutes ago | parent
However, it doesn't take away the concern of architecture, design, etc. and questioning if the current solution is well designed or not.
In other words, if you can't question the AI and refute it in a topic, you aren't expert enough to use AI in that area in a engineering manner.
Granted, not everything needs an engineer behind it. A shack to store some tools will survive long enough probably
Schiendelman 27 minutes ago | parent
vorticalbox 23 minutes ago | parent
They argued this still allowed them to fully understand what has being implemented and how it fitted together.
I’ve been doing this since I read that and it also allows you to catch stupid stuff while your typing, you can reason about what each little change does and why it’s needed.
This also lets the LLM change the future of the plan if you fine something.
This turns out to save a whole bunch of time later because you already know how it works.
It’s not nearly as fast as just letting the agent do everything.
hyperpape 24 minutes ago | parent
I'm going to read you charitably, and assume that what you really meant is "the burden of proof is entirely on you, and is set unreasonably high." Because of course, if you do think someone has done something wrong and want to say it publicly, you do need a solid reason.
pphysch 19 minutes ago | parent
dvh 5 minutes ago | parent
thomascountz 49 minutes ago | parent
So, I want to keep pulling the thread: is it worth reading—meaning, understanding—the code in order to prevent p95 latency from skyrocketing, avoid OOM death, and keep our apps reliable for customers?
The cost of understanding the code is ostensibly very high relative to just using a clanker (citation needed), so does paying that cost translate to value—what is it worth? Concretely, if vibe coding increases bugs and enshittification, but decreases spending without decreasing revenue (read: customers suffer, but they don't leave), do we still need to pay the cost of reading code? Is it better to invest in stickiness, lobbying, and market capture?
I hope this comment isn't read as advocating for this; it's more of a thought experiment about pragmatism and trade-offs. I know that I personally care a lot about understanding the code, and I believe I'm paid to do exactly that (I very much enjoy understanding code and nobody is paying me to run a business, so I may be biased in this). In everyday SaaS-land—not talking about critical safety systems—we've seen production databases destroyed, personal data leaked, platforms unwittingly exploited, and UX bugs creep into our operating systems, and yet the companies involved keep on keeping on.
Is thinking, meaning taking the time to actually understand what these systems are doing, going to increase their shareholder value?
as1mov 4 minutes ago | parent
Translating this from Linkedin-speak: Is it okay to subject our users to shitty software and while we use the money saved to bribe politicians, circumvent laws and buy our competitors to kill them?
oulipo 2 minutes ago | parent
discreteevent 47 minutes ago | parent
Schiendelman 26 minutes ago | parent
ionetan 17 minutes ago | parent
throwaway2836 7 minutes ago | parent
variety8675 47 minutes ago | parent
treetalker 42 minutes ago | parent
CoolestBeans 35 minutes ago | parent
jamienk 28 minutes ago | parent
Aurornis 13 minutes ago | parent
Then respond with that addressed, with a firm but polite explanation that the document has some problems that need to be addressed carefully before we invest time on it.
None of this works if it’s coming from your boss, but it’s very effective at making people think twice before sending you slop.
People only do the workslop thing when they believe the benefits of showing the work outweigh the reputational risks. If they get caught every time they do it and exposed on an email chain, they start doing less.
OptionOfT 8 minutes ago | parent
BUT because it is AI it's not that section that's addressed, it's about 90% of the document that now has changed, and I need to spend another gargantuan effort to review it. It's like by trying to be helpful I actually lose more time.
The AI has made it so that the thinking before writing is mostly gone, and shifted that step to the reviewers.
stephbook 34 minutes ago | parent
It's easy to port a codebase (at least, if you have automated tests), but once you've done that, do you
- Implement features in the old code and port again?
- Implement them in the new, unfamiliar codebase?
- Just write a Jira ticket and let the agent YOLO it?
wuhhh 28 minutes ago | parent
sergiotapia 26 minutes ago | parent
Not a good look tbh
tripleee 21 minutes ago | parent
If he truly believed in the idea of never reading the code, he'd fire all his developers and have the designers do it all - create very high level feature descriptions and iterate on them. Put your money where your mouth is
wilg 7 minutes ago | parent