On Getting Management Interested in Improving Quality?

npoole asks: "Like many of the Slashdot readers, I am a programmer and have been pushing out repetitive database content for about a year. The work simply doesn't stop and the more we get it seems the less we ensure quality work. I have been debating telling my boss that either we take less clients, less money, more quality work or I am leaving. Is this a smart thing to do? I'm making very good money doing quick hacks to push out websites, but it's not very project oriented as much as it's become 'throw in pre-written, pre-used functions'. Any advice on how to ensure quality in our work without telling my boss it's either my way or the highway?" Of course, improved quality in any product affects the bottom line, and it's the bottom line that managers are paid to keep up. How can a developer communicate to managers (both open and closed) the value of better quality in development, and how long should one try before giving up?

Comments

It gets easier with time.

[jedwards]

With a large customer base, once the complaints start coming in management (and everybody else) starts to realise that it is no fun supporting a low-quality product.
I'm not guarenteeing that everything will magically change overnight, but if you can propose a chunk of work that can be done which doesn't visibly add value; but will help keep a large number of customers off the phone, then you might be listened to more than now.

Round of applause, that penguin!

[leonbrooks]

I know from personal experience that if I'm not motivated by anything more than just getting the job done, then I won't produce the same quality code that I would have under favorable circumstances. Not due to time constraints, but because there's no motivation for me to do anything more than the bare minimum.

I second that, wholeheartedly.