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
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.
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.
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.
fuck you
“I just want to be a cog in the machiiiiiiine why are you bringing up these things that make me think?! ew ethics and integrity are so hard”
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. on topic of which, this excellent post
So you don’t do code review? Something that’s pretty much industry standard?
What on earth do you work on where it’s inconsequential to trust someone new to the industry blindly?
If I could trust someone anything remotely close to “blindly”, they absolutely would not have been hired as a junior.
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
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
projection belongs in cinemas and SFPs, don’t go casting your misunderstandings onto me
Okay, I’m going to have to borrow this. Also, nice handle.
The comments are all there if you want to read again and point out how that’s not true.
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
I, for one, am not in the industry and can’t figure out why people are coming at you with guns blazing. 🙄
it’s because he has shit for brains