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/
![Write Better JavaScript with Promises]()
You've probably heard the talk around the water cooler about how promises are the future. All of the cool kids are using them, but you don't see what makes them so special. Can't you just use a callback? What's the big deal? In this article, we'll...
![Page Visibility API]()
One event that's always been lacking within the document is a signal for when the user is looking at a given tab, or another tab. When does the user switch off our site to look at something else? When do they come back?
![Do / Undo Functionality with MooTools]()
We all know that do/undo functionality is a God send for word processing apps. I've used those terms so often that I think of JavaScript actions in terms of "do" an "undo." I've put together a proof of concept Do/Undo class with MooTools.
The MooTools...
![Drag and Drop Z-Index Stacking]()
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!