Timeline for Design pattern for creating object hidden from client
Current License: CC BY-SA 4.0
3 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Nov 17, 2018 at 15:33 | comment | added | Paul | @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. | |
| Nov 17, 2018 at 15:22 | comment | added | Corey P | 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. | |
| Nov 17, 2018 at 8:05 | history | answered | Paul | CC BY-SA 4.0 |