4 ms·

Throwing away an established code base is a completely different thing from throwing away a few-days-old prototype, and not what the article is suggesting. The

Throwing away an established code base is a completely different thing from throwing away a few-days-old prototype, and not what the article is suggesting. The points you mention don't apply to the prototype case.

tuwtuwtuwtuw 3y ago
Yeah, this thread is a somewhat strange read. People don't seem to understand what "draft" or "prototype" means. Odd.
- redblacktree 3y ago
  Just like management. I can't tell you how many times I've written a "Proof of Concept" that became production code.
  - doublerabbit 3y ago
    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.
  - Vicinity9635 3y ago
    [dead]
  - gillesjacobs 3y ago
    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.
  - Tokumei-no-hito 3y ago
    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.
ninepoints 3y ago
This is such a HN phenomenon it infuriates me. Read article. Then read comment that misconstrues article to be something completely different, accompanied with loud critique. Read replies all in violent agreement to obviously self-evident strawman.
- duxup 3y ago
  Sadly, it’s an everywhere phenomenon :(
  - Vicinity9635 3y ago
    [dead]
- quickthrower2 3y ago
  It is a something-man. Maybe a strawman? Or a weakman?
  - alsetmusic 3y ago
    He-Man? Superman? Batman? Captain Planet… wait.
- mathisfun123 3y ago
  The misunderstanding you have is that often the article isn't the point. Just like a football match in a pub isn't always the point. People just want to chime in - the comment section is like an ephemeral pub. If that bugs you because you consume information on the web rather than socialize, the solution is simple: don't read comment sections and make up your own mind about the article.

tuwtuwtuwtuw 3y ago

Yeah, this thread is a somewhat strange read. People don't seem to understand what "draft" or "prototype" means. Odd.

redblacktree 3y ago
Just like management. I can't tell you how many times I've written a "Proof of Concept" that became production code.
- doublerabbit 3y ago
  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.
- Vicinity9635 3y ago
  [dead]
- gillesjacobs 3y ago
  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.
- Tokumei-no-hito 3y ago
  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.

ninepoints 3y ago

This is such a HN phenomenon it infuriates me. Read article. Then read comment that misconstrues article to be something completely different, accompanied with loud critique. Read replies all in violent agreement to obviously self-evident strawman.

duxup 3y ago
Sadly, it’s an everywhere phenomenon :(
- Vicinity9635 3y ago
  [dead]
quickthrower2 3y ago
It is a something-man. Maybe a strawman? Or a weakman?
- alsetmusic 3y ago
  He-Man? Superman? Batman? Captain Planet… wait.
mathisfun123 3y ago
The misunderstanding you have is that often the article isn't the point. Just like a football match in a pub isn't always the point. People just want to chime in - the comment section is like an ephemeral pub. If that bugs you because you consume information on the web rather than socialize, the solution is simple: don't read comment sections and make up your own mind about the article.