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

help-circle
  • Yes, you can make players pre-plan. You nudge them.

    No amount of nudging will make some players do anything. Some players are obstinate and frankly not very good, but honestly the solution to “this player won’t stop looking at their phone and their turns take forever” may be to remove them from the group.

    Why does it matter how much time everyone takes?

    I don’t want to wait 5 minutes for someone to dither and dither and finally decide “I attack”


  • jjjalljs@ttrpg.networktoRPGMemes @ttrpg.networkUnprepared
    link
    fedilink
    arrow-up
    3
    arrow-down
    1
    ·
    22 hours ago

    This was a weirdly aggressive comment.

    The solution is the pre-planning, which does not need a timer, nor is it a guaranteed result of a timer.

    You cannot make players pre-plan. The timer encourages pre-planning, or at least rapid decision making on the fly. Both have the desired result of the game moving at a quicker pace.

    It also has the benefit of creating an impartial tool for measuring, instead of relying on subjective “You’re taking a long time.” It is harder to argue with a clock. This is an advantage.

    There was a problem, and in trying to fix it, the DM created a second problem.

    What is the second problem?


  • The other day I was updating something and a test failed. I looked at it and saw I had written it, and left a comment that said like “{Coworker} says this test case is important”. Welp. He was right. Was a subtle wrong that could’ve gone out to customers, but the wrong stayed just on my local thanks to that test.


  • I would have questions about how they work with a team and structure.

    Are they going to be okay with planning work out two weeks ahead? Sometimes hobbyists do like 80% of a task and then wander off (it’s me with some of my hobbies).

    Are they going to be okay following existing code standards? I don’t want to deal with someone coming in and trying to relitigate line lengths or other formatting stuff, or someone who’s going to reject the idea of standards altogether.

    Are they going to be okay giving and getting feedback from peers? Sometimes code review can be hard for people. I recently had a whole snafu at work where someone was trying to extend some existing code into something it wasn’t meant to do*, and he got really upset when the PR was rejected.

    Do they write tests? Good ones? I feel like a lot of self taught hobbyists don’t. A lot of professionals don’t. I don’t want to deal with someone’s 4000 line endpoint that has no tests but “just works see I manually tested it”



  • I don’t always run a timer, but it is a tool in my box.

    Mostly it comes out when I feel like the players are spinning their wheels. Like, they know they need to get into the server room on the 10th floor. There’s a front door with security, a back door with an alarm, etc. The players are just going round and round with ideas but not doing anything.

    I’ll say “I’m starting a five minute timer. If it hits zero, something interesting will happen”.

    If it hits zero and they’re still stuck, then as foretold something interesting happens. A rival group rolls up and firebombs the entrance before heading inside. A security drone spots them and is calling the cops. Whatever. Something that forces them to act.

    In combat rounds I sometimes do the same, but only if it feels like they’re not making progress. Maybe it’s a little rude sometimes, but I value keeping the scene moving forward. I don’t want to keep spending three minutes on “should I move? How far can I move again? Is there a range penalty? What if I use a spell first can I still shoot?” stuff. Especially if it’s rules minutia they should already know.

    The amount of times I had to remind an old group’s bard that yes, in DND 5e you can move AND take an action was too high.



  • This is a good answer.

    At my job, there was a desire to do a big rewrite of the system. It was a disaster. We spent like 8 months on this project where we delivered no value to customers. Then there was essentially a mutiny from the engineering team and we killed it.

    We’ve since built on top of the original system and had, in the words of product leadership, “the most productive quarter in the history of the company”.

    Now, why was it a disaster? The biggest reason was that people, especially people in leadership positions, did not understand the existing system very well. They would then make decisions based on falsehoods and mythology.





  • I don’t think I’ve ever desired to have speech as an interface for a device.

    Yeah, I could yell at it “Open the browser and go to uhh the order of the stick comic index page” and maybe it would get it right. Or I could just… click on the browser, type oot and pick it from the drop down. Faster, no error, no expensive processing.

    I don’t drive (cars are a bad form of transit and I’m lucky enough to not need one) and I’m not hands-full in the kitchen often.