Comment #1 posted on 2016-12-14 02:03:49 by dodddummy
I've only just started this ep but wanted to stop and comment. So many of my prototypes are running in production as we speak. Many of them still with original known bugs no body ever got around to fixing. I've learned not to be embarrassed over this. After all, they put them in production and didn't bother to fix the bugs for years and years.
Comment #2 posted on 2016-12-15 09:51:45 by clacke
Re: protos in production
You have a point, maybe my suggestion to make sure the prototype cannot possibly be taken into production is too extreme.
I agree with you that one shouldn't be embarrassed over it when it happens. Bad code that solves the problem and doesn't eat more maintenance resources than it's worth is good code.
I think it's one of those pieces of advice that, like all (?) good advice, has a dynamic to it should not be taken to far in either direction.
"Your prototype will be put in production" as a warning is counteracted by "... but perfect is the enemy of good". If your proof of concept actually solves the problem, maybe it *should* be put in production.
I think the nuanced lesson to take home from this aphorism is this: The hacker should be aware that their code may be put into production at any time, so that they can make the right balance of decisions on what quality it should be when presenting it.
Note to Verbose Commenters
If you can't fit everything you want to say in the comment below then you really should record a response show instead.
Note to Spammers
All comments are moderated. All links are checked by humans. We strip out all html. Feel free to record a show about yourself, or your industry, or any other topic we may find interesting. We also check shows for spam :).