Ask HN: Layered Design or Flat Design?
I am writing a web app with the intention of evolving the app as and when the requirements evolve.
While writing the code I am faced with the dilemma of whether to just provide mechanisms at the lower level and push the policy handling at the higher levels, or just flatten the design and handle both mechanism and policies at the same level.
There are pros and cons of both approaches.
So how does one overcome this dilemma when dealing with evolving requirements?