https://eng.uber.com/research/keeping-master-green-at-scale/
1,089 karma · joined September 14, 2012
https://eng.uber.com/research/keeping-master-green-at-scale/
Pretty much exactly what you're describing haha (with obviously a fair bit of artistic license).
> They do, however, include negative emission techniques on a huge planetary scale that is yet to be invented, and that many scientists fear will never be ready in time and will anyway be impossible to deliver at the scale assumed.”
Imagine somebody said "a meteor is going to hit the Earth in 11 years and end life as we know it unless we made massive changes to our way of life and invented new technologies to thwart it." I fully believe we as a species could collectively band together to stop it.
What's so horrible about climate change is it's not that the world ends in 11 years. It's that in 11 years we likely are doomed to watch our own extinction. On top of that, we're not even beginning to deal with the problem in a way that gives hope for the future. I can't think of a more existential crisis inducing reality.
Is this the fox news talking point? This exact sentiment is slathered all over those hateful vile Facebook comments at the bottom of the article.
I don't like arguments like this. This is true for any number of tasks that a layman wouldn't care to understand. You still will do them anyway, regardless of whether or not your user cares. It doesn't take a lot of experience to see the correlation between poor engineering practices and poor user experience.
Now, I don't think the author was using this argument to pitch poor engineering, but there are good reasons for setting up resilient and consistent build deploys, as he addresses. I think the only real takeaway is "dont over-engineer your infrastructure" which is just an extension of generally "don't over-engineer."
Every time infrastructure gets talked about on HN the conversation gets so sidetracked. The real problem is that people don't think about infrastructure in the context of a holistic view of a project. The hours you spend setting up your project with resilient and consistent CI builds are many times more valuable down the road.
I think people need to not be so afraid of spending time on infrastructure. People already err on the side of spending less than more time on infrastructure. I don't think it's wrong at all that the author spent hours building an automatic build process for his project, especially because now that he's set it up he can refer to it in the future. Maybe with his newfound knowledge and experience on the problem means that he can leverage it with little effort in the future. None of this is a bad thing especially if you think about your engineering career on a macro scale instead of week to week.
I strongly dislike the notion that on-prem hosting is somehow a bad thing, or too cumbersome, or otherwise totally solved by cloud providers. AWS specifically is hugely convenient in a number of ways, but it doesn't come close to the cost savings from running your own infrastructure. You need a pretty large amount of capital and engineering talent, but it really is worth it even in the short term (~3-5 years).
I think people would be shocked at what the money comes out to be if they saw costs from companies doing their own physical infrastructure. AWS makes you pay through the nose, seeing the difference would change a lot of minds I'm sure.
This sounds like exactly what I'm advocating. I wasn't saying that you need to build specifically with Kubernetes in mind, but some people aren't even thinking about what it means to deploy to Heroku. Maybe you do some small amount of reading and research to know "switching from heroku to kubernetes is a viable migration path.' What I strongly dislike is this mentality:
> taking more time away from actually building your side project
None of what I've mentioned is time taken away or lost. Time spent doesn't just pause when you are ready to deploy or productionize. SWEs need to think more holistically about their software's lifecycle.
I generally dislike this way of thinking. Infrastructure is a core component of whatever it is you're building, not an afterthought. Maybe you can defer things until a little bit later, but if you can build with infrastructure in mind you'll be saving yourself so many headaches down the road.
You don't need to build with the entire future of your project's infrastructure in mind, but deploying your project shouldn't be "ok now what?" when you're ready, like it was a big surprise.
Maybe they have better tools for managing package dependencies but Go doesn't have to deal with interpreter dependencies, which can be a major headache. Go also doesn't have the problem of conflicting system level packages.
Honestly no matter how good your deployment practices are, if you have to manage an application's deployment long term you're going to have dependency problems of some kind. I'd rather deal with those problems at compile time than hit an edge case during deploy or in prod.
This already happens without block chains.
I feel like this is a problem that is pretty commonly exercised in our legal system and incarceration is usually a strong last resort motivator.
Weird seeing a repost on the website where a lot of the story unfolded on the same day.
The other option is that these frequent winners are surrogates for others who can or would not hand in their lottery ticket on their own.
What follows the razor?