Yeah, if that's how it supposed to work, then I've not been anywhere that does it right. We're always working ones like what I mentioned in the post.

Yep, this would be good feedback up the chain. People above you should be working on breaking the company level goals into team and role specific ones.

Edit: just to note that I have some other criticisms of OKRs, but having them be way too high level, broad, and not actionable should not be the problem.

Please share your criticism. I would be happy to get as much perspective on the topic as possible.

The problem I encountered was having, or the notion of wanting, a product roadmap which is produced from stakeholder, C-level, product- and IT team input parallel to OKRs. I feel this is an anti pattern. You have OKRs and they make your quarterly roadmap or you don't apply OKRs at all to the producing team.

Would love to hear if you're able to make it work by adjusting the details of how it's carried out.

Great point. Could definitely point to leadership being out of touch with what really needs done.

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.

I would encourage you to try meditation. It's not a cure for depression, but it can have effects that help. In the Zen tradition, Brad Warner's books have been very helpful to me. http://www.amazon.com/Hardcore-Zen-Monster-Movies-Reality/dp...

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 think it's a great thing to say to someone who agitates a suicidal person, personally.

No, it's pretty appropriate in this situation. Don't be an ass.

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.

The iPad does not have that limitation. Applications are not run as root. If they were there would be no need for jailbreaking.

That's not true, Applications could still run as root but be signed and subject to approval as they are now. The only difference I can think of is they just wouldn't be sandboxed any longer.