logoalt Hacker News

pllbnk • yesterday at 2:30 PM • 2 replies • view on HN

I think minority do. Imagine, you have been vibe-coding this project for a while and it works kind of fine but you just have to fix a few more bugs and you get something like `node /tmp/claude-1000/-home-user-source-github-user-hn/27b740b1-9a45-47f3-ab99-61e5e3cf779a/scratchpad/hidden-smoke.mjs; echo "exit=$?"`. (I took it from my own agent right now and I don't have any idea what it's doing. Thankfully, it's sandboxed so I don't care _that much_ right now). Is it bad? You can probably go into that mjs file and see what's in there, but so far it's been fine every time, why would it be different this time? Approve!

We will see many disastrous bugs and hacks in the coming years with the way most developers are coding right now.

If you take time to understand _everything_ that an agent is asking of you, then nearly all those advertised productivity gains would be wiped out.

Replies

godelski • today at 7:01 AM

  > I think minority do
Let's be real, the minority of people understand bash. It is a terrible language with tons of footguns[0], albeit a very useful language and still worth learning. The number of ~/.claude/settings.json I've seen with "permissions": { "allow": ["Bash(find *)"]} I've seen is crazy[1]. Hell, most people I talk to think `find` is a tool that is used for searching for files. I mean... it does that... along with arbitrary code execution ¯\_(ツ)_/¯

[0] https://mywiki.wooledge.org/BashPitfalls

Edit:

[1] Fuck it, here's the lazy search: https://github.com/search?q=%22Bash(find%20*)%22&type=code

➕ show 2 replies
crooked-v • yesterday at 6:05 PM

For me, step 1 of trying to make Claude even vaguely usable is putting in a hook that just tells it 'FUCK YOU, STOP USING PIPES' whenever it tries to chain multiple bash commands.

➕ show 2 replies