OKR's without strategy or context (or OKR's substituting for a strategy or context) is a killer I've seen. Especially if I'm "laddering up" my product's OKRs.
This is where the bi-directional approach does work better than strictly top-down or bottom-up; my leadership probably doesn't see the opportunities or constraints for my product, but for my opportunities to be attainable, I need to be swimming the same direction as my organization. Strategy gives me context for where I should be playing.
The community itself - the Joe Runner types - are absolutely great, and I can't see that changing.
An anecdote: I went to see my buddy run a 50 miler in the Charlottesville VA area a few weeks ago. I remember being told how great the race was a few years ago - cheap, fun, great afterparty. This year, entry fees were much higher, the post-race spread was more or less nonexistent... signs of nickel-and-diming everywhere.
I suspect that's fairly common now- RD's looking to make a profit through their racing companies.
*Barkley. You have to superhuman to finish one lap, let alone the race itself...
At spirit, ultrarunning is the polar opposite of tri- laid back, get it done fast or slow, have a beer after (or during...), most importantly, stop and help others, thank volunteers midrace, etc. That has been my experience thus far.
But money's seeping into the sport through sponsorships and purses, so let's not be naive - cheating is probably already happening (haven't seen it firsthand so I can't say it definitively), and it's to the point that influential voices in the sport are trying to figure out what to do about it.
So I guess I'm curious about how Italy's system works then? It's an empirical question, how much money would I have to be offered to turn on a system of convenience and perhaps monetary discounts? (I'm not considering the downside of off the book transactions as a consumer, I realize).
Is it feasible for a domain to only accept ads with static content?
Or, for dynamic content, share the relevant portions of their own JS / envelope third party JS into their own code base (and presumably scrub it/test it)?
I'll give you one reason. I've never done any front-end stuff before. But maybe a month ago, I got curious. Perhaps because I read HN everyday.
And if you try to immerse yourself in the front-end world, you get 'yeah, learn HTML/CSS/JS, BUT, also learn Angular, React, JQuery, et. al...' It's good to get a reminder that Javascript in and of itself is a capable language. I'm sure I'm not the only one in this camp.
Maybe it didn't need to be 12 minutes, and it was certainly more of an 'oh, interesting' than anything, but I'm glad I took the time to watch it.
> a minimum five-minute delay between pick-up confirmations being sent out and drivers being able to collect their passengers
> a requirement that private-hire companies let customers pre-book cars up to seven days in advance
Um. Perhaps it would be better if the black cabs focused their efforts on enhancing their own user experience rather than trying to artificially cap it? :)
Also, this article links to nothing regarding the decision, it's just a single (unnamed) author's quick take, which is disappointing - if he/she is going to write so little, could they please provide a link to a first-hand source (the decision itself?) or a more thorough analysis?
I see from this that there are still several (perhaps minor) measures up in the air, and one measure that will be adopted is a "formal English language requirement[1]."
This is where the bi-directional approach does work better than strictly top-down or bottom-up; my leadership probably doesn't see the opportunities or constraints for my product, but for my opportunities to be attainable, I need to be swimming the same direction as my organization. Strategy gives me context for where I should be playing.