3 ms·
the way to go is do 2, read what you wrote, then throw it out and do 1. now you know better what docs are worth reading, and you'll digest them faster with cont
by tomjakubowski 3y ago
the way to go is do 2, read what you wrote, then throw it out and do 1. now you know better what docs are worth reading, and you'll digest them faster with context gained from your throwaway.
it will be only a little bit slower than 2 on its own and it will be written better because it's not just accumulated debris from your learning
- beardedetim 3y agoI 100% agree with this. Have always called it `throw-away development` where you build a prototype just to understanding what it is that you are actually solving/building. Then, once you understand, implement the _actual_ thing you need to, taking the learnings from the throw-away. It takes a _tad_ longer than if you had magically known what to do from the get-go but the learning is invaluable.
- notpachet 3y agoJust as long as you avoid the trick where you complete the POC, and then your manager moves you onto something else and reassigns a junior to productionize the POC.
- commandlinefan 3y ago> reassigns a junior to productionize the POC At least until the deadline passes and he still doesn't have it working, then you have to do the something else you moved on to _and_ productionize the POC that was already overdue last week.
- w0m 3y agoThe problem when you do 2 'just enough' for it to (barely) work - if you show it to your manager, they'll Ships It and you'll get put on a new project to hack together.