Not git, Perforce, but I used to have a guy on my team that would do weeks of work without checking in. 1000s of lines in 10s of files.
I gave him shit for every code review, every time we had 1-on-1s, and while he was doing his tasks. Nothing got through to him.
So I just kept dragging him back on check-ins. I'd nitpick the shit out of every line (and normally I hated that.) His stuff would inevitably break the build or be full of bugs anyway (duh) so I never felt bad that I was holding back his career since he was never getting things done "on time."
If you can't/won't break your work down into smaller chunks you aren't a skilled programmer and/or don't have respect for the people you work with who have to review your shit.
“People say ‘Well, this could be just a short-term thing,’ and maybe it is, but it also could be a long-term, structural thing,” he said.
This is ultimately my hope with all of this. We increase trade and connections with everyone else in the world and they all do as well. As it backfires(?) and brings down the US hegemony, Canada needs to be prepared to leave big brother behind and move on with our cousins and siblings from another mother.
I think some drone factories might be in good order for Canada, too.
Yeah. I'm ignoring the strawman part of the argument that the people calling wolf for the past 80 years were always lying, since it doesn't affect red shirt's wrongness.
No, he's still wrong. Even if he has been conditioned to ignore the term because of overuse of the term, he's still wrong.
The people who ignored the boy the third time he cried wolf were wrong. The proof they were wrong is that they lost their sheep. The moral of the story isn't "don't listen when little boys cry wolf three times and the first two times turn out to be false." The moral is "don't cry wolf when there is no wolf or people will stop listening to you."
So you can argue that the people who conditioned red shirt not too look were wrong, i.e. "the boy who cried Nazi", but in this case red shirt is most definitely wrong.
They're right though, Pepsi is not god damn "okay". Pepsi is great.
(though I'll drink any of my top 5 interchangeably, except for the sugar, and I only have any of them as a treat now after years of drinking way too much.)
Operator: Hotline.Andy: Hi, yes, I'm calling because it's more than four hours and your ad said to call if it's been more than four hours.Operator: How much of the medicine have you taken, sir?Andy: I haven't taken any, but your ad said that if you've had an erection for more than four hours, you call.Operator: You're only supposed to call if you've taken the medicine.Andy: Okay. I'm sorry. I must not have heard that part.Operator: Yes. If you haven't taken the medicine, you don't call.Andy: Right. I'm sorry. Right. So, there's nothing you can do? I just don't wanna--Operator: There's nothing I can do. I'm in Bombay, India.Andy: Okay. No, not you personally. I just don't want--I just don't want to have an erection anymore.Operator: You know, you could have sex.Andy: Okay. Yup.Operator: That's one thing people do when they have an erection.Andy: Yeah, that's not an option. I don't have sex.Operator: Okay, well, then you can masturbate.Andy: I'd rather not masturbate.Operator: If you'd like the erection to go away, you can light a match, blow out the flame and put the hot ember on your wrist. And that will focus the brain elsewhere, and you will lose your erection.Andy: Really? That'd work?Operator: Take your finger and flick your testicle, and if you do that till it hurts, your erection will go away.Andy: Okay, all right. It sounds unpleasant and it is.Operator: It is a trick we use in India.Andy: Okay, those are all good pieces of advice. I really appreciate it.Operator: We appreciate your business--oh, no. We didn't get your business!Andy: No, not this time. I guess I didn't need you this time. Thank you.
Not git, Perforce, but I used to have a guy on my team that would do weeks of work without checking in. 1000s of lines in 10s of files.
I gave him shit for every code review, every time we had 1-on-1s, and while he was doing his tasks. Nothing got through to him.
So I just kept dragging him back on check-ins. I'd nitpick the shit out of every line (and normally I hated that.) His stuff would inevitably break the build or be full of bugs anyway (duh) so I never felt bad that I was holding back his career since he was never getting things done "on time."
If you can't/won't break your work down into smaller chunks you aren't a skilled programmer and/or don't have respect for the people you work with who have to review your shit.