Punkie

This is something that influences a lot of culture. Like most people when they think of style and decor in the 1980s, are thinking of Los Angeles in the 1980s. The rest of America was not always neon pumps, leg warmers, and thin piano ties.

I had a motherboard like this: the USB ports didn’t work until it booted into an OS. You had to connect a PS2 to make changes in the BIOS, and could only boot from IDE. It was super-annoying.

We had a case not too long ago where someone “recruiting” for one of the GAFAM who was stealing PII by “accepting” applicants, getting their IDs and personal info for supposed employment, and when these people showed up for work, the real company had never heard of them. I think they got 30 people last time.

Not currently, but I did a few sides jobs in the last ten years.

I am a Linux systems administrator. Before I did full contract work, I did part time contract work (alongside my full time salary job) for a general contractor as a piecemeal basis. A job here, 20 hour support there. Some jobs I made $300, some $3000. It was sporadic and came in waves. I got this from a former contract job who recommended me when they folded.

I also did writing gigs. I optioned a few scripts and sold a few short stories. That’s still ongoing, but I haven’t sold anything for a few years.

Mental health never being addressed, so we’re also too tired.

Someone did a study at MIT about tin foil hats, and found that not only do they not screen radio interference, in some cases, can actually magnify them.

Conclusion: The helmets amplify frequency bands that coincide with those allocated to the US government between 1.2 Ghz and 1.4 Ghz. According to the FCC, These bands are supposedly reserved for ‘‘radio location’’ (ie, GPS), and other communications with satellites (see, for example, [3]). The 2.6 Ghz band coincides with mobile phone technology. Though not affiliated by government, these bands are at the hands of multinational corporations. It requires no stretch of the imagination to conclude that the current helmet craze is likely to have been propagated by the Government, possibly with the involvement of the FCC. We hope this report will encourage the paranoid community to develop improved helmet designs to avoid falling prey to these shortcomings.

Probably HR (or the NCS equivalent) never told the right people. I am not saying this is actually what happened, but a lot of IT bemoan the fact they are never told some rando employee was fired because HR neglects to inform them. Sometimes it takes months to discover, and even with a 90 day password/login lockout, some halfway decent admin could get around this by secretly building a back door, and using the messed up communication and politics between departments to hide this. Even in the 1990s, I saw people put in “time bombs” in their code that “if such and such is not updated in 6 months, run destructo-script A.”

But imagine someone like Kandula Nagaraju here. Worked in QA, probably did a great jobs with some skills, but had the personality of swallowing broken glass. He was terminated in October 2022 due to “poor work performance,” which could mean anything. “Not a team player.” Or maybe he really was an idiot: I mean, a smart person would have a conniption, but get employed elsewhere and then slam his former company at parties. “Those NCS folks didn’t know what they had with me!” But this guy was probably someone with some anger management issues, probably a jerk, and possibly stupid. He might have had revenge fantasies, and set up a small virtual server posing as a backup code mirror. But outside the audits, it allowed ssh from the outside, and hid it through a knockd daemon. Or maybe only launched ssh at certain hours before shutting it down again. Silently working away in a sea of virtual servers with little to no updated documentation. He gets in, has internal access, and runs a script with admin credentials because they don’t rotate their AWS keys/secrets quickly enough. Or didn’t even know he was let go.

After Kandula’s contract was terminated and he arrived back in India, he used his laptop to gain unauthorised access to the system using the administrator login credentials. He did so on six occasions between Jan 6 and Jan 17, 2023.

That’s embarrassing to the company. Not only did he get in, but SIX TIMES after he was let go. he probably knew what order to run the delete commands (like, say, an aws “terminate-instances” cli command from a primary node), and did so one by one, probably during hours with the least amount of supervision, where the first few alerts would take hours to get someone in the monitoring chain to wake an admin. Given his last day was in November, and he got back in January, the admins probably thought their 90 access credential rotation was “good enough,” but he got in on his 80th day or whatever.

I know this because I have had to do triage when a former contractor did this to a company I worked for. But instead of wiping out instances, he opened a new set of cloud accounts from the master account, put them in an unmonitored region (in this case, Asia), and spun up thousands of instances to run bitcoin mining. Only because AWS notified us of “unusual traffic” were we made aware at all, and this guy knew his shit and covered his tracks very well. He did it at a speed that could have only been automated. Thankfully, AWS did not charge us the seven figure amount that this activity amassed in just three days.

Pro Cavity Creeps agenda:

I remember hearing that some Hollywood contracts require that if you sign up for some studio, you must make X amount of films. Big stars get to chose those films to some degree, but once in a while, they have to do “a stinker” to end the contract as “X amount of films done, okay?” or something. Contractual Obligation and all. This film feels like a dumping ground of a lot of those contractual obligation hires from the trailer alone.

MBAs who contract dev work out to India to make a quick buck without realizing how bad the code they’re going to get back usually is.

Ah, but some of them DO know what they are doing! In the IT world, I have seen where people say a job is about 2-3 years, show no loyalty to the company, and so on. But they don’t understand managers are doing this, too. Many KNOW these outsourcers are shitty (or don’t care because that’s not a metric they care about beyond selling points), but in a 2-3 year turnaround time, by the time it’s apparent they don’t work, the people who made those decisions are already gone. They ALSO thought ahead to the 2-3 year plan. Here’s how that goes:

Year 1: Make proposal based on costs. Find someone in Puna who will sell you some package with some bright, smiling, educated people who speak whatever language and accent that makes your pitch. Proposals are made, and attached to next year’s budget.

Year 2: Start the crossover. Puna Corp has swapped out the “demo people” for their core chum bucket. Sometimes, they don’t even change the names. How is an American gonna know that the Vivek Patel they saw in the demo is not the same guy named Vivek Patel who is working with your bitter employees who see the writing on the wall? Sadly to many who don’t care, “they all look/sound alike.” Puna is a product, their employees are a static pattern of commodity. Your people say they are shit, but, “oh, those grumbling employees. Your job is safe! We can’t fire you, you are too valuable!”

Year 3: The crossover has gone badly, but you are already looking for the next company to work for. The layoffs happen, and all the good folks are gone, and replaced by the Puna Corp folks. Things start to go badly, but you already got one foot out the door, charming your way into another company.

Year 4: You’re gone. Your legacy is that you saved a butt-ton of money. You are a success! The product is shit, but that’s not your problem. By the time the company realizes the tragedy, it’s middle manager versus middle manager, all backstabbing and jumping ship. Customers don’t matter, marketing covers up the satisfaction. “Wow,” you say. “Things sure when to shit THE MOMENT I LEFT.” You look fantastic! When you were there, you saved money! When you left, it all went downhill! You are a goddamn rockstar. Then repeat.

I have seen this happen since the 90s with a lot of tech folks. Everyone thinking short term for themselves. Only the customers get screwed via enshittification.

It would have been the 1990s by ADC, a street map company local to this area (and possibly other cities).