Okay, sure, do fast. Then:

• I’ll add a refactor task to the backlog filed under “tech debt”
• please confirm again that you know we are still behind on security updates and that you’re ok with it because you are responsible for how I spend my hours
• I’d like more time to spend on bugs before we lose customers.
• Also I won’t touch that buggy part without taking the time for a rewrite because we did it “fast” per your request and it’s so hard to maintain now that it becomes a time sink on every minor change
• I know we are under time pressure right now, but as a stakeholder I request we plan a few sprints for improving reliability of our product
• It’s not “fun” to work on our code. We might lose developers if we do not address this. We both know the good coders will have no problem finding a new job and you’ll end up with the bad ones.
• Either that, or plan for loss of personnel and the extra time we need for the hiring process and the loss of developer hours

Change management! :-)

Or, if possible, change employer.

(And I know we’re in meme-land, but I always see it as a developer’s task to inform of the trade-off between fast and good)

Don’t you need to declare new Balls() first? Or do you suck() Balls static?