51–60 of 71 posts
Earlier quoted context omitted.
OP here: we don't give Claude Code access to prod. Everything is isolated cloud accounts for this purpose. E.g. we give Claude credentials for db - but it's never prod data.
You should edit the article to suggest this point, it may not be obvious to everyone reading it.
> Did you find an issue that Claude did not, because you ran the webserver end to end, connected to a real database? Good, now give Claude Code an API key to the database and get out of the way. No need for copy-paste next time. Often I notice errors trying it out in production. This assumes you trust it with access to the production database. How far are you willing to go? LLM's are gullible, so you should never giv…
What a hellscape we've created for ourselves. My job is to get out of the way of an AI agent? People were writing bad code before, but at least they were looking at it. It is very difficult to judge whether the code AI spits out is correct or not. My job is to write correct code, and I'm not at all convinced that's easier with an AI. It's a lot easier to write correct code myself than to catch every subtle bug introd…
I was handed a project someone vibe coded with Claude and it took me hours just to get it running to discover it was missing the entire interface and all the queries were for sqlite while the DB to setup for it was mysql. The patch diff file between what claude produced and the functional version I got working was over 11k lines
Whether you like the vibe coded app or not, you would have had fewer errors if Claude had been testing it end to end while vibe coding.
I actually agree partially with the title. I just let the agent run - it'll run better diagnostics than I can (misc. git, permission checks, commands with flags I don't remember). If the process yields an error - it means it can't solve it and I have to step in. Being desperate and copy pasting the error back in is just foolish procrastination. The actual body of the article with just passing in your api keys is insa…
We assume that every API key we put into Claude Code can be leaked and therefore make sure there's nothing sensitive behind them.
I wasn't expecting the answer to be "because copy-pasting would involve too much thinking". Some people are borderline afraid to touch their keyboards these days.
Earlier quoted context omitted.
OP here: we don't give Claude Code access to prod. Everything is isolated cloud accounts for this purpose. E.g. we give Claude credentials for db - but it's never prod data.
But what if there's only an error in prod?
Earlier quoted context omitted.
Of course he is because even if the doctor typed like that, how would the patient see it? They don't do that in the exam room with the patient there. I wonder how long it's been since they've even had an appointment with their doctor if they think that is what actually happens.
Yes they do. General physical appt. 6 months ago. Doctor spent 2x more time on the wall-mounted EHR terminal slowly typing and clicking through menus than having a conversation or doing physical exams. Just means their interface and workflow is bad and needs to be improved though, not that the doctor needs to be removed from the process altogether.
Earlier quoted context omitted.
I read and understand the code using my brain, by constructing a mental model and reasoning about it. An AI can't do this because they don't have mental models and don't do reasoning.
I am out of my depth here and don’t know anything about how other people reason and construct mental models, but I mostly talk to myself about the problem and then do something at the end of that. There’s no point where I like have the whole solution in my minds eye (for programming topics, maybe for a drawing or a sculpture or removing a transmission or something I can do that). Following the output of agent “thinki…
>Did you find an issue that Claude did not, because you ran the webserver end to end, connected to a real database? Good, now give Claude Code an API key to the database and get out of the way. No need for copy-paste next time Yup, that is why we are seeing so many production databases being deleted, endless vulnerabilities. No engineer with proper common sense will grant an agentic AI, API access to the database. "O…
I audibly gasped when I read that. You would hope that "no engineer with proper common sense" will do that. The more we offload our thinking to agents though... I feel like it will be harder to reason against it as time goes on, until someone gets burned personally. Where I am there is zero emphasis on security with agents
The other engineer who doesn't take shortcuts and does thing properly will be scolded (at best).