Thanks so much for your reply and for your comment at the blog. On Apr 4, 4:32 am, Christian Catchpole <[email protected]> wrote: > My response: > > Good API design should also allow for plugable Coffee Shop > implementations (perhaps even coffee machines). I have found though > that different shops have different cup sizes in terms of volume and > labels (Small, Medium, Large, Tall, Verde, Grande etc). With no ISO > standards for coffee cup sizes (that I know of), I would suggest two > parameters. Millilitres, and an option for round to nearest vs round > up to larger size. And yes, I’m being sarcastic. > > Oh, and waiting for coffee should involve some kind of call back > “Christian your large latte is ready”, rather than polling the queue > (this will annoy you, and the queue) > > In all seriousness though, I do like the elegance of a orderSmall() > orderMedium() method etc, the down side obviously is when an order is > typically dynamic, being generated from an input request, you would > have to do a case style decode and method calls. So the choice of enum > or param type could (should?) be based on how the input is to be > generated. > > On Apr 4, 6:39 am, Abder-Rahman <[email protected]> wrote: > > > > > Simply follow this link to view the > > article:http://www.agilejavaoop.com/java/how-to-make-your-java-code-understan...
-- You received this message because you are subscribed to the Google Groups "The Java Posse" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/javaposse?hl=en.
