Program Design - Package by Feature vs. Layer or Both?

Question

I am in the design stage of a web application that allows users to create requests of work and the workers to put time against those requests. The application will also have

Answer 1

5 years later...

(Suspenseful music in the background)

Imagine this ridiculous situation:

Managers company, Programmers company, Human Resources company and Marketing company, where the Programmers company will only have programmers and no managers, marketeers or human resources;

We wouldn't want to split co-workers by their profession instead of organizing (self-coordinating) teams, or would we?

Packaging stuff together by what it is, and not by what it does, will only make you jump 10 times to the place you are looking for.

Now doesn't that just look sexy? By looking at the structure, you can already tell what the app is all about. Not satisfied? Read full article.