DISQUS

Not being a java guy, my vote should probably count as half a vote, but I'd go for packaging by feature. This discussion actually gives me a slight deja-vú from the discussions that appeared when Ruby on Rails started pushing the REST strategy: it can be a means for getting a better design:

If you have code that seems to span several features it could probably make sense to try to look at it as a feature itself. Especially if the code in question is util code - seriously: does anybody regard authorization code as util code these days? - there's probably a feature you failed to identify as a feature.

At the same time, straightjackets are seldom a good thing, and neat ideas tend to get irritiating after a while. But this discussion seems highly relevant!

Being new to the term I had a good laugh; you just nailed it. It seems somewhat related to aesthetiritis, where a programmer (probably one new to, and sold on, Ruby on Rails) is so obsessed with making his code "beautiful" that it becomes totally ungraspable.

Great article!
I both like your coding style and the opinions you quote from the book, the way you tie the two together is awesome.

The way you reimplemented the render method is among the better examples I've seen of how to replace if/else-spaghetti with "imperative" code - thanks!

Great article!
I both like your coding style and the opinions you quote from the book, the way you tie the two together is awesome.

The way you reimplemented the render method is among the better examples I've seen of how to replace if/else-spaghetti with "imperative" code - thanks!