I would be at the beck and call of several of those beasts
as a sysadmin, maybe that was why the guy asked me if I have ever felt stomped upon and whether I could hold my own. hmmm things to think about
Any opinions expressed by me are mine alone, posted from my home computer, on my own time as a free American and do not reflect the opinions of any person or company that I have had professional relations with in the past 55 years. meep
|
|
Now. Gimme those perms now!
I mean it. I'm trying to code here, I got a junior next to me who is supposed to be giving me help yet he's only distracting me. Those bastards said pair programming would be better. Fuckers.
|
|
Pair programming is fickle.
You need both programmers at a similar level of experience and ability, just with a somewhat different skillset. That's when it works the best and works amazingly well. It is when there is a noticeable difference in ability level that it doesn't work. (Been in both situations.)
Wade. Static Scribblings http://staticsan.blogspot.com/
|
|
Never had that dynamic
Time spent with equal or better coders was usually during the design / split out work phase, and then an occasional "Hey, you: I need another set of eyes".
Then project consolidation / hand off to the next guy as I went to the next project. Other than that, I usually had a well chosen junior who tagged along with everything I did, and supported my systems, but he knew to stay quiet when sitting near me while coding. |
|
What I figured a good dev can do.
And that is ask questions. And a good senior dev knows how to ask the right question when he has to try a thorny problem in someone else's head. :-) (Which is the "I need a second set of eyes" scenario.)
Good pair programming simply makes this happen a thousand times quicker. Wade. Static Scribblings http://staticsan.blogspot.com/
|