Kick offR1: Many classes use plug-in methods/algorithms. Use lambda functions to configure them.

R2 Exit a sub routine in one place only

QuoteOriginally posted by: rmaxR2 Exit a sub routine in one place onlyIndeed.The other day I was brushing my teeth. My girlfried called me, so I left the room and went out to talk to her. She happened to come back to the bathroom with me and commented that I had left the tap running. I said that I had behaved like a routine with more that one exit point. She called me sad. I found it quite pleasing.R3 favour association over composition and composition over inheritance

QuoteR3 favour association over composition and composition over inheritance N:N better than 1:N better than 1:1? (brilliant R3, I'm gonna frame this one!)

R4 When you say to yourself "I will kludge this in as it will be quicker" it NEVER EVER is. When you come back to use the code you will either (a) swear (b) rewrite it as you should have done initally.

R5 floats, doubles, etc. are NOT real numbers (ints aren't integers, either)

QuoteOriginally posted by: Traden4AlphaR5 floats, doubles, etc. are NOT real numbers (ints aren't integers, either)Agree on floats and doubles etc. Nasty things.Integers are perfect and friendly though...surely....? What don't I know?

QuoteOriginally posted by: rmaxQuoteOriginally posted by: Traden4AlphaR5 floats, doubles, etc. are NOT real numbers (ints aren't integers, either)Agree on floats and doubles etc. Nasty things.Integers are perfect and friendly though...surely....? What don't I know?Upper bounds! Actual integers can be arbitrarily large but ints and longs cannot. Sooner or later one will discover that adding 1 to an int or a long produces a very negative number.

Unsigned integers are a form of modular ring, all perfectly well-defined :-)OTOH, signed integers are... scary :-One of my personal favorites:R6. Minimize scope

QuoteOriginally posted by: Traden4AlphaQuoteOriginally posted by: rmaxQuoteOriginally posted by: Traden4AlphaR5 floats, doubles, etc. are NOT real numbers (ints aren't integers, either)Agree on floats and doubles etc. Nasty things.Integers are perfect and friendly though...surely....? What don't I know?Upper bounds! Actual integers can be arbitrarily large but ints and longs cannot. Sooner or later one will discover that adding 1 to an int or a long produces a very negative number.I remember as a yoof being interested that on a BBC Model B you could execute Call !-4 and that would perform a soft reset. I never understood it until I was older and realised of course that you were actually Calling &FFFC.

QuoteOriginally posted by: rmaxQuoteOriginally posted by: Traden4AlphaQuoteOriginally posted by: rmaxQuoteOriginally posted by: Traden4AlphaR5 floats, doubles, etc. are NOT real numbers (ints aren't integers, either)Agree on floats and doubles etc. Nasty things.Integers are perfect and friendly though...surely....? What don't I know?Upper bounds! Actual integers can be arbitrarily large but ints and longs cannot. Sooner or later one will discover that adding 1 to an int or a long produces a very negative number.I remember as a yoof being interested that on a BBC Model B you could execute Call !-4 and that would perform a soft reset. I never understood it until I was older and realised of course that you were actually Calling &FFFC.Indeed! And that leads to:R7 Avoid really clever tricks that depend on quirks such as executing Call !-4 when you were actually Calling &FFFC.

R8. You are not using recursion enough in the solution

R9: In order to get the real project estimate, multiply the developer's estimate by 3.

QuoteOriginally posted by: rmaxR8. You are not using recursion enough in the solutiondoesn't this contradict R7 ?

QuoteOriginally posted by: daveangelQuoteOriginally posted by: rmaxR8. You are not using recursion enough in the solutiondoesn't this contradict R7 ?The perenial debate about recursion. I think that used correctly it can improve code. Used badly it just makes things more complex.Personally I think it is ok to use it where you are applying a simple atomic operation to a clean data-structure.In this case you get nicely condensed code where the intention should be clear by virtue of the target data structure.Its bad when it is unnecessary, or where the intention is difficult to understand. For example using it in calculations (without an accompanying datastructure) is dangerous and seldom if ever necessary (in my opinion).However I dont think it violates R7, which to my interpretation is making a statement about not utilising side-effects (either in a 'clever' or stupid manner - just don't do it!) By definition side effects are implicit and implementation specific. Utilising recursion properly should not automatically mean exploiting side effects. However it is a valid concern that recursive algorithms might encourage one to do so.