116
Starting every coding task with a prompt
(sopuli.xyz)
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
this post was submitted on 05 Jun 2025
116 points (99.2% liked)
Programming Circlejerk
204 readers
2 users here now
Community to talk about enlightened programming takes
Rules:
- read and follow the programming.dev code of conduct
- no flamewars
- mark your unjerks
- only programming related content allowed
- link to the original source
- do not mention this community in places like hackernews, lobste.rs, or the general programming communities on Lemmy where we source jerk material from.
founded 4 months ago
MODERATORS
My bosses keep trying to get me to do this. They don't understand that the work they give me is complicated and niche. The chatbots do not help at all, ever. It's shit.
I don't understand why these numbskulls pay me if they think my job is so easy that a fucking chatbot can do it.
They need to see if it can be done before they fire you. But if you're not trying they can't start seeing. So you need to set least try for them to see.
Call me paranoid, but it feels like having professionals consistently brute force the output from these systems into something usable would provide a rich resource to improve them to the point that they can.
they want you to model your work processes so the AI can duplicate you.
Yeah, every so often I do want to give it a try, to see what's possible, but I just immediately bounce off from trying to explain my task in a prompt. There's so much context one needs to be aware of, I'd have to write a whole essay into there.
And that's when I'm lucky, when I myself know what needs to be done. More often than not, I start implementing and then find out what the steps are. Finding that out upfront, so I could try to write it into a prompt, takes an insane amount of effort. And especially so, when I can't rely on the instructee thinking logically to catch when I made a mistake.