This is so delicious, I'm sure the code guys were like. "Well our jobs are safe right!? I mean who is going to make sense of this convoluted kludge we've baked our job security into." Another one pipes up, "Yeah and if they ask me for information on the Commie Troll farms and all of the Bots, I'll tell him to go pound sand!" Boasting over lunch.... "We should hold the data hostage until he meets our demands."
(one hour later...) "Fuck! Can you believe it! They locked us out. I thought he would keep us until at least after Christmas!"
Speaking of the jilted coders who left a legacy of convoluted code kludges. . When you build a system, that treats all like data equally, it is bug free, robust and those systems never fail. The broken link is usually other systems that interface, network or hardware failures, but those systems that were wrote to call a spade a spade. Never fail software wise. The code is also easy to manage, and you don't need a million Unit tests to see if they will fail or not. They are simple classes, that are passed into simple functions, or touples passed in to construct those classes and initialize them and pass them into simple functions. The problems arise when management and end users start calling for what I have always called. "The Fred Exception"
"Hey I know you've been really busting your ass to make a scalable flexible system, that is easy to interface and communicated with other systems from legacy to tech not even invented yet. But we have a special customer named Fred. Can you check to see if any of the 5 million orders coming in every day are from Fred. If it is, I want you to bypass all of the complex data loading, constructing and marshalling, and pass it straight to the main business requirement function, without any context?"
Of course you suggest creating a new Customer type, and create new business rules so the process I created to populate a new customer or order object in our ERP, will have all of the other required attributes. Where if it's a new type, those can be auto loaded with common data to make it comply with the process. That way we're not parsing every element in the array to initialize a class just to parse if it's that's pesky fucking Fred! And also that way when Fred's brother Paul wants some of the action. I'm not having to put a ternary to distinguish which one of these special fucks gets the Fred Exception.
Now I'm explaining all of this because for those of you that are NOT technical, and don't understand what it takes to write a stable solid system. Will understand what Google, Facebook and Twitter did to their well established codebase, to accommodate the DOJ, the Media, and the Commies Fred Exceptions, only Fred in this case was Donald Trump.. And We are all Paul. If you all recall before Trump came along Google was good at what it did, we considered it our second brain, and queried it before even consulting our brains. Twitter was awesome, it was used by the Elitists. Globalists, Socialists, Commies, and the mainstream media down to their knees. The propaganda publishing machine they made to keep the masses in check, was being turned on against them, and bringing it's master down. So how did all of the tech companies react. You better bet your Ass, they created a bunch of Fred Exceptions, and created queues, and privacy breaking backdoors to just manually keep tabs on accounts they didn't agree with. Robbing these tech services useless to anyone other than Dictators and Tyrants looking to keep their users in check.
This is the code rubbish that Elon is inheriting. By time these projects get to the sloppy point that they surely must be by now. It's hard to distinguish between code originally commented out, if not deleted, and code iterations of various censorship attempts. And the hodgepodge of desirable features created since that timeline verses desirable features that were deleted or commented out. They often have a gap between what is required to invoke those objects or save them to the database.
My guess is Elon is going to have to scrap the majority of the codebase, and start all over from scratch. Using older requirement gathering if Twitter even still has that around.
Would Twitter had been required to save the codebase from before 2012 - 2016ish and they started screwing with their algorithms and replaced with manual blue haired specimens? Or did Elon buy their codebase as it was at the time of the offer?
patrick.net
An Antidote to Corporate Media
1,233,278 comments by 14,744 users - AD, AmericanKulak, Blue, Booger, Ceffer, HeadSet online now