You're supposed to be technically proficient in the technology, but not "smart" enough to ask good questions about the product, direction, or ANY of the decision-making.

You're supposed to be a zealot for the project, doing it EXACTLY the way the boss wants it, even if it is wrong. You're supposed to volunteer at least 55-60 hours a week, and be willing to do more when the boss asks, without giving it a second thought.

You're not supposed to have your own opinions about how things SHOULD be done, because they might get in the way of what the boss wants to do (even if it's totally and completely wrong).

You're supposed to listen and not speak, unless asked. When asked how long something will take, the answer should be "a day or two", even if it means that you'll be up for the next 48 hours straight to complete that something.

I'm IN that environment right now. We just went through a 102 item list of "customer requirements", which we're supposed to have coded, tested, and feature complete by the end of next week.

No architecture, no thinking about it. Not allowed. Just DO! DO! DO!

This is for the new product.

And the owner hasn't even given a thought to why his current product is an "also-ran" in the market he was supposed to dominate. He doesn't understand why it's "too complicated", "too hard to use", and "advertised features don't work". The system architect has proposed a new "architected" product, but it just got put on the back burner, because the VC owner guys don't think we'll be able to convince people to switch.

Funny, but I'm predicting our new product will probably be an "also-ran", too.

Perhaps I'll have a new job by then, or maybe I should talk to my "old job" boss (not fond of that).

Glen Austin

I WANT TO WIN! I want to create a software product in a market that people want, and that I can deliver, hopefully via some kind of Internet model.

I'm thinking more and more that instead of working for these bozos, that I need to do something different for a while, like teach school and use the free time to work on a software product, following good development processes.

I can't just quit my job, because we would be out of money in about 3-4 months, and I don't think I can get a good product built in that time.

But, if I had a job with defined hours, and I wasn't obligated after hours, but still make "decent" (30-40k) money, then that 3 months could end up being a year or more. If my wife worked full time, I might even be able to continue teaching for several years to get the product right.

I would have to start in August, with the school year, so I'd wouldn't have 3 months of unemployment prior to working.

I'm just getting really tired of working for people who think they understand software, systems, and feel like they have to lie, cheat, work their people unreasonable hours, and steal to win.

I do believe that nice guys DON'T finish last, because they're straight with their customers.

Glen AUstin