190
top 40 comments
sorted by: hot top controversial new old
[-] talkingpumpkin@lemmy.world 114 points 2 days ago* (last edited 2 days ago)

Being able to use an LLM turns a layman into a coder no more than being able to use CAD turns them into an engineer.

It's a real pity that LLMs seem to have taken over as the sole topic of discussion in programming communities such as this one. It might be just me, but I find the whole topic barely interesting at all (ie. not more interesting than the discussions about stackoverflow coding we used to have).

[-] Womble@piefed.world 7 points 1 day ago

But at the same time everyone having a CAD machine (or 3D printer) allows a lot of people to solve engineering type problems they have without an engineer, which is the article's point.

[-] talkingpumpkin@lemmy.world 2 points 15 hours ago* (last edited 15 hours ago)

IDK.

I just asked this to perplexity as an experiment:

write a macos terminal command that makes a backup copy if all files in documents/ my home adding the current date and time to each filename

Here's what it concocted:

cd ~ && find Documents -maxdepth 1 -type f -exec sh -c 'for f; do cp "$1" "Documents/$(date +%Y%m%d-%H%M%S)_$(basename "$1")"; done' _ {} +

Now, I am no "prompt engineer" and surely there are better way to ask it stuff, but then again a layman is no prompt engineer either.

So the question is: would a layman be able to provide feedback and have perplexity fix its command?

My "layman-like" feedback (now that I re-read it, IDK how much a layman would have used "recurse"... I'm doing my best here):

I want the files copied to a "backups" folder in my home. It should also recurse into the "documents" folder.

mkdir -p ~/backups && cd ~/Documents && find . -type f -exec sh -c 'mkdir -p "~/backups/$(dirname "$1")" && cp "$1" "~/backups/$2/$(date +%Y%m%d-%H%M%S)_$(basename "$1")"' _ {} "$(pwd)" \;

Feeback:

it says "No such file or directory" (because of $PWD passed as $2 - of course I didn't say this to the LLM)

mkdir -p ~/backups && rsync -a --include='*/' --include='*.*' --exclude='*' --no-links ~/Documents/ ~/backups/"$(date +%Y%m%d-%H%M%S)"/

the date must be in the file name

mkdir -p ~/backups && find ~/Documents -type f -exec sh -c 'dir="~ /backups/$(dirname "${1#"$2"}")"; mkdir -p "$dir"; cp "$1" "$dir/$(date +%Y%m%d-%H%M%S)_$(basename "$1")"' _ {} ~/Documents \;

I don't think I need to continue?

BTW: the LLM also instructed me to do a whole bunch of seemingly useless stuff, like giving Terminal.app full disk access via System Settings > Privacy & Security > Full Disk Access (which I assume is actually a thing in macos but can't verify as I run linux)

edit: I hope I didn't misinterpret the bash commands (I didn't actually run them) and spotted the right bugs in them - even if I didn't I guess my point still stands?

[-] ulterno@programming.dev 8 points 1 day ago

I can use CAD. I am an engineer.
But noone will ask me to draft a building design on AutoCAD, same as noone will ask me to do so with pencil and paper.
Because I don't know buildings.

Sure, I might be asked to copy a pen-paper drawing onto CAD, but a Civil Engineer with CAD will do that better and a photo tracing software might do it as well as me.

So while a good enough LLM might code as well as a coder, Programming is more than just coding and making anything new, requires programming.

Being able to use an LLM turns a layman into a coder no more than being able to use CAD turns them into an engineer.

Perfect analogy.

[-] Feyd@programming.dev 17 points 2 days ago

I am 100% with you. I am so sick of LLM shit clogging up the feed

[-] RedstoneValley@sh.itjust.works 55 points 2 days ago

While I (almost) agree with the conclusion, there is a lot of bullshit and unproven assumptions in this blog post. I always cringe about the "AI is democratising software development" argument in particular. This is just wrong on so many levels. Software development is not an ivory tower. Everyone with an internet connection had access to all the resources to learn the necessary skills for free, for decades. Everyone who had an interest in actually learning that stuff and putting a bit of effort into it was able to do so. What LLMs provide is not democratising anything but advertising the illusion that everyone can produce software, effortless and without any skills whatsoever. Software development is much more than just churning out lines of code that seem to work. The Vibecoding approach is like trying to build your own car without having the skills and asking an AI to construct it as the sum of individual parts which all come from different car models from a Lada to a Ferrari. The end result might be drivable, but it will be neither secure nor efficient nor fast nor stable nor maintainable etc. A Frankenstein car. Everyone with half a brain would agree that's not a good idea, however with LLMs people just do pretend its fine.

[-] red_tomato@lemmy.world 52 points 2 days ago

It’s easy to overestimate how much of software engineering is about coding, when in truth it’s mostly about the code you don’t write.

[-] msage@programming.dev 11 points 2 days ago

I always get upset when people write unclear lines.

I do a lot of code reviews, and it's taking years to explain how to write code that makes sense. Some are better, some just write, or worse - copy, things that are ambiguous, or are made such by copying them with small changes.

It's very difficult to specify bullet-proof rules for good code. And after every step devs find more ways to fuck it up.

[-] Gonzako@lemmy.world 3 points 1 day ago

Yeah, what's worked for me best is never doing straight up copy paste but try to walk through the script as I write it down because if I don't understand it I can't modify it.

[-] Ephera@lemmy.ml 3 points 2 days ago

Yeah, my current software project at work was basically half a year of feature development and since then, we've purely tried to get it into the real world, which meant evaluating use-cases to see where it falls flat and what needs stabilizing, as well as figuring out people's needs and how our software can assist with that, then setting up a demo and hoping they find money somewhere...

[-] kibiz0r@midwest.social 21 points 2 days ago
[-] Flamekebab@piefed.social 18 points 2 days ago

An interesting way to try to spin disposable spaghetti code as a positive.

I think ignoring that a tool has valuable uses is cutting off the nose to spite the face in a way.

While LLMs are annoying as fuck to deal with and work with with corporate CEOs telling all of us to "Use them or face unemployment"; it cannot be ignored that they have valuable use cases.

This article tries to identify the real world use case for an AI/LLM, which is as an ephemeral problem solving machine, much like google or stack overflow has been in the past, just on steroids.

Once you're done with the solution: throw it away.

LLMs are not to be trusted to write software, but they can generate code to solve mundane problems encountered during software development.

[-] ExLisper@lemmy.curiana.net 19 points 2 days ago

I've been saying this for years (maybe I need to start a blog?). Being able to make an app and make a product are completely different things.

If one person can quickly create an app someone else can as easily create open source version and just give it away. To offer a product you need sales, customer service, technical support and so on and creating this organization has nothing to do with writing code. There are exceptions like video games where one person can create and distribute a product but it's because it's more art than engineering. For a SaaS platform to be a "product" it needs to offer functionality that's impossible to implement for a small team in a short period of time or evolve using AI.

[-] LordMayor@piefed.social 10 points 2 days ago

There are more exceptions than just games. I know someone who made a good career writing statistical forecasting software. It was just himself and he had some large corporations as clients.

There a niches of expertise for which most businesses don’t need dedicated employees or even software licenses. But, you’re not going to write the software with AI because it takes domain experience and expertise that AI can’t emulate.

[-] codeinabox@programming.dev 12 points 2 days ago

This article is quite interesting! There are a few standout quotes for me:

On one hand, we are witnessing the true democratisation of software creation. The barrier to entry has effectively collapsed. For the first time, non-developers aren’t just consumers of software - they are the architects of their own tools.

The democratisation effect is something I've been thinking about myself, as hiring developers or learning to code doesn't come cheap. However, if it allows non-profits to build ideas that can make our world a better place, then that is a good thing.

We’re entering a new era of software development where the goal isn't always longevity. For years, the industry has been obsessed with building "platforms" and "ecosystems," but the tide is shifting toward something more ephemeral. We're moving from SaaS to scratchpads.

A lot of this new software isn't meant to live forever. In fact, it’s the opposite. People are increasingly building tools to solve a single, specific problem exactly once—and then discarding them. It is software as a disposable utility, designed for the immediate "now" rather than the distant "later."

I've not thought about it in this way but this is a really good point. When you make code cheap, it makes it easier to create bespoke short-lived solutions.

The real cost of software isn’t the initial write; it’s the maintenance, the edge cases, the mounting UX debt, and the complexities of data ownership. These "fast" solutions are brittle.

Though, as much as these tools might democratise software development, they still require engineering expertise to be sustainable.

[-] themaninblack@lemmy.world 3 points 1 day ago* (last edited 1 day ago)

The bespoke short-lived solutions angle is an interesting one, to be sure.

I wonder how many orgs will back themselves into a corner thinking their product will be short lived but it ends up hanging out for a while, as you mentioned.

Honestly this feels like an extension of this Agile/Scrum madness we’ve been dealing with since the mid-2000’s. Instead of the next quarter, we’re only building things with a view of the next two weeks.

Now it’s measured in hours, and even then we can give a prompt to an LLM and have a half working thing to throw away after it converts that PDF to a CSV.

I worry about the craftsmanship leaving this field. Engineers used to push back and for good reason.

[-] ICastFist@programming.dev 19 points 2 days ago

The democratisation effect is something I’ve been thinking about myself, as hiring developers or learning to code doesn’t come cheap.

It's not really "democratizing" anything, since anything made that isn't like a simple calendar or forum will come with more bugs than working features. Low and no-code development options have been available for ages, so "doesn't know how to code" was never an actual barrier to making software. Not only that, learning to code could be done effectively for free for well over 15 years now, online resources have only gotten better. It was never about the (lack of) money, it was always about time needed. "I don't want to/can't learn this, yet I want the thing done" - that's why we pay professionals.

However, if it allows non-profits to build ideas that can make our world a better place, then that is a good thing.

At best, they'll get semi-working prototypes. At worst, they'll try to sell said prototypes as end products. Besides, anything that is "a disposable utility, designed for the immediate “now” rather than the distant “later.”" is extremely unlikely to make the world a better place.

[-] fonix232@fedia.io 3 points 2 days ago

what a load of bull.

AI doesn't "democratise" coding. One still needs to understand the basics of computer science, as well as higher level software design, to make use of AI tools and get actually usable results.

LLMs can write good code but they require constant guidance to do so. This is something that people need to understand. AI in coding is like Photoshop to an "analog" artist - super useful IF you know what you're doing, but as a complete stranger to the topic, all you'll do is basic tinkering.

[-] Womble@piefed.world 3 points 1 day ago

I think you are vastly overestimating the level that statement is pitched at. The overwhelming majority of people dont even know how a for loop works. However they can ask an LLM to write a script to change this list of files with inconsistent numbering conventions and put them in a consistent order. That's the level of spreading out the ability to program that we are dealing with.

[-] fonix232@fedia.io 3 points 1 day ago

Basic scripting is hardly programming, and it's been available in various user-friendly forms for quite a while...

Problem is that most people do seem to treat LLMs as if they could replace a well trained engineer. Including middle managers who want to cut costs at all price.

[-] Womble@piefed.world 1 points 17 hours ago* (last edited 17 hours ago)

And those people who think LLMs will replace software engineers any time in the near future are wrong. But it can still be the case that LLMs are democratizing coding ability to those who otherwise wouldnt have it while at the same software engineering as a discipline isnt going anywhere.

Its not just basic scripting either, often when people start coding in earnest their programs are just a huge pile of statements connected together with if statements and mutating global variables. and LLM can help show best practices like encapsulating logic into functions and isolating side effects.

[-] monogram@feddit.nl 1 points 2 days ago

Fuck off AI

this post was submitted on 12 Jan 2026
190 points (94.8% liked)

Programming

24394 readers
304 users here now

Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!

Cross posting is strongly encouraged in the instance. If you feel your post or another person's post makes sense in another community cross post into it.

Hope you enjoy the instance!

Rules

Rules

  • Follow the programming.dev instance rules
  • Keep content related to programming in some way
  • If you're posting long videos try to add in some form of tldr for those who don't want to watch videos

Wormhole

Follow the wormhole through a path of communities !webdev@programming.dev



founded 2 years ago
MODERATORS