CodeinWP CodeinWP

The Complete Guide to Commenting on Web Design Blogs

Read the whole article.

58 Responses

  1. Izzat Aziz says:

    haha, well put straight to bottom line.
    but sometime, post way too long..

    • Alex Hall says:

      If the post is way too long then you haven’t appreciated it and understood it fully and therefore would be providing comments, or questions that have been answered or discussed in the bits you didn’t read.

      You can only validly comment on a post you have completed read and understood (unless you haven’t understood it, and are questioning it).

  2. Jordan says:

    Niiice. Sums it up pretty well.

  3. Joe Makala says:

    This post was a complete waste of my time…

  4. Richie says:

    Haha… pretty much open and shut case… perfectly put, Louis x-)

  5. varunsain says:

    The ‘Comment Rules’ at the end made more sense than your article…

    Was funny tho..

  6. Jae Xavier says:

    seems “impressive enough”

    you could have tweeted this. ^ . ^

  7. Aidan says:

    Oh yes…..Read and be understand!

  8. dule says:

    Read the Whole? What is Whole?

  9. Phil says:

    ehm, that’s not just the guide to commenting on design blogs but rather every blog ;-)

  10. Pusparaj says:

    Haha. Very intuative, very inspirational, very motivating, just kidding. hahaha.

  11. Clayton says:

    Yes, this is a very good starting point. Nice typography!!!

  12. Ilie Ciorba says:

    Great post Luois :) I wrote it twice to understand what’s happening :)

  13. BlogyMate says:

    It is very good article, no doubt.

  14. BWD says:

    Its a great post. Thanks!!

  15. so, where is the article?

  16. LemonPro says:

    Where is the article? :P

  17. Radu says:

    :applauding in agreeance:

  18. Patrick says:

    haha. yeah, that sums it up!

    Well, it’s not really a guide, but it’s definitely the most important thing. Nice idea for an article!

  19. Jon says:

    How do you read a hole?


  20. Tom says:

    WOW. You guys rock! This magazine is awesome! Keep it up! Awooosaaam! ;)

  21. Tom says:

    Need to correct my previous commnts: will read the whole article later – but so far: great! I agree in all points. One thing: I think you have wrong spelling (could call it typo, since I know) somewhere up there. But otherwise – I enjoyed the read.

  22. *reads the whole post*
    … IDIOT

  23. Idk… sometimes everyone seems to fill their articles with complete bull**** just so they can have a high AVG time on site, go to the bottom, get the gist of the argument/article and I feel I have a firm grasp on it. 90% of the rest of the articles are opinion.

    I’d rather not waste my time.

  24. Vimal says:

    Lol –> KISS in action… Shouldn’t we also read the comments too? :)

    • Actually, that’s a very good point. But sometimes, it just takes too long to read all the comments, so I personally don’t think that’s always necessary. It just might be good behaviour to mention that you didn’t have time to read all the responses.

  25. webangel78 says:

    Yes this is the truth! :)

  26. Scott says:

    TLDNR ;)

    Excellently put!

  27. Ah ah, i did it this time :)
    but sometimes you just want to scan the post and focus on the content which fits your needs…

  28. aditia says:

    ahahay thats straight true,

  29. pooja says:

    i will bookmark this blog now. In this blog have many information.

  30. IcarusForde says:

    Brilliant article! So true. :)

  31. Yes true and it took long time to read this one :)

  32. Belissimo! Perfect article! It’s a very funny. LOL!!!

  33. another_misguided_commenter says:

    Awesome WordPress tutorial about threaded comments!

  34. Chris Lawlor says:

    So true – but the best part is all of the “where’s the article” comments : )

  35. Wish all posts were this long :D

  36. You are totally right IHMO, designers need to listen to pop music more often to increase productivity!

    Great article admin!


  37. Whale says:

    Some should actually read them twice!

  38. Saurabh Shukla says:

    Bang on target.
    I’m jealous.
    I’m sure enough chuckles went into it!

  39. Daniel says:

    tl;dr lol

    But seriously you make a good point here. I really dislike it when people post uninformed and sometimes nasty comments because they have missed the point of the article.

  40. vikas says:

    Hi!This is awesome guide to comment on web design blog.
    Thanks for reading.

  41. I really appreciate your article!

  42. ArdianZzZ says:

    TwoThumbs! i like it! :)

  43. Fadli Idris says:

    Hahahaha nice idea

  44. Proniit says:

    haha nice idea for an article…. good one

  45. Quickest article read ever! I actually looked twice for the article, then realized that the article was one line! Hilarious!

  46. Devsmith says:

    The Title is good and tell about important of Web design. Can’t see what article is made and i do know how 53 Comments?

    Good work.. Keep it up…

  47. This Blog post is not very Useful. It is waste of time.

  48. Rocky Singh says:

    Hey I found this article very helpful. This is what I was looking for. Definitely I will bookmark it. Check for mine too.”

  49. Aaron Taylor says:

    I love the way you put this together. Really Creative :)

  50. When leaving a comment on a blog or article, read it thoroughly before sharing your experience and suggestions, in my opinion.

Leave a Reply

Comment Rules: Please use a real name or alias. Keywords are not allowed in the "name" field and deep URLs are not allowed in the "Website" field. If you use keywords or deep URLs, your comment or URL will be removed. No foul language, please. Thank you for cooperating.

Markdown in use! Use `backticks` for inline code snippets and triple backticks at start and end for code blocks. You can also indent a code block four spaces. And no need to escape HTML, just type it correctly but make sure it's inside code delimeters (backticks or triple backticks).