scrose
Joined 7 years ago
Joined 7 years ago
They never mentioned whether it’d actually be beneficial for the government.
Can’t wait for all of our federal agency buildings to be named after different members of the Trump family once they’ve changed hands! /s
The simplicity of the approach seemed pretty awesome
I think "new" would make sense and I accidentally conflated them also writing about the EPA rolling back *existing* standards for other appliances in this article.
The only part of the article that explained what was done states: "Today’s actions postpone the efficiency standards for the following home appliance rules:"
Would a title of "US energy department indefinitely postpones efficiency standards for home appliances" sound less deceptive to you?
This is a very odd take. The title is based on the only part of the article that isn't PR fluff and describes what was done:
> Today’s actions postpone the efficiency standards for the following home appliance rules:
Central Air Conditioners
Clothes Washers and Dryers
General Service Lamps
Walk-In Coolers and Freezers
Gas Instantaneous Water Heaters
Commercial Refrigeration Equipment
Air CompressorsI’ve been working with AWS for about 8 years now and have worked on supporting dozens of projects across 5 different orgs ranging from small 5-person shops to 1000+ people. I have only seen a handful of cases where serverless makes sense.
> Taking a legacy application that runs on a single server and is struggling to scale with spaghetti of config files all over the box and security issues that have gone unpatched because no one wants to touch the box as it’s too dangerous to change anything, as everything is intertwined. No backups or unverified backups. No redundancy. No reproducible environments so things work on local but not on remote. Takes devs days to pin the issues.
All of these issues are easily possible with many serverless options. What it really sounds like is your org went from a legacy architecture that built up a ton of tech debt over the course of years and had no one owning the basics (ie backups) to a new one with less tech debt since it was built specifically around current issues you were facing. In 3-5 years I wouldn’t be surprised to hear the pendulum swinging back in the other direction as staffing and resources change hands and new requirements emerge.
It’s often the opposite, but most people don’t see that until after they’ve built their infrastructure around that, get locked in, and then start seeing the surprise bills, difficult to diagnose system failures, and hard-limitations start rolling in.
A bit of early skepticism, and alternative solutions with a long-term perspective in mind, often go a long way.
Your idea of ‘containment’ in this sense means you’re defending the equivalent of a gang of serial rapists and murderers entering innocent people’s homes, taking their families hostage, and saying the home is now theirs.