Yea so far DOGE doesn't seem like they take any time to ask questions or research before doing anything.
Understandably everyone is upset about what "DOGE" is doing. But on top of those harms, the killing of USDS (or at least ending its core mission) is also a real harm.
Although overshadowed by Kubernetes elsewhere in the industry, I suspect that Pivotal's Cloud Foundry Platform as a Service (PaaS)--which the US General Services Administration's (GSA) internal digital transformation consultancy, 18F, adopted[0] in 2015 significantly influenced the software delivery philosophy of the federal government by making trivial heretofore disastrously cumbersome provisioning, staging, and deployment processes. The step away from hand-provisioned virtual machines to elastic, accommodating environments may have made agile development possible in federal offices, bringing our government into the 21st century, only fifteen years late.
I distinctly remember the switch from "here's your VM" to "here's my code," and--as an application developer--I never want to go back.
0. See: https://cloud.gov
"Internal team, what's your current greatest pain point?" -> Make that easier / faster / better
Where have we heard this before?
They even broke the USGS earthquake maps. Yesterday morning you could check the site for new quakes anywhere on earth and end up with a really good idea where it was on earth because there were several map styles available as overlays - Terrain, gray scale, street, ocean, etc.
Yesterday afternoon the only map layer available was an ocean layer showing continents, islands, seafloor profiles etc with no place names available at all.
Late yesterday night or early this morning they added another layer, USGS topo, that has generalized landforms and cultural stuff like roads, with enough detail that you can zoom in and find your town here in the USA. The problem is that this layer is totally broken outside the US.
If you are like me and you're monitoring new activity in the Aegean Sea that topo layer is completely broken. If you zoom to a level where you would expect to see individual towns, etc you will find the Aegean Sea labeled as being in the Pacific Ocean and all the coastline and landform data completely broken so that it isn't possible to identify any of the islands that could be affected in the region.
If you look at all the seas in the Mediterranean you will find it labeled as the Pacific Ocean and that label persists all the way across the Atlantic at that zoom level until Bermuda where you can see the Atlantic Ocean label.
Frankly, whoever did this probably has a good start on eating a giant bag of dicks.
Pretty obvious that they aren't sending their best to do their dirty work. These DoGE guys are ultimately expendable and if things go south for the current administration the DoGE guys will need to be absorbent enough to handle all the blame that will fall on them when people begin to be held accountable. They need to be multi-layered Downy guys. The men at the top will slick themselves down with lawyers so it all slides downhill and hang everyone else out to dry once they are past their usefulness date.
It is happening contemporaneously with all the other bullshittery so I think it is a reasonable conclusion that DoGE personnel directed by someone likely unelected and so far unaccountable are the parties responsible.
I'm not sure why someone would intentionally destroy the utility of a site that has been extremely useful, not only for Americans but for people anywhere who needed to understand earthquakes and their local historical seismicity.
I can't remember at time in at least the last 15 years when the site has not worked flawlessly serving data about new and historical seismicity from all over the globe in a way that allowed the user to customize the view to fit their own needs.
I agree with a couple of posters that think this may be an effort to rename the GoM to the GoA since all the place names are missing from the Ocean map and the places names that are present on the USGS topo map are full of stupid errors that suggest that they modified naming of water features and it broke something for their map layer.
As an oil and gas industry person I have to chuckle to think about all the things that have to happen for that industry to ever come into compliance with this bullshit renaming. There are thousands of wells in databases globally named with a Gulf of Mexico nomenclature. That's just the wells. Each of them likely has multiple dozen products with a GoM tag to identify the well it belongs to. There are probably millions of line miles of seismic data from dozens of large and small seismic data acquisition projects, all of which use GoM nomenclature since the standard nomenclature in the industry relates things to a Client, Line, Area, Survey or similar parameters so that if it happened in the Gulf it will have GoM in the name somewhere and in the metadata associated with the project since that is how you geolocate things in the industry. You reference it to an actual physical location known to less than a cm in many cases.
Sounds like a lot of busy work for anyone in the industry and possibly an opportunity for a consultant to step in and handle all the renaming that will need to happen if there is any effort to comply. They'll need to know multiple databases upside down and sideways since each operator manages things their own way. And they'll need to be comfortable sitting idle while the IT guys sort out access permissions for every legacy file and folder once they discover where the data management division has them stored. You'll also be the fall guy if some of the data gets corrupted but, shit happens. Sounds like a sweet gig.
Give us the inside view from your office chair.
I just think that there are lots of incompetent people in government to begin with who could have messed this up in an attempt to rename, and was interested in understanding whether you had inside info about whether it was the people in DOGE. You have a lot of insightful info in your response, but none that looks like a smoking gun to me like "I know someone at USGS who saw it being done", so to me it looks like an accusation that might not stick. That's all. But we're on the same side here.
Thanks for your clarifying reply as it helps to understand where you're coming from.
>I just think that there are lots of incompetent people in government to begin with who could have messed this up in an attempt to rename
As I mentioned earlier up in the thread when you raised concerns about things breaking all the time due to incompetence, this site has a long history of delivering timely information to global users without breaking. When massive changes like the ones that we observe happen which affect how information is delivered those things are routinely announced in advance and users are provided an opportunity to use the "upgraded" version of the service and submit observations about usability, etc so that there is ample time to take user input before it goes live, replacing the old method of data delivery and/or display.
These changes happened between breakfast that morning and early afternoon with no announcements to users that anything on the site would be changed. All these display options disappeared and in their place we initially had a single layer with no place name information at all. A user would need to know some geography in order to be able to figure where the new quakes were occurring.
Sadly enough, that means that some users would see a nice map overlay with dots on it but would not know where those events occurred due to deficiencies in their education.
Since that first set of deletions, another layer was added, the USGS Topo layer and that layer has since been updated to rename a large body of water to Gulf of America and that is the label that appears when the site loads. There are place names, roads, terrain, rivers, etc in that layer so it is easier for even the non-geography nerds to determine where an event occurs relative to their own location.
Other changes have happened and from the changes it is reasonable to conclude that the persons making the changes did not have experience using the GIS software that enables all these useful displays. With that in mind it becomes increasingly unlikely that regular USGS employees made these changes since there obviously are people there at the agency who have all the skills needed to quickly change things without breaking them and the normal process of notifying users of upcoming site changes was not followed.
Overall I think it is unfortunate that you have so little trust in federal government employees. I have a dog in the hunt so I have a window into how things work at the federal level. My spouse has had a decades long career in a federal agency and I can tell you that the individual people in the agency are not usually the problem.
Every time there is a new administration that new administration has the opportunity to nominate new leadership for all the departments. You already know this and have seen it in action. The positions are seen as an opportunity to promote the agenda of the new administration and to reward those who helped them be elected. Too often we see people installed as agency heads who have no background domain experience or worse, they have experience in sectors that did not benefit from following agency guidelines about handling federal monies. They are there to shake things up and they bring a list of things that must be changed to fit the new agenda.
The agency employees have to adjust everything that they do to fit the new agenda and this causes inefficiencies in the system as all existing employees have to be trained on how the new director wants the agency to work and on the new director's guidelines and agenda. I can say that it is increasingly common for an agency to need to educate new directors about what they are constitutionally allowed to do so that some of the new agenda does not force nor does it allow anyone downstream to break any existing laws.
Governments are large. Any time something gets large there is the possibility that inefficiencies develop.
The decision to describe government employees as incompetent is inaccurate in general though I'm sure there are exceptions. You think there are "lots" of incompetent people in government and at any description of "lots" between a couple and thousands you are likely correct.
Don't paint them all with the same brush. Maintaining a government position involves annual training and recertifications, deciphering the meaning behind small changes in the text of rules and guidelines that they must follow, and understanding how to manage groups of people efficiently so that everyone stays engaged in their assigned tasks and meets targets assigned by agency "leadership".
My own definition of "lots" based on years of observations and conversations with someone inside a large federal agency is that the least competent are frequently found at the top of the agency and they bring their own group of managers into the agency in order to pivot to their new agenda. Those lower on the food chain must attempt to adjust or seek a transfer to an agency with less induced dysfunction or to a private entity.
I don't personally think that rate of competence in federal workforce is worse than any other big organization, especially outside of politically appointed leadership. Massive leadership changes can still create operational disruption by offering the opportunity for career brownnosers to demonstrate their fealty by empowering them to force their zeal onto others. I wonder if something like that happened here, where some MAGAt within USGS staff decided to skip a bunch of review process either to make themselves look good or out of fear that they'd look like they're resisting orders.
Isn't renaming a place rather common? Even nations were recently renamed (Swaziland, Macedonia).
Therefore the software (database included) managing the data (used by the USGS earthquake's) probably offers a way to rename a place.
Is there any documentation exposing how to perform such a renaming? Is it up to date and accessible (or did someone modify/hide it in order to annoy DOGE)? Was it not strictly followed by the person(s) who tried to rename this Gulf? Are all technical thingies associated to such a renaming free of major bugs?
If all answers to those questions are "yes" then the person(s) who tried to rename is the sole culprit.
If there is a single "no" then at least another person should be put into scrutiny.
Trying to sea-lion your way through this convo after the person replying to you gave a detailed breakdown of the situation is gross. Don't be a sycophant.
There is no problem from their point of view, they are succeeding from their perspective, and musk's, and trump's and every other anti-america neo nazi shitlicker who got them there.
[1] https://www.reuters.com/world/us/thousands-fired-trump-musk-...
The way the government has been run the past decades doesn't work, demonstrably. Every important metric has worsened.