I remember myself procrastinating in using of Design Pattern in production code, after reading the information about the GoF patterns.
On the paper everything looked very easy and understandable. But after you might fall in trap of fear of using this knowledge in production code, because:
- You have a very limited time dedicated for the task. So you can’t find the time to do the things “in right way”
- You haven’t enough experience of some particular Design pattern, so you don’t know how to exactly implement in real problem solving. So you spend more time and get out of time scope for task and schedule. So you decide to refuse “the hard right way”, and implement an easy and dirty “temporary” solution.
If you refused to implement the pattern, you haven’t improve your experience with this pattern. It is an infinity loop: you can’t implement because you don’t have a required experience. Time passes, and you will have the exact same problem in future, and the initial conditions(level of experience with particular pattern) are still low.
I was in this loop for a couple months. And after I recognised this behaviour habit, I’ve asked for help more my more experienced co-workers. The advice was simple and easy:
You can’t succeed without failure. If you want to become more experienced in Object Oriented design and Design patterns, you have to have a will in this trend, and still moving nonetheless the periodic temporary failures.
Tags: design patterns, ood, oop
