• boblin@infosec.pub
    link
    fedilink
    arrow-up
    60
    arrow-down
    13
    ·
    1 year ago

    You can’t run vmalert without flags

    Running grep without parameters is also pretty fucking useless.

    500 words in to the over 3,000 word dump, I gave up.

    Claims to have a Unix background, doesn’t RTFM.

    Nobody really uses Kubernetes for day-to-day work, and it shows. Where UNIX concepts like files and pipes exist from OS internals up to interaction by actual people, cloud-native tooling feels like it’s meant for bureaucrats in well-paid jobs.

    Translation: Author does not understand APIs.

    Want an asynchronous, hierarchical, recursive, key-value database? With metadata like modified times and access control built-in? Sounds pretty fancy! Files and directories.

    Ok. Now give me high availability, atomic writes to sets of keys, caching, access control…

    I’m ashamed enough that I can’t really apply to these jobs

    This reads as “I applied to the jobs and got rejected. There’s nothing wrong with me, so the jobs must be broken”.

      • xantoxis@lemmy.world
        link
        fedilink
        arrow-up
        18
        ·
        1 year ago

        Eh, I wouldn’t worry too much. I’m 48, and this rant still sounds like “old man yells at cloud” to me too.

        It’s not age, it’s willingness to adapt.

        • IphtashuFitz@lemmy.world
          link
          fedilink
          English
          arrow-up
          3
          ·
          1 year ago

          Exactly. 25 years ago I helped manage a Sun cluster. 20 years ago I was on a team that managed roughly 3000 Linux servers in a data center. We racked them, monitored them, wrote tools to configure & manage them, etc. Ten years ago I helped manage Linux systems that were physically managed by a hosting provider, and we never actually saw/touched any of the hardware.

          Today I help manage hundreds of AWS instances and also use tools/services from providers like Splunk, Akamai, and others. I haven’t seen/touched a physical server in years. It’s now all virtually managed via web portals, API’s, tools like terraform, etc.

  • Throwaway@lemm.ee
    link
    fedilink
    arrow-up
    12
    arrow-down
    1
    ·
    1 year ago

    I swear Im a decent coder, but fuck me if kubernetes and that whole ecosystem just confuses me

    • boblin@infosec.pub
      link
      fedilink
      arrow-up
      11
      ·
      1 year ago

      I am someone with kubernetes in my job title. If you as a developer are expected to know about kubernetes beyond containerizing your application then your company has set itself up for failure. As you aptly said kubernetes is an ecosystem, and the dev portion is a small niche of that.

    • Gsus4@feddit.nl
      link
      fedilink
      arrow-up
      1
      ·
      edit-2
      1 year ago

      What makes DevOps so different from sysadmin? Recruiters always told me “it’s nearly the same”, but I never got the job, so I guess idk.

        • Gsus4@feddit.nl
          link
          fedilink
          arrow-up
          2
          ·
          edit-2
          1 year ago

          Makes sense I didn’t get the job, I only vaguely know the difference and it was mostly theoretical stuff like CI/CD, but those recruiters really wanted to throw me at random interviews to see if I’d stick :D

          PS: sorry I offtopic’ed to recruiter-hating, gonna go find a community for that.

          • toasteecup@lemmy.world
            link
            fedilink
            English
            arrow-up
            2
            ·
            1 year ago

            You good homie. I shit on recruiters frequently. I have them hitting me up all the time for in person stuff from LinkedIn when it actively says no in person stuff

      • ck_@discuss.tchncs.de
        link
        fedilink
        arrow-up
        7
        arrow-down
        1
        ·
        1 year ago

        It’s actually pretty distinct. DevOps refers to the mindset (or philosophy, if you will) of “you build it, you run it”. It boils down to you as a software developer are also responsible for packaging up you masterpiece, pushing it through CI, getting it deployed and making sure it keeps on running smoothly. It is designed to shift responsibilities away from the sysadmin to the developer.

        The problem with this is that it’s not a role or a job title, so recruiters and HR does not know how to work with it. Hence, they invented the DevOps “Role” because it sounds more modern. So in reality its used as a marketing term most of the time. So when someone pitches you a DevOps jobs, this tells you a few things:

        • they don’t know what they are talking about
        • the company behind the offer puts a lot of meaning into titles, which means things will likely be pretty hierarchical even though they claim it won’t be
        • they’ll likely try to pay you less that your worth
  • safjx@lemmy.world
    link
    fedilink
    arrow-up
    11
    arrow-down
    1
    ·
    1 year ago

    “I used to be with ‘it’, but then they changed what ‘it’ was. Now what I’m with isn’t ‘it’ anymore and what’s ‘it’ seems weird and scary. It’ll happen to you!”

    Literally old man yells at cloud

  • TCB13@lemmy.world
    link
    fedilink
    English
    arrow-up
    9
    arrow-down
    1
    ·
    edit-2
    1 year ago

    “Clould-native” software co-exists with corporate jargon. They obscure and complicate in the interest of perpetuating lucrative contracts over productive environments.

    “Cloud Engineers” get paid $150K+ to fiddle with these strings and make sure it’s all escaped/delimited correctly in YAML files. It’s a fucking mess. I’m ashamed enough that I can’t really apply to these jobs. Maybe writing and running software on servers in the commercial world is not a good fit for someone like me who despises corporate jargon.

    This.