I find it incredibly useful to do this with code too! If you’re managing a service/library that other humans integrate with, write some fake integration code a

I find it incredibly useful to do this with code too! If you’re managing a service/library that other humans integrate with, write some fake integration code as if you are one of those other humans. I don’t mean end-to-end tests, this is even dumber than that, and must be done _way_ before codifying behavior with tests coverage to avoid future regression. Is the integration clunky, or worse, are some interactions not even possible? This exercise will shine a sobering light on such sharp edges. Would one small interface change eliminate 30 lines of frequently duplicated integration code? Is required functionality missing? It is difficult to surface all such usability issues in a vacuum, but they surface very naturally when actually using the tool that you are building— even if it’s all made up so far. Remember, this is for people to _use_, not a piece of art to be observed but never touched. Put into metaphor: don’t build the world’s fastest car and omit the steering wheel, gas and break pedals, seats, doors, windows, mirrors, etc., all because you never stopped to think about how someone might _drive_ the damn thing.