As someone who strives for simplicity, some things from this resonate with me, but there are many others that are just bad advice or wishful thinking.
> Solve problems instead of creating them
Whenever you write code, you inherently create problems. For every line of code you write to solve any problem, you create bugs, technical debt and maintenance problems for someone in the future. The only way to not create problems is to not write code, and therein lies the challenge.
> Do everything yourself
Yeah... no. A modern developer relies on _mountains_ of code just to use an editor. Will you write your own editor, networking stack, kernel, firmware and OS as well? If the answer is "no", take the same approach with the software you write. Don't liberally import any dependency you find, and certainly try to reduce the amount of 3rd party code that you use, but also be pragmatic and don't reinvent the wheel if there's a perfectly good one someone else built for you. The best you can do is take a glance at how it was built, and try to follow and understand updates when they happen, but this DIY/NIH obsession is ludicrous.
> Code that we didn't write we do not understand.
Have you tried reading it?
> Avoid all ornaments. We eschew all visual gimmicks, animations and eye-candy.
Awful advice. Good UIs are accessible and enjoyable to use. Just because you prefer your UIs to be spartan, doesn't mean your users will as well. You are building software for other people, right? If anything, make your software configurable so that your users have the option of configuring it to their needs and preferences.
> Do not listen to others. We never take a software methodology, school of programming or some random internet dude's "manifesto" at face value.
I will gladly disregard this "manifesto" as well then. :)
Also, the least you could do is use a spellchecker for such an enlightening document, or maybe write your own?
> Solve problems instead of creating them
Whenever you write code, you inherently create problems. For every line of code you write to solve any problem, you create bugs, technical debt and maintenance problems for someone in the future. The only way to not create problems is to not write code, and therein lies the challenge.
> Do everything yourself
Yeah... no. A modern developer relies on _mountains_ of code just to use an editor. Will you write your own editor, networking stack, kernel, firmware and OS as well? If the answer is "no", take the same approach with the software you write. Don't liberally import any dependency you find, and certainly try to reduce the amount of 3rd party code that you use, but also be pragmatic and don't reinvent the wheel if there's a perfectly good one someone else built for you. The best you can do is take a glance at how it was built, and try to follow and understand updates when they happen, but this DIY/NIH obsession is ludicrous.
> Code that we didn't write we do not understand.
Have you tried reading it?
> Avoid all ornaments. We eschew all visual gimmicks, animations and eye-candy.
Awful advice. Good UIs are accessible and enjoyable to use. Just because you prefer your UIs to be spartan, doesn't mean your users will as well. You are building software for other people, right? If anything, make your software configurable so that your users have the option of configuring it to their needs and preferences.
> Do not listen to others. We never take a software methodology, school of programming or some random internet dude's "manifesto" at face value.
I will gladly disregard this "manifesto" as well then. :)
Also, the least you could do is use a spellchecker for such an enlightening document, or maybe write your own?
- "we often evade our responsibilty"
- "True mastery transcendends"
- "Forcing others do upgrade"