The new guy is putting me on the defensive. And I couldn't be happier about it. Here's some rules to help foster a more inclusive environment on your team, on where developers of all skills feel comfortable asking those powerful question: "why?"
There's this new guy on our team. He's really smart. Probably smarter than me. Should I be worried about him trying to take my job?
You may be familiar with the term rubber duck debugging [https://en.wikipedia.org/wiki/Rubber_duck_debugging]. This is the idea that in order to help a programmer solve a problem, s/he should explain it to some kind of inanimate object (most commonly a rubber duck), because in
The problems started small, as they often do. But as we've seen many times before [https://www.exceptionnotfound.net/how-do-you-fix-an-impossible-bug/], lots of small problems in quick succession tend to make one big problem. In this case, the problem got big fast. It started off easy enough: read the big report,