An iterative process of "plan, do, test, improve" shouldn't leave an engineer's head. If we outsource "plan" to a manager, "test" to another blabbering idiot with a corporately purchased donut hanging off his mouth, the cycle becomes too long to actually work. Multiplied by an engineer's despair because he's obviously clever enough to see the whole picture, this is a recipe for disaster.

Throwing man-hours in there won't solve anything.

Yes, to make this work, our engineer has to have a rich and diverse skills tree. But that's not a rare thing! I've seen unassuming engineers flourishing once given freedom, demonstrating ownership and a huge range of proficiency.

Outsource culture barely utilizes 5% of what engineers are capable of, and while treating them like this, they proceed to make engineers feel even more desperate. Great minds need to utilize their whole set of abilities to feel like they're needed and appreciated. It gives them satisfaction.

@kiki agreed, and this works fine, until the MaNaGeRs want everything done in the next 5 minutes - simply no understanding of the time things take to implement properly

@fullstackchris managers are like side effects. You should not let them enter your company (codebase). Once they do, it cascades beyond the point of no return

Engineer’s time is too valuable to run tests.

Also, I can sum up this rant into a single sentence, typically a go-to for engineers: "you can't fix stupid"