-
Archives
- December 2018
- October 2018
- March 2018
- October 2017
- February 2017
- April 2016
- March 2016
- February 2016
- March 2015
- December 2014
- October 2014
- August 2014
- July 2014
- February 2014
- October 2013
- September 2013
- August 2013
- July 2013
- June 2013
- April 2013
- March 2013
- January 2013
- October 2012
- July 2012
- November 2011
- October 2011
- September 2011
- August 2011
- July 2011
- June 2011
- May 2011
- April 2011
- March 2011
- February 2011
- January 2011
- December 2010
- November 2010
- September 2010
- August 2010
- July 2010
- June 2010
- May 2010
- April 2010
- March 2010
- January 2010
- December 2009
- November 2009
- September 2009
- August 2009
- July 2009
- June 2009
- May 2009
- March 2009
- February 2009
- January 2009
- December 2008
- November 2008
- October 2008
- September 2008
- August 2008
- July 2008
- June 2008
- May 2008
- April 2008
- February 2008
- January 2008
- December 2007
- November 2007
- October 2007
- September 2007
- August 2007
- July 2007
- June 2007
- May 2007
- April 2007
- March 2007
- February 2007
- October 2006
- September 2006
- August 2006
- July 2006
- June 2006
- May 2006
- April 2006
- March 2006
- February 2006
- January 2006
- December 2005
- June 2005
-
Meta
Category Archives: code review
Code review #10: No emailed code questions
[Update #1: below is added in response to Hersh’s comment] Developers have this: “I am too busy to comment” “Comments are a waste of time because no one reads them” “What should I say? (read this previous post about commenting … Continue reading
Posted in code review, self improvement, technical
2 Comments
Code Review #9 : The importance of doing the small things right
Do the small things right. Make sure your craftmanship shows pride. The code “working” is not enough. The craftmanship. The attention to detail is equally important. Part of the way that Steve Jobs made Apple great is his insistance on … Continue reading
Posted in code review
Leave a comment
Use Subclasses and alternative interface implementations to reduce “future” bugs
One of the little-appreciated consequences of subclassing or alternative implementations of Java interfaces is to reduce or eliminate “future bugs”. “Future bugs” are bugs that are currently not wrong, but will cause problems in the future. Every conditional ( if, … Continue reading
Posted in code review
Leave a comment
How to do a redirect after POST
Continuing an StackOverflow answer: Its a little non-obvious but: create a keyed-object in the user session. the value is a Request + java Future for the result return immediately with a client-side redirect. while the client-side redirect is being handled, … Continue reading
Posted in code review, technical
Leave a comment
Code Review #8: When to comment
The last ? in a series of posts about commenting. See “the why”. See “not commenting is career threatening”. And the comment that started this off! This post should have really been the second one I wrote. The first post … Continue reading
Posted in code review, management
1 Comment
Why and when to wrap external library classes
At some point, every developer starts using an external library. They then have to decide if that external library should be wrapped in their own custom interfaces and classes. If the external library would be pervasively imported in throughout the … Continue reading
Posted in code review, hibernate, technical
Leave a comment
Interfaces vs. abstract classes
Sigh … some people just don’t get it…. 😛 Interfaces rock! Below is my comment from stackoverflow.com, a question about how to handle the “interfaces v. abstract classes” interview question in an interview. First, the “only one super class” answer … Continue reading
Posted in code review, technical
Leave a comment
Code Review #7 – Comment the “why” not the “what”
[This post continues the response to Mike.] Clean “good” code is good but not enough. Code needs comments — but the right kind of comments. “What” comments are useless and the most quickly out-dated. An example of a what comment … Continue reading
Posted in code review, management, technical
7 Comments
Not commenting code is dangerous to your career
There is this myth that code can be self-documenting and that comments are not necessary in good code. Michael recently comment on an earlier blog post advocating the idea of self-documenting code. “Self-documenting” code is a career-damaging concept, because: Your … Continue reading
Posted in code review, management
3 Comments
Code Review #6 – ‘Too smart’ aka scared of being dumb
One of the biggest failing junior developers have is that they are too ‘smart’. ‘Too smart’??? How can someone be ‘too smart’? Actually pretty easily. ‘Too smart’ is when the person spent hours looking at a problem. And the next … Continue reading
Posted in code review, management, technical
1 Comment