They have onsite eye exams as well for ~$65, but you'll need to find a way to reimburse with your insurance provider on your own (for out of network).
22 karma · joined August 22, 2013
They have onsite eye exams as well for ~$65, but you'll need to find a way to reimburse with your insurance provider on your own (for out of network).
I'm definitely a bigger fan of Tufte's books than his in-person lectures.
https://www.washingtonpost.com/news/the-switch/wp/2017/07/16...
http://abx.digitalfeed.net/list.html
Pretty much found the same thing for myself at 256+.
I'm not sure the platform itself is as important to achieving this goal so much as the decision-making ability of the engineers themselves, though. Maybe a tendency to pick shiny because of shiny is just a way that poor decision-making surfaces? However, I don't see a problem picking an appropriate solution that happens to be shiny.
Anyways, kudos for sharing the wisdom.
We don't have the equivalent in software, and we also seem to have a recurring discussion about effective ways to filter people during an interview process. I've certainly had mixed results in my limited sample set when considering past experience to actual performance of hires.
Is there a good way to translate the value of someone's experience?
EDIT: For that matter, I guess I should wonder how folks translate the value of people in those other fields effectively (or if they do at all).
I know understanding CS fundamentals and employer expectations about this are a lightning rod here, so I don't want to apply a value judgement on that here. However, what's the equivalent to the board or bar exams in our field (that lets us compare ourselves to those fields)?
Chaos Monkey fits when people build and deploy their services with the notion that any particular instance (or dependency) could fail at any given time. It's a tough road to evolve out of a legacy, monolithic stack without much redundancy baked in.
It's an interesting thing to watch evolve over the next few years, but I know it sucks for most of the global market with the current catalog disparity. It's hard to say which of the platform or the content are the cart and the horse, though. Do you need the platform to deliver before you ramp the content, or do you need to ramp the content before you open up the platform?
If anything, I'd argue that globalizing Netflix combined with stronger control over their own original content enables Netflix to move towards an endgame where lots of niche audiences are served (rather than only mass markets). At CES, Ted Sarandos (VP of Content) mentioned that traditional TV had to hit home runs all the time, while Netflix can score with singles, double, etc. Why would Netflix jeopardize this advantage and hop in the time machine to become an outdated TV company?
It sucks that House of Cards and some of the older original content (particularly the more popular titles) aren't globally available, yet, but I believe (also from the CES talk), this was done because Netflix couldn't afford the financial risk at the time (and/or simply could not afford the global rights) for some of these shows. More recent/upcoming shows are licensed globally, so there's an apparent effort to ensure that Netflix moves to having a single global catalog. This obviously takes time, though, as the whole original content engine starts to ramp and new licensing deals are struck.
From what I've read and played with (briefly), JRebel gives you a bit of this experience on the Java side as well, though I've never used it extensively enough to know if it delivers a comparable experience.
It's not that far removed from what many web application developers take for granted in terms of ability to make/test/refine changes on a live system with ease, but it does bring more of this experience to other functional domains.