5 ms·
> identifying the bugs that junior developers have written Bugs are written by all seniority levels of engineers. “To err is human,” after all. Junior develope
by drewbug01 7y ago
> identifying the bugs that junior developers have written
Bugs are written by all seniority levels of engineers. “To err is human,” after all. Junior developers hold no monopoly on mistakes.
- dmm 7y ago>> identifying the bugs that junior developers have written > Bugs are written by all seniority levels of engineers. Sure but the Senior devs are too arrogant to ask for help ;)
- to11mtm 7y agoSounds more like a mid level dev. IME Seniors aren't afraid to ask for help when it makes sense to.
- Kalium 7y agoIf anything, it's been my experience that the bugs from the junior devs are often more obvious and easier to fix. Any junior dev can make a minor logic error. It takes a senior dev to mis-architect a whole system.
- Aeolun 7y agoJunior devs can absolutely mis-architect a system if you give them enough leeway because they’re described to you as senior developers.
- rurban 7y agoNormally it's the mid-level dev who mis-architects a system. It's called overarchitecturing. Seniors rarely overarchitecture.
- jkoudys 7y agoTrue, but there's no award for how obvious the average bug is. I've also found we often reach huge problems after being distracted by a bunch of minor sloppiness. Submit a PR that has a serious flaw in it, but is otherwise top-quality, and people may find that flaw. Submit the same PR, but name every variable "data" or "value", change every constant to an uncommented magic number, and cram in some jQuery functions even though it's deprecated in your project, and reviewers will happily point out all those things while completely missing the serious flaw.
- ledauphin 7y agoOf course! But I'm addressing how senior developers spend their _time_. They don't often spend lots of time helping with bugs written by other senior developers.