• 1 Post
  • 1.18K Comments
Joined 3 years ago
cake
Cake day: July 3rd, 2023

help-circle
  • No disagreement here.

    I realized when reading one of the other comments that my similarly sized complaint is it creates a lot of potential for problems at the game level as well as narrative when people make their characters in isolation. I kind of assumed that comes packaged with “and you all meet in a tavern”.

    Like, everyone makes a fighter and shows up to session 1. The dm’s going to have a head scratcher thinking about balance, and some players might be annoyed they don’t really have a niche of their own. A weird party like that can work, but it’ll be a happier experience if folks talk about it ahead of time.


  • It can work, as clearly shown by your rather wholesome example and many people’s games. But it’s also leaving a very large surface area for problems. Unlike real life, you can just avoid that by making your characters together.

    Maybe I should have said in my previous thread that while the “you all meet for the first time” is kind of cliché, there are more serious problems at the game level. And like it can work if everyone makes a fighter, but you can also make everyone’s lives easier if you discuss up front.


  • So as a senior, you could abstain. But then your junior colleagues will eventually code circles around you, because they’re wearing bazooka-powered jetpacks and you’re still riding around on a fixie bike

    Lol this works in a way the author probably didn’t intend. They are wearing extremely dangerous tools that were never really a great idea. They’ll code some circles, set their legs on fire, and crash into a wall.


  • I think the best game I’ve done started as “it’s a DND world and you’re a band on tour”.

    It started with a simple “the bridge is out on the way to your next show”, then there was a battle of the bands, a sketchy record label, and then the players organized a recall of the mayor that was in bed with the capitalists. That game went great places.














  • Oof. I’ve had places that the pipeline was getting long. At one of my previous jobs I made it so all the tests could run locally, and we were keeping the full build as slow as possible.

    We also didn’t do any browser tests (eg: selenium) because those tend to be slow and most people are bad at making them stable.

    It’s important to know whats worth testing.



  • There’s a lot of fear at my job about changing code. I’ve been trying to tell them to start writing automated tests. Or at least a linter to check for syntax errors. They’re all like “ooh that sounds hard maybe next quarter”

    Meanwhile, a trivial change requires a whole day because the developer has to manually test everything.

    I just unilaterally added checks to code I have ownership over, but anything shared I’m getting “maybe in two quarters we can prioritize this” from management.


  • jjjalljs@ttrpg.networktoProgrammer Humor@programming.devScrum
    link
    fedilink
    arrow-up
    37
    arrow-down
    2
    ·
    24 days ago

    My job has a “scrum master”. She’s nice, I guess, but as far as I can tell her entire job is sharing her screen so we can look at tickets. Then people tell her what to click on and what text to change. It’s excruciating because it would just be faster for the person talking to change it, instead of being like “remove the second bullet point. No, not that one”

    On top of that they have all these tasks for “unit testing” but they don’t actually do unit testing. Someone just said, in the distant past, we should do testing so it’s there.