• CanadaPlus@lemmy.sdf.org
      1·
      4 days ago

      Huge application. Dominating it’s industry. It had only one user on a DBs with a password that hadn’t been changed in over a decade. Same user/pass for each DB as well. The DBs were all publicly accessible. The applications, clients, engineers, and everyone else used that singular user.

      At least one of those people seriously considered doing crime, right? It would be like shooting fish in a barrel and, with simple steps to hide your network origin, there would be no way of finding the culprit. With the kind of ransoms you could get from a company like that you could go and live happily ever after in Dubai.

      Absolute madness.

  • CanadaPlus@lemmy.sdf.org
    31·
    4 days ago

    For the small niche that would find it comprehensible, that would be gold. Maybe it would work as a YouTube channel.

    The trick is that software companies and their clients tend to be more publicity-averse than restaurants, and for Kitchen Nightmares they need to find ones that will straight-up agree to be made an ass of to get on TV.

  • ChickenLadyLovesLife@lemmy.worldEnglish
    2·
    5 days ago

    This was my entire 25-year career. No way in hell would I want to watch a show like that.

    Although if there were a show based on my career, I’m sure the highest ratings would be the show where my coworker fires a 125 mph knuckle ball a foot above a 10-year-old kid’s head. It was the only time in my career when I had to physically intervene to prevent a fistfight between my boss and the client.

      • ChickenLadyLovesLife@lemmy.worldEnglish
        3·
        5 days ago

        We got hired by a company that was developing a remote-controlled baseball launching machine. The machine itself was just the standard two spinning wheels (although the max rotational speed of 125 mph was a lot for this sort of thing), but it could also pivot 360 degrees and also angle itself between straight up and 45 degrees down towards the ground, so it was capable of simulating any hit ball in baseball. The idea was that you would put this machine at home plate and then the coach could walk out among the players and use the remote (which was a Windows Mobile PDA) to generate any kind of hit, like a grounder to short or a pop fly to right field etc. Because the wheels could be independently controlled, you could put any kind of spin you wanted on a ball by having one wheel spinning faster than the other.

        Really a cool device and a cool project, but my coworker who got the gig was a remarkably terrible programmer who spent more than a year fucking things up in various ways. At one point, for example, he spent three months trying to develop a Physics engine to control where the ball went, despite the fact that a) he knew nothing about Physics, and b) the Physics of a spinning baseball is actually incredibly complicated and well beyond the processing power of a PDA circa 2005. Not to mention that the balls used varied tremendously in how old and scuffed up they were, which would have defeated any attempt to calculate where they were going with any kind of real precision.

        Despite being well over budget and past the original schedule, he had things sort of working (sometimes) and the client asked him to produce a variant of the software that would let the machine be used by Little League coaches. My coworker in addition to writing the version to scale back the speeds appropriately, also decided to completely change the API that was used to communicate with the machine. Previously, the speeds had been specified by short integer values between 0 and 32768, but he decided it would be better to use floating-point values between 0 and 1. All well and good, except his way of dealing with the huge amount of compiler errors this generated was to cast all the hard-coded short int values as floats and clamp the result between 0.0 and 1.0.

        As bad as this was, he also decided to test this version - for the first time - on a field with actual Little Leaguers (in his defense - but only slightly - we rarely had access to the actual machine itself, so proper testing was always difficult). The coach sent the command for a slow grounder to the shortstop. This should have produced a horizontal ball with about a 30 mph speed on the bottom wheel and 35 mph on the top wheel to give it some topspin. Instead, his hard-code int values were about 10000 and 12000, which got cast and clamped to 1.0 by the API call - in other words, maximum speed (125 mph) on both wheels. This ejected a ball with no spin going 125 mph, the most deadly knuckleball in human history (human pitchers throw knucklers at maybe 50 mph and they’re nearly impossible to hit or even catch). At least he had the angle and azimuth “right” so this was fired straight at the shortstop! Had it hit him, the kid for sure would have badly concussed and very possibly killed, but fortunately it sailed just over his head.

        • CanadaPlus@lemmy.sdf.org
          1·
          4 days ago

          This is one of those moments I’m depressed I’m poor and this guy probably wasn’t. Just, how do you fuck up that bad?

          • ChickenLadyLovesLife@lemmy.worldEnglish
            2·
            4 days ago

            He knew the secrets: blame your tools and be the same religion as your bosses. He was also, to his credit, a fantastic softball player, which helped the company team win the championship every year.

          • ChickenLadyLovesLife@lemmy.worldEnglish
            4·
            5 days ago

            And this wasn’t even his biggest disaster as long as you don’t count the potential for death. The baseball-throwing gig was just him and his manager; for his next project he led a team of five developers that turned three months into three years and never produced working software. The only revenue it ever produced was an initial $50K from the client that was later refunded to preempt a lawsuit. For the project he chose Ruby-on-Rails despite the fact that neither he nor anybody else on the team - nor anybody else in the entire state for that matter - had any experience with RoR. I have to give him credit, though: he was a true Renaissance Man in the sense that he could fuck up a project in any language or platform.

  • tiredofsametab@fedia.io
    1·
    5 days ago

    Someone would have to look at and understand the existing code and infrastructure rather than just throwing it all away and writing a data migration. In other words, it would never happen.

  • philthi@lemmy.world
    3·
    4 days ago

    I would watch this. Especially if it was an angry Brit, rather than a dramatic American. And even more if it didn’t keep replaying the same 5 minutes of telly before and after each ad break. And even more if it didn’t have an ad break every 10 minutes that lasted 5 minutes.

  • Psaldorn@lemmy.world
    2·
    6 days ago

    Look at this ci deployment! THE TESTS ARE TURNED OFF. YOU’RE RAWDOGGING PRODUCTION.

    Oh my days. Your AWS isn’t destroying old deployments, no wonder you’re indebt, you have seven times more compute than NASA FOR FUCKS SAKE.

  • kautau@lemmy.world
    1·
    6 days ago

    “And the big surprise, is that the fucking image uploads are being stored in fucking RAW!”

    • sylver_dragon@lemmy.worldEnglish
      1·
      6 days ago

      You joke, but I’ve actually been responsible for a coder getting shown the door for running a coin miner on his work laptop.

      In his defense, cyber security at that company was crap for a long time. After a ransomware outbreak, they started paying attention and brought some folks like myself in to start digging out. This guy missed the easy out of, “hey that’s not mine!” The logs we had were spotty enough that we would have just nuked the laptop and moved on. But no, he had to fight us and insist that he should be allowed to run a coin miner on his work laptop. Management was not amused.

      • lemsip@sh.itjust.works
        1·
        5 days ago

        Am I just stupid or does that seem like an extreme reaction?
        Apart from the ~0% profitability these days, what’s the issue with running a coin miner?

    • CanadaPlus@lemmy.sdf.org
      1·
      4 days ago

      TBF if I was writing code for my dog I’d pull out all the stops. Only the best for such a good boy! He would eat almost anything, though.