• 1 Post
  • 29 Comments
Joined 2 years ago
cake
Cake day: June 12th, 2023

help-circle















  • If we can simply help Americans understand small-s socialism from small-c communism, we’d be in much better shape.

    Because yes, my healthcare is already paid in advance by me and everyone else from our taxes; and my buddy’s emergency Sunday morning quintuple stent install after the widowmaker heart attack and two ambulances and a bed in one hospital before transfer (a third bus) to the regional trauma/cardiac center for the operation and 2 weeks of aftercare was free to him that day – and his only concern was not dying. And that’s not just normal but that’s the general expectation. No monthly subscription, no premium cost, no user fee, just paid-parking and vendor-machine food for visitors not coming in via the train.

    Our upcoming election will gut that, though. Being bankrupt, losing retirement savings and mortgaged to the hilt at 61 is the American dream mr Polievre has for all Canadian plebes.


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



  • corsicanguppy@lemmy.catolinuxmemes@lemmy.worldOrwelluan
    link
    fedilink
    English
    arrow-up
    19
    ·
    4 days ago

    It’s not evil. It’s merely

    • the wrong tool
    • built wrong
    • on wrong principles
    • by a bad team
    • who has poor coding and interaction

    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?