tag:blogger.com,1999:blog-28344720.post4808622745242366708..comments2024-02-21T06:47:29.430-07:00Comments on Chip Overclock<sup><small>®</small></sup>: The Code Also RisesChip Overclockhttp://www.blogger.com/profile/11195242013008369733noreply@blogger.comBlogger3125tag:blogger.com,1999:blog-28344720.post-67283311113439097532012-05-18T15:36:05.899-06:002012-05-18T15:36:05.899-06:00Chip,
You missed the chance to reiterate the impo...Chip,<br /> You missed the chance to reiterate the importance of defining "done" before you start any task. As an advocate of TDD, I expected you do emphasize this key point.<br /><br /> KenAnonymousnoreply@blogger.comtag:blogger.com,1999:blog-28344720.post-18464281377840883862012-05-05T09:59:21.348-06:002012-05-05T09:59:21.348-06:00Code which accomplishes its intended purpose is su...Code which accomplishes its intended purpose is successful. It it's intended purpose is to generate revenue, code that does not generate revenue is not successful. If you don't know why you're writing a piece of code, maybe it's time to think about not writing it.<br /><br />This next point is worthy of at least one entire article all by itself. There is a strong tendency in all Chip Overclockhttps://www.blogger.com/profile/11195242013008369733noreply@blogger.comtag:blogger.com,1999:blog-28344720.post-81625747248456922172012-05-05T07:59:45.464-06:002012-05-05T07:59:45.464-06:00Doesn't good code depend on the metric used to...Doesn't good code depend on the metric used to measure the code?<br /><br />Does it make money? Is it elegant? Is it understandable/maintainable? Did it get completed on time with the expected quality? How long is the life of the code?<br /><br />Is (the code/a book) ever finished from the authors perspective?<br /><br />I've seen really bad code make lots of money and I've seen Todd Blachowiaknoreply@blogger.com