Comment by sofal
17 years ago
I think that enterprise teams typically follow strict syntactic coding standards and then check off the "maintainable" and "readable" requirement from that alone. Additionally, they generate mountains of bloated Word and PowerPoint documents and then consider that responsibility fulfilled. They end up with an incredibly expensive, over-engineered mega-application that exacerbates rather than solves the intended problem. Don't think that this doesn't happen.
There are only so many things that you can force upon a team of programmers, and overall quality and cohesiveness aren't among them.
It's fairly easy to degenerate "enterprise developers" when you're defining what "enterprise" means.
My definition of "enterprise developer" comes directly from working in a gigantic financial company as well as an even more gigantic government defense contractor. Would you like some more anecdotes?
No, because an "anecdote", by definition, is not statistically relevant.
"Enterprise teams" are not, inherently, profoundly stupid in their practice of software engineering, and not all "hackers" inherently produce worthwhile, quality code.
This completely fabricated fable of software engineering is a simple straw man argument, and I've flagged it accordingly.
3 replies →
I could supply some as well to support your claim.