Generic vs Concrete software design

What worked for others in other scenarios might not work for you.

Concrete system design discussions are best done by the people involved in working in the system. It'll be more specific.

This is why the "architect" role is not that good, because their role is to create generic system design. Sean goes as far as:

architects can both claim credit for successes (after all, it was their design) and disclaim failures (if only those fools had followed my design!)

Generic system design is helpful for:

• new systems
• tie-breaking between decisions for existing systems