How do you all remember the software patterns available for use? I mean, at this point I kinda stick to the patterns that already exist in the codebase I'm in. But I feel like I might need a poster or some visual reference to glance at all dreamy like 🤔 I guess it gets easier?
Conversation
Ultimately trying stuff I've read about or seen before, then trashing it if it doesn't work out is what helps me learn internalize things the best. We need to allow more time for people to learn this way!
1
2
I also try to ease my way towards learning the underlying theory of the tools I'm using, so that I can see the building blocks of the higher level patterns. Seeking out the historical context of the patterns helps too - it makes it more interesting to learn and easier to recall.
1
1
One thing that helped me a bunch with the OO design patterns was leaning new languages from other paradigms - often there's other languages out there that can express the ideas more naturally, and you can then reverse-translate it back into the OO language.
1
That's something that requires more time investment though. Note that it works the other way too. And you'll see patterns in other languages pop up too to express things that are more awkward there.
1
It's one of those things where a gradual layering of knowledge and skills help. As I get more and more different perspectives on how programming works I find I can collapse down seemingly disparate ideas into easier-to-remember 'core ideas'. Then later expand them out on demand.
Not sure if that helps at all - I have an odd approach to learning that is kind of hard to describe! A wall poster seems good if it helps you! 👍