One of the Best Bits of Programming Advice I ever Got

#1

Post by apgwoz » Mon, Sep 26, 2011, 10:19 AM UTC

One of the Best Bits of Programming Advice I ever Got
objology.blogspot.com

Re: One of the Best Bits of Programming Advice I ever Got

#2

Post by praptak » Mon, Sep 26, 2011, 11:51 AM UTC

I was lucky enough to get an equivalent piece of advice from "Object Oriented Programming" by Peter Coad & Jill Nicola ( http://amzn.com/013032616X ) which was the main textbook for an OO course during my CS studies. There are good examples there that illustrate this and many other useful rules (of thumb) of OO modeling.

Re: One of the Best Bits of Programming Advice I ever Got

#3

Post by latch » Mon, Sep 26, 2011, 11:52 AM UTC

Google has posted warning signs to look out for in code (1). One of them is very similar:

  Suspicious names: context, environment, principal, container, or manager

(all of the things google mentions, are things I've seen much, much more in Java codebase than anywhere else)

(1) http://googletesting.blogspot.com/2008/11/guide-to-writing-t...

Re: One of the Best Bits of Programming Advice I ever Got

#4

Post by timclark » Mon, Sep 26, 2011, 11:53 AM UTC

I particularly dislike classes called *Helper

Re: One of the Best Bits of Programming Advice I ever Got

#5

Post by Kototama » Mon, Sep 26, 2011, 11:55 AM UTC

Even better: don't use objects at all. Use a functional programming language.

Re: One of the Best Bits of Programming Advice I ever Got

#6

Post by philbarr » Mon, Sep 26, 2011, 12:11 PM UTC

I generally accept the point made in the article, but what should I use in place of "Controller"? If using MVC I generally call it "ApplicationController" or "SimpleController". Should it be "Application", "ApplicationControl"...?

Re: One of the Best Bits of Programming Advice I ever Got

#7

Post by jwdunne » Mon, Sep 26, 2011, 12:12 PM UTC

latch wrote: post #3

Google has posted warning signs to look out for in code (1). One of them is very similar: Suspicious names: context, environment, principal, container, or manager (all of the things google mentions, are things I've seen much, much more in Java codebase than anywhere else) (1) http://googletesting.blogspot.com/2008/11/guide-to-writing-t...

http://misko.hevery.com/code-reviewers-guide/flaw-digging-in...

This is the full article mentioned above.

Re: One of the Best Bits of Programming Advice I ever Got

#8

Post by cousin_it » Mon, Sep 26, 2011, 12:37 PM UTC

Kototama wrote: post #5

Even better: don't use objects at all. Use a functional programming language.

Object oriented programming is the sweet spot solution to many problems. For example, if you have a UI with several text fields, it's natural to think of them as objects that have methods like setText(), setEnabled() and such. These methods often have side effects and that's their whole point.

Of course functional programming also has use cases for which it is the sweet spot solution, e.g. writing compilers.

Re: One of the Best Bits of Programming Advice I ever Got

#9

Post by ilcavero » Mon, Sep 26, 2011, 12:41 PM UTC

good explanation of procedural vs OO programming, but I got kind of lost with the -er tip, is it all about naming conventions, should I go and rename all my ZzzXxxer classes to XxxxZzz?

Re: One of the Best Bits of Programming Advice I ever Got

#10

Post by ubernostrum » Mon, Sep 26, 2011, 12:43 PM UTC

Kototama wrote: post #5

Even better: don't use objects at all. Use a functional programming language.

I see, your bullet is apparently more silver than mine? :)