Thanks for another example of how OKRs aren't working for devs. A part of the inspiration to write this was that I noticed most developers feel that something is wrong with the OKR process, but they can't put their finger on exactly what.
I don't think anything is as good as screen hero used to be. The problem that I've had since it's been integrated with Slack is that it often acts like there's not enough bandwidth. Choppy connections, etc. I end up switching to a Google Hangout which will typically work fine.
I think there's some clear space for "remote pair programming" tools.
This would not be an effective method for the Southern USA. Nashville, which is most certainly up and coming, is also springing up "Hot Chicken" shacks left and right in the hippest areas.
I appreciate the thoroughness of your comment. I also agree with some of what you said. For me, TDD is not so much about testing the code as it is about effectively writing the code. The only point that you brought up that I would like to make a counter argument to is the idea that you should get the design right on the first try. I don't agree that it is a good idea to design the system thoroughly up front. For me, using unit test to allow me to refactor throughout a project is very useful and allows me to become better at design everyday. It's an excellent way to prefect your skills as a code designer. It also leads to a code base that can be explained without any "well it used to..." sort of talk.
But again, I emphasis that I found everything else that you brought up to be perfectly valid.