4 ms·

I paint (mostly acrylic) and code. To me, the notion of building a practice run is very liberating; it enables me to think about components, how they should be

I paint (mostly acrylic) and code. To me, the notion of building a practice run is very liberating; it enables me to think about components, how they should be named/organized, how they interact without the pressure of "getting it right the first time". The time-box for throwaway work should be small. Small enough such that you feel a firm confident grip on the plan at hand. If you have something fully end-to-end operational then more than likely the throwaway has been overworked. I encourage you to consider trying out more throw-away work before writing the real thing. You find yourself with not only a more lucid vision of what goes in to the "real thing" but a little more muscle memory in getting started down the right path.

AstralStorm 8y ago
Unfortunately you cannot throw away a building with a fresco, and many useful applications are of this sort of size. (Even something as "simple" as email.) The best you can do is paint the fresco on paper, digitize, design the building outline and iterate 3D building designs. And you have not considered materials and structural design at this point and do not even have a scale physical model. Prototypes work for small, enclosed apps with limited functionality. Not even video games most of the time and these are relatively small and specific. Word processor? Good luck. DAW? Oh my. CAD/CAM tool? You've got to be kidding me. IDE? Nope. A compiler? You'll rewrite it a few times. Desktop environment? A good recipe to lose users. Even CRUD... You cannot iterate a painting into a building with a fresco. The thing is that currently an MVP is definitely huge, as much as startups would like everyone else to believe otherwise.