punkwalrus

joined 1 year ago
[–] [email protected] 21 points 3 weeks ago (2 children)

When eventually washed off, the aerogel is handily broken down by soil microbes.

I am not going to claim to be an expert on any of this BUT that wording sounds suspiciously like bullshit. Maybe it's not, but it's one of those phrases that sounds like when vitamin companies claim that more B12 has shown to fix whatever ails you. Or "our plastic is environmentally friendly: 100% recyclable, and breaks down into teeny micro-particles over time, and gets absorbed by the sea life like ordinary sand..."

[–] [email protected] 6 points 1 month ago

That explains why it's so hot outside.

[–] [email protected] 36 points 1 month ago (1 children)

I have had two tech jobs like that, even before COVID, starting in 2016. The first time, it was a company that outgrew their workspace. They put us in 'rent-an-office' spaces for a bit, and then my boss started working from home a few days a week. Then he allowed me to. We moved to a new office, but it was always empty in my section. That was fine, too, but the commute was terrible, so I started doing 2 days a week, then once a week, then a few times a month. I rarely saw my other coworkers in person, and nobody said anything aloud.

The next job started because of COVID, and when they started doing RTO, they also wanted to do "hot desking" (no assigned seating) and open office plans, and I was not having that. I was not going to work in a "cafeteria" like setting. So I got contracted work and have worked from home 100% for several years now. Nobody has office space, and we work all over the world to collaborate. I get paid very well.

I hope i never had to go back to an office. I reach retirement age in about 15 years, and I am hoping to make it.

[–] [email protected] 9 points 3 months ago

Pro Cavity Creeps agenda:

[–] [email protected] 39 points 5 months ago (1 children)
  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
[–] [email protected] 5 points 6 months ago (1 children)

"The price of being right" enters into this as well. It can be very frustrating when you let something go because the minor details do not matter, but being 100% technically correct has hazards of its own in a social narrative.

[–] [email protected] 72 points 6 months ago (18 children)

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

[–] [email protected] 93 points 6 months ago* (last edited 6 months ago) (7 children)

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.

[–] [email protected] 14 points 7 months ago (1 children)

I hate to be honest, but I used Amazon Prime a lot because:

  1. I cannot drive. Thus, getting to the store is difficult.
  2. I must bring in 3-4 items a week, so yeah, I save on shipping.
  3. Auto-subscriptions save a little.
  4. I have priced a lot of stuff over the years, and while Amazon is not always the best, the convenience is impressive.
  5. They have, multiple times, been incredibly helpful with customer service. Like above and beyond.
  6. COVID and nobody masks around here. I have an autoimmune condition, so it's important that I not leave unless it's a medical appointment or similar need.
  7. They just have stuff I can't find anywhere. Yes, as some have said, caveat emptor, but that's true for all the stores.

I also save a shit ton of money. When I used to browse Walmart or Target, I used to buy a lot of shit I didn't need. I don't get as distracted with focused buying. I also order from Aliexpress if I can wait 30 days, and I have only been ripped off three times in several years, for a total of maybe $35.

I'm not saying my way is better, and certainly not if it's better for you, but it's been a godsend to the house-bound.

[–] [email protected] 231 points 7 months ago* (last edited 7 months ago) (2 children)

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.

[–] [email protected] 9 points 8 months ago

It used to be blizzards in the DC area, but with global warming, I haven't seen one since 2016. Hurricanes and tornadoes are rare, but do happen. I suspect hurricanes will become more common. I have rapid "go to bags" and some canned supplies. Generally, with hurricanes you get ample warning. We also have places to go in Appalachia (relatives), so we wouldn't have to shelter.

[–] [email protected] 1 points 8 months ago

Yeah my childhood sucked, and knowing I'd have another 12 years of abuse with nobody taking me seriously because I'm a kid? No thanks. I could put $10mil to good use right now.

view more: next ›