Prototypes are not only great for learning concepts better, but they are also great for doing highly reliable project estimations. Here’s how …

Prototyping is about building fast and low-quality stuff that is never meant to be shipped to production, nor is expected to follow any best practices. They are meant to gather the information, build an understanding, and then be thrown away.

Project estimations are hard, as we all are guilty of making random guesses while estimating efforts. Instead, it is better to build a quick prototype and make an informed decision. Prototypes help us answer some critical questions.

• what will be a tentative task breakdown
• how long each task would take
• what are the unknown unknowns
• which parts of the system are hard, and where the risks lie
• more importantly, can this even work

Beyond technical feasibility, prototypes also help in gauging whether people even care about the solution. Sometimes, showing a quick demo is enough to validate interest or reveal disinterest before you go all-in.

It’s often better to spend a few hours testing an idea than to invest weeks in something doomed from the start.

If you are learning new things every day, Prototyping is the easiest way to build a practical understanding, be it around system design, advanced algorithms, or even an idea that you find interesting. You often learn faster by doing than by just reading or planning.

Remember, it’s okay to discard prototypes. Their value is in what they teach you, not in their longevity. Make prototyping a habit. Most prototypes don’t take more than 200 lines. Treat them as experiments and not polished products.

So, when in doubt, code it out.