• 0 Posts
  • 12 Comments
Joined 1 year ago
cake
Cake day: July 2nd, 2023

help-circle



  • This meme was clearly made by someone who doesn’t use or understand TypeScript.

    It was made by someone who doesn’t understand types, period.

    Curious if it’s the same wizard who was explaining that Linus doesn’t understand programming because he has opinions on arm vs Intel architecture. EVERYONE programs in JavaScript anyways and my JavaScript always works on arm. Has Linus lost the plot?





  • Yeah exactly. I think you hit the nail on the head with the “(and never look at it again)”.

    It’s not explicit in the meme. “Not doing it” and “never look at it” are totally different things… But I think you’ll fill it in based on your personal experience.

    I’m sorry your backlog doesn’t get regularly revisited.

    If I were you, I’d push for setting aside time to get it under control.

    If your backlog is gigantic, I expect there will be pushback just because once the problem gets sufficiently large nobody is brave enough to broach it.

    But, you can apply story slicing skills to these kinds of problems too. Break it down into smaller bits with clear and realistic objectives. Setting aside 30 minutes with the goal of, say, picking 5 items on your backlog that you know you won’t ever do because they’re super low value? Pick 5 items and close them off as won’t do. Baby steps.


  • I’m the Sr. Dev in this meme.

    I usually just do this when a jr has fallen in love with a piece of work and wants to keep polishing it. They start to confuse “I could do X” with “I should do X”… And confuse “less than perfect but still acceptable” with “bug”.

    I tell them to slap it on the backlog and to move on.

    We have backlog grooming meetings every few weeks. If they still actually want to do it, we can talk, but like 19 times out of 20 they’ve found a new shiny rock by then anyways, and we’re now in a position where we can both agree it isn’t a good use of our time, and close it out as a “will not do”.

    You don’t need aggressive POs or scrum masters to operate as a pragmatic team. I far prefer having a lean overhead. When there are more people shouting directions than people actually coding you’ve got too many cooks.