Map first, build second
System Design
Most software fails before the first line of code—in rushed assumptions and the wrong problem framed too quickly. We map the real system first: users, constraints, trade-offs, and the seams that survive the next pivot.