hm https://github.com/bluesky-social/social-app/blob/main/CLAUDE.md
-
@andymoose @cwebber @kkarhan it's like they didn't even like programming at all.
-
@andymoose @cwebber @kkarhan it's like they didn't even like programming at all.
@tootbrute @andymoose @cwebber at least the white #Neurotypical heterocisbinary men are...
- You know, the #McAfee - kind that only do #IT because they 'failed to the top'.
- Like a shitty parody of "Bighead" from #SiliconValley...
- You know, the #McAfee - kind that only do #IT because they 'failed to the top'.
-
@andymoose @cwebber @kkarhan I have an entire graveyard of people who are dead to me now because of this. It's unfortunate. I've lost so much respect for so many people.
-
@res260 Sadly a likely observation
![😕](https://board.circlewithadot.net/assets/plugins/nodebb-plugin-emoji/emoji/android/1f615.png?v=28325c671da ":\")
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 -
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@cwebber Ah yes, LLMs are finally good now, this is probably the fourth or fifth time I've heard it and at this point it's like the boy who cried wolf, I'm not even going to bother testing out the LLMs of today to see what they get wrong, I'm just not going to believe their advocates
-
@andymoose it’s like everyone who has ever been a source of my feelings of imposter syndrome literally decided to let an imposter take the wheel
-
@andymoose @cwebber @kkarhan I have an entire graveyard of people who are dead to me now because of this. It's unfortunate. I've lost so much respect for so many people.
@theorangetheme @andymoose @cwebber I ditched enough way before that...
https://infosec.space/@kkarhan/116168104713958627 -
@theorangetheme @andymoose @cwebber I ditched enough way before that...
https://infosec.space/@kkarhan/116168104713958627@theorangetheme @andymoose @cwebber be glad you don't work for some "#AI" shill who literally thinks 'genociding the world is good, actually'...
-
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
are you fucking kidding? holeee shit
-
@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?
