hm https://github.com/bluesky-social/social-app/blob/main/CLAUDE.md
-
@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 @cwebber I agree, I think a lot of people don't consider their code craft, but maybe the final product more so
-
@erincandescent @cwebber I agree, I think a lot of people don't consider their code craft, but maybe the final product more so
-
@cwebber I found LLM generated code in vim today
-
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 based on how well bsky tends to work i feel like this is likely
-
@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.
->
-
@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.
->
@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
-
@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
@thebluewizard @andymoose @cwebber And it's in our best interest for that to happen sooner than later so the fallout for everyone else is kept minimal...
-
@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
@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 ./BACKUPSNot 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"
-
@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
@thebluewizard @andymoose @cwebber @kkarhan And even if they had the prompts, that's no guarantee that the LLM will produce the same output if fed those prompts again. All they could depend on is the raw source code the original dev had generated, no matter how incomprehensible it is.
The sad part is the company won't blame LLMs for the situation, they'll blame the new devs for not being able to make things work.
-
@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 ./BACKUPSNot 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"
@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...
-
@thebluewizard @andymoose @cwebber @kkarhan And even if they had the prompts, that's no guarantee that the LLM will produce the same output if fed those prompts again. All they could depend on is the raw source code the original dev had generated, no matter how incomprehensible it is.
The sad part is the company won't blame LLMs for the situation, they'll blame the new devs for not being able to make things work.
@tknarr @thebluewizard @andymoose @cwebber exactly that!
Cuz I've seen that shit even with "traditional IT".
- Ever had to "unfuck" a #ZFS on top of a Hardware-#RAID controller?
- If you know, you propably already run to the toilet to throw up, because one should not violate THE ONE RULE OF USING ZFS...
- Ever had to "unfuck" a #ZFS on top of a Hardware-#RAID controller?
-
@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...
@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.
-
@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.
@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"...
-
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
Bit of a tangent, but a few months ago, when tech nerds on bsky and fedi started talking about Framework being a milkshake duck, Bsky staff immediately started bragging how cool and fast and powerful their Frameworks are. -
@erincandescent @cwebber I agree, I think a lot of people don't consider their code craft, but maybe the final product more so
@res260 @erincandescent @cwebber if you care about the final product, surely you should care about how it’s made?
I see so many apologists for LLM usage recently trying to distinguish between the outcome and the process, as if the quality of the outcome isn’t defined by the process.
-
@res260 @erincandescent @cwebber if you care about the final product, surely you should care about how it’s made?
I see so many apologists for LLM usage recently trying to distinguish between the outcome and the process, as if the quality of the outcome isn’t defined by the process.
@benjamineskola @res260 @cwebber is this an argument of quality or of morals?
Because morals.. people can have different views on. But quality is very much about the end result -
@benjamineskola @res260 @cwebber is this an argument of quality or of morals?
Because morals.. people can have different views on. But quality is very much about the end result@erincandescent@akko.erincandescent.net @benjamineskola@hachyderm.io @res260@infosec.exchange @cwebber@social.coop If the thing isn't "make once and forget" the process is very much part of quality, because it decides if the thing is maintainable.
-
@erincandescent@akko.erincandescent.net @benjamineskola@hachyderm.io @res260@infosec.exchange @cwebber@social.coop If the thing isn't "make once and forget" the process is very much part of quality, because it decides if the thing is maintainable.
@airtower @res260 @benjamineskola @cwebber two projects with identical code are, modulo institutional knowledge, equally maintainable; would you disagree? -
@airtower @res260 @benjamineskola @cwebber two projects with identical code are, modulo institutional knowledge, equally maintainable; would you disagree?
@erincandescent @res260 @cwebber @airtower
'modulo institutional knowledge' is doing a lot of heavy lifting there since that's half the problem with LLM usage
and the other half of the problem is the assumption that an LLM will produce identical code
so I don't think there's a useful discussion to be had if those are your assumptions
-
@erincandescent @ryanrandall @cwebber its not the same Why. They both have photos of their real face on the internet I checked.
@liaizon @erincandescent @ryanrandall @cwebber this is the one from the mirror universe
