• 0 Posts
  • 52 Comments
Joined 1 year ago
cake
Cake day: September 4th, 2023

help-circle










  • rainynight65@feddit.detoMemes@lemmy.mlwater...
    link
    fedilink
    arrow-up
    2
    ·
    5 months ago

    My in-laws brought me back a pack of 4 different craft beers from a trip recently. I can’t drink and enjoy them - way too hoppy. Even the Pilsner - and I like a good Pilsner - was not enjoyable at all. The one that’s left is the dark beer - going to be an expensive dirty Diesel one day.


  • Any company with reasonably involved processes (read: more than three steps) should have clearly documented SOPs, policies and process documentation. This has nothing to do with the level people are at. I’m at senior level and sure as shit don’t remember every detail of something that was verbally communicated to me months ago unless I do it every single day, and even that’s error-prone. I write step by step instructions on processes for myself and everyone else.

    Benefits of this approach:

    • It’s not stuck in my or anyone else’s head, but clearly spelled out
    • people can follow the process again and again, no matter how much time passes between each time - you’d be surprised how much people forget if they don’t do something on a daily basis
    • clear documentation removes doubt
    • clear documentation is beneficial to newly onboarded staff. Nobody gives them a half-baked version scraped together from memory fragments
    • people can point out potential issues with the process, and the documentation can be amended/updated
    • I myself can go back to it if I have even the slightest amount of doubt on a detail.

    Drawbacks of this approach:

    • someone has to write the document
    • someone has to maintain it


  • The difference is, Devops isn’t a bubble that everyone is waiting for to pop. I’ve been in that field for over ten years now, and properly implemented it is a net gain for everyone who does it. The reason companies are falling over themselves trying to hire ‘Devops’ is because they still haven’t properly cottoned on to the concept but are afraid of falling behind. And yes, I can absolutely attest to the fact that Devops is a tough market to hire in at the moment, that there are a lot of places who don’t have the first clue about what Devops really is, and - similarly to Agile - think they can add some buzzwords to their toolchain and call Bob their uncle. And there are a lot of candidates who somehow acquired a Devopsy title in all that chaos, but all their CVs have are tech buzzwords, and when you interview them they’re clueless. That doesn’t change the fact that Devops is a solid concept with high benefits for those who understand it.

    AI, and more specifically GenAI and LLMs - is more like crypto, in the sense that people are trying to get rich from it without having the first clue what it is. It’s this shiny new thing that everyone is rushing to get on board with, but I have yet to see someone propose a use case that actually makes sense, couldn’t be implemented better without AI, and is a net gain for those using it. Right now it’s all this nebulous bullshit, everyone just slaps their own coat of paint onto ChatGPT and calls it a day. Useful AI-adjacent concepts like Big Data and Machine Learning have been around for much longer than the tooling underpinning the current hype, and already have a lot of very valid use cases.

    By the way, I work with a bunch of high aptitude Devops engineers and none of them are thinking about adding AI to our pipelines, not even to pad their CV.