destructdisc@lemmy.world to Fuck AI@lemmy.world · 2 days agoYou see "14 year old developer" and you're impressed until you read on and realize the little fucker is just paying Claude to slopcode the entire thing for himlemmy.worldimagemessage-square172linkfedilinkarrow-up11arrow-down10file-text
arrow-up11arrow-down1imageYou see "14 year old developer" and you're impressed until you read on and realize the little fucker is just paying Claude to slopcode the entire thing for himlemmy.worlddestructdisc@lemmy.world to Fuck AI@lemmy.world · 2 days agomessage-square172linkfedilinkfile-text
minus-squareReygle@lemmy.worldlinkfedilinkarrow-up0·2 days agoI hate to be “that guy” but who/what do you think is writing Windows updates
minus-squareFoxAlive@lemmy.ziplinkfedilinkarrow-up0·2 days agoA 14 year old kid with 9000 dollars and a Claude subscription?
minus-squareFoxAlive@lemmy.ziplinkfedilinkarrow-up0·1 day agoVisually the gag of the 13 layers of leadership at microsoft all watching over one kid vibe coding all their services is pretty funny.
minus-squareTigeroovy@lemmy.calinkfedilinkEnglisharrow-up0·2 days agoI mean I assume that’s what’s happening and why it all fucking sucks.
minus-squareReygle@lemmy.worldlinkfedilinkarrow-up0·2 days agoThey pushed an update yesterday that makes applications hang when users try to print. If your machine shits the bed whenever you try to print, remove KB5132061 and reboot. This has to be the worst timeline. If it isn’t I don’t want to see what is.
minus-squaresnugglesthefalse@sh.itjust.workslinkfedilinkarrow-up0·2 days agoNot regretting deleting windows earlier in the year…
I hate to be “that guy” but who/what do you think is writing Windows updates
A 14 year old kid with 9000 dollars and a Claude subscription?
Pretty much.
Visually the gag of the 13 layers of leadership at microsoft all watching over one kid vibe coding all their services is pretty funny.
I mean I assume that’s what’s happening and why it all fucking sucks.
They pushed an update yesterday that makes applications hang when users try to print. If your machine shits the bed whenever you try to print, remove KB5132061 and reboot.
This has to be the worst timeline. If it isn’t I don’t want to see what is.
Not regretting deleting windows earlier in the year…