Requirements Are Always Wrong

Thomas Soares
Aug 5, 2019 · 4 min read

As software engineers, we tend to operate under the assumption that our job is to take a set of requirements as input, and emit a bunch of code that meets those requirements as output. If our code does what the requirements say, we give ourselves a big high-five and walk away believing that we’ve done our job. It is a comfortable (for us) modus operandi, and allows us to conveniently place blame elsewhere if the solution we build…