Thinking like a developer, part II: design the edge cases