I remember interviewing at Google years ago (if you’re keeping score, it was 2012/2013 just before their stock hiccupped and my onboarding was killed as I was only a 97% fit), and the guy was religious about page load times. “We cut 200 lines of code if it’ll give us a millisecond of page load speed”, that kind of thing.

How they’ve fallen.

If you believe my therapist friend who is also non-normative in a relevant fashion, demands for pronouns are often ‘othering’ in result, and thus go from farce to force.

So, I write fewer email.

Jira, which is available as on-prem version.

Check again.

Either way, I’d consider moving off Jira.

2025’s version of Gone Goat Farming ?

Ha! My deepest experience with postgres was watching it fall over and wedge daily when run behind red hat’s satellite (the flailing lame foreman one, not spacewalk).

Wow, was it ever a dog. Yeah, I get it: the company who shat Systemd on the planet can’t be asked to do much better, but still.

1. One party continually tries to pass legislation for safety nets and consolidated services and is blocked by the party that’s controlled the show for almost 40 years

2. That party goes for tax cuts and havens to keep it’s rich donors happy while blocking anything that helps the other 99%

3. You: “both sides. I’m smarter than all of you”

Really?

I wish I lived in a world where this seemed absurd.

They hate us first.

Source: lived there 8 years.

Stayed with FB despite Cambridge because Portal TV.

I’ll still maintain an account because Portal TV.

It’s a gorgeous product done wrong by meta and in need of a cloning.

Yeah. Threats are speech that attracts repercussions.

Who says NAS to mean anything other than Network-Attached Storage?!?

“When I say left, I kinda mean right half the time almost.”

The wd60efrx is a 5400 with 0.00% failure. I think all the WD reds were 5400.

Criticizing Ubuntu is hivemind? Wow. Now do Systemd critics.

what has meta done that was good

Facebook Portal TV. What a great device: “call mom” and it calls on her TV where she can see whom it is instead of her tiny phone screen. The cam was good, it panned and zoomed to focus on the speaker really well, and the sound was great. It’s a small unit that also does zoom and prime and Netflix and Plex. The M assistant is good, but it basically leverages a built-in Alexa for external control.

Then Cambridge analytica. Every new review is like “this is an amazing device, but don’t get it because fuck Facebook.”

Now it’s been orphaned: voice control is busted. No apps updated or installed. But if you had the apps installed they still work. TV calling still works if my mom can find and figure the remote.

And there’s been no replacement tech, which makes this unit that much better than everything else since it’s peerless.

There ya go. We bought 1 and then 3 more for family just before COVID.

Iso27002 fail.

• docker kills validation, so we can’t assure consistency as we’re essentially dividing by plaid.
• npm can’t be run in prod due to inconsistency of upstream, and dev tools which are verboten in stage/prod.

an open-source social media scheduling tool.

Pshaw! Didn’t you read the tin? It’s the ultimate open source social media scheduling tool.

I do. I will. Sorry it triggers ya.

Except, I won’t wait for an answer. In my job it just means a wall of text is incoming, so come back in like a minute.

“as above, so below”

If your test and prod are different, you need to ensure your manager understands the risks you will not magically account for. It’s on their head when it fucks up.

Testing in prod requires its own separate indemnification because that’s also only ever after direct orders.

It’s great to use an editor designed and built when vietnam and leaded gas were all the rage.

As an end-user (that is, the IT staff that will be deploying/managing things), I prefer less-frequent releases. I’d love to see 1 or 2 releases a year for all software

The hard floor for release frequency must always be “as security issues are fixed”, and those will rarely be infrequent in our current environment of ever-shifting dependencies.

If your environment is struggling to keep up with patching, you need to analyze that process and find out why it’s so arduous.

As an example, I took a shop from a completely manual patch slog 10 years ago to a 97% never-touch automated process. It was hard with approvals and routines, but the numbers backed me up. When I left 2 years ago, the humans had little to do beyond validation.

The sad news is, the great loss of mentors after Y2K will be seen again after RTO, and we’re not going to fix the fundamental problems that enable longer release cycles in a safe way; and so shorter update cadence will be our reality if we want to stay safe …

… and stay bleeding-edge. Shifting from feature-driven releases to only bugfix-driven releases means no churn for features, but that’s a different kind of rebasing. It’s the third leg of the shine-safe-slack pyramid; choose 2.