💾 Archived View for tilde.town › ~dozens › gemlog › 7.gmi captured on 2024-02-05 at 09:55:52. Gemini links have been rewritten to link to archived content
-=-=-=-=-=-=-
1. Don't write any code! If you can avoid writing code, do it.
2. Delay writing code! If you must write code, put it off for as long as it takes to thorougly understand and map out the problem. Draw lots of diagrams.
3. Throw away your code! After you thoroughly understand the problem, make some crappy proofs of concept and prototypes. It is important you make this code as crappy and unmaintainable as possible so that the POC is not confused by stakeholders for the real product. Ideally, write it in a language/platform that is not supported by your organization. Throw it away.
4. Reduce complexity as much as possible! Radically limit your dependencies. Keep pieces of your code that work together physically close to each other. Limit your abstractions. Hide the complexity of your modules behind simple interfaces.
5. Be consistent! Your conventions for naming variables and functions and git branches and commit messages isn't as important as /having/ a convention and sticking to it.
EOF