Karmic Rules for Writing Pretty Good Code

In order by insertion:

0. Minimize external dependencies and try not to use shitty libraries.

1. Troubleshooting works just like the regular kind: you won't hit your target if you don't have one.

2. Nothing raises issues like contact with reality.

3. If you want to get a complex process right, template it.

4. A work in progress is the best kind.

5. Generic logic + custom config ≫ custom logic

6. It is better to do things on purpose than by accident: ergo, design.

7. Iterating: regularly on purpose ≫ by accident with your hair on fire.

Contributors

Submit an issue with your entry.