Ms. ArmoredThirteen

  • 0 Posts
  • 28 Comments
Joined 2 years ago
cake
Cake day: June 1st, 2023

help-circle


  • Ms. ArmoredThirteen@lemmy.mltoProgrammer Humor@lemmy.mlDeployments
    link
    fedilink
    arrow-up
    1
    arrow-down
    1
    ·
    7 months ago

    What about a bash script that calls your CI/CD because the system is so old and complex anyone learning how to use it immediately builds a 1-off tool to hide what they don’t need but then everyone starts relying on that 1-off bash script so you extend the functionality then replace it with a proper tool then let that rot so you need a new bash script to call that to hide the useless parts?





  • Haha, in highschool I put sheep.exes into the school labs startup folders as a prank once. A couple days later the tech teacher approached me and was like “nobody’s in trouble but these things are a nightmare and if I have to reimage half the lab to get rid of them it would personally ruin my day”. Somehow all the sheep were gone by the next day






  • Okay so the dumb part is a lot of this is me abstracting away our complex build system. I’ve basically bubble-gummed a dedicated build system in top of it for only the tasks I do. At a certain point if I start adding configurations or timing I might as well just wrap it in gradle or something. But the system that I’m calling is already their attempt at simplifying another build system that’s underneath it that was written by the old guard using arcane sorcery. The whole thing is a mess


  • This is part of why I still have manual kickoffs for mine. Never need to worry about work getting done while I’m away or getting done suspiciously fast. Also they should have paid you lol, the dingdongs. Would cost a lot more just in work lost having someone else spend time deciphering and fixing it. They could always get someone else up to speed with the system after it is fixed by you so there’s little or no down time