3 ms·
What I do is classify parts as either prototype or release. Prototype is code that is built for the sake of proving something - it might be to gauge user behav
by muzani 7y ago
What I do is classify parts as either prototype or release.
Prototype is code that is built for the sake of proving something - it might be to gauge user behavior, or convince investors/customers you can do this cool stuff. It might be because it's hard to plan something and easier to hack it together.
Prototype code is built disposable. You can throw it away and replace it with an optimized thing later, and they're decoupled enough to be disposed. For pre-PMF startups, nearly 100% of code is prototype.
For prototypes, I write tests, but it's a manual checklist. It's also usually user behavior focused, such as "user tries to upload 15 images from third party photo gallery and gets an error limiting them to 5 images at a time".
There's some point where it's more efficient to write tests than keep pressing buttons.
Once you decide a feature is concrete (probably someone is paying for it), then you can refactor that and do some TDD on it.