Do all the things like ++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatarSign Up
Fast-Nop2197411dThat's the most moronic way to abuse a senior dev - instead of letting him lead a TEAM of juniors.
C0D44673111dForced pair programming is shit and never ends well.
Optional and by choice pair programming is where the magic lies after both devs have attempted it alone. Both devs are trying to solve a complex problem neither of them can do alone, and can bounce off each other to solve the problem at hand.
MagicSowap25011dI think you are wrong
The senior dev should struggle on his own for a while before the junior comes in and starts throwing new ideas ;)
RANTSMCPANTS19110dShut the fuck up. I always wanted to be reduced to nothing but one of my own testes. One of a pair. Pair programming is the only thing the gives me hope.
RANTSMCPANTS19110d@C0D4 Pair programming works great between junior and senior. So long as it's still maintained that the junior is the junior and the senior is the senior. Usually both gain more when the senior operators and the junior observes. Only about one in 20 should the senior watch what they are doing to achieve the gain.
Saw a talk online about this this
Novice, Armature, Professional, Expert
Novice + Armature = good
Professional + Expert = perfect
Expert + Novice = catastrophe
tirthaguha10The truth, whole truth, and nothing but there truth.
nachocode18If you had one language One framework To code everything you want Would you learn it or let it pass His cod...
CodeBlooded9Me: Sometimes I talk to myself while debugging. Me: OMG 😱, me too.. Me: Lets try pair programming next ti...