I mean when I check my feed much of the Bluesky eng team seems to be posting about how great Claude is all the time so I have been background wondering how common vibecoding is in that ecosystem
@cwebber Earnest and also deeply befuddled question:
Do you happen to know if this "Why" is the same "Why" who wrote "Why's? (Poignant) Guide to Ruby"?
(Seems very unlikely to be the same person—but I'm so out of the loop that this name confusion also feels like when people are excitedly talking about the Swedish metal band "Ghost" but I mistakenly think they're excitedly talking about the Japanese experimental psych-folk band "Ghost".)
I have this suspicion that the ATproto stack, at least the stuff from Bluesky, is heading towards "majority-vibecoded" but that's mostly just from seeing a lot of posts from the Bluesky eng team rather than me having spent much time in the codebase
Why is def hugely responsible for Bluesky/ATProto's design and if *he's* mostly letting Claude write 99% of his code, the rest of the eng team is likely to be heading in that direction too?
@cwebber I'm hanging out there a lot and yes there is a lot of vibecoding. However, they don't seem to vibecode more than the average paid software dev.
In 2024, I'd say about 20% of my friends vibecoded. Today the number looks more like 90%. This is not specific to atproto, my understanding is that most people vibecode nowadays.
> Oh interesting, people who don’t know how to build software are getting mad at my post about building software. Cute. > > Let me be clear, over the next year, the job of software engineer will shift dramatically to no longer have typing syntax into an editor as its primary time sink.
@cwebber also, I can see this type of situation very, very easily spiraling into a classic "death by convenience." How long until the primary engineers no longer understand the how their program is built or what motivated ostensibly insignificant decisions that eventually add up
@cwebber I'm really not a huge fan of how ready people seem to be to just completely relinquish their ability to code. It does not take long for your brain to wallpaper over entire skillsets.
You can guess my opinions, but I have left them out of this particular thread. My goal here was actually just to see if my gut sense was correct that Bluesky was heading in a vibecoding direction. I think that feels fairly confirmed based off the discourse I highlighted and also what seems to be an indirect response from Bluesky's team (though I think that's more because of what @davidgerard wrote about it than what I did)
Anyway, gnarly time, but people can decide for themselves whether that aligns with their values. One thing seems for sure: it's a bet many orgs are making, and this will be one thing where in the ~decentralized space we'll be learning much more about whether that bet pays off and results in a better or worse ecosystem over time.
It does seem like I kinda kicked off A Discourse but I mean, it feels like it's worthwhile for people to know whether or not the infrastructure they are relying on is increasingly vibecoded or not, at minimum, so they can make decisions for themselves.