this post was submitted on 10 May 2026
63 points (94.4% liked)

Programming

26924 readers
254 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
you are viewing a single comment's thread
view the rest of the comments
[–] BlameThePeacock@lemmy.ca 3 points 4 days ago (1 children)

You're both correct, and also wrong.

A lot of code already exists. Or at least in a close enough form that it can be easily adjusted to address a new situation.

When someone comes up with an idea for a new App at this point, it's almost never because it's an entirely new branch of computing. It's very likely just CRUD with a visual design, and then a small more complex algorithm to mix the data around behind the scenes.

What's the difference between a dating app and an automatic meal plan builder? The algorithm doesn't care about whether or not the recipe swiped back when it matches it up to you.

You're right that they're not going to be inventing entirely new things most of the time, that's just not what's needed of them most of the time.

[–] luciole@beehaw.org 3 points 4 days ago (2 children)

Fortunately software is much more than App ideas fishing for VC investments. A lot of us are building actual tools for nurses, teachers, technicians, artists, students, etc. We have to analyze these human beings' role in society, their needs, their situation, which is different from merely preying on their attention span. Programming languages are still the most reliable way to specify how the software must behave. And once the software is done, it is merely born. It then lives through a steady flow of continuous adaptation until one day it dies as all things do. Downplaying the human condition is a mistake.

[–] iglou@programming.dev 1 points 3 days ago* (last edited 3 days ago)

You missed the point. The point is that almost all software today follows the same general ideas, patterns, etc.

The quality of the output of AI is not tied to what these patterns are used towards. Even if, say, your tool has a completely new network protocol. An LLM will still "understand" that it is a network protocol, that it serializes following rules that you tell it, serializes and deserializes the way you decide, then it will write that down in a memory and be able to work with that.

A new file format? Same. A very specialized new kind of No-SQL database that fits your very specific tool better? It will also write down in a file how it works and be able to use that.

It's as good as the documentation you give it is. Which, for basic things such as setting up a basic REST API, it has learned in its training data. If it hasn't, it's up to you to provide it, and it will be perfectly able to use it.

Even if you build some weird unique assembly language it will be able to use it if you give it the set of instructions and their documentation.

[–] BlameThePeacock@lemmy.ca 1 points 4 days ago

A medicine dispenser application for a nurse is still just CRUD operations for the most part. There's nothing innovative about how the code would be written in an application like that.