this post was submitted on 10 Feb 2026
210 points (94.5% liked)

Programming

25698 readers
90 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
top 50 comments
sorted by: hot top controversial new old
[–] codeinabox@programming.dev 115 points 1 week ago (19 children)

This quote on the abstraction tower really stood out for me:

I saw someone on LinkedIn recently — early twenties, a few years into their career — lamenting that with AI they “didn’t really know what was going on anymore.” And I thought: mate, you were already so far up the abstraction chain you didn’t even realise you were teetering on top of a wobbly Jenga tower.

They’re writing TypeScript that compiles to JavaScript that runs in a V8 engine written in C++ that’s making system calls to an OS kernel that’s scheduling threads across cores they’ve never thought about, hitting RAM through a memory controller with caching layers they couldn’t diagram, all while npm pulls in 400 packages they’ve never read a line of.

But sure. AI is the moment they lost track of what’s happening.

The abstraction ship sailed decades ago. We just didn’t notice because each layer arrived gradually enough that we could pretend we still understood the whole stack. AI is just the layer that made the pretence impossible to maintain.

[–] Feyd@programming.dev 61 points 1 week ago (2 children)

LLMs don't add an abstraction layer. You can't competently produce software without understanding what they're outputting.

[–] chicken@lemmy.dbzer0.com 31 points 1 week ago (1 children)

The author's point is that people already don't understand what the programs they write do, because of all the layered abstraction. That's still true whether or not you want to object to the semantics of calling the use of LLMs an abstraction layer.

[–] Feyd@programming.dev 34 points 1 week ago (2 children)

Not knowing what cpu instructions your code compiles to and not understanding the code you are compiling are completely different things. This is yet another article talking up the (not real) capability of LLM coding assistants, though in a more round about way. In fact, this garbage blogspam should go on the AI coding community that was made specifically because the subscribers of the programming community didn't want it here, yet we keep getting these trying to skirt the line.

[–] codeinabox@programming.dev 15 points 1 week ago (5 children)

In fact, this garbage blogspam should go on the AI coding community that was made specifically because the subscribers of the programming community didn't want it here.

This article may mention AI coding but I made a very considered decision to post it in here because the primary focus is the author's relationship to programming, and hence worth sharing with the wider programming community.

Considering how many people have voted this up, I would take that as a sign I posted it in the appropriate community. If you don't feel this post is appropriate in this community, I'm happy to discuss that.

load more comments (5 replies)
[–] chicken@lemmy.dbzer0.com 5 points 1 week ago (1 children)

Talking about low level compilers seems like moving the goalposts, since they are way more well defined and vetted than the mass of software libraries and copy pasted StackOverflow functions a large segment of programming has been done with.

[–] tomenzgg@midwest.social 4 points 1 week ago (2 children)

A chicken in a programming comm.‽

Please tell me you write in Scheme…

load more comments (2 replies)
[–] mesamunefire@piefed.social 6 points 1 week ago (1 children)

I mean you can ...but its gonna be slop.

[–] MNByChoice@midwest.social 12 points 1 week ago (1 children)

One can get paid and advance through a career producing slop.

Good engineering is hard, and lots of that no longer happens.

[–] pinball_wizard@lemmy.zip 5 points 1 week ago (1 children)

One can get paid and advance through a career producing slop.

And thank goodness for that! LoL.

I wonder if how many people who write code for a living genuinely think, deep down, they're truly awful coders because they've only ever coded in an environment that demands the fastest, absolute barest minimum quality. It's so rare to get to write code exactly how one would prefer it.

[–] queerlilhayseed@piefed.blahaj.zone 12 points 1 week ago (7 children)

I feel like they kind of lost the thread here, even though I think I agree with the idea that vibe coding is a fundamentally different thing than another layer of abstraction. There's no need to punch on the web developers. We've all known, for the last several decades at least, that we don't have to understand the entire mechanism completely. No one is out there doping their own silicon and writing JS apps to run on it. The whole point of layered abstractions is that you can build on a set of assumptions without having to know all the implementation details of the layers below. When an abstraction leaks, then it can be useful to have some facility with the lower levels, but no person alive is a master of the full stack. The beautiful thing about abstractions is that you don't have to be. That's still true with vibe coding, just with the extra complexity of having a ticker tape spitting out semi-coherent code faster than any human could type it, which moves the dev from a creative role to more of an administrative one, as they mention earlier in the piece, which 1) is not nearly as fun, and crucially 2) doesn't help you build the muscles that make one good at code administration.

[–] pinball_wizard@lemmy.zip 5 points 1 week ago* (last edited 1 week ago) (1 children)

No one is out there doping their own silicon and writing JS apps to run on it.

Ahem. Right. That would be silly. No one would do that.

(Quick, I'll change the subject!)

I'll...uh... So Rust sure looks nice. Nothing silly going on there.

(Joking aside, I've really never done that. I can't claim I've never done anything similarly silly and wasteful. But I haven't done that, anyway.)

(Edit: yet.)

As I typed it I felt in my bones that someone was going to come along with an example of someone doing exactly that. I kinda hope someone does, I've looked into homegrown silicon and it looks... very difficult and expensive.

load more comments (6 replies)
[–] idunnololz@lemmy.world 12 points 1 week ago* (last edited 1 week ago) (1 children)

I've had this problem with abstractions for the longest time. Of course whenever I say anything negative about abstractions I just get dog piled so I don't usually like to discuss the topic.

I think abstractions as a tool is fine. My problem with abstractions is that most developers I meet seem to only talk about the upsides of abstractions and they never take into account the downsides seriously.

More often then not, I just think people treat abstractions as this magical tool you cant over use. In reality, over use of abstractions can increase complexity and reduce readability. They can greatly reduce the amount of assumptions you can make about code which has many many additional downsides.

Of course I'm not saying we shouldnt use abstractions. Not having any abstractions can be just as bad as having too many. You end up with similar issues such as increased complexity and reduced readability.

The hard part is finding the balance, the sweet spot where complexity is minimized and readability is maximized while using the fewest amount of abstractions possible.

I think too often, developers would err on the side of caution and add more abstractions then necessary and call it good enough. Developers really need to question if every abstraction is absolutely necessary. Is it really worth it to add an additional layer of abstraction just because a problem might arise in the future vs reducing the number of abstractions and waiting for it to become a problem before adding more abstractions. I don't think we do the latter enough. Often times you can get away with slightly less abstractions than you think you need because you will never touch the code again.

[–] queerlilhayseed@piefed.blahaj.zone 8 points 1 week ago* (last edited 1 week ago)

I think the design of interfaces is a difficult and subtle art. You have to have a very refined understanding of both of the layers being interfaced, so you can understand where the boundary should go and what shape it should have so concepts don't get split across layers. You also need to have a keen understanding of how the humans using the interface will behave in the future, which is really hard and often impossible. I think that's why interfaces tend to evolve over time along with the tech, because assumptions built into them were either incorrect, or became incorrect (or just confusing) as the technical landscape shifts around them.

Speaking of shifting landscapes, I think one of the fundamental practices of engineering is prototyping: building a thing that does what you think you want, even if it's janky or unscalable or has an insane cyclomatic complexity or w/e. Sometimes building the janky version can lead to insights into how an improved version can be made; insights that would be very difficult or impossible to predict if one tried to build the perfect version on the first go.

This causes some problems in corporate development, because the chance to learn from a model and iterate on it directly is so rare. The vast majority of the time (IME), as soon as the janky version fulfills the client's list, it moves into production and the improvements are, if not written off entirely, put on the backlog of tasks that will never be more important than building out the next new thing. It's still possible to iterate ideas in future new projects, it happens all the time, but it's different than building one thing and refining it in an iterative development cycle over a long term.

load more comments (16 replies)
[–] TheGiantKorean@lemmy.today 23 points 1 week ago (3 children)

Man. I so feel this. I'm 51 and started programming when I was 10. It's not anything like it used to be. I miss those days.

[–] sping 31 points 1 week ago (4 children)

It's so much better! Tooling is many orders of magnitude better and so many libraries give you deep power from an easy API. What used to be a team and 18 months is a library install and a day so you're free to do much bigger things.

Christ even version control. The shit I put up with over the years.

load more comments (4 replies)

You can still program in those platforms, if you want to.

load more comments (1 replies)
[–] ieGod@lemmy.zip 19 points 1 week ago* (last edited 1 week ago)

I feel like a lot of concepts are being conflated.

Plug and Play arrived. Windows abstracted everything. The Wild West closed. Computers stopped being fascinating, cantankerous machines that demanded respect and understanding, and became appliances. The craft became invisible.

I disagree with this. The craft is still alive and well, it's just specialized. As complexities in approaches grow, it's not possible for a single person to know every register of every subunit all the way up to high level application software in any reasonable manner. You can totally write your own bootloader for your current hardware. Nothing is stopping you. Is the argument that the financial utility is lowered? Is it that he chose voluntarily to focus on application layer development?

This is like someone who built their own bicycle lamenting they can't do the same for a modern EV.

[–] fubarx@lemmy.world 15 points 1 week ago* (last edited 1 week ago) (3 children)

Wasn't "lo-code" a BIG thing a few years ago... that would destroy programming and make every PM a developer? Whatever happened to that? 🤔

Edit: read the HN comments. If I ever go back to consulting, I'm 10x-ing my rate to work on cleaning up this slop. I'm not anti-AI coding and use it for my own projects, but if you just give it a prompt and walk away, you will be very sad later.

There's a BIG difference between prototypes and something others have to use. As the lo-code folks found out the hard way.

[–] wer2@lemmy.zip 5 points 1 week ago
  1. Programming language invented: Everyone can code now! Programming is dead!
  2. Cobol invented: Everyone can code now! Programming is dead!
  3. BASIC invented: Everyone can code now! Programming is dead!
  4. UML to Code/Executable UML: Everyone can code now! Programming is dead!
  5. Low code: Everyone can code now! Programming is dead!
  6. AI: Everyone can code now! Programming is dead!

Yep, any day now...

load more comments (2 replies)
[–] Feyd@programming.dev 14 points 1 week ago (1 children)

I say that knowing how often those words have been wrong throughout history.

Yup

Previous technology shifts were “learn the new thing, apply existing skills.” AI isn’t that. It’s not a new platform or a new language or a new paradigm. It’s a shift in what it means to be good at this.

A swing and a miss

[–] OpenStars@piefed.social 8 points 1 week ago

Technically it would have been true, it's just that A"I" does not deliver on that promise.

[–] groucho 14 points 1 week ago (2 children)

I wonder what the venn diagram of people that started coding as kids and people that enjoy vibe coding looks like. Informally, the degens on my squad that started on their parents' computer loathe AI, and the people that stumbled into it in college are all about the vibe code.

[–] zod000@lemmy.dbzer0.com 4 points 1 week ago

Probably two distinct circles that don't touch if I base it on people I know and myself.

load more comments (1 replies)
[–] entwine@programming.dev 10 points 1 week ago

I had a realization recently. All the pro-AI people pushing vibe coding or "coding assistants" are completely missing the point.

These tools aren't helping you write code, you are helping the tool write code, because it can't do it on its own yet. The more they improve, the less you're needed.

Idk if they'll ever reach the point where you can actually give it a prompt, and it'll provide a fully functional implementation on its own with no human intervention required. If it does, I can't imagine that tech would be as available as it is now. Your peasant ass isn't going to be vibing the next big thing that's for sure.

[–] NostraDavid@programming.dev 7 points 1 week ago (2 children)

Creative constraints bred creativity.

That might explain why there's so much crap coming out of the gaming industry. All the old constraints are gone, so everything now very much looks the same.

Just give yourself artificial constraints.

[–] Skullgrid@lemmy.world 8 points 1 week ago

That might explain why there’s so much crap coming out of the gaming industry.

not really, it's more of an economic situation instead of a tech one. Indie games are doing just fine, more or less (the choose 1 of 3 fad is a pain).

load more comments (1 replies)
[–] sobchak@programming.dev 7 points 1 week ago

Just don't use AI coding tools then? Studies show they make people less productive anyways.

[–] ICastFist@programming.dev 5 points 1 week ago

They’re writing TypeScript that compiles to JavaScript that runs in a V8 engine written in C++ that’s making system calls to an OS kernel that’s scheduling threads across cores they’ve never thought about, hitting RAM through a memory controller with caching layers they couldn’t diagram, all while npm pulls in 400 packages they’ve never read a line of.

Yeah, I noticed something was off around the time every new app was essentially "the fucking website on a self contained chrome browser", aka electron. Sure, it was sold off as being a "write once, run everywhere", but a significant number of said programs and games were still either windows or android exclusive because ha ha fuck you (anyone that's dealt with RPM MV/MZ knows it).

Some layers of abstraction are incredibly welcome - not having to worry about cycles and RAM addressing, having immediate access to graphics without having to reinvent pixel pushing function; but (imo) everything on top of a browser is just an endless series of "why?"

[–] bridgeenjoyer@sh.itjust.works 5 points 1 week ago (3 children)

I wish i could have started then! I'm not really interested in modern coding, it doesn't seem as interesting...I kind of want to read the whole c64 manual and try programming on it, but I guess there isn't much point to that nowadays

[–] Valmond@lemmy.dbzer0.com 11 points 1 week ago

Of course there is, it is fun!

What else do you think the "point" of living is?

[–] lurker2718@lemmings.world 5 points 1 week ago

You could also try microcontroller programming. There you have control over everything and i guess it should be similiar to programming in early days. I started around ten years ago with Arduino and also directly programming them and it still interests me. And with a little hardware you could do some interesting projects. I would even say it could be relevant for career if you want that.

load more comments (1 replies)
[–] jimmy90@lemmy.world 4 points 1 week ago (1 children)

high level code generating tools have come and mostly gone

we will see if this one is good if it works and we can maintain the code it makes

simple

[–] Skullgrid@lemmy.world 5 points 1 week ago* (last edited 1 week ago)

high level code generating tools have come and mostly gone

he's talking about languages that don't touch bare metal, not WYSIWYG editors

EDIT: WYSIWYG stuff continues to live , fucking salesforce

[–] talkingpumpkin@lemmy.world 4 points 1 week ago (3 children)

This isn’t a rant about AI.

I feared thus would be about AI, but... this might actually be interesting! I'm glad I started reading.

This time is different [...] Previous technology shifts were “learn the new thing, apply existing skills.” AI isn’t that.

Well f*ck you and give me back the time I wasted on that article.

Guys, can we add a rule that all posts that deal with using LLM bots to code must be marked? I am sick of this topic.

load more comments (3 replies)
load more comments
view more: next ›