I Built the MVP First. Then I Wrote the README.

Description and use

<p>I did this in the wrong order.</p> <p>At least, that was my first thought.</p> <p>I was building a small project that checks images and documents for privacy risks. The backend came first, then the API, then a frontend that finally made it feel like an actual service.</p> <p>Somewhere along the way, I realized something.</p> <p>I had built quite a lot before properly organizing the requirements and documentation.</p> <p>Normally, I would expect the order to look more like this:</p> <blockquote> <p>requirements → design → implementation → testing → documentation</p> </blockquote> <p>Mine loo

Problem

<p>I did this in the wrong order.</p> <p>At least, that was my first thought.</p> <p>I was building a small project that checks images and documents for privacy risks. The backend came first, then the API, then a frontend that finally made it feel like an actual service.</p> <p>Somewhere along the way, I realized something.</p> <p>I had built quite a lot before properly organizing the requirements and documentation.</p> <p>Normally, I would expect the order to look more like this:</p> <blockquote> <p>requirements → design → implementation → testing → documentation</p> </blockquote> <p>Mine loo

Outcome

<p>I did this in the wrong order.</p> <p>At least, that was my first thought.</p> <p>I was building a small project that checks images and documents for privacy risks. The backend came first, then the API, then a frontend that finally made it feel like an actual service.</p> <p>Somewhere along the way, I realized something.</p> <p>I had built quite a lot before properly organizing the requirements and documentation.</p> <p>Normally, I would expect the order to look more like this:</p> <blockquote> <p>requirements → design → implementation → testing → documentation</p> </blockquote> <p>Mine loo

Evidence

I Built the MVP First. Then I Wrote the README.

Source