1.There are three states of being. Not knowing, action and completion.00

2. Accept that everything is a draft. It helps to get it done.
3. There is no editing stage.
4. Pretending you know what you’re doing is almost the same as knowing what you are doing, so just 5. Accept that you know what you’re doing even if you don’t and do it.
5. Banish procrastination. If you wait more than a week to get an idea done, abandon it.
6. The point of being done is not to finish but to get other things done.
7. Once you’re done you can throw it away.
8. Laugh at perfection. It’s boring and keeps you from being done.
9. People without dirty hands are wrong. Doing something makes you right.
10. Failure counts as done. So do mistakes.
11. Destruction is a variant of done.
12. If you have an idea and publish it on the internet, that counts as a ghost of done.
13. Done is the engine of more.

There is also an illustration for it

This manifest critics modern (bloated, unreliable and worsening over time) softwares.
It favorises self-reliant programming (few features and simplicity, minimum amount of dependencies, write your own tools). It has benefits such as learning, improving skills, simpler code, simpler tools, easy modification and deployment.

Use vanilla HTML/CSS
Don't minimize that HTML
Prefer one page over several
End all forms of hotlinking
Stick with native fonts
Obsessively compress your images
Eliminate the broken URL risk

1. Simplicity is essential
2. Solve problems instead of creating them
3. We are not smarter than others, others are usually not smarter
4. Do everything yourself
5. Strive for robustness
6. Do not think you can make computing "secure"
7. Use input devices when they make the most sense
8. Avoid all ornaments
9. Tools are just tools
10. Be humble
11. Don't work for free if you do not enjoy it
12. Do not listen to others

Software is a way to get something done.

The followers of the Code It Yourself Manifesto believe in these things:

• We implement it according to our own goals.
• We make mistakes and learn from them.
• We learn how our tools we depend on need to work.
• We gain a deep understanding of our problem domain.

Another manifesto. Thanks for it. I add it to the collection.