Same goes for prototyping. I don't see much of a correlation between willingness to prototype and seniority, either.
Same goes for prototyping. I don't see much of a correlation between willingness to prototype and seniority, either.
Railing against code coverage is at this point just as dogma as insisting on it.
What I'm railing against is the idea that seniority is a prime indicator to the effective strategy parent comment insists on, which simply doesn't mirror my experiences. What I see is juniors picking up the habits of their superiors. They're learning this dogmatism from somewhere.
Willingness is one thing, but getting yelled at for learning and doing your best is another. I never treat my Juniors like that, and encourage a 75/25 working/improving split. Still, several frequently get anxiety about how long it's taking them to clear tickets.