4 ms·

Thank you for this list. Most of it is indeed common sense that we've heard in other places, but I've favorited it to use as a checklist in the future :)

• Klathmon 10y ago
  No Problem! It was kind of nice to actually write it down, a bit of an ego boost to really lay out things that I have learned! I will give one warning that a lot of what I really learned is when to prioritise one of these things and when it's okay to let it slip. Like should I push the launch date back 2 weeks to implement bug reporting? Is it okay to launch even though I don't have 100% test coverage? When should I prioritise writing tests for the remainder of the code? How much time is too much time to test a particularly difficult to test portion of code? I don't really have answers or rules for those, but after living through each of them, I have a much better feel for what to do. And as always, shipping is better than not shipping. Code that you never release because you are always trying to make it perfect doesn't help anyone. At some point, good enough just needs to be good enough.