markdown guide
 

A prototype is usually just the central part of an idea or an experiment. Of the experiment is successful I might copy and paste pieces of it but usually you can just refactor and get to a mvp.

The production code needs a few checks before being considered as such, like deployment code, health checks, making sure there are no obvious security issues and so on.

Frameworks tend to help in building prototypes, then it's up to you.

My favorite tool for throwaway experiments (which actually is also production ready) is Flask, you can easily write a web app in one Python file and go from there

 

I dunno if you're talking about this, but when I start a project I create the file system architecture from scratch, and create the desired files (empty, of course) to validate the structure. It worked to me to think about naming and high level abstractions before I am coding.

Classic DEV Post from Jun 13

Async, Parallel, Concurrent Explained - Starring Gordon Ramsay

Complex computing concepts simplified

Julian Garamendy profile image
I'm developing productivity tools for game teams at King.com