Many users agreed with Paul Graham that programming already relied on unread external dependencies, while others criticized the trend as already harmful and enabling shallower AI-assisted development.
Based on 28 visible X reactions from 321 accounts; directional sample.
Ask a question below.
Published answers will appear here.
@paulg No, it was decentralized collaboration. Other people read the code and we reached organic consensus. If you followed this absolute slop canon of a retard, I hope this was a wake up call. If he writes this tweet, it's a guarantee he will make you dumber.
via X@paulg Before designing ArchiveOS (project name FACTool), in April 2023 I proto-vibe coded a "skeleton" for an archives system. That was the AI unlock for me. I'm reverse engineering myself into becoming an engineer. It's so freaking awesome!
via X@paulg Installing something is not the same as implementing the vibe of it Vibe coding is amazing and is not possible without llms
via X@paulg You're absolutely correct & raise a valid substantial point.
via XThe 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
via XIt'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.
via XBefore 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.
via XStuff was already going to hell before the invention of the hellmobile-9000
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.
@paulg Installing something is not the same as implementing the vibe of it Vibe coding is amazing and is not possible without llms
via X@paulg You're absolutely correct & raise a valid substantial point.
via XThe 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
via XIt'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.
via XBefore 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.
via XStuff was already going to hell before the invention of the hellmobile-9000
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 with Paul Graham that programming already relied on unread external dependencies, while others criticized the trend as already harmful and enabling shallower AI-assisted development.
Based on 28 visible X reactions from 321 accounts; directional sample.
Ask a question below.
Published answers will appear here.