• 0 Posts
  • 919 Comments
Joined 2 年前
cake
Cake day: 2023年6月12日

help-circle
  • I dunno how long that’s been for you, but I got too injured while on the ROTP programme (that’s how poor kids go to school). And I was out with some non-transferrable skills (5.56 percussion, anyone? One-armed sign language?), surfing a couch and a little broken. This was early '90s.

    You know what? You’re gonna second guess things for a long while, deciding things were or were not your fault. You’re gonna feel a little ‘flat’ about things for some time as well. That’s common and I remember it well. Like, the house could fall down around me and I was so dampered for adrenaline that I’d reeeeally not care but probably slowly cope with that too.

    Save the manga. You’re maybe gonna like it again, along with other things too. Maybe, maybe not, but keep the options open.

    Boot tears you down to pieces so they can build a soldier out of you, and getting dropped from a programme abruptly is super-jarring, but you have an opportunity to rebuild yourself as a pretty awesome human again. Decide who you are After Basic, take the good lessons and try to shed the OCD of boot and, um, Other Bad Shit, and see if you can build a You that is driven and goal-focused, but also invested in fluffy civvy stuff.

    Then - in your own time - decide whats next with the help of your friends.




  • Ha! I use it to write Ansible.

    In my case, YAML is a tool of Satan and Ansible is its 2001-era minion of stupid, so when I need to write Ansible I let the robots do that for me and save my sanity.

    I understand that will make me less likely to ever learn Ansible, if I use a bot to write the ‘code’ for me; and I consider that to be another benefit as I don’t need to develop a pot habit later, in the hopes of killing the brain cells that record my memory of learning Ansible.








  • If we keep acting like anyone with a D by their name is perfect we’ll never fix shit.

    Progressives usually don’t (value based on group membership). You know those disappointments only got into power because they were the least-bad option. Because progressives don’t value loyalty; progressives need to fall in love.

    Thing is, they have just one option, and it’s merely the lesser of two evils. They need more less-evil choices. They need more people saying “people have the right to defend their land” and blow the dog whistle, and then say “that’s not their land. That’s not defending” when they get in.

    I say that’s 45 disappointments, but it’s only 45. Promise me you’ll get it to 44 and lower if they’re in your area. Do what you can, at least.

    This isn’t a movie script; it’s a continual slog with a progress report every 2 years. This is one time when “line must go up” from the pit it’s in now. So. And I mean this after all that rambling.

    Primary their asses.





  • corsicanguppy@lemmy.catoSelfhosted@lemmy.worldRelease frequency preferences
    link
    fedilink
    English
    arrow-up
    4
    arrow-down
    1
    ·
    edit-2
    13 天前

    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.