“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.
everything controlled by our government is
The questions been beggared.
That’s kinda it. Been working a lot.
Still requires docker?
Ah. So MM’s still in the sidelines and IBM still pulling strings, so little chance of ditching fucking systemd in Fedora, and thus RedHat. That’s the one good thing I can see from a regime change: improvement of the codebase by, for example, pruning pet projects when the pets leave for Microsoft.
You’re debating whether not-3 is the same as “less than three”.
It’s => but not <= so it’s not ==.
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.
The Killing with Joel Kinnaman and Mireille Enos. What a rough series but those two really seemed to mesh well.
It’s not evil. It’s merely
and now RedHat’s wunderkinder has moved onto Microsoft where he’s a better fit. Ideally, we can go back to Linux again.
Simple.
As someone who ran security for an enterprise OS company, I can’t see why there’s any debate on this. Are we used to choosing comfy things despite the safety concerns, now, or just when Lennart shits them out?
Yeah. They’re the bigger threat. Sure.
someone who picked their team and now hates all the other team
False. All the other teams are varying degrees of well-built. Systemd is badly-built by bad people and pushed via market dominance. It’s the Internet Explorer of inits.
Nothing new, just forgotten.
Aw jeez not this again.
emails
Look; If you can’t spell the word, I’m not going to assume you’re an expert in it.
You say “secede” funny.
If they truly are business orientated let them invent something and go market it and be an actual entrepreneur in the real world,
They’re going to do none of this, even if you did the hard work of writing all those words. No dentist wants to take his 9 years of schooling - or something equally ridiculous - and gamble his food security on a 99%-failure like every other startup. It’s a non-starter.
Yeah, they’re running extortion rackets, sure. But for any dentist who survived that gauntlet, let him cook. Don’t hate the playa`. Change the system and force them into a humane model.
Survey seems broken. JavaScript crutches?
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.