In the first of a two-part series, we'll explore how to avoid bad data and validate data at the boundary of a Phoenix application.