What you describe is absolutely what I meant in this article, it will fall in the “Just do it” category… To me expend x days proving if something maybe right or wrong is a waste of time as you woud only find out once that you actualy try it for real.

Thanks for your comment!!!

I’m not sure I totally understand your definition of a proof of concept. For example, I needed to create a widget that could be easily included on any webpage. I’ve created them before using an iframe but I wanted to move forward with a full javascript on demand implementation.

As it was, I just went ahead and did it with the javascript with the knowledge that it might not work and I’d have to fall back to the iframe approach. Would that be considered a proof of concept or would it fall in the just do it category?

What I’m trying to say in this article is that, if you need a framework, just use it, and if you can’t pick one, because you are not sure, I would suggest to start development with a couple of options.

Expending x days trying to prove which one is going to fit better in your application, is, in my opinion, and for the reasons listed in this article, a waste of time, basically because is impossible to figure that out until you actually use it for your application.

Anyway, I understand what your point is, if in your experience you have found that proofs of concepts have drove you to the right directions, then just keep doing it, I’m just writing this article from my own experience.

In any case, thanks for you comment.

Professional people do prototypes and POC to validate a technology choice. That will save time in the medium term and will prevent problems with external library.

If you prefer rush, you do as you want but POC are good for professionnal projects.

Best regards.