4 ms·
What about cross-discipline? What if a problem comes up that would be better solved with technology Y instead of X and you are an X master but random intern hap
by xigency 9y ago
What about cross-discipline? What if a problem comes up that would be better solved with technology Y instead of X and you are an X master but random intern happens to know Y. Are you still the fastest? What if the intern is better at making slides for code reviews that show important trends? Or they can write fantastic documentation? Or tools?
I'm sure you're a quick learner but at least in scenarios I've worked in there are often many, many possible solutions and no specific "right answer."
After all, it's hard for anyone to be right all of the time.
- g051051 9y agoNone of that has anything to do with the original blanket assertion of "good junior devs can code not only "just as fast", but probably faster too!".
- xigency 9y agoAye, but you probably can't code faster if you have to read a manual first? It is easy to construct scenarios where someone from a bootcamp could code "faster" than a principal, senior lead, or CTO of all things. It's just a matter of picking the problem. A better point is that this drought of new talent is just the other side of the pendulum. In the odd years, the problem is layoffs and difficulty finding work without being a new-grad or knowing the latest tech fad. You've seen some of those summers, too?
- g051051 9y ago> Aye, but you probably can't code faster if you have to read a manual first? If we both had to read the manual? Yeah, I'd still be faster. It's just as easy to cherry-pick for one side or another.
- virgilp 9y agoThe general point he makes is that "if I define what speed means, I always code faster", so yeah, he's right. Sort of :)