Day 5/90: Control flow — if, switch, loops
90 Day Go Challenge: Zero to Production
Today I focused on making control flow — if, switch, loops feel like concrete data modeling and control flow, not syntax trivia. The strongest checkpoints were make values, structs, and interfaces say one clear thing about the state they represent, use control flow and method choices to make valid transitions obvious, and prefer small explicit data shapes over clever abstractions that hide the real meaning.
The mistake I wanted to avoid was using broad or vague types until the data model stops explaining itself. The day felt better once the service boundary stayed visible and each component had one job.
The goal for tomorrow is simple: keep the rule clear enough that the next service still feels related to the same design idea. I also want to keep tracing one request path end to end because it exposes weak assumptions faster than a larger demo.
Top comments (0)