• morgunkorn@discuss.tchncs.de
    link
    fedilink
    English
    arrow-up
    1
    ·
    3 days ago

    Don't look up has a pretty accurate depiction of what the billionaires will be able to achieve when the end of the world comes.

    And the series Mr. Robot did very well by showing realistic software and hardware all along.

    • ramirezmike@programming.dev
      link
      fedilink
      arrow-up
      34
      ·
      7 days ago

      WHY DID THIS 3 POINTER TAKE FIVE DAYS

      YES YES, IT’S NOT TIME BUT WE ARE TRACKING IT THAT WAY BUT IT’S IMPORTANT FOR YOU TO NOT THINK OF IT THAT WAY WHEN YOU ESTIMATE BUT WHY DID YOU GO OVER THREE DAYS

      • jubilationtcornpone@sh.itjust.works
        link
        fedilink
        English
        arrow-up
        3
        ·
        5 days ago

        Don’t look at me. I voted five. And then when the scrum master was like, “jubilationtcornpone, are you ok with it being a three?” I said “No.” But someone who thought they knew better decided it was going to be a three anyways.

      • normalexit@lemmy.world
        link
        fedilink
        arrow-up
        16
        ·
        7 days ago

        Let’s all head to the conference room, so we can discuss the definition of a story point for an hour. I’d also like to talk about why we are behind schedule and our velocity is dipping. Let’s make it two hours.

        • vithigar@lemmy.ca
          link
          fedilink
          arrow-up
          2
          ·
          edit-2
          6 days ago

          Management where I work finally unbent and admitted that story points were time.

          …but also want to continue raising velocity in each sprint.

          • chilicheeselies@lemmy.world
            link
            fedilink
            arrow-up
            2
            ·
            6 days ago

            Dont worry, they are unserious about actual results; they just care about the appearance of results that they can report up. Just start padding extra… Fucking story points…jesus… To each ticket. Now everyones charts look like their velocity increased. Dont worry, noone is actually measuring results.

            • vithigar@lemmy.ca
              link
              fedilink
              arrow-up
              3
              ·
              6 days ago

              That’s exactly what we ended up doing. Every story has now become one Fibonacci step higher than it would have been before.

          • NotMyOldRedditName@lemmy.world
            link
            fedilink
            arrow-up
            1
            ·
            6 days ago

            I don’t even see why them roughly representing time is a problem due to them raising in a fibonacci sequence.

            If they were a day each, it’s not like the jump from 5 to 8 means it’s going to take 3 more days, but that it’s gotten more complex and maybe it’ll still be 5 or 6 days but I can’t be sure because this one has a lot more unknowns that might not reveal themselves until I’m into it. That’s why we’re forced to go from 5 to 8 and not a 6 or 7.

            The uncertainty is built right into it, so it can’t be exact time, but at the same time trying to ignore that they’re still time related is stupid.

  • Anticorp@lemmy.world
    link
    fedilink
    English
    arrow-up
    44
    ·
    7 days ago

    PM: “Hey, I know you said it’ll be done in a week, and you need me to stay out of your way so you can focus, but it’s been 7 hours and I was wondering if you have an update for me. Can you create a report that outlines what you’ve done, what is remaining, and precisely when each step will be finished so that I can pester you about each step throughout the development process, interrupting your productivity? It makes me feel like I’m contributing.”

  • 🔍🦘🛎@lemmy.world
    link
    fedilink
    English
    arrow-up
    40
    ·
    7 days ago

    Not programming, but the plot of Shin Godzilla was about bureaucratic red tape holding back the actual solutions.

    • IzzyScissor@lemmy.world
      link
      fedilink
      arrow-up
      22
      ·
      edit-2
      7 days ago

      It’s my favorite Godzilla movie because of this aspect. There’s a scene where I lost it in the theater when the >!Prime Minister is completely certain in telling the press that Godzilla will absolutely never, not in a million years, not make landfall… only to have an underling whisper in his ear that Godzilla just made landfall.!<

      I worked for a Japanese company at the time, and could recognize that it wasn’t even heightened for parody. That’s just exactly how it is.

    • tetris11@lemmy.ml
      link
      fedilink
      arrow-up
      21
      arrow-down
      1
      ·
      edit-2
      7 days ago

      WHICH IS WHY WE SHOULD DEREGULATE EVERYTHING! INCLUDING FOOD AND DRINKING WATER, AND WE SHOULD ALLOW ALLOW COMAPNIES TO DUMP INTO RIVERS!

      I love hollywood

        • tetris11@lemmy.ml
          link
          fedilink
          arrow-up
          3
          ·
          6 days ago

          Oh I thought it was one of newer ones. I was envisioning the creep of conservatism into films, like that scene from Independence Day where Will Smith declares that he never wants to pay taxes

  • UnderpantsWeevil@lemmy.world
    link
    fedilink
    English
    arrow-up
    20
    arrow-down
    2
    ·
    6 days ago

    Do I really need to open a ticket for this

    Yes

    UNIRONICALLY, ASSHOLE! IT’S THE FIRST THING YOU SHOULD HAVE DONE!!!

    Fucking “hey guys, we are bringing in someone from another department and they need to catch up. What’s the project looking like?”

    “I don’t know. Nobody wrote anything down and now it’s scattered across six didn’t PCs in various states of dysfunction.”

    IT guys think they’re all Michael Jordan right until they get the ball.

    • chilicheeselies@lemmy.world
      link
      fedilink
      arrow-up
      9
      ·
      6 days ago

      I get the message here for sure, but imo tickets (while important) take a back seat to a rich commit history. Ifbthe commit messages and history are high quality enough, one can tell whats up with the code sinply by looking at the log.

      Tickets on the otherhand are in a secondary system. Of course, they can bind the work of multiple projects together. But honestly, has anyone ever been able to just reach the ticket history and know everything about a project without asking someone?

      • UnderpantsWeevil@lemmy.world
        link
        fedilink
        English
        arrow-up
        7
        ·
        6 days ago

        tickets (while important) take a back seat to a rich commit history

        I’ve found people who do one will manage the other with ease. But “oops! No ticket” is a canary telling me their commit log is going to be shit.

        But honestly, has anyone ever been able to just reach the ticket history and know everything about a project without asking someone?

        I’ve been able to find out the status of individual half-finished bugs off a ticket log and work/reassign it quickly. Without a ticket in queue, I’ll either discover the issue has been completely ignored or that multiple people pioneered their own boutique fix without talking to one another.

        • chilicheeselies@lemmy.world
          link
          fedilink
          arrow-up
          3
          ·
          6 days ago

          I’ve found people who do one will manage the other with ease. But “oops! No ticket” is a canary telling me their commit log is going to be shit.

          Thats an astute observation. I really cant refute that haha.

        • jj4211@lemmy.world
          link
          fedilink
          arrow-up
          2
          ·
          6 days ago

          Problem in some teams are the respective audiences for the commit activity v. the ticket activity.

          The people who will engage on commit activity tend to have a greater common ground and sensibilities. Likely have to document your work and do code reviews as the code gets into the codebase and other such activity.

          However, on the ticket side you are likely to get people involved that are really obnoxious to contend with. Things like:

          • Getting caught up in arguments over sizing where the argument takes more of your time than doing the request
          • Having to explain to someone who shouldn’t care why the ticket was opened in the first place despite all the real stakeholders knowing immediately that it makes sense.
          • Work getting prioritized or descoped due to some political infighting rather than actual business need
          • Putting extra work to unwind completed work due to some miscommunication on planning and a project manager wanting to punish a marketing person for failing to properly get their request through the process
          • Walking an issue through the process to completion involves having to iterate through 7 states, with about 16 mandatory fields that are editable/not editable depending on which state and sometimes the process is stuck due to not having permission because of some bureaucratic nonsense that runs counter to everyone’s real world understanding.

          In a company with armies of project managers the ticket side is the side of dread even if the technical code side is relatively sane.

          • oo1@lemmings.world
            link
            fedilink
            English
            arrow-up
            1
            ·
            6 days ago

            Haha, i’d write a thousand pages of documentation before entering ticket hell. I fact I do put a lot of information into the ticket - they still won’t read it though and i’ll have to repeat myself 15 times to 5 different people.

            The solution to this problem. . . I have no idea, but I’m sure they’ll appoint another delivery manager who will get hired by the ones who already know fuck-all to know less than them.

            I’ve found that the few managers who want documentation, get documentation, and the others who want tickets and “story points”, get tickets and fictional bullshit - in general.___

            • jj4211@lemmy.world
              link
              fedilink
              arrow-up
              2
              ·
              5 days ago

              Don’t know about solving, but at least can see the signs:

              • If there’s a lot of layers of middle management between you and the head of the company
              • There are people with oddly narrow scope of responsibilities, a scope that doesn’t make any sense to be a dedicated full time job
              • Excessive numbers of “cute” acronyms to apply to everything and everyone
            • Kissaki@programming.dev
              link
              fedilink
              English
              arrow-up
              2
              ·
              5 days ago

              The solution to this problem. . .

              is that they have to create a support ticket with you, that you then put in progress, and you walk them through your documentation, and then log your time spent onto that ticket. (/s)

    • Kissaki@programming.dev
      link
      fedilink
      English
      arrow-up
      2
      ·
      edit-2
      5 days ago

      There’s an alternative to creating too many tickets that only add overhead and then make it harder to get into the project. Creating a good amount of tickets.

      I took the OP reference as demand for ticket creation when they don’t make sense and only hinder development through unnecessary overhead. E.g. creating a ticket before a quick analysis, or creating individual tickets when one story/feature ticket would be enough. Or more specifically in this case, having to create one before fixing a critical blocker.

  • Thebeardedsinglemalt@lemmy.world
    link
    fedilink
    arrow-up
    13
    ·
    6 days ago

    The person in charge trying to coordinate the whole thing, who’s asking for status updates on a daily basis and jumps down your throat if you don’t respond in a timely fashion, takes weeks to respond when asked for critical input. Also…

    Leader: The world is going to end in 5 days, we need that product now!!!

    Programming team delivers a functional product.

    4 days later…

    Programming team: did our item save the world

    Leader: I haven’t gotten to it yet, I’ll take a look by EoD.

    • wer2@lemm.ee
      link
      fedilink
      arrow-up
      4
      ·
      7 days ago

      If you hate the taste of scrum give SAFe a try! (but really, please don’t)

      • frezik@midwest.social
        link
        fedilink
        arrow-up
        2
        ·
        6 days ago

        I believe that the problem with agile is that it’s not enough like waterfall. That’s why SAFe is for me.

        So glad we dropped that shit.

        • Cid Vicious@sh.itjust.works
          link
          fedilink
          English
          arrow-up
          2
          ·
          6 days ago

          It doesn’t really matter what they call it. Companies that want to be waterfall (or more accurately, whose executives want waterfall style commitments) are going to be waterfall even if they call it Scrum.

    • VoterFrog@lemmy.world
      link
      fedilink
      arrow-up
      2
      ·
      6 days ago

      I mean, Agile doesn’t really demand that you do or don’t use tickets. You can definitely use tickets without scrum.

  • umbraroze@lemmy.world
    link
    fedilink
    arrow-up
    7
    ·
    5 days ago

    I once read about Andy Warhol’s film Empire and thought it could form a decent stylistic background for a movie about your average programmer’s work day.

    One continuous 8 hour shot of a programmer sitting by a computer, slowly scrolling through a code, pausing for a long time to stare at particular sections, and occasionally saying “why the fuck doesn’t this work?”

  • Phoenix3875@lemmy.world
    link
    fedilink
    arrow-up
    16
    ·
    6 days ago

    An app that will save the world…and other fantasies that software developers tell themselves to feel important

  • vga@sopuli.xyz
    link
    fedilink
    arrow-up
    14
    ·
    6 days ago
    "Why isn't this ready yet? The meteors are falling in an hour?"
    
    - Oh sorry I got distracted by Youtube for a minute
    
    "...You've been doing this for a week"
    
  • xorollo@leminal.space
    link
    fedilink
    arrow-up
    9
    ·
    6 days ago

    Yeah, except Joe doesn’t just say “yes”. He’s got some corpo speak about making sure outcomes align with the the most emergent needs and ensuring Joe has a he right information to manage expectations.

  • IzzyScissor@lemmy.world
    link
    fedilink
    arrow-up
    11
    ·
    6 days ago

    The sequel is when the original programmers die and a new team has to come in and figure out WTF their code is doing or even supposed to be doing.

    • SneakyWeasel@lemmy.ca
      link
      fedilink
      English
      arrow-up
      3
      ·
      edit-2
      6 days ago

      I am currently doing this right now, pharma code team gave me a whole program and now i need to find out how everything works…

        • SneakyWeasel@lemmy.ca
          link
          fedilink
          English
          arrow-up
          2
          ·
          5 days ago

          Found a couple infinite loops that were causing systems to crash. Slowly coming along. Going to take a bunch of time to allow it to become operational again

        • naught101@lemmy.world
          link
          fedilink
          arrow-up
          2
          arrow-down
          1
          ·
          5 days ago

          17 bugs detected including 4 security threats, and we still don’t even know what the programming is supposed to do

    • kubica@fedia.io
      link
      fedilink
      arrow-up
      6
      ·
      7 days ago

      Why won’t you sprint the sprint so we can get more sprints in the sprint?

  • Aceticon@lemmy.dbzer0.com
    link
    fedilink
    English
    arrow-up
    11
    ·
    edit-2
    6 days ago

    Half way into saving the World it turns out you need some data that’s not even being collected, something that nobody had figured out because nobody analysed the problem properly beforehand, and now you have to take a totally different approach because that can’t be done in time.

    Also the version of a library being include by some dependency of some library you included to do something stupidly simple is different from the version of the same library being included by some dependency of a totally different library somebody else includeed to do something else that’s just as stupidly simple and neither you nor that somebody else want to be the one to rewrite their part of the code.