223 karma · joined March 27, 2019
Are there any resources or strategies you would recommend to help with this?
- I haven't found a credible source corroborating the claim made in this article.
- Their FB page has surprisingly little traffic for a news site and their twitter account was suspended recently.
https://www.facebook.com/then24dotcom/ https://twitter.com/then24dotcom
- Their contact email is...not one you would expect for a legitimate news site (celebsbabe @ $major_mail_provider).
Edit: formatting
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.
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?
>> 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'?
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.
I thought gamma rays were filtered out though the atmosphere.
I love having the Linux kernel with a nice UI but there are some useful commands that are missing.
There are ways to get them set up but in any case it’s kind of a pain
https://docs.aws.amazon.com/AmazonCloudWatch/latest/monitori....
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 ohshit@amazonasws.com. 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.
Agreed. I have several (very smart) coworkers in other countries. And our political system is an atrocious thing to watch these days. Whatever happened to compromise?
I don't think anybody really knows for sure what the future holds. The thing is with cloud computing and with the spread of technology into the developing world they will likely be needing engineers too.
Of course that may not happen if the software world is so carved up that all of the business goes to a handful of companies that are employing a fixed number of people and concentrating the gains.
And if Elon Musk has a breakthrough with neuralink, then maybe we'll all be out of a job. Why write code when you can think print('hello world')?
On the other hand, big players can get disrupted, technology can change, and its not like every human being has the capacity/stomach for the abstract problem solving we do day to day.
Thank you thank you thank you cloud providers for making compute power so cheap. I realize you do it because you know you will eventually make the money back 10000x over when we persuade our bosses to lock in to your ecosystem, but I don't care. (Capitalism is not perfect, but hey, sometimes it can be okay)
DO tutorials are amazing, by the way. I learned so many things from your docs, it shows a lot of hard work by some very talented people.
Some people understand this stuff, and some people don't, and I don't see a lot of ways for someone who doesn't get it to become someone who gets it.