3 ms·
But you're not going to realize which way it's better unless you've written the bad code before.
by ffsm8 2y ago
But you're not going to realize which way it's better unless you've written the bad code before.
- BiteCode_dev 2y agoTangential, but I think that's the problem with trying to learn from design patterns. I read about them and tried to apply them. That's backward and didn't produce anything good. I started to understand them by doing it the other way around: - Coding, solving problems. - Reading other people's sources. - Then reinventing half a terrible design pattern. - Later on, looking at a book: "ohhh, that's what I tried to do" or "ohhh, hence the snippet in that source". - Now I can discuss with people about the pattern and name my code entities according to that. Design patterns are a communication tool.