I was reading the article Why data centers fail to bring new jobs to small towns by Alison DeNisco Rayome.
This is a subject that I can relate to as I’m from the area where Facebook plopped down a data center outside the rural town of Forest City, North Carolina. The chatter from elected officials and Facebook themselves was that this would be a boon for the local economy and create numerous new jobs. But, while the temporary outsourcing of local construction laborers was a small uptick, the same problem that was experienced by E. W. Gregory appeared. Data centers are, more or less, gigantic network closets. There is simply no need for that many technical staff. In any case, Facebook continued expansion projects, with the latest being as recent as 2016. An estimated “125 full-time jobs [and] full-time third party (sic) contractor positions” would be created. This is in a county with a population of around 65,000 with a workforce of roughly 26,000 people. Therefore, the presence of Facebook will theoretically have a 0.004% positive impact on a county that is already below the poverty line. Data USA states that the 2017 median household income was $38,573 (USD), which is $19,079 (USD) less than the median income of the country as a whole. The outlier in this instance is the Lake Lure area, which comprises the western half of the county (see below). Forest City (and my subsequent hometown of Ellenboro) is center and right.
What an impact that data center is having, huh? When examining the most common and most specialized jobs, there was no change in the years since the data center’s operation:
I should also mention that Walmart is the biggest employer in the county. So why did Facebook choose Rutherford County and why did the county commissioners (and Duke Energy) bend over backwards to give them so much economic incentive? The answer is always the same: taxes. From the article Study: Facebook Data Center in North Carolina Has Massive Economic Impact, we see that $198,000 were added to local property tax rolls and $336,000 tax was paid on electricity usage (the state managed to get $194,000 in franchise taxes). The article goes on to boast that “[o]ver three years (since the site went live in April 2012) the data center resulted in addition of 4,700 across North Carolina, including direct creation of 2,600 jobs.”
Am I mad that Facebook built a data center in my former back yard? Hardly. I don’t live there and they are free to purchase land and set up shop wherever they want. What does irritate me is when they (in conjunction with the local government) start blowing smoke up the collective asses of the local populace. Of course, this is the same populace who keeps voting in the aforementioned local government, but what do I know? Apparently what’s good for the county’s (and state’s) goose is good for the gander.
So the next time someone suggests to you that a new data center is going to turn the town on its head and make waves, take it with a grain of salt.
Better yet, smack them with a car battery.
In a sense, it really spoke to me. I have spent countless hours in situations where the current environment were “handcuffed” as it were to tech that had, at the surface, seemed like it had lived past its prime.
Or had it?
Many instances–public sector especially–are not by any means cutting edge. The utility sector, for instance, in many instances utilizes a de facto serial standard since 1979 that is (by itself) highly succeptible to man-in-the-middle attacks and is very limited in what data it can hold. Other cases it’s a matter of needing to get something out the door as fast as possible. One of my contracts involved an organization that needed an in-house web-based ERP yesterday. (They already utilized an ERP system from Infor that ran on an AS/400 but it was unable to effectively meet the requirements of the vendors for product listing and RPG IV programmers cost a buttload).
If you are a web developer or programmer, you can already feel the nausea. If you’re not, then understand that this was the equivalent of building Frankenstein’s monster from IKEA using parts you ordered off eBay.
But: it worked. To the best of its ability, it managed to get the job done. Yes, there were a lot of innefficiency in some of the operations that took place, but it got the job done, which to the company was “Good enough.” The skeleton team grew by six people and, from what I hear, is still chugging along with backlog of features that may never be toppled, but that’s a story for another day.
In his article IT’s Famous Last Words: If It Ain’t Broke, Don’t Fix It, Peter Waterhouse states:
Maybe chasing after the “latest in greatest” isn’t the answer to remaining ahead of the curve in information technology, at least all the time. One should always evaluate their toolset and make adaptations as necessary in order to fulfill the needs of their customers. Last I checked there is still a need for C programmers.
In the public sector where availability of service, not competition, is the biggest worry, it is prudent to not disrupt the flow of what is provided to the citizens. We still see a lot of “obsolete” tech that still functions being utilized, especially in terms of the hardware that supports the legacy applications. An example is from the article DoD is migrating to Windows 10 and it will probably stick around forever by Kelsey D. Atherton:
Ensuring compatibility of these legacy apps is critical, so specialy care must be taken to ensure that they can be brought gently into the twenty first century.
So in answer to the question on whether “obsolete” tech is “broken”, the answer is: it depends.