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/
![Send Text Messages with PHP]()
Kids these days, I tell ya. All they care about is the technology. The video games. The bottled water. Oh, and the texting, always the texting. Back in my day, all we had was...OK, I had all of these things too. But I still don't get...
![How I Stopped WordPress Comment Spam]()
I love almost every part of being a tech blogger: learning, preaching, bantering, researching. The one part about blogging that I absolutely loathe: dealing with SPAM comments. For the past two years, my blog has registered 8,000+ SPAM comments per day. PER DAY. Bloating my database...
![Create Short Preview from Video]()
![CSS Tooltips]()
We all know that you can make shapes with CSS and a single HTML element, as I've covered in my CSS Triangles and CSS Circles posts. Triangles and circles are fairly simply though, so as CSS advances, we need to stretch the boundaries...
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!