social-app/CLAUDE.md at main · bluesky-social/social-app

The Bluesky Social application for Web, iOS, and Android - bluesky-social/social-app

GitHub
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
Let's see if anyone on Bluesky / the ATmosphere can say more https://bsky.app/profile/dustyweb.bsky.social/post/3mg6qipl6a22o
Christine Lemmer-Webber (@dustyweb.bsky.social)

Curious if vibecoding / AI agent assisted dev is currently common in ATmosphere dev? The feelings about AI generated code are def different on here than on fedi, so... I see a CLAUDE.md in bluesky-social/social-app https://github.com/bluesky-social/social-app/blob/main/CLAUDE.md

Bluesky Social

Example: https://bsky.app/profile/why.bsky.team/post/3meomclcfss2w

> Until December of last year I was using LLMs as fancy autocomplete for coding. It was nice for scaffolding out boilerplate, or giving me a gut check on some things, or banging out some boring routine stuff.
>
> In the past two months Claude has written about 99% of my code. Things are changing. Fast

Why (@why.bsky.team)

Until December of last year I was using LLMs as fancy autocomplete for coding. It was nice for scaffolding out boilerplate, or giving me a gut check on some things, or banging out some boring routine stuff. In the past two months Claude has written about 99% of my code. Things are changing. Fast

Bluesky Social

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 much of 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.

@res260 Sadly a likely observation :\

So many people just giving up on their craft.

@cwebber @res260 I feel like there's always been a lot of software development that isn't craft but it's just shuffling bits around.

I don't really know how to feel about a lot of it these days. I've played around with some of the tools for work and there's certainly a lot of areas where they can write basically the same code that I would have done with less tedium, and by some metrics they do a better job (mostly things that are good practice but I couldn't be bothered).

Is that abandoning craft or careful allocation of executive function? I don't know.

I definitely think these things aren't going away. The bubble will pop, it'll maybe kill the big AI companies, people will stop shoving chat bots everywhere, but I don't see any way that LLMs don't remain a fact of life, and I don't know what the long term implications are of this
@erincandescent @res260 @cwebber I am no fan of tedium for tedium's sake... but why specifically slop machines, which are notoriously unreliable, to solve this problem, aside from all the money that got poured into this technology? Could the same money have been used to develop languages and frameworks with sensible defaults and configurations, thereby eliminating (or vastly reducing) the need for tedium?

@sitcom_nemesis @res260 @cwebber I think there’s a spectrum

There’s code we keep repeating in broadly the exact same structure, just with different details fileld in. That’s boilerplate.

There’s code that’s unique and creative and requires thought. That’s “the meat of the problem”.

But there’s lots of stuff in the middle where it’s not quite creative, doesn’t really require thought, but either because of domain requirements, accidents of history, or just because you’re gluing two libraries together that hadn’t ever seen each other, is too irregular to really code generate but is not actually interesting.