Open braydie opened 8 years ago
I agree with that
:+1:
Agree, however the topic seems so vast that it would deserve not only a chapter, but probably a whole book to at least lay out the types of methodologies and what each entails.
@maciej-gurban - completely agree with you. My guess would be that the chapter would merely introduce the concept of design patterns, surmise the pros and cons of using them and then point to further reading on specifics
I think we could definitely expand this section, with references, starting with the "Gang of Four" book and then reference design pattern books in particular languages.
As @maciej-gurban mentions, it is probably not best to try to teach design patterns here. However, I would like to have a statement about how to recognize when a design pattern might help you (e.g., when you find yourself doing the same thing twice or three times)
Software Architecture should be correct name to represent the section, we can add the small section inside that like: Design Pattern, Architecture Pattern
I've started something here
It's in a separate branch and will remain so until we're happy with the content to go back into master
For design patterns in python https://github.com/faif/python-patterns
Any suitable link for design pattern in ruby
How's this one going?
Currently we have 1.11 "How to Learn Design Skills", and I think getting an understanding of well-designed software is very important (especially as a beginner), but should we look to include a section later on (perhaps in Intermediate) on when to use (and not use) design patterns? Currently 1.11 makes no mention of them and even having an awareness of them can be beneficial.