yep. on topic of which, this excellent post
froztbyte
yw
these arseslugs are so fucking tedious, and for almost 2 decades they've been dragging everything and everyone around them down to their level instead of finding some spine and getting better
I’m sorry, do you trust junior engineers blindly?
as a starting position, fucking YES. you know why I hired that person? because I believe they can do the job and grow in it. you know what happens if they make a mistake? I give them all the goddamn backup they need to handle it and grow.
"this is why code review is so important" jfc. you're one of those "I've worked here for 4 years and I'm a senior" types, aren't you
and the engineers I know who are still avoiding it work noticeably slower
yep yep! as we all know, velocity is all that matters! crank that handle, produce those features! the factory must flow!!
and you fucking know what? it's not even just me being a snide motherfucker, this rant is literally fucking supported by data:
The survey found that 75.9% of respondents (of roughly 3,000* people surveyed) are relying on AI for at least part of their job responsibilities, with code writing, summarizing information, code explanation, code optimization, and documentation taking the top five types of tasks that rely on AI assistance. Furthermore, 75% of respondents reported productivity gains from using AI.
...
As we just discussed in the above findings, roughly 75% of people report using AI as part of their jobs and report that AI makes them more productive.
And yet, in this same survey we get these findings:
if AI adoption increases by 25%, time spent doing valuable work is estimated to decrease 2.6% if AI adoption increases by 25%, estimated throughput delivery is expected to decrease by 1.5% if AI adoption increases by 25%, estimated delivery stability is expected to decrease by 7.2%
and that's a report sponsored and managed right from the fucking lying cloud company, no less. a report they sponsor, run, manage, and publish is openly admitting this shit. that is how much this shit doesn't fucking work the way you sell it to be doing.
but no, we should trust your driveby bullshit. motherfucker.
"despite the many people who have shown time and time and time again that it definitely does not do fine detail well and will often present shit that just 10000% was not in the source material, I still believe that it is right all the time and gives me perfectly clean code. it is them, not I, that are the rubes"
probably Hary Pawter
because otherwise they'll have to admit how much ~~copyrighted material they've stolen~~ "fair use they're employing"
I’m a senior software engineer
ah, a señor software engineer. excusé-moi monsoir, let me back up and try once more to respect your opinion
uh, wait:
but I can’t trust a junior engineer to be perfect either
whoops no, sorry, can't do it.
jesus fuck I hope the poor bastards that are under you find some other place real soon, you sound like a godawful leader
and the engineers I know who are still avoiding it work noticeably slower
yep yep! as we all know, velocity is all that matters! crank that handle, produce those features! the factory must flow!!
fucking christ almighty. step away from the keyboard. go become a logger instead. your opinions (and/or the shit you're saying) is a big part of everything that's wrong with industry.
I swear all those fuckers are like "I was 4 rooms over but just heard the word 'paprika' being screamed from someone over this way. time for you to hear all about my bowel issues, in detail! you wouldn't believe what happens if I smell onions", but at a conference as a lightning talk to the main hall
same here, works fine in Fx (133, aarch64)
the looting of the commons continues apace
I'm not too surprised by this happening (and I see the specter of the same thing approaching with salt (bought by vmware bought by broadcom...)), but god am I tired of how fucking effective the method is
gap's closer now
yep yep. no code review. no version control either. that’s weak shit only babies use. over here you deploy patches by live editing app memory in production, and you update the codebase by editing the central repo using vscode remote. everyone has access to it because monorepos are what google do and so do we.
you have a 100% correct comprehension takeaway of what I said, well done!
jfc no wonder you’re fine with LLMs