The Truth About Code Review

By  on  

Code review is an essential practice for organizations that cater to large amounts of traffic and want to ensure maintainability throughout a team of developers.  Of course that doesn't mean that every developer on the team thinks and codes the same way, so code review (in many cases) is in place to ensure that the code has no loose ends or security holes.  If there was ever an accurate illustration of code review, this would be it:

Code Review

No one is ever completely satisfied with each piece, but as long as there's nothing insecure or dysfunctional, it's usually best to let it pass.

Image source: http://commadot.com/

Recent Features

Incredible Demos

  • By
    MooTools: Set Style Per Media

    I'd bet one of the most used MooTools methods is the setStyle() method, which allows you to set CSS style declarations for an element. One of the limitations of MooTools' setStyle() method is that it sets the specific style for all medias.

  • By
    CSS Sprites

    The idea of CSS sprites is pretty genius. For those of you who don't know the idea of a sprite, a sprite is basically multiple graphics compiled into one image. The advantages of using sprites are: Fewer images for the browser to download, which means...

Discussion

  1. So true!! lol

    • Stephen

      I would add comprehensible/maintanable to the requirement to let it pass.

  2. LOL. This is incredibly funny, and incredibly true!

  3. Loilo

    I actually like this version more. :-)
    http://www.osnews.com/images/comics/wtfm.jpg

  4. Heh, good stuff!

  5. LOL i saw this for the first time on the book http://www.amazon.com/Clean-Code-Handbook-Software-Craftsmanship/dp/0132350882. I was reading in the beach and start laughing by my self. Weird!

Wrap your code in <pre class="{language}"></pre> tags, link to a GitHub gist, JSFiddle fiddle, or CodePen pen to embed!