• 4 Posts
  • 42 Comments
Joined 2 years ago
cake
Cake day: July 3rd, 2023

help-circle










  • I personally prefer consistent and smaller releases. It offers less opportunity for big bugs to creep in along with smaller fixes and features.

    I saw agile mentioned here but here’s another suggestion. Agile can be helpful in the right situations but for solo devs/tiny teams, I really recommend looking into Basecamps “Shape Up” method. It uses longer cycles vs shorter sprints with a cool down period in between.

    So in the case of OP, they could set a 6 week cycle and plan for things that can definitely be completed during that time period. Right at the end of the cycle you release. The goal is to finish before the cooldown to give yourself time to breathe and plan what to do for your next cycle. Play around with a fun feature, learn about a new tool or technique you wanna try, organizing your backlog, etc. You don’t want to spill tasks into the cooldown. Else it’s not a cooldown.

    The online version of the Shape Up book is free and can be found here.








  • nnullzz@lemmy.worldtoMicroblog Memes@lemmy.worldThe audacity
    link
    fedilink
    English
    arrow-up
    7
    arrow-down
    1
    ·
    5 months ago

    Honestly I said that from my toilet. But the point is that businesses that tend to say no to their employees about PTO normally aren’t operating in a way that gives employees the freedom to have a life outside of work. Sure, there’s the odd chance that it’s not the case, but more often than not this is what happens.

    The hypocrisy IMO comes from the act of “oh well I couldn’t give you the time off, you took it anyways, so you’re fired.” Which I get from a business perspective bc the employee went against the schedule, but why not find ways to not let your team get to that point. Most small businesses don’t even offer PTO to begin with.

    Creating an unhealthy work environment, then punishing your people for it is being a hypocrite.