HN user

epiphanitus

223 karma

--- My views are my own and do not reflect those of any of my employers, past or present.

Posts10
Comments129
View on HN

The source of this article seems kind of dodgy.

- 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

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?

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.

https://www.youtube.com/c/JiveTurkeyCrew/featured

What’s the backstory to why apples bash has to be different than gnu bash?

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

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.

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.

Lots of good suggestions here but one I’ll add is that maybe you should find a job working for a cause greater than yourself. There are a ton on nonprofits out there that are in desperate need of technical people to help them. My advice if you want to go this route is to stick to orgs that do concrete things for people, like find people housing, or teach English, or provide assistance with addiction, etc. I’ve done some non technical work pro bono and it was some of the most fun working I’ve ever had. You will have to accept a lower salary but if you’re looking for meaning out of work there’s nothing like it.

> Unfortunately, this won't last forever. Other countries are catching up to the U.S. quickly. Eventually, development will move to cheaper labor countries like so many other industries. What is frustrating though is that if the U.S. actually focused on developing its talent, we could maintain the lead for another decade or two longer than if we just sit on our hands. With that extra lead time, we could come up with the next major industry (AI-training? quantum computer programming?), but as it stands now, many other countries will be equally poised to jump on the next opportunity and we'll squander our lead forever.

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.

I was in a similar position not too long ago. I had nothing but a liberal arts degree, a miserable first career and a yawning resume gap. I just stumbled into coding and I was completely addicted. After many months cobbling together a frankenstinean tangle of Kubernetes clusters, db instances and even an AI that could write bad limericks, I got a job as a backend engineer. You have to work your tail off in this job but its a life changing opportunity in a field where you get to make things for a living and there's always something new to learn.

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.

+1. Maybe this is more important at a big company that at a startup where your business model and your tech is either good enough or it isn't. But even then you still have backers, etc.

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.