>When you interview ask how many people with MBAs and no programming experience you'll be working under. That is a good heuristic for future pain and frustratio

>When you interview ask how many people with MBAs and no programming experience you'll be working under. That is a good heuristic for future pain and frustration. My experience has actually been the exact opposite. Working with an engineering manager and an engineering team can be just as frustrating since they often want to build the "perfect product" instead of getting a working model up and running first or a decent prototype. It can also mean that we have to use the engineers pet technology instead of something that may work better for the task at hand. Right now I am in some trouble because I used an alternate and quicker technology(flask) to get a prototype up for some customers. It took weeks instead of the usual months to get stuff up and running. Business is happy and understand this is a prototype. Engineering manager is pissed because we should only have built it with our standard framework and not have had the prototype.