In other word your code is probably terrible and you force bad behaviors on other?I'm too much of a perfectionist. I'd start rewriting people's code. And if someone rewrote mine a fist-fight would ensue.
TLP ?Come play TLP. Forget this compsci shit -- it's vastly overrated and boring.
You are expecting a group of introverts to work at high capacity for large amount of time?I could see the benefit of it in a larger shop in order to onboard someone to their practices. I can also see the efficacy of doing it to reduce overhead, especially when it comes to code review and code merging. Cannot tell you how many times a bullshit delay could have been avoided at my last place with something like this in place.
What I can't see is how it's feasible long term unless you have firm rules in place on "driver" rotation. Otherwise you're paying people to sit around and watch someone else work.
Honestly, I would use it for training. Put the new person in the hot seat and start telling them what to do, and it would be an interesting way to force them to learn techniques from the whole team and hopefully they'd be smart enough to ask a lot of questions about what people are getting them to do.Sounds dumb as shit. I'd rather just put two devs next to each other with their own comps.
I know exactly what you mean. Or someone doesn't understand anything going on so they resort to large-scale ideas that don't require thought. Or someone has pet ideas or major disagreements with the direction so they propose something wildly different.We just use Crucible and Fisheye for code reviews. You get solid knowledge transfer using these tools and it doesn't force you to sit next to someone and look over their shoulder while you pair program. The only problem is with some people they like to try and flex their big nuts and over not really useful information in the code review just "Well I'd do it this way" and shit without actually addressing the code under review.
And no performance gain was made in the reduction to two and now there is massive confusion as to what is done in the 2 linesFuckin idiot used 31 lines and I did it in 2
Well aware actually.Growth is when you realize that the next guy who looks at your code is going to say the exact same thing.
People who ask incessant questions, you have to teach them not to come to you. Never answer their question. Give them the slightest bit of info and tell them where to go look to find the answer. Them coming to you will just create more work for them so they'll stop.I have mentored junior guys for the past 5 years now, and i have zero problem with it.
The problem is that this guys is supposed to be at the same level as me, andhe cant even merge his own code... and on top of that, well just read the thread for my history with him.
The other option is that he is just pretending to be dumb just so I do more work... (this is my wives theory). I'm about to tell him, before you call me over, at least google the problem.
If he sends an email just email him back with links to StackOverflow and Google. Give him an appropriate amount of time to figure it out, based on how fast you think the problem can be solved versus how long you think it might take him to solve, then head over and ask what he learned. Make sure to CC your boss and bring him over when you to go ask as well. If he's as bad as you make him out to be, then he'll have done next to nothing. A few times like that and a trip to the front door with all his belongings might be in the works.People who ask incessant questions, you have to teach them not to come to you. Never answer their question. Give them the slightest bit of info and tell them where to go look to find the answer. Them coming to you will just create more work for them so they'll stop.