06 — Library
Technical library
Written by engineers about work they have actually done: methods, trade-offs and the decisions that get expensive later.
- Entries
- 5
- Formats
- Article · Guide · Note
- Average length
- 10 min
- Cadence
- Fortnightly
Article14 Jul 2026
Reading code you did not write
Most engineering time is spent reading, not writing. This is a repeatable method for getting oriented in a system you did not design.
8 min read
Read →Tutorial02 Jul 2026
Designing a REST API you can version
Versioning is a design problem long before it is a routing problem. The decisions that hurt later are made in the first week.
14 min read
Read →Guide21 Jun 2026
A first month with Kubernetes
The concept surface is enormous and most of it is irrelevant to your first deployment. This is the subset that pays for itself immediately.
11 min read
Read →Technical Note09 Jun 2026
Why your model looks better than it is
A validation score is a measurement of your evaluation setup at least as much as it is a measurement of your model.
6 min read
Read →Career30 May 2026
Writing an engineering portfolio that reads well
Reviewers spend two minutes on a portfolio before deciding. Those two minutes are spent looking for evidence of judgement.
9 min read
Read →
Questions
Questions, answered
01What goes into the library?
Reference writing on engineering practice: decisions, trade-offs and post-mortems that stay useful after the tools change.
02How often is it updated?
Continuously. Pieces are revised when the practice moves rather than being left to age with a publication date.
03Can I use this material with my team?
Yes, for internal reading and discussion with attribution. For redistribution or programme use, write to hello@devcse.com.
04How does a piece connect to the rest of the platform?
Each piece links to the technology areas and tracks it supports, so reading turns into building without a detour.