Self-development for an engineer is deliberate practice on the next constraint in your job — not collecting certificates. The refresher posts on this site exist so you can rebuild a mental model in an hour; they are not a career plan.
A practical loop
- Name a gap you hit this month (e.g. “I cannot read an
EXPLAIN,” “I froze in the incident call”). - Do one small reps cycle: a kata, a postmortem facilitation, a PR in an unfamiliar layer.
- Put it in production or in a real review. Unused notes decay.
Depth beats a scatter of frameworks. One storage engine, one HTTP stack, one observability tool, well, will transfer. Twenty tutorials will not.
Example
What breaks it: a certificate collected the month after an incident where nobody could read an EXPLAIN.
Better: one deliberate rep on that gap, then used in a real review the same month.
Pitfalls
- Learning only on the employer’s stack until you cannot interview.
- Learning only for interviews until you cannot ship.
- Side projects that never see a user or a test.
Mentoring is the other half: mentoring. Technical spine: start from SOLID and defensive programming.