Sam Altman is one of the dullest, most incurious and least creative people to walk this earth. This is, after all, the person who once tweeted 'i am a stochastic parrot and so are u', in response to Emily Bender's (entirely incisive and absolutely brilliant) critique of what his large language model...
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.
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.
This is a pretty funny interaction when you realise that you just misread the froztbyte's self-reply (and the survey) as pro-AI, so you were just aggressively agreeing with each other all along
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
word. When I hear someone say "I'm a SW developer and LLM xy helps me in my work" I always have to stop myself from being socially unacceptably open about my thoughts on their skillset.
and that’s the pernicious bit: it’s not just their skillset, it also goes right to their fucking respect for their team. “I don’t care about just barfing some shit into the codebase, and I don’t think my team will mind either!”
let me back up and try once more to respect your opinion
The point of me saying that was to imply I've been in the industry for a couple of decades, and have a good amount of experience from before all this. It wasn't any kind of appeal to authority, but I can see how you can read it that way.
jesus fuck I hope the poor bastards that under you find some other place real soon, you sound like a godawful leader
I'm sorry, do you trust junior engineers blindly? That's gonna lead to a much worse outcome than if they get feedback when they do something wrong. Frankly, I don't trust any engineer to be perfect, we're humans and humans make mistakes, that's why we do code review as a fundamental skill in this industry. It's one of the primary ways for people to develop their ability.
yep yep! as we all know, velocity is all that matters! crank that handle, produce those features! the factory must flow!!
In an industry where many companies are tightening the belt, yes it's important to perform well—I kinda want to keep my job and ideally get a good bonus. It would be pretty foolish to leave free productivity on the table when the alternative is working harder to bridge the gap, where I could spend that energy doing more productive stuff.
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
@froztbyte@9point6 There's a distinct difference between "I have twenty years of experience" and "I've had the same ten minutes of experience over and over again, over a twenty year period" 🤷
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!
Interesting you bring up reading comprehension because this whole thread started with me saying I would not trust a junior engineer to be perfect or trust them blindly.
You proceed to die on the hill that you would do that for some reason, despite now implying that you do, in fact, do code reviews—which we do because people can't be trusted to be perfect
someone who thinks "the buck stops here => nothing is true; all is permitted" probably won't get much out of "here are all the places ive found shit where neurons should be" so idk
Acting superior presses the dopamine button. Especially since the other poster keeps being mature and kind in their responses, really gets that feedback loop going.