Because to us developers, we've seen a lot of business folks who just don't get what it is we do. Unrealistic expectations, no concept of technical debt, endless pushes for solid deadlines despite being told things won't happen on those dates, no understanding of what it takes to scale things past a certain level, etc, etc, etc.
If you're an MBA with a CS degree, or even simply someone who has actually done your share of boots on the ground dev work, this attitude probably doesn't apply to you. MBAs have a perception, rightfully so I think, of not really understanding what happens to turn all of their great ideas into working software. There's also nothing like company wide (or god forbid, external) emails promising features by a specific date without having consulted developers on timelines, or worse, having consulted them on the timeline without taking into consideration that it requires moving everything else they're working on down the line to meet that deadline. "Oh, it's just adding a textbox here, plugging it into a formula, and spitting it out over here here and here, how hard can it be? An hour tops."
If you're an MBA with a CS degree, or even simply someone who has actually done your share of boots on the ground dev work, this attitude probably doesn't apply to you. MBAs have a perception, rightfully so I think, of not really understanding what happens to turn all of their great ideas into working software. There's also nothing like company wide (or god forbid, external) emails promising features by a specific date without having consulted developers on timelines, or worse, having consulted them on the timeline without taking into consideration that it requires moving everything else they're working on down the line to meet that deadline. "Oh, it's just adding a textbox here, plugging it into a formula, and spitting it out over here here and here, how hard can it be? An hour tops."