The original source was probably a front. This new source is better, but their source is Russian State TV. I would be interested in whether the law actually exists, and if so whether it is really applied consistently without exceptions for 'special' people.
Thanks for your comment, I appreciate your willingness to share a contrarian perspective.
Question, how would a virus that spreads primarily indoors and rarely spreads outdoors accumulate enough viral load over enough hosts to spill over into humans? It seems like this would be difficult in an open-air wet market.
One problem is, many if not most engineers work in corporate environments where they have to deal with expectations and deadlines. Mgmt may perceive reimagining a system to be a risky long-term bet and its tough to persuade them of the benefits. In their defense their hesitation may be justified. I hate crappy hacks but at the end of the day there's a reason why they get piled on so much.
So I guess the question is - what's the best way to scope and evangelize a 'moonshot' project? Or should you just shut your trap and go join a startup?
I love the mix of the ambience and the narrator. Those PSAs and old narrations really add an interesting dimension to it. Question, where do you find those voice samples?
If anybody is looking for something new to listen too, he made an album with John McLaughlin and 3 other jazz gods called Five Peace Band. One of my favorite albums of all time.
Thanks. Getting into this was purely accidental. I had an interest in machine learning that required more and more complex pipelines to feed it. I kept adding on layers of complexity until I was running a Kubernetes cluster and a database. Learning kubernetes meant learning about bash and containers, which were useful later.
I'll check out Network Algorthmics, thank you for the recommendation.
>> But, ultimately, the best asset for somebody with a CS background is not so much having immediate knowledge, but knowing where to acquire knowledge as necessary. If you have a general idea that for a specific scenario, you can acquire X knowledge in Y resource as you go along
These days my goto resources are SO, Slack, Github issues, etc. Any recommendations beyond that? Or by 'where to acquire knowledge' do you mean 'how to categorize problems'?
Put more simply, there is a big difference between the capacity to care about other people's feelings, and the capacity to understand them.
Some understand but do not care, whereas some care but do not understand. It dovetails really well with creativity but it can introduce many challenges in life.
There's actually a former US Navy Sonarman who has a youtube channel called Sub Brief and it's amazing. He left the service in 90s (IIRC) but he shares all kinds of interesting knowledge on how torpedos and mines work, all the different kinds of accidents and mishaps that happen - he even analyzes different disasters like the Kursk and how they likely happened. I highly recommend it if you're into subs.
SRE here. I feel for your situation. Here's some advice. One simple thing you could do is set up AWS billing alarms and have them delivered to a notification app like PagerDuty.
If you don't want to pay for PD, you can patch together any number of ways to get your phone to scream and holler when it gets an email from [email protected]. It's also good to have clear expectations as to whose responsibility it is to deal with problem x between the hours of y and z and exactly what they are supposed to do.
Keep the alerts restricted to the really important stuff, because if your team becomes overloaded with useless alerts they will 1) dislike you and 2) be more prone to accidentally mistaking a five alarm fire for a burnt casserole.
There are more complex systems you could build, but that's a start.
That's crazy, my mom who lives in the Seattle area got sicker than she's ever gotten with that bug. I knew it was going around, but I had no idea it was THAT rampant.