162 karma · joined April 17, 2015
Not necessarily. I've seen/heard engineers who take great glee in pointing this out, but they don't understand the real dynamic. The managers have probably read the mythical man month too.
If as a manager you report a problem to your boss, you're likely to get "help", even if you already have a plan. Sometimes the least costly "help" is to accept additional "resources" and fence them off someplace they don't do damage so that the rest of your team can execute its real plan. Turning down help can damage your credibility/relationships which is what you depend on to be "allowed to be successful". It's emotions, not logic.
Or, if you really really want to, you can tell your boss they're an idiot and need to learn about Brook's law.
What I notice is that the nest does a really great job managing the temperature in my house and keeping it comfortable. It just works and it became a default expectation. We had to go back to the old thermostat after an issue with our furnace, after which I started getting a ton of complaints from everybody about too cold/too hot. It's a great example of a technology that works really well.
BUT when I purchased this, this is exactly what I was afraid of. I think this is a huge problem for the software industry in general: most companies don't last. As a customer you can't place your trust in them as they'll be gone in 5 years.
But what if how they want to work is "Dark Scrum"... or some kind of Agile religion, or waterfall.
The performance FUD is probably just deflection.
As DHH himself says, engineers are in short supply - so their preferences tend to get listened to.
Instead, they just asked you to stop pointing out the problems?
Were these problems nitpicks, personal preference (as some here are apparently assuming) or were they objectively technical issues?