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.

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.

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.

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.

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.

Well, it really reminds me of that famous GreenText about pickles

Well, they may like the attention and validation it brings. I knew someone who was asexual that had a lot of dotcom money. He loved to go to Vegas and gamble. He knew the house was stacked against him. He knew that the girls who sat on his lap only liked him for his money. He still loved the attention he got when he tipped big. I saw him tip a waiter $200 on a $150 meal. He LOVED it. And why?

"I used to be poor. I was a nobody. Now I make people happy with my money, and I feel good about myself."

Can't beat that.

When I was 19, I had friends from high school who were still younger, and one of them was my friend Julie who had helicopter parents (she would have been 17-18). I was doing security at an event where the radio headsets we had were super-shitty, and the guy running security was a dumpster fire on his own. Julie's parents forbid her from going to the event, and grounded her to her room. Then her dad called the hotel where the event was being held, was told Julie had "run away" to this event, and that I was somehow responsible. Given she was a minor, the event runners were understandably concerned, although they were frustrated that Julie's dad was unable to describe her in a way that was useful: "Asian, wearing black, or a tee-shirt, or something. Ask Punkie where she is." So they contacted the head of security to find me on my rounds to see if I knew what this crazy man was talking about. The head of security said "okay" and did nothing.

At some point, the head of security was fired for a variety of reasons, and this increased the level of miscommunication. Meanwhile, Julie's dad was calling every few hours, demanding to know where his daughter was. And soon there was a concerted effort to find me, which was complicated because of the communication issues. By the time someone found me and the connection was made, my response of, "I have no idea, Julie said her dad forbid her coming here," was not what they wanted to hear, and met with skepticism "You're not hiding her, are you? Like she ran away with you in some tryst? She's 17 and you're 19, that could have legal ramifications!" No. We're platonic friends, I don't know where she is. if I tried to bonk the poor woman, she'd clobber me.

Meanwhile, Julie's dad finds Julie in her bedroom, right where he left her. Julie later told me that she was ignoring her dad calling for her, and didn't "come downstairs" like he demanded because she assumed it was a trap to get her punished for leaving her bedroom while she was grounded. So naturally, her dad assumed she wasn't in the house. Because he called for her and she didn't answer.

Poor Julie. Her parents were crazy-nuts.

I can answer this: my son was born in 1990. We were extremely poor.

We had midwives help us out as best they could, to the tune of about $3200 at the time. The birth got complicated due to a variety of health factors, and both my son and wife almost died (not because of the midwives). Luckily the midwives had a direct line to Georgetown Hospital, and the cesarean was done there. The total hospital bill was $58,000, or $138k in today's money, although hospital costs have rose much higher vs inflation, so maybe it would be in the $200k range now. She was in the ICU for a week, hospital for another week, our son for about 3 weeks.

My wife job didn't have health insurance, because it wasn't required back then. Because she was gone a week, her job fired her for an unexcused absence. Oddly enough, this made her unemployed and Washington DC had some law (or rule or something) that immediately dropped the hospital bills because of her unemployment. In the end, we had to pay $15k to about two dozen practices who individually sued us, which took 7 years to pay off and a lot of court visits and wage garnishments. It financially ruined us, pretty much. Both suffered a lot afterwards because we just couldn't afford minimal care. It was hellish. I can't imagine how much worse it would be today. We got evicted from our apartment, and lived in government housing for six years.

So, yeah. Don't have a baby in America unless you can guarantee it will be healthy and you have a lot of money. Most of my friends don't have kids, they simply can't afford it and look at it like the previous generation looked at concepts like summer homes and yachts. Nice luxuries, but way out of affordabilty.

I was burned afoul by a former admin who, instead of diagnosing why a mail service was failing, labeled a script as a /etc/cron.d file entry as "..." (three dots) which, unless you were careful, you'd never notice in an "ls " listing casually. The cron job ran a script with a similar name which he ran once every 5 minutes. It would launch the mail service, but simultaneous services were not allowed to run on the same box, so if it was running, nothing would happen, although this later explained hundreds of "[program] service is already running" errors in our logs. It was every 5 minutes because our solarwinds check would only notice if the service had been down for 5 minutes. The reason why the service was crashing was later fixed in a patch, but nobody knew about this little "helper" script for years.

Until one day, we had a service failover from primary to backup. Normally, we had two mail servers servers behind a load balancer. It would serve only the IP that was reporting as up. Before, we manually disabled the other network port, but this time, that step was forgotten, so BOTH IPs were listening. We shut down the primary mail service, but after 5 minutes, it came back up. The mail software would sync all the mail from one server to the other (like primary to backup, or reversed, but one way only). With both up, the load balancer just sent traffic to a random one.

So now, both IPs received and sent mail, along with web interface users could use. But now, with mail going to both, it created mass confusion, and the mailbox sync was copying from backup to primary. Mail would appear and disappear randomly, and if it disappeared, it was because backup was syncing to primary. It was slow, and the first people to notice were the scant IMAP customers over the next several days. Those customers were always complaining because they had old and cranky systems, and our weekend customer service just told them to wait until Monday. But then more and more POP3 customers started to notice, and after 5 days had passed, we figured out what had happened. And we only did Netbackups every week, so now thousands of legitimate emails were lost for good over 3000 customers. A lot of them were lawyers.

Oof.

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

Moe (萌え, Japanese pronunciation: [mo.e] ⓘ), sometimes romanized as moé, is a Japanese word that refers to feelings of strong affection mainly towards characters in anime, manga, video games, and other media directed at the otaku market. Moe, however, has also gained usage to refer to feelings of affection towards any subject.

Moe is related to neoteny and the feeling of "cuteness" a character can evoke. The word moe originated in the late 1980s and early 1990s in Japan and is of uncertain origin, although there are several theories on how it came into use. Moe characters have expanded through Japanese media, and the concept has been commercialised. Contests, both online and in the real world, exist for moe-styled things, including one run by one of the Japanese game rating boards. Various notable commentators such as Tamaki Saitō, Hiroki Azuma, and Kazuya Tsurumaki have also given their take on moe and its meaning.

https://en.wikipedia.org/wiki/Moe_(slang)

• Panic at the Cisco

I used to troll my roommate: I have a Multi-Band wireless access point, and I would name other networks stuff to mess with them. They are from Louisiana, and are very proud of their culinary roots. One day, they came back from a trip with the relatives, and brought home some boudin, which I cooked and served with rice. I thought it was sausage, but it's a blend of pork cooked down with onions, peppers, seasonings, AND cooked rice, so serving it with rice was redundant, apparently. They got SO ANGRY, that to this day, I am not allowed to eat it in front of them, so I have been trolling them for "boudin with rice" everywhere I can. When they still lived with me, I changed the "ancillary network names" shit like, "Boudin with rice," and "Mild crawfish with ketchup," and "Campbell's New England Gumbo" and a ton of other culinary "bastardizations" of authentic Louisiana cooking. So every time they were on their laptop, I'd hear a "... Boudin corn dog--OH MY GOD PUNKIE YOU BASTARD!!! AAUGH!!!"

My first wife is suddenly alive and meets my second wife. Awkward.

What might be worse is if someone was there that you didn't know that you had sex with. Like some random person who raped you while you were unconscious after a party in college, or your uncle from your childhood.

It's a myriad of issues.

1. Farts are not considered to be socially acceptable, and thus one loses "social status" if one farts. So at an early age, you learn to hold it in. This has been going on since antiquity, as it is the source of the oldest humor seen via graffiti.
2. You can get in trouble if you fart (I guess because of #1). I knew of a few times someone farted, and the teacher sent them out for punishment for "disrupting class."
3. People learn to fart silently, usually through experimentation and training to avoid item #1.

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.

Just in case people actually think this is a good idea: do not. Plastic, uncontrolled spray, and blowback is just really shooting uncontrolled fire in all directions. It works in your cartoon world head, but I know someone who tried and suddenly the failure (like escaping fumes around the holder, gasoline versus rubber gaskets meant for water) make you go, "Oh. Right." Thankfully, they only got first degree burns on their face, head, hands, and arms, a weird balding patterns, and missing eyebrows. Thankfully, someone had an ABC fire extinguisher nearby. Yes, alcohol was involved.

The ones I have seen that work involve metal tubing and a secondary mixing of forced air along with a special fuel. https://www.recoilweb.com/flamethrowers-once-tools-of-war-now-toys-67763.html

Scissors and knives.

I used to sell high end stuff like that, and let me tell you, there's a trope about crafters considering murder when someone uses their, say, fabric scissors or sewing scissors to cut paper or something that ruins them. For scissors, however, nothing is more expensive and delicate than a decent set of haircutting shears used by professional hair stylists. Fuck, some go into the HUNDREDS of dollars or more. And then some clown wants to cut some box open with them.

Knives, though. Good set of chefs knives goes into the thousands. Like the kind used by professional chefs. I had some chef clients who tell me horror stories about some kitchen yokel using a $350 hand forged Santoku to stab open a can of tomato paste or toss into a cutting board like a throwing knife.

But even basic knives. People using them as prybars, hammers, screwdrivers, and tossing them in a drawer with other metal rattling around.

In the late 1980s, I had a roommate who graduated with a business degree and got recruited for a government contractor right out of college. She packed up her life and moved to the DC area. A month into her new job, the contract was pulled. But because she had a clause in the recruitment contract, they couldn't fire her. But they had no work for her, either. So she had to come to work every weekday, 9-5. She'd sit at her desk with nothing to do. They didn't ask her to look busy, just present.

She read about 3-5 novels a week. Over the next few months, we watched her get more and more depressed. She'd complain about her situation, but it fell on deaf ears. "Must be nice," people said in jealousy. "Get paid to do nothing." She became despondent in the lack of people's sympathy. "Nobody understands how much this sucks!"

Eventually, she got a new job. Her mood vastly improved.

I'll never forget that lesson. People need to feel useful, productive. Sitting at a desk with nothing to do, no purpose, no validation. It will destroy you.

Having seen these in a demo, they have weight triggers to prevent that. Also in or demo, one got stuck on a power cord, the other on a electrical plate in the floor.

Solicitation at my door.

1. I have a sign, on my door, that says "no solicitors."
2. By law, all solicitors must have a solicitation license from the county on their person. It's a photo ID issued by the county. None of them do.
3. I work from home with a handicapped wife. Do not bother me.

I give them one chance to go away. If they press it, I demand to see their license, which "Oh it's in the truck" or "it's in the office" or "I am not soliciting, I am giving you a FREE ESTIMATE..." I call the cops. Fuck em. Non-emergency number, I state a description of a suspicious man who refused to show me a solicitation license, and kept asking me to open my door. I describe the direction they are going with dates, streets, and times.

A few get nabbed. Some of these guys are known to the police because they are possibly casing your house and they have a ton of camera evidence of them peeping in windows and gates.

I worked for a large computer company in the late 90s, early 2000s. When XP came out, they said there would be no site licensing. This meant we had to keep track of license keys for thousands upon thousands of systems, costing millions. This was before KMS or anything.

"Nothing we can do," Microsoft said. "We have no gate key."

Our server farms at the time were 40% Windows NT 4, 55% Sun systems, and 5% Linux. So we said, "okay," and called Red Hat. In a year, our back end was 60% Sun, 35% Linux, and 5% Windows NT. We were already in talks to start switching to Linux workstations for desktops.

"Oh, you mean this gate key," said Microsoft.

Asshats. They lost our server business, but let us use XP with a site license.

The weird thing is this is the exact argument many people give for socialized medicine: the wait times. "Imagine if the hospitals were run with the efficiency of the DMV. A,trak, or the Post Office," meant as a negative slant. "Imagine if FedEx was the only game in town, and to mail letter was $10, and to receive mail and packages was a $25/mo service charge, plus fees for every item delivered."

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.

This could also be survivors bias.

Now, in my beliefs, I agree with you, having also lived that dialup BBS life in the late 80s and early 90s. But part of me always triggers when I hear "when I was a kid, I [did thing] and I turned out fine!" Because maybe we did, and those that didn't aren't posting about it. The same arguments are used about bike helmets and seat belts.

The social media of today is like comparing "I ate hamburgers as a kid, and I turned out fine," and comparing them to eating fast food burgers every day. There's a difference in volume, calories, and lifestyle.

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.

Try making $150k in a "reasonably priced area." It can be done, but is not the norm. The problem is that to make a good salary, you have to be in a place that pays those wages. Obviously, this attracts more people, so real estate is more expensive.

The trick is to make $150k in some kind of sweet spot where housing does not compensate. But it's always a moving target and is extremely difficult. Then in you lose your job? Start all over again.

1. Things like CNC machines and proprietary interfaces to TOL equipment, like bus fare systems, message boards, etc.
2. Don't connect them to the Internet (most can't, anyway, but some systems use a run-of-the-mill PC, so...)
3. Don't install anything on them that wasn't supposed to be installed, even wallpaper as this could fuck up the resolution of a small 240 x 180 screen

They had a multimillion dollar transit project near where I loved, like $112 million to replace a train station, a subway stop, and a major bus terminal to combine them into a single entity near Washington DC. They projected 3 years from start to finish, but it took almost 7. They had to reroute the entire bus terminal to surrounding streets and parking garages, which was a traffic nightmare. People using the train station or subway had to reroute their walk sometimes up to a mile off their present walk. While doing demolition, they found that the previous bus terminal was on the site of an old gas station which had been improperly sealed off: they just filled the tanks with concrete. Underneath that, they found tons of the the natural mineral serpentine, which naturally contains asbestos. So now they had a biological hazard which they had spent the last few months blowing up with dynamite into the surrounding city. After that was cleaned up and sealed, The got underway.

There were a ton of other mistakes, but when it was completed, they found defects. The superstructure is made of concrete and thus construction specifications were replete with engineering criteria for the composition of the concrete, and its pouring, curing and tensioning. The Inspector General systematically examined 22 project management and control points from the time concrete was mixed until the time it was ready for final inspection. 14 of 22 control points that should have minimized defects were weak or ineffective. Those defects may require recurring engineering inspections, higher maintenance costs, and they could shorten the planned 50-year useful life. In addition, the IG described the risk of concrete falling onto transit-center patrons.

The entire thing was a huge boondoggle costing the downtown untold millions into the future.

No age limit in this household. I'd say "just show up with a bag," but I just gave treats so some 4yo with no bag. If an adult asked? They'd get them.

I just want to be kind. I wasn't allowed to trick or treat as a kid. I did as a teen, and you know what? Nobody cared how old our group was. We got candy like the rest of them. God bless those neighbors.

And God bless Halloween.

This reminds me of some Ohio Christian university advertising racial diversity in all their media, and some guy exposed them as having exactly three non-white students, all whom turned out to be shills from another country who were technically employees.

About 20 years ago, I used to keep Lego Bionicles at my desk, but had to stop because pranksters would do this, and then HR would make negative comments.

A lot of outsourcers do this. Here's my experience with a few companies.

• The "team" you meet are competent, English speaking fronts. They are the demo models of the people who will work on your projects.

• After the contract is signed, these people are swapped out with randos of varying competence.

• In some cases, some of these randos are further hidden behind aliases: people with names that are actually more than one person sharing logins and passwords.

• They will string you along, trying to charge maximum hours worked without regards to product or services delivered.

• Most of these companies have a "bucket of crabs" mentality: the managers are horrible, the staff incompetent, and once the gain some skill, they leave for better companies. They backstab one another, hijack projects to fuck over coworkers, and lie and cover their tracks. Some of this is cultural, like a caste system, while some are just racist.

At one time, these people were pretty good, but they realized they had skills and left for other countries for better pay and better working conditions. The bids got more and more competitive, cutting costs until they were literally filled with low-skilled labor who can't be promoted or leave for economic or competence reasons.

My wife stayed in a rural town near Shichigahama for a week. Nobody spoke English except a few students. But the citizens did speak Japanese louder and slower, showing that's a universal trait. It actually helped, as my wife knew SOME Japanese.

The stupid thing is that they could have approached this in a much less dickish manner. Seriously. First, they are making money off us as it is with their demographics and the fact they are not utilizing this cash cow as before means they have gotten too greedy for their own good, or mismanaging funds which is a completely unrelated problem. Long ads, unskippable ads, expensive premium. This is the beginning of the end of something they used to offer as free, resting on their laurels as a monopoly, like the airline industry. When they are now practically forcing the cobra effect. Eventually, it will get so silly, it will go the way of the dod like Angelfire. AOL, and Geocities. Or, soon, Netflix.

I would have started it similar to Patreon, like, "by donating $1/mo, you can support artists like this," and incentivize the publishers with monetary gain and higher search results. Nobody is gonna miss $1 or $12/year. You multiply that by millions of viewers, that's millions of dollars on top of their demographics. Second, they could have had a 5 second bumper, similar to PBS, like "This and other find content is brought to you by Exxon and the Chubb group" or whatever. Five seconds. Front and back. Not enough to cause outrage. Skippable, but not so annoying, everyone skips.

Friend of mines teen daughter did something similar. She posted on Instagram that she was at home, bored, fml, and all that. Sadly, some of her friends posted from the party. With her tagged.

"OMG SHOTS WITH #STACY!!! BFF AND JDC!!!"

Like, pictures of her and everything. Her dad made her write 100 times, "I need better friends" as part of her punishment, lol.

I pretend to be another call center. Or an IVR.

"Thank you for calling Punkadye Laboratories and Archives. My name is Terry. May I have your GSN number please?"

I don't know what a GSN number is; just something that I made up. Once in a while, I get an actual person, but I insist that I have "their latest GSN or a recent invoice," before I continue. I have "a call center voice," and can reasonably fake gender neutral.

Sometimes I answer, "Thank you for calling Punkadye Laboratories and Archives. Please listen closely, as our menu options recently changed. If you know the number of your party's extension, you may dial it at any time. If this is a billing question, please press 1. If this is technical support, please press 2."

Rarely does the call get past the press one part. Often this cuts the latest wave of calls quickly.

I worked in a job with build scripts. Developers would list what they wanted in a drop-down menu on a website, with very few "fill in the blanks." This would create a template, which was sanity-checked.

One of the "fill in the blanks" was "home directory of user, if not default /home/username." Some people filled it in, some didn't. A lot of "users" might be apps with /home being "/opt/appname" "/var/www/html" or something. We checked to make sure that directory existed, if not, create, and set permissions. Easy peasy, all automated. Ran this lots of times.

Then one day, the script failed. Borked the whole box. Sometimes the VM was corrupt, so delete VM and try again. Usually worked. But this time, the build kept failing. The box went down. Wasn't even bootable. This happened several times with this one build. So we mounted the borked drive under a new VM and checked out the logs. Just like the dessert stage of Willy Wonka chewing gum, it always failed at the last stage: making /home directories.

It would create them, then halt that it could not find bash. We looked for bash on the bad drive, and it was the usual /bin/bash shortcut to /usr/bin/bash and we were truly puzzled. I did a chroot to the drive and NOTHING worked. It just hung. That was the first clue.

The second was looking through the build script (in bash, which we didn't write) and checking the steps. Looked it the logs. Always died at creating some user named sapadm, the user for the HANA database. Eventually, I checked the configure file, and noticed it was the only user with the odd home directory "/usr/sap." Then it hit me: the permissions.

The script, thinking it was a home directory, did a chmod - R 755 for all directories and chmod - R 644 for all files! That meant, while creating home, it made everything under /usr not executable anymore! Holy shit, no wonder nothing worked! So we commented out that user in the config, ran the build again, and we were good! We created the sapadm by hand, and then later fixed the bug in the script.

SANITIZE YOUR DATA. Or you might turn Violet Beauregarde into a blueberry.

Without going into detail about how their personality types were both wonderful, but clashing, there's the obvious point that my first wife would have to cope that she's been dead for many years and that I moved on. That wouldn't be pleasant. She would probably see me happy with my second wife as happy as I was with her, and think, "what the HELL?" "Well, you died." "Okay," she'd say, and definitely NOT be okay. I might add, "you said I needed to find someone after you're gone," which I think the reality of what that meant in a context in front of her would hit her like an iron fist. We were each other's first, see. My second wife would be gushing towards her, thanking her for everything in an awkward way, because while I was truthful about my previous marriage, I was also really kind. My second wife is also a widow, so she gets it. She credits my wife for "the man I have now," which is true. I am a better person because of my first wife, but I have also changed and "grown" a little since her death. So now, I would be a different person to her. One seasoned by the death of a spouse. That shit changes you.

I think a majority of our discussion would be, "well, what has happened in the world since 2014, then?" and that would be... bad. For all the reasons most people looking outside of this room would know. My first wife would be very upset how things progressed a few years after she died. "Trump? The asshole from The Apprentice?" And so on.

My wives did meet, but didn't know it. My wife was kind of a local celebrity, but my second wife was a vendor IN those circles. I has also met my first wife several times, but only as a character in the background. If that makes sense. We friended because of a local widow's group, which she still runs with a friend. We didn't even start dating until years after both our spouses passed, and only recently remarried. Our friends, many of them mutual since way before, approve of us finding one another.