29

Two friends and I are about to publish a side project in two weeks (for an open Beta) it feels good but I am kind of nervous...

Today I found new bugs and I don't know yet if we have the time to fix them all...

Do you have any tips / experience you could share with me?

Comments
  • 14
    Done is better than perfect. Just ship it and fix your bugs in a subsequent minor release. Congrats on your new product and enjoy! 😸
  • 12
    Fun fact, you'll never stop finding bugs if you search hard enough ;)
  • 5
    Get an overview of the bugs, prioritize for go-live and then fix one after another based on the priority.
    Bugs that don't matter for the first run can be fixed afterwards.
  • 1
  • 1
    Coffee helps.
  • 6
    @qbasic16 All bugs are equal, but some bugs are more equal than others.

    If you don't prioritize, chances are you did not fix the one that turns out to be the one that ruins it all.

    So whatever you do, make a conscious decision and never ever let things slide.
  • 3
    And its still beta so bugs are allowed (depending on release scheme). Normally beta is useable and decently looking with still a few bugs.
  • 8
    @Codex404 beta is actually short for:
    Bugs Emitting Terror Again

    And Alpha:
    Alternate Less Public Hate Assembly
  • 3
    If you can fix them before launch, then great! If not, then you can be me and fix in prod! 🤓
  • 0
    @uziiuzair that should not be an issue we have multiple environments an error reporting tool and a CI Cd system in place
  • 1
    @alwaysmpe if you knew how much coffee I drink you wouldn't recommend drinking more...
  • 3
    @needToRoll just have a 24/7 coffee infuse. Remove your blood and make it coffee.
  • 3
    @Codex404 Idk if my heart would appreciate that...
Add Comment