Many users agreed that programming had already shifted toward managing unread dependencies before vibe coding emerged, because it accurately describes the pre-existing trend toward library-glue code.
Based on 14 visible X reactions from 218 accounts; directional sample.
Ask a question below.
Published answers will appear here.
@paulg We know. And that was already bad, heading in a bad direction. Many tried making that exact argument. Yet here we are.
@paulg Paul you just don’t get it. THAT was real programming, not this slop that is functionally the same but different from how I do it
@paulg Spot on! We basically transitioned from writing code to just managing dependencies.
@paulg You're absolutely correct & raise a valid substantial point.
@paulg We know. And that was already bad, heading in a bad direction. Many tried making that exact argument. Yet here we are.
@paulg Paul you just don’t get it. THAT was real programming, not this slop that is functionally the same but different from how I do it
@paulg agreed: AI naturally accelerates the library-glue trend.
@paulg Haha very true!
The scale & turnover of modern companies pushed this too. The person who wrote the code you are fixing left the company 5 years ago. Working in code you are familiar with is unusual for most engineers Very clear how few vibecoders have worked with interns. Every piece of code is untrusted lol
It's interesting in this case how well AI fits into existing trends. Programming wasn't evolving in this direction because AI was coming. No one knew it was. And yet we end up with what looks like a smooth acceleration along much the same path.
Before vibe coding became a thing, programming was already evolving in that direction. It already increasingly consisted of installing and configuring stuff other people wrote, without reading the source.
Many users agreed that programming had already shifted toward managing unread dependencies before vibe coding emerged, because it accurately describes the pre-existing trend toward library-glue code.
Based on 14 visible X reactions from 218 accounts; directional sample.
Ask a question below.
Published answers will appear here.
@paulg Haha very true!
The scale & turnover of modern companies pushed this too. The person who wrote the code you are fixing left the company 5 years ago. Working in code you are familiar with is unusual for most engineers Very clear how few vibecoders have worked with interns. Every piece of code is untrusted lol
It's interesting in this case how well AI fits into existing trends. Programming wasn't evolving in this direction because AI was coming. No one knew it was. And yet we end up with what looks like a smooth acceleration along much the same path.