Live data from Hacker News

Coding Horror: Code: It's Trivial

codinghorror.com

1–10 of 47 posts

Re: Coding Horror: Code: It's Trivial

#5
Code may be trivial, but it's still the critical path.

Even if you do everything else well, your chances of success decrease geometrically with the crappiness of your code. Or...

Success = (A+B+C+...+Z) * SQ^2

where SQ is Software Quality and A thru Z are everything else.

Re: Coding Horror: Code: It's Trivial

#6
post #3

It's interesting quite how much "defensive" blog content those couple of HN comments sparked off.

Almost any response was guaranteed fairly decent coverage from news.yc.

True. I was actually looking forward to see the guy attempt the "clone". For all the meta discussion about what exactly "clone" completely entails simply the idea of trying to roll out something along the same lines in a weekend is intriguing.

Could it be done? How would it go down? Would working processes change? Is there stuff to learn about the development process that speed highlights?

It could make a great discussion!

Re: Coding Horror: Code: It's Trivial

#7
post #2

> No, I don't take this claim seriously. Not enough to write a response. Uhhh, isn't the post his response? Just saying.

I believe he meant a direct response to the 'in a weekend' claim itself. Which he doesn't respond to, aside from citing Benjamin Pollack.

The rest of his post is more of what we've had in every thread on the subject: Doing It vs Doing It Well

(edit: sp)

Re: Coding Horror: Code: It's Trivial

#8
Jeff's conclusion reminded of an adage I read recently about creative work (pardon me for paraphrasing and savagely butchering the author's idea -- I can't seem to find the source now): "Creative work of high quality is not the end. The real work stars once you're done with your work, for making people interested and know about it is as important as your creation itself." In other words, the real work starts once you're done coding.
Post reply on HN