Skip to main content
Software Engineering

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

6
  • 13
    Always fix bugs first, see Spolsky's classic piece: joelonsoftware.com/2000/08/09/… (point 5 is the relevant one). Commented Dec 20, 2023 at 11:32
  • 7
    I've made similar complaints myself. The demotivating part was not fixing bugs (which is development work), but rather 1) being directly exposed (and seemingly accountable) to the expectations of users who had been sold something we were not delivering, and 2) having to work around significant limitations in a product we were not really able to change. Make sure you are solving the right problem. Commented Dec 20, 2023 at 11:42
  • 7
    If you have a single developer, and there are enough bugs to take all this developer's time, then you have a serious problem. You should stop development altogether until this is under control since new development will (inevitably) introduce new bugs, making it impossible to keep up. Commented Dec 20, 2023 at 16:14
  • 1
    @JacquesB unless that development is to redesign something to be less likely to "attract" bugs, currently the developer might just patch one small issue after another without being able to look at a bigger solution... but I guess you meant feature development? Commented Dec 20, 2023 at 19:10
  • 2
    As to what to do - have you asked your developer? What do they think? You should consider their input. Commented Dec 21, 2023 at 14:02