3 ms·

Summary: The author clickbaits the title with "don't do X". Proceeds with a life story of his struggles ommiting what X is.

pattrn 8y ago
Sorry about that. I guess I didn't really think much about the title sounding like clickbait. The phrase is what motivated me to write the post, so I used it as the title. Perhaps I should put quotes around it?
- turdnagel 8y ago
  Quotes would probably be more "accurate," but I don't think they'd quell this person's (unwarranted) complaints. I believe sharing your story was valuable and I look forward to reading more of your blog.
  - pattrn 8y ago
    Updated. Thanks!
- quickben 8y ago
  It would help, thank you for that. I was expecting an actual example, which what was my problem with the title. It was more subtle than that so I read the whole thing but kept wanting to know what the damn line was. The downvotes that I am receiving actually reflects the same conceptual problem that you are outlining in the article. People are nice. They don't call out bullshit early on, and companies end up with nice-but-incompetent that can't deliver quality (but apparently can downvote on HN thinking they are doing right in life following the echo chamber). This doesn't plague many other licensed industries. Either you reach a level to get your license (and lose it if you are incompetent), or won't be doing your professional job at all. There is no "nice" in law, medicine, architecture, etc, where professionalism is concerned. It's conflicting. Should we be altruistic, promote teaching, but also promote being not nice? Or shall we be selfish, keeping quiet and ensuring our personal job-security because we can fix messes afterward. Overall, I think your blog is in the right general direction. Best of luck.
lmkg 8y ago
X in this case is copy-pasting code into production from blogs that explicitly say not to copy-paste their code into production. I do not feel it was omitted from the article, it was stated rather directly more than once. Perhaps you were expecting a description of why that particular code was unsuitable for production? The blog is about the process of writing code, not the code itself.
jasonlotito 8y ago
> The author clickbaits the title with "don't do X". It's not. > Proceeds with a life story of his struggles ommiting what X is It does.
Walkman 8y ago
If you can't even read, why bother commenting?
- dang 8y ago
  Please don't reply to a bad comment with a worse one. Personal attacks in particular will get you banned here. https://news.ycombinator.com/newsguidelines.html https://news.ycombinator.com/newsguidelines.html

pattrn 8y ago

Sorry about that. I guess I didn't really think much about the title sounding like clickbait. The phrase is what motivated me to write the post, so I used it as the title. Perhaps I should put quotes around it?

turdnagel 8y ago
Quotes would probably be more "accurate," but I don't think they'd quell this person's (unwarranted) complaints. I believe sharing your story was valuable and I look forward to reading more of your blog.
- pattrn 8y ago
  Updated. Thanks!
quickben 8y ago
It would help, thank you for that. I was expecting an actual example, which what was my problem with the title. It was more subtle than that so I read the whole thing but kept wanting to know what the damn line was. The downvotes that I am receiving actually reflects the same conceptual problem that you are outlining in the article. People are nice. They don't call out bullshit early on, and companies end up with nice-but-incompetent that can't deliver quality (but apparently can downvote on HN thinking they are doing right in life following the echo chamber). This doesn't plague many other licensed industries. Either you reach a level to get your license (and lose it if you are incompetent), or won't be doing your professional job at all. There is no "nice" in law, medicine, architecture, etc, where professionalism is concerned. It's conflicting. Should we be altruistic, promote teaching, but also promote being not nice? Or shall we be selfish, keeping quiet and ensuring our personal job-security because we can fix messes afterward. Overall, I think your blog is in the right general direction. Best of luck.

lmkg 8y ago

X in this case is copy-pasting code into production from blogs that explicitly say not to copy-paste their code into production. I do not feel it was omitted from the article, it was stated rather directly more than once. Perhaps you were expecting a description of why that particular code was unsuitable for production? The blog is about the process of writing code, not the code itself.

jasonlotito 8y ago

> The author clickbaits the title with "don't do X". It's not. > Proceeds with a life story of his struggles ommiting what X is It does.

Walkman 8y ago

If you can't even read, why bother commenting?

dang 8y ago
Please don't reply to a bad comment with a worse one. Personal attacks in particular will get you banned here. https://news.ycombinator.com/newsguidelines.html https://news.ycombinator.com/newsguidelines.html