https://chrome.google.com/webstore/detail/recipe-filter/ahlc...
Chrome: https://chrome.google.com/webstore/detail/recipe-filter/ahlc...
FF: https://addons.mozilla.org/en-US/firefox/addon/recipe-filter...
Source code (there's Safari in there if you don't mind building it yourself): https://github.com/sean-public/RecipeFilter
I was spurred into action by a comment here on HN back in 2017: https://news.ycombinator.com/item?id=15755378
It got demoed to the world during WWDC 2020, which was really neat: https://youtu.be/Kwh2y6VkzoA
In Seattle, for example, I think the sun would rise before 5 am as late as early August. On the other hand, if Seattle stayed on DST (+7) year-round then the sun would rise after 8AM from early November to late February, and as late as 9AM in December.
Seattle is an extreme case, because it is so far north, but New York City is not that different, and I think more people would bemoan the lack of after-work daylight during spring and summer than currently bemoan the switch, and would be unhappy about it for a longer period each year.
Of course, if we got rid of DST, we could all just agree to get up earlier in the summer. Maybe we could even standardize that by agreeing to all start getting up earlier on the same day each spring. :-)
Yeah, I don't know how long that'll stay true when you have a guaranteed buyer for a product...
Can someone explain how amazon did well because of state intervention in local health? I don’t see the connection.
A lot of the work of an EM is wading into the slurry pit with a shovel so your team are free to get the job done: bashing your head against InfoSec teams stuck in the '80s so the CI/CD toolchain can deploy to production, negotiating freedom with a CTO who wants to specify everything to the level of individual data structures, convincing HR that no, we really do need to pay for a good senior and not hire someone with 2 years experience in a configuration galley because they're cheap.
On top of that there's the process battles; in older firms, all those interminable "but can't they just use Waterfall?" meetings that go on for hours and are spawned every time there's a minor project manager reshuffle. In newer ones, the ongoing fight of, "you can't address debt or build foundations for the future, we need features, if it can't be done in less than a week it's not MVP enough"
There's a fine balance in that I think a good EM lets their team know this is going on and get involved where they want without dumping all the crap downward. Not least because they should be coaching their team leads in that responsibility, so they can take the career step when they want.
Going back to the article, as others mentioned it does read a little bit more like a "why I'm frustrated with my manager" than a "how to be a good EM", but it's easy to misconstrue the meaning of text.
What does this mean?