Oh, but I didn't understand it was about optimization... Good practice is to not optimize prematurely ;) For example, inlining some message send, replacing explicit iteration message by more obscure to:do: or whileTrue: loops etc... are not good practices, just compromises... Nicolas 2011/12/24 Nicolas Cellier <nicolas.cellier.aka.nice@gmail.com>:
Bad practices and anti-pattern might be very instructive too...
Nicolas
2011/12/24 Stéphane Ducasse <stephane.ducasse@inria.fr>:
On Dec 24, 2011, at 3:07 PM, Alexandre Bergel wrote:
Not sure what you mean with good coding practice, but here my contrib:
- the command pattern (e.g., OB, Mondrian Easel, MonticelloBrowser) - symbol polymorphic to block and other object-as-function
Not sure that this is a good practices. I think that you like them because you use Smalltalk as a DSL.
- writing test before fixing code - having short methods indeed
Here is what I started to write.