Open
Description
Code in qualitymatters
at this moment is grouped into packages by layers (api, models, network, etc). Instead, it might be better to group bits of code by features / use cases. Such structure is easier to understand, extend and refactor. Please, see this article here: http://www.javapractices.com/topic/TopicAction.do?Id=205
It also might be not applicable to qualitymatters
, since project itself is quite small, so horizontal slicing (by layers) can also work.
What do you think?