Comments on: Name your objects right http://maxheapsize.com/2010/02/09/name-your-objects-right/ Oliver Wehrens on Programming and Agile Fri, 27 Aug 2010 10:08:53 +0000 http://wordpress.org/?v=2.8.4 hourly 1 By: Rayk http://maxheapsize.com/2010/02/09/name-your-objects-right/comment-page-1/#comment-4374 Rayk Wed, 10 Feb 2010 14:40:18 +0000 http://maxheapsize.com/?p=447#comment-4374 Good point Olli. IMHO a good data modelling (and skilled modeller) could face and hopefully solve this issue. The "HitOrMiss" sugestion describes a finite domain, where as "FraudDetectionResult" is a more or less business object. The try to bring this all in alignment with an overall data modell let you detect quite early that something is wrong with "HitOrMiss". Regards Rayk Good point Olli.

IMHO a good data modelling (and skilled modeller) could face and hopefully solve this issue. The “HitOrMiss” sugestion describes a finite domain, where as “FraudDetectionResult” is a more or less business object. The try to bring this all in alignment with an overall data modell let you detect quite early that something is wrong with “HitOrMiss”.

Regards
Rayk

]]> By: Oliver Wehrens http://maxheapsize.com/2010/02/09/name-your-objects-right/comment-page-1/#comment-4359 Oliver Wehrens Tue, 09 Feb 2010 22:04:48 +0000 http://maxheapsize.com/?p=447#comment-4359 "Clean Code" is a pretty good book. My management bought into it and help people implementing our own variation. “Clean Code” is a pretty good book. My management bought into it and help people implementing our own variation.

]]> By: Juho Vepsäläinen http://maxheapsize.com/2010/02/09/name-your-objects-right/comment-page-1/#comment-4355 Juho Vepsäläinen Tue, 09 Feb 2010 18:42:58 +0000 http://maxheapsize.com/?p=447#comment-4355 Quoted for truth. Same applies for other programming constructs you happen to use of course. The original Logo programming language used "TO" keyword as a prefix its functions. I think that encapsulates well the idea how one should name functions and methods. The idea also helps you to maintain some clarity. In case of variables one should take the scope of a variable in count. The longer the scope, the more descriptive the name should be. If the scope is short, a simpler name will do. I gathered these ideas from "Clean Code" by Martin and "Code Complete 2" by McConnell. So far following them has worked out just ok. :) Quoted for truth.

Same applies for other programming constructs you happen to use of course.

The original Logo programming language used “TO” keyword as a prefix its functions. I think that encapsulates well the idea how one should name functions and methods. The idea also helps you to maintain some clarity.

In case of variables one should take the scope of a variable in count. The longer the scope, the more descriptive the name should be. If the scope is short, a simpler name will do.

I gathered these ideas from “Clean Code” by Martin and “Code Complete 2″ by McConnell. So far following them has worked out just ok. :)

]]>