P1
Scope before content
Every module states what it covers, what it deliberately excludes and what you should be able to do at the end. Ambiguous scope is how time disappears.
04 — Method
How DevCSE works
Four stages, repeated at every level. The sequence is deliberate: nothing is built before it is practised, and nothing ships without review.
- Stages
- 4
- Measured on
- Demonstrated skill
- Review
- Written
- Pace
- Self-directed
- 01 / Learn
LEARN
Structured material with a stated scope. You know what a module covers before you start it, and what you should be able to do after.
- 02 / Practice
PRACTICE
Short exercises directly after each concept. Repetition on the parts that are actually hard, not on the parts that read well.
- 03 / Build
BUILD
Every path ends in work you can show: a running project, a written decision log, and code someone else can read.
- 04 / Grow
GROW
Review, feedback and the next step. Progress is tracked against skills, not against hours of video watched.
Operating principles
P2
Practice next to the concept
Exercises sit directly after the idea they test, and repetition is weighted towards the parts that are genuinely hard rather than the parts that read well.
P3
Evidence, not attendance
Progress is recorded as demonstrated capability: a running artefact, a written decision log, code someone else can read without you in the room.
P4
Feedback with reasoning
Reviews explain why, name the trade-off considered, and end with a concrete next step. A verdict without reasoning teaches nothing.