FRESH

Hacker News

Ten years of deploying to production

53 points by mooreds

by andersmurphy

5 subcomments

> In that decade, this company was behind the curve
I like to think there is no curve only fashion. I've seen company's that were so behind that they managed to avoid adopting disasters like microservices etc. I've seen companies ahead of the curve go from monolith to microservices back to monolith.
Also funny that the ops team is now back just rebranded as the platform team.
Plus ça change.

by deterministic

0 subcomment

If you are thinking about AWS or (worse) deploying on AWS you are definitely behind the curb of the companies who badly regretted that decision and are moving away from AWS due to cost.
The smart companies completely skip the cost and time spent moving to AWS. They instead use Linux-boxes-in-the-cloud solutions with zero integration of AWS specific services, making it easy to deploy on multiple host platforms world wide, and saving $millions.

by JEONSEWON

2 subcomments

by icameron

3 subcomments

That’s a tough policy to only update prod biweekly! It would be super frustrating if you had a bug crawl out and not be allowed to patch it for 2 weeks. This post really expresses the frustration of working in a bureaucratic environment where developers don’t have full access to change production.
That being said CI/CD is a luxury for coders at lean startups, but there’s still a lot of jobs where you have to work with some DevOps Team to deploy your code to prod. Organizations past a certain size have more hoops to jump through, for reasons.
Of course as a dev it’s ideal to have full access!