Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Proposed new section - Design patterns #33

Open
braydie opened this issue Jan 10, 2016 · 11 comments
Open

Proposed new section - Design patterns #33

braydie opened this issue Jan 10, 2016 · 11 comments

Comments

@braydie
Copy link
Owner

braydie commented Jan 10, 2016

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.

@amrFHamza
Copy link

I agree with that

@oktapodia
Copy link

👍

@maciej-gurban
Copy link

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.

@braydie
Copy link
Owner Author

braydie commented Jan 11, 2016

@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

@oktapodia
Copy link

If you want to get a list of design pattern in PHP, you can go here

@RobertLRead
Copy link
Collaborator

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)

@ImDineshSaini
Copy link
Contributor

Software Architecture should be correct name to represent the section, we can add the small section inside that like: Design Pattern, Architecture Pattern

@braydie
Copy link
Owner Author

braydie commented Jan 15, 2016

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

@jubrilissa
Copy link

For design patterns in python https://github.com/faif/python-patterns

@ImDineshSaini
Copy link
Contributor

Any suitable link for design pattern in ruby

@unknownbreaker
Copy link

How's this one going?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

8 participants