mixed · practice
Engineering practice: git, code, tests
The craft half of the job, plus a weekly coding exercise to actually practise on.
·
By Amit Chakraborty — Kolkata, India · Remote worldwide
What you will be able to do
Work in a way that other engineers, and your future self, can follow.
Syllabus — 12 chapters
- 1. Git as a thinking tool — Write commits that explain a change to a stranger, including you in a year.
- 2. Branching, rebasing and conflicts without fear — Resolve a real conflict and recover from a mistake using the reflog.
- 3. Code review: what to look for, in what order — Review effectively and receive review without defensiveness.
- 4. Naming, the hard part — Name things so the code stops needing comments to be readable.
- 5. Functions, modules and where to draw the line — Decide what belongs together using something better than instinct.
- 6. Comments that earn their place — Write the comments that survive and delete the ones that lie.
- 7. Testing: what to test and what not to — Decide where tests pay for themselves.
- 8. Test doubles and the mocking trap — Use fakes and mocks without testing your own mocks.
- 9. Refactoring safely in small steps — Change structure without changing behaviour, provably.
- 10. Debugging as a discipline — Bisect, hypothesise and prove, rather than changing lines hopefully.
- 11. Reading code you did not write — Get oriented in an unfamiliar codebase quickly.
- 12. Deliberate practice that compounds — Build a weekly routine that makes you measurably better.
0 of 12 published. A new chapter every Sunday night. Free to read.
Learn it free, elsewhere too
The documentation, videos, books and practice sites worth your time on this subject. All free. None of it is mine.