My first experience with X and Grok. Ho lee shit it's worse than bad. They're literally showing us what their future technocracy government will be like. You thought automated Customer Service was bad over the phone? Wait til it's like that for EVERYTHING π
(media.greatawakening.win)
Trust That Ai Knows π©Hitsπͺ
I would not be surprised to learn that lefty software people that worked for twitter put millions of lines of code into the algorithm with hard-coded filters to block thousands of specific people.
I don't know what it is, but every piece of SW I've ever had to touch that was previously developed by left leaning developers has always been the worst pile of steaming poo spaghetti code. They can't write simple code to do a simple task. Half the time when they see my code, I've been told it's all wrong. Does it work? - yes. Is it simple? - yes. What's wrong with it? - long philosophical argument about coding styles, cross functional platforms, don't like it, etc, - but not one word of why.
I write A + B = C. Done
They write a half dozen or more cross linked functions and subroutines that check the scope of each variable, bit shift the numbers to drop unwanted significant digits (because you have to have a check for that), maybe convert types because the function that is allowed to do the addition only accepts a specific type like a string that requires it's own conversion to actually perform the addition, etc. And if you think you're going to get away with writing A + B = C, think again - they've already written algorithms to scrub the code looking for code like that outside of their approved function to perform that task.
You might thing I'm joking. I wish I was. It wasn't specifically A + b = C, because that would be too obvious, but it was enough other relatively simple tasks to drive a guy mad.
"I don't know what it is, but every piece of SW I've ever had to touch that was previously developed by left leaning developers has always been the worst pile of steaming poo spaghetti code. They can't write simple code to do a simple task."
We affectionately referred to this as, "running around the house ten times to get through the front door."
The nice thing about object oriented code is you can define the house, define the door, define the path around the house, inherit the path distance and loop counts from the requirements class, and implement an Interface to execute the run function, run loop counter, and run complete event, door handing functions & events, and house entered definitions & events.
Otherwise, how are going to know if you actually went through the front door without a task complete event from the interface that was observed by 3 other unrelated threads?