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

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?

Also https://bsky.app/profile/pfrazee.com/post/3meogr22l3k2d

> A year ago, I thought LLMs were kind of neat but not that useful. I saw the code autocomplete and thought, meh.
>
>Last summer just flipped. I never ever thought I would see automated code generation like we see now.
>
> I know there’s baggage but you need to know the coders are being real about this

Welp, there we go https://bsky.app/profile/why.bsky.team/post/3mgaqaaisfs2e

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

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.

@cwebber ai usage has been normalised in most of the atproto dev ecosystem for a while now. just as some recent other examples,

tangled's seed round also explicitly mentions ai agents for coding as a use case (https://blog.tangled.org/seed) , and semble also targets ai agents as a use case (https://blog.cosmik.network/updates-february-2026)