Christine Lemmer-WebberMar 3
hm https://github.com/bluesky-social/social-app/blob/main/CLAUDE.md
social-app/CLAUDE.md at main · bluesky-social/social-app

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

GitHub
Show threadChristine Lemmer-WebberMar 3
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
Show threadBenderIsGreat34Mar 3
@cwebber @kkarhan The most disappointing thing about AI (in the software development space) is how quickly and gleefully so-called senior engineers abandoned their craft for vibe coding.
Show threadThe Blue WizardMar 4

@andymoose @cwebber @kkarhan Disclaimer: I never use any LLM stuff, so I may be off base here.

I have a thought about that!

Imagine a scenario: Thanks to the layoff of developers thanks *dry tone* to the "insanely great" promise of LLM, there is now a lone developer vibecoding the main application for the company. Let's say he is doing well. But remember that he must feed a series of prompts, refining and growing the application as he progresses. Then he got a new job and left the company.

->

Show threadThe Blue WizardMar 4

@andymoose @cwebber @kkarhan The company then got a problem: Even after hiring a new developer (or two...who knows?), they can't figure out how the code work (no real documents) and, worse, the prompts the original developer wrote is not kept. IOW there is no "source code", so to speak. Disaster eventually strikes the company as a result.

Ain't that wonderful, huh? *sarcastic tone*

Multiply that by ten thousands of this scenario across various companies and we got a real economic crisis!

END

Show threadWulfy—Speaker to the machinesMar 4

@andymoose @cwebber @kkarhan @thebluewizard

So yeah, that's what happens when you suck at vibecode

1. Write a basic .MD file

2. Part of the MD file is writing every delta into
a ./DOCS and ./BACKUPS

Not only you have every .release you can roll back in source code, but you have every delta in DOCS

The folks who sucked at being a "real" programmer suck at #vibecode

P. S. You don't read source code when you vibecode.
Folks who "WAAAH BUT SAUCE KODE" never vibecoded.

"Using AI is a learned skill"

Show threadKevin Karhan 
@n_dimension @andymoose @cwebber @thebluewizard Granted, "#VibeCoding" is just a different term to "bossing around #AI until it does 50% what it should do and calling that a success when a #Skiddie copypasting shit would've done a better job even when half the amount wasted on *"#AI" Tokens...
Mar 4 at 2:55amWeb
Show threadWulfy—Speaker to the machinesMar 4

@andymoose @cwebber @thebluewizard @kkarhan

"Bossing AI around" is actually a very good description of #vibecoding

I call it "Hitting the machine with a stick" (like a recalcitant) mule.

However, the accuracy is significantly better than 50%

Granted, #Ai will get into the weeds sometimes.

But because I was a shit programmer before Ai (slow and dim) Vibecoding makes me better.
There were times I would get stuck on a bug for a day, with Ai, I can mush it in 15 min max.

In my experience, majority of errors are regex or basic syntax, my Webby got carded last night because the Ai commented out whole anti-carding logic by accident, even though I got it to check it twice.

Each fuckup makes you write better prompts.

Show threadKevin Karhan Mar 4

@n_dimension @andymoose @cwebber @thebluewizard I still think it's #WastefulComputing and doesn't really help oneself to become better at coding.

  • Or not even better at reviewing and testing.
  • At best it'll make one better at documenting requirements.
    • Basically doing a shitty way to learn "Requirements Engineering"...