Re:Throw away your first draft of your code
by tuwtuwtuwtuw on Friday August 04, 2023 @04:00PM
(#37005082)
Yeah, this thread is a somewhat strange read. People don't seem to understand what "draft" or "prototype" means. Odd.
[ Parent
| on HN ]
Re:Throw away your first draft of your code
by redblacktree on Friday August 04, 2023 @04:50PM
(#37005701)
Just like management. I can't tell you how many times I've written a "Proof of Concept" that became production code.
Re:Throw away your first draft of your code
by doublerabbit on Friday August 04, 2023 @05:34PM
(#37006197)
I did that today. Rewrote a bash script in to a perl script as Proof of Concept. it's now in UAT... but I like perl, hey ho.
Re:Throw away your first draft of your code
by Vicinity9635 on Friday August 04, 2023 @09:30PM
(#37008060)
To turn this around, a proof of concept is the fastest way to get code into prod ;)
Re:Throw away your first draft of your code
by gillesjacobs on Saturday August 05, 2023 @06:23AM
(#37010664)
This has caused me so much grief. I find it key to communicate to all stakeholders the production process from PoC to MVP to MVP+.
Still managers always push against redoing work they can see working for the happy flow.
Re:Throw away your first draft of your code
by Tokumei-no-hito on Sunday August 06, 2023 @10:42PM
(#37029418)
I feel this. What I do now is increase the points of the PoC (real estimated PoC time + optimization).
I get the PoC down asap then as soon as it’s proven (privately to myself) I move onto optimizing. If it fails then I communicate early to discuss a change of scope.
Assuming it succeeds, by the time I present it I have already done significant work making it production ready. So to request an extra 10-25% time to “smooth out the edges” goes over easy after the demo.
In reality I end up with 50-75% time to get it prod ready. The rest is QA + prod bug fixes to take it over the (practically scoped) finish line.