• Jaloopa (registered) (unregistered)

    What's the problem? There's a bug, it's logged so the bug can be removed. De-bugged, if you like

  • A-nony-mouse... (unregistered)

    "The power of a good devops team is that you can get fast, reliable, and repeatable deployments. ".... That is one part, and in many cases only a very small part...

    My favorite: "“DevOps is the union of people, process, and products to enable continuous delivery of value to our end users.” – Donovan Brown.

    https://devblogs.microsoft.com/devops/what-is-devops-donovan/

  • my name is missing (unregistered)

    Copypasta is the favorite food of terrible programmers everywhere.

  • (nodebb)

    DevOps is where those who are unsuccessful as programmers (like me) go to pasture. It's easier to keep up with new DevOps tools than with new Javascript frameworks.

  • (nodebb) in reply to my name is missing

    Indeed. It especially shines, when even comments/javadocs are copied and only the method name is changed.

  • Alex (unregistered) in reply to A-nony-mouse...

    Yeah, but the same fluff would equally well describe the process of mailing a $10 gift voucher to your customer every week. Remy's version has the advantage of specificity. And not sounding like a lifestyle coach or motivational speaker.

    Incidentally, as someone who works mainly in financial reporting (wherein "programming" normally refers to VBA macros), can I just ask anyone who works in an environment with real DevOps to take a moment to count their blessings? The closest I've recently seen to a DevOps workflow was a script that could be used to "compile" a bunch of .BAS files into a single VBA add-on.

    (Which was still a significant improvement on the status quo because it meant the macros could actually be version-controlled! But scoring a 2 on the Joel Test shouldn't exactly be a cause for celebration.)

  • (nodebb)

    We have this product delivered as part of our ERP solution. The logger snafu is the least of our problems. The whole thing looks and feels and runs like it's a high-school programming project, and whenever there's a problem you have to sift through gigs of Info-Spew to find an actual error (which you can't do by searching for "error" because that's on almost every line).

    Bad as this is, it's only my SECOND least favorite "feature" of this system.

  • Guest (unregistered)

    Never saw FISI before and did not notice the pop-up. Looked it up. The only result that seemed to fit was Fecal Incontinence Severity Index. Seemed about right and was going with it until I noticed the pop-up. Still think the first one works.

  • 🤷 (unregistered)

    Well, at least they HAVE logfiles. I used to work as a company where the entire "logging" consistet of "catch (Exception ex) { Console.WriteLine(ex.Message); }". If you were lucky. Sometimes, there wasn't even a try-catch and programs would just fail, without us knowing, because some Admin logged on to the server in the morning and clicked away all error messages.

  • Sole Purpose Of Visit (unregistered) in reply to Bananafish

    Aw, go on. Enquiring minds need to know.

    What's the Frist?

  • mushroom farm (unregistered)

    oh, you think this is bad? when i worked at the largest enterprise devops provider, i saw data management code that was worse than this every day.

  • Prime Mover (unregistered)

    We had a case where one of the members of the offshore team was given the responsibility of managing the build process. He was given a default build script, with the view that he would need to configure it per project according to the needs of the individual project.

    So I delivered my new project to him for it to be incorporated into the automatic build process, and he immediately rejected it as being non-compliant. Why was that? Because the build process fell over. Well all you need to do is to change your build process to do x,y,z we told him. Easy to do, that's why you've been given a customisable script.

    6 months later and he still hadn't got the auto build process working, and we were the ones with eggies on our faces because he had told his higher-ups that the delay was caused by us refusing to follow the instructions he had given us to amend our project so it was compliant with the basic default build script that we had originally given him.

    And because the management structure of that project had also been transferred offshore, leaving only the actual senior developers and project manager Europe-side, they backed him up over it and made us (at considerable inconvenience and another round of laborious testing) redesign our architecture so it fitted into his damn build process which we had designed in the first place.

    I no longer work at that company (I made my own way through the exit hatch, now earning 2x what I was) but it still makes my blood boil thinking about it.

  • Osric (unregistered) in reply to ESkIiHccraVBD

    You have experience of the method name getting changed to match what it now does? You sure are lucky.

  • NotAThingThatHappens (unregistered)

    This site is now known as: What The Fornicate

  • akozakie (unregistered)

    Less like devops, more like dev-oops.

  • Prime Mover (unregistered) in reply to akozakie

    Dev-oops? More like duff-oops.

  • (nodebb) in reply to Sole Purpose Of Visit

    Aw, go on. Enquiring minds need to know.

    What's the Frist?

    The Frist thing I hate is that the "flow" system is a 100% Java contraption that creates 7 JVMs integrated into a grid that -- wait for it -- only runs on Windows. Because....... Java only runs on Windows....?

Leave a comment on “Going with the Flow”

Log In or post as a guest

Replying to comment #:

Log Out

« Return to Article