Reading Programming

I've been working this software job for nearly four months now. Every couple of days my boss gives me a new piece of functionality to add. That's fine. I like being needed, and it's good to have something to do.

But we just keep adding and adding features to this software. And most of our clients haven't even used half of these new features. And when they do, they find some bugs our Quality Control dept didn't find.

And I say to myself "No shit? Maybe we could have caught those if we weren't busy cranking out four other major features at the same time."

Our current sales manager has held similar positions at some other software companies. He said the developers at these other companies also complained about that. And they had teams of twenty or thirty developers (our staff is five developers).

And since these bugs aren't caught, half our functionality development time gets interrupted with critical fixes fir code we wrote a few months ago.

Can we just slow down? Is there an unwritten rule that says software has to be developed at the speed of light? Or at least a speed that keeps the developers doped up on coffee and working about five hours over time every week?

Why don't we just do a good job the first time? It'll take the same amount of precious time either way. It'll be less stressful. And it will make us look more competent to our clients.

Are all software jobs like this?

Please contiune to vote AND post.

Are all software jobs like this?

As far as it concerns juggling your own idea of quality work between the demands off your boss and clients, I believe most are. The worst thing is that when you step up and explain to them why feature XY is a bad idea and how less will be more in the long run, they won't understand or truly agree even if you can persuade them to take your advice.

'Yeah, That's what Jesus would do. Jesus would bomb Afghanistan. Yeah.' - snowlion

This post was edited by Jaz on Sep 28, 2005.