Start here
Software Habits Every Maker Should Learn
A practical overview of the habits that turn a throwaway script into a project you can still understand, fix and extend months later, from backups to tests.
Software Bench
Habits and concepts that make small software projects reliable.
Start here
A practical overview of the habits that turn a throwaway script into a project you can still understand, fix and extend months later, from backups to tests.
A plain-language explanation of web APIs: how requests and responses work, what status codes, keys and rate limits mean, and how to use an API politely.
Why a public project needs a licence, how permissive and share-alike licences differ in concept, and what to think about before you choose. Not legal advice.
Compare table-based SQL databases with flexible NoSQL stores, and learn how to pick sensibly for a small project such as a sensor logger or personal app.
A systematic approach to finding faults: reproduce the problem, narrow it down, test one hypothesis at a time and verify the fix, instead of guessing.
Learn which datasheet sections to read first, how to find absolute maximum ratings, pinouts and wiring details, and how to avoid common misreadings.
How to model a device as states and transitions so control code stays manageable, with a simple example, common pitfalls and tips for testing the logic.
How to start automated testing on a small project with nothing more than a script: what to test, how to keep logic testable and how tests catch regressions.
A conceptual introduction to Git: commits, branches, history and remotes, and why even a solo maker benefits from tracking changes to a project.
Practical advice on naming, structure and commenting that makes code easy to understand later, with guidance on when a comment helps and when it hurts.
Related topics