The Truth About Code Review
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:
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/
![5 Awesome New Mozilla Technologies You’ve Never Heard Of]()
My trip to Mozilla Summit 2013 was incredible. I've spent so much time focusing on my project that I had lost sight of all of the great work Mozillians were putting out. MozSummit provided the perfect reminder of how brilliant my colleagues are and how much...
![Welcome to My New Office]()
My first professional web development was at a small print shop where I sat in a windowless cubical all day. I suffered that boxed in environment for almost five years before I was able to find a remote job where I worked from home. The first...
![MooTools FontChecker Plugin]()
There's a very interesting piece of code on Google Code called FontAvailable which does a jQuery-based JavaScript check on a string to check whether or not your system has a specific font based upon its output width. I've ported this functionality to MooTools.
The MooTools...
![Adding Events to Adding Events in jQuery]()
So true!! lol
I would add comprehensible/maintanable to the requirement to let it pass.
LOL. This is incredibly funny, and incredibly true!
I actually like this version more. :-)
http://www.osnews.com/images/comics/wtfm.jpg
Heh, good stuff!
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!