Linux nerd and consultant. Sci-fi, comedy, and podcast author. Former Katsucon president, former roller derby bouncer. http://punkwalrus.net

  • 1 Post
  • 18 Comments
Joined 1 year ago
cake
Cake day: June 22nd, 2023

help-circle


  • One revolution I have realized in baking is the recent trend to start talking about weight and not volume in recipes for certain dry ingredients like flour. Three cups of fluffy sifted flour is a lot less flour than three cups of densely packed flour. Same with brown sugar, or wondering if you need a “flat teaspoon” vs. a “heaping teaspoon” of something.


  • This was also where “yo momma” insults were also invisible to me. Like, “You don’t even know my mother, you’re just saying that and it makes no sense.” It wasn’t a trigger for me like it was other kids. I saw it for what it was. I’d tell my friends, “they just say that to get you mad, don’t listen,” but they’d get mad anyway. It’s like they couldn’t help it. I think dares were in that headspace as well.

    I wasn’t popular growing up. I was really awkward and non-athletic, so I didn’t bow to peer pressure as much as the other kids. I was going to be unpopular either way, so…




  • This sounds kind of sad, but bear with me. This was c. 1976-1980.

    My father was mostly absent, but I prefered his neglect to his abuse, so that was okay. He’d go on business trips a lot. My mom was an alcoholic, and sometimes she’d be passed out for days. I grew up an only child in a suburban home, and some weekends a year, I had the house to myself. From age 8-12, I had a few weekends here and there where fortune fell upon me and I’d be alone in the house with no real responsibilities. Friday night home from school to Monday morning going to school, all I had to do was check if my mother was still passed out, and if so, it was like one long vacation from my life to be myself. Bonus if there was still food in the house, which usually there was something I could cook myself.

    I wasn’t allowed to watch TV as a kid, except sanctioned PBS shows, but we had a small B&W TV in the kitchen for my mom’s soap operas and cooking shows. I’d drag up all my Legos, pour them on the kitchen table, and watch “illegal TV” all weekend while building stuff with my Legos. Eating when I wanted to, or not, and I had free reign of pretty much anything there.

    My positive childhood memories are scant and few, and most are just things like that. Like “sometimes the sun came out, if only for a brief time, before the storms returned.” I have a lot more as an adult.





  • 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.



  • 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.


  • The thing is that for a majority of cases, this is all one needs to know about git for their job. Knowing git add, git -m commit “Change text”, git push, git branch, git checkout , is most of what a lone programmer does on their code.

    Where it gets complicated real fast is collaboration on the same branch. Merge conflicts, outdated pulls, “clever shortcuts,” hacks done by programmers who “kindof” know git at an advanced level, those who don’t understand “least surprise,” and those who cut and paste fixes from Stackexchange or ChatGPT. Plus who has admin access to “undo your changes” so all that work you did and pushed is erased and there’s no record of it anymore. And egos of programmers who refuse any changes you make for weird esoteric reasons. I had a programmer lead who rejected any and all code with comments “because I like clean code. If it’s not in the git log, it’s not a comment.” And his git comments were frustratingly vague and brief. “Fixed issue with ssl python libs,” or “Minor bugfixes.”


  • I married my first wife when she was 18 and I was 20. We went through a lot of hardship. It should not have worked out: we were both poor, from broken homes, in an LDR from different worlds. She was the popular girl, I was a shy and awkward nerd. When we got married, we had only been in one another’s presence for a few weeks total. I went into the marriage not expecting a path or plan, as my parents were toxic which ended with my mother’s suicide, and my mother in law had been married 4 times before she became single for the last time. None of us had healthy marriages to draw from. At our wedding, her relatives even said, “I give it two years, tops.” We were desperately poor, and struggled most of our marriage with health and money issues.

    But we made it work for 25 years. We’d still be married, but she passed away ten years ago. We became “foxhole buddies,” us against the world.


  • Worked a job where I had to be a Linux admin for a variety of VMs. To access them, I needed an VPN that only worked inside the company LAN, and blocked internet access. it was a 30 day trial license on day 700somthing, so it had a max 5 simultaneous connection limit. Access was from my heavily locked down laptop. Windows 7 with 5 minutes locking Screensaver. The ssh software was an unknown brand, “ssh.exe” which only allowed one connection at a time in a 80 x 24 console window with no ability to copy and paste. This went to a bastion host, an HPUx box on an old csh shell with no write access to your home directory due to a 1.4mb disk quota per user. Only one login per user, ten login max, and the bastion host was the only way to connect to the Linux VMs. Default 5 minute logout for inactivity. No ssh keys allowed. No scripting allowed, was like typing over 9600 baud.

    I quit that job. When asked why, I told them I was a Linux administrator and the job was not allowing me to administrate. I was told “a poor carpenter always blames his tools.” Yeah, fuck you.


  • Concussions. Especially when they are used as plot vehicles where someone is knocked out, and they wake up in a jail cell or whatever.

    If you got hit THAT hard on the head that you’re unconscious and unresponsive for hours? You are going to wake up dizzy, nauseated, and disoriented with a huge headache, loss of motor control, and a disorienting tinnitus. Possibly permanently. Your brain swelled up and cut off blood flow. You might look like a stroke victim. You will not wake up, rub your head, then pick a lock in a dark room and construct a bomb with a gum wrapper and a smoke detector battery. You will weep, vomit, and be unable to walk straight until you get real medical attention.

    Some action stars get knocked out almost every episode. I think MacGyver would have been mentally incapacitated after just a few shows.