3 ms·
In my experience, this is what actually happens. A developer makes a low-quality, low-effort prototype under the assumption it won’t ship. Someone sees it. It g
by shortcake27 3y ago
In my experience, this is what actually happens. A developer makes a low-quality, low-effort prototype under the assumption it won’t ship. Someone sees it. It gets shipped. Everyone loses.
- jstarfish 3y agoSabotage your prototypes then. Have it reset its state every 5 minutes or deliberately leak memory.
- gjvc 3y agoSneaky move.... but then, in the eyes of some people, you might well appear not competent to put together a working system, so make sure you know your audience.
- sodapopcan 3y agoYa, this basically. It helps if you have tests because when prototyping, you can write things in a way which break tests and ideally break other features. It works enough that you can validate the one idea. That way it will never pass CI.
- hyperthesis 3y agoThey are cunning. You cannot sabotage it enough to fool them.