<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Boundaries on Brian Faust</title><link>https://wimdy.works/tags/boundaries/</link><description>Recent content in Boundaries on Brian Faust</description><generator>Hugo</generator><language>en-US</language><lastBuildDate>Mon, 01 Jan 0001 00:00:00 +0000</lastBuildDate><atom:link href="https://wimdy.works/tags/boundaries/rss.xml" rel="self" type="application/rss+xml"/><item><title>Validate at the Boundary You Control</title><link>https://wimdy.works/thoughts/validate-at-the-boundary-you-control/</link><pubDate>Thu, 01 Mar 2018 00:00:00 +0000</pubDate><guid>https://wimdy.works/thoughts/validate-at-the-boundary-you-control/</guid><description>&lt;p&gt;A booking request contains a recipient email and a phone number made entirely
of spaces.&lt;/p&gt;
&lt;p&gt;For one delivery service, email is enough. For the same service with a
particular handoff option, a phone number is mandatory. For another service,
phone is always mandatory.&lt;/p&gt;
&lt;p&gt;So is the phone optional? That question is already too vague. There is no
honest global rule such as “phone is nullable” or “phone is required.” The
answer depends on the operation the request asks the system to perform.&lt;/p&gt;</description></item></channel></rss>