Skip to main content

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

2
  • thanks for your answer. While my approach may seem complex, in reality it really isn't. It's starting with a simple watered-down design. UML is a great tool to start simple and it's very good practice to implement design patterns, even in the simplest of designs. Design patterns help code become more stable, scalable, and easier to maintain. It's important to implement them early, so you don't have to go back and implement them once the project grows large. Commented Nov 17, 2018 at 15:22
  • @Corey, I appreciate your position; I used to feel the same way until I started seeing g how much of it was just useless bloat that was actually slower to implement and didn't provide the theoretical benefits in practice. But everyone has a different journey, I wish you the best. Commented Nov 17, 2018 at 15:33