893

Programmers are no longer needed! (lemmy.ml)

submitted 2 months ago by cm0002@lemmings.world to c/programmer_humor@programming.dev

147 comments fedilink hide all child comments

you are viewing a single comment's thread
view the rest of the comments

[-] Semi_Hemi_Demigod@lemmy.world 227 points 2 months ago

Describing what they want in plain, human language is impossible for stakeholders.

[-] Sunsofold@lemmings.world 88 points 2 months ago

'I want you to make me a Facebook-killer app with agentive AI and blockchains. Why is that so hard for you code monkeys to understand?'

[-] LordCrom@lemmy.world 35 points 2 months ago

You forgot we run on fritos, tab, and mountain dew.

[-] criss_cross@lemmy.world 10 points 2 months ago

Maybe he want to write damn login page himself.

[-] pinball_wizard@lemmy.zip 10 points 2 months ago

Not say it out loud. Not stupid... Just proud.

[-] eager_eagle@lemmy.world 32 points 2 months ago

Even writing an RFC for a mildly complicated feature to mostly describe it takes so many words and communication with stakeholders that it can be a full time job. Imagine an entire app.

[-] madcaesar@lemmy.world 19 points 2 months ago

Getting ai to do a complex problem correctly takes so much detailed explanation, it's quicker to do it myself

[+] TurdBurgler@sh.itjust.works -8 points 2 months ago* (last edited 2 months ago)

While it's possible to see gains in complex problems through brute force, learning more about prompt engineering is a powerful way to save time, money, tokens and frustration.

I see a lot of people saying, "I tried it and it didn't work," but have they read the guides or just jumped right in?

For example, if you haven't read the claude code guide, you might have never setup mcp servers or taken advantage of slash commands.

Your CLAUDE.md might be trash, and maybe you're using @file wrong and blowing tokens or biasing your context wrong.

LLMs context windows can only scale so far before you start seeing diminishing returns, especially if the model or tools is compacting it.

Plan first, using planning modes to help you, decomposition the plan
Have the model keep track of important context externally (like in markdown files with checkboxes) so the model can recover when the context gets fucked up

https://www.promptingguide.ai/

https://www.anthropic.com/engineering/claude-code-best-practices

There are community guides that take this even further, but these are some starting references I found very valuable.

[-] onlyhalfminotaur@lemmy.world 27 points 2 months ago

So even more work than actual coding.

[-] expr@programming.dev 22 points 2 months ago

Yup. It's insanity that this is not immediately obvious to every software engineer. I think we have some implicit tendency to assume we can make any tool work for us, no matter how bad.

Sometimes, the tool is simply bad and not worth using.

[-] Semi_Hemi_Demigod@lemmy.world 6 points 2 months ago

Everyone is a senior engineer with an idiot intern now.

[-] AdamBomb@lemmy.sdf.org 3 points 2 months ago

That’s not all! It’s also less rewarding!

[-] TurdBurgler@sh.itjust.works -1 points 2 months ago* (last edited 2 months ago)

Early adopters will be rewarded by having better methodology by the time the tooling catches up.

Too busy trying to dunk on me than understand that you have some really helpful tools already.

[-] jacksilver@lemmy.world 10 points 2 months ago

While you're right that it's a new technology and not everyone is using it right, if it requires all of that setup and infrastructure to work then are we sure it provides a material benefit. Most projects never get that kind of attention at all, to require it for AI integration means that currently it may be more work than it's worth.

[-] TurdBurgler@sh.itjust.works 0 points 2 months ago

This is why I say some people are going to lose their jobs to engineers using AI correctly, lol.

[-] onlinepersona@programming.dev -3 points 2 months ago

"If I need to write boilerplate and learn a new skill, is it really worth it?"

[-] jacksilver@lemmy.world 1 points 2 months ago

My point was the investment in vs the value out may not be worth it for many projects. Beyond that, it may not be maintainable for all projects (at least with how fast things have been changing in this space and the heavy reliance on 3rd party systems to make it work).

[-] TurdBurgler@sh.itjust.works 1 points 2 months ago* (last edited 2 months ago)

It's professional development of an emerging technology. You'd rather bury your head in the sand and say it's not useful?

The reason not to take it seriously is to reinforce a world view instead of looking at how experts in the field are leveraging it, or having discourse regarding the pitfalls you have encountered.

The Marketing AI hype cycle did the technology an injustice, but that doesn't mean the technology isn't useful to accelerate determistic processes.