Ultimately speaking, the dimensions that are going to matter most in determining whether it's OK to do imperative design are:
- If the project size is large.
- If the project complexity is high (we just discussed this one with CRUD apps).
- If the project is enterprise software (this is software serving an organization with several teams, where each team has a set of employees with roles that carry out a specific set of activities- think major airports, large e-commerce giants like Amazon, or Wal-Mart).
This book’s mission is to teach developers the essential skills and practices to write testable, flexible, and maintainable code.
You can read more about the learning journey in the "Software Design and Architecture Roadmap 🖼️".
Already bought it?
If you’ve already purchased the book, click here to re-send your link. You can read the online wiki or download a copy of the book in PDF, EPUB, and Kindle versions.
You can read the intro to the book for free and visit solidbook.io to buy the book/wiki (it's currently on pre-sale for 33% off)! For recent updates, click here. To get an idea of my writing, read some of my best free content here and here.