Anti Mediocracy Manifesto for Software Development

"It does not matter how many people use framework X."

Unfortunately, it does. It sort of makes sense Manifest Against Mediocracy includes such statement, since this is the large impediment in fight against mediocracy, but simply asserting it doesn't make it true.

The term "client" is being used (once):

> Therefore, our true purpose is to express the intentions of our clients using as little code as reasonably possible, accompanied with lots of documentation and lots of tests (testing code and unit tests don't count as LOC).

Software Engineering is an exercise in compromise. How does the risk of a bug compare with the benefits of the code?

I think it's fair to say that there is more code being written today, by a more diverse group of people, than ever before. It would be a real shame to tell them the amount of code they should be writing is 0 since that's the only way to prevent bugs.

These lines sound like a recipe for scope/feature creep and never ending development process.

>Never do requirement analysis. Never write technical requirements or functional ones. If you do, you have already failed.

In that case, how do you know when the software is finished and your contract has been fulfilled?

>Creative solutions are often holistic in nature, driven by first-hand experience, discussion, interaction and... thinking. If you want a developer to write a great piece of code, let him or her scratch the itch you're trying to scratch.

So, you do all your thinking, without capturing anything, and then the software is finished when the developer is bored?

These may make sense in a Utopian existence where profit means nothing. However in the real world, projects are driven by requirements, and the developer that can fill these requirements the fastest is the developer that will prosper the greatest.