Think Like a Software Engineer
Build the judgment behind the code. Decompose problems, weigh tradeoffs out loud, debug from evidence, and review code, all through interactive scenarios instead of writing Go.
Courses
Problem Decomposition
Break a fuzzy problem into pieces that each do one thing, with clear boundaries between them. You decide what the pieces are and what depends on what, before any of it turns into code.
Engineering Judgment
Speed against correctness. Simple against flexible. Build it yourself or take the dependency. Work out what each side costs and make the call the project actually needs.
Systematic Debugging
Memory climbs overnight, requests start timing out, background jobs stop finishing and nobody knows why. Trace the failure one step at a time, rule out what it is not, and narrow it down to the line that caused it.
Reading Code & Review
Spot the code that should not reach production. Work through real diffs, mark the lines that are wrong, and say what each one breaks once real traffic hits it.