Not as familiar with WordPress, but if that’s the case, yeah, I don’t have high hopes for this going well…

Not as drastic as the headline makes it out to be, or at least so they claim.

“We acquired Tumblr to benefit from its differences and strengths, not to water it down. We love Tumblr’s streamlined posting experience and its current product direction,” the post explained. “We’re not changing that. We’re talking about running Tumblr’s backend on WordPress. You won’t even notice a difference from the outside,” it noted.

We’ll see how that actually works out. Tumblr’s backend has always seemed rather… makeshift, so I’m curious to see how they manage to do that. Given Tumblr’s technical eccentricities, a backend migration could probably do a lot of good for the functionality of the site, if done properly. I have my doubts that WordPress’ engineers will be given the time and resources to do a full overhaul/refactor though, so I’m fully expecting even more janky, barely functional code stapling the two systems together.

Is this implying that a publicly-traded corporation whose software is installed on millions of computers around the world has the same level of agency and responsibility as a preschooler?

I mean, yes, Microsoft bears responsibility for blindly accepting whatever deployment package CrowdStrike gave it and immediately yeeting it out to 100% of customers via Windows Update without any kind of validation or incremental rollout, and should probably be sued for it. That still doesn’t negate the complete and catastrophic failures at every step of the development process on the part of CrowdStrike. It takes a lot of people to fuck up this bad.

Is the 4x10 really worth the extra day off? Tbh I’m not sure it would work very well for me… I find just one 10-hour day to be kinda draining, so doing that 4 times a week every week feels like it might just cancel out any benefits of the extra day off.

Don’t most indemnity clauses have exceptions for gross negligence? Pushing out an update this destructive without it getting caught by any quality control checks sure seems grossly negligent.

Reading into the updates some more… I’m starting to think this might just destroy CloudStrike as a company altogether. Between the mountain of lawsuits almost certainly incoming and the total destruction of any public trust in the company, I don’t see how they survive this. Just absolutely catastrophic on all fronts.

Huh. I guess this explains why the monitor outside of my flight gate tonight started BSoD looping. And may also explain why my flight was delayed by an additional hour and a half…

It’s honestly incredible that Bing even still exists, much less is still being actively being pushed by M$

Good to see they’re branching out with their business model. Can’t just commit to a single strategy these days. Sometimes it helps to rebase your priorities to avoid creating new issues.

Ok, bad jokes aside, how did it taste?

If you do the first promotion assignment for a class, you’ll get an extra active perk slot on that miner, but other than that, overclocks will be the main form of further progression.

Bugs in tests aren’t necessarily exceptions. You could be incorrectly setting up your function inputs, or just making the wrong assertions.

I don’t really get how “overt racism in a job description” is programmer humor, but alright

deleted by creator

No resolution of tech debt, ONLY DELIVER

Then another message popped up. This time with a console.warn() logging level, so I just couldn’t ignore it.

That’s how you know this one’s fake. Most unrealistic part of the whole story.

It does some funky things with type coercion and comparison which I don’t particularly like, but I generally understand why it does things that way.

A lot of the weird quirks of JS come from the desire to avoid completely blowing up and crashing as much as possible, which makes sense in a web dev context. Forcing weird operations to at least return something can prevent an unhandled error state in a single component from causing an entire page to crash, even if that component ends up malfunctioning as a result.

And WanderingDwarfMiner. Rock and Stone!