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

How should one use this? #30

Open
030 opened this issue Jul 19, 2017 · 2 comments
Open

How should one use this? #30

030 opened this issue Jul 19, 2017 · 2 comments
Labels

Comments

@030
Copy link

030 commented Jul 19, 2017

Should one do a go get or should one copy and modify the code in the personal projects

@tmrts
Copy link
Owner

tmrts commented Jul 19, 2017

The purpose of the repository is:

  • To show what a pattern is
  • When that pattern should be used
  • What should you be careful when you use the pattern
  • How you can use the pattern

There are fully working code examples for some patterns, but I'm removing them when I can, because they usually add a lot of boilerplate, they increase the maintenance burden and they force a person who wants to learn to go through a lot of lines to understand the essence of a pattern.

Ultimately, I want every pattern to be like strategy pattern, which is concise and easy to understand.

@tmrts tmrts added the question label Jul 19, 2017
@030
Copy link
Author

030 commented Jul 19, 2017

@tmrts What about adding this to the README? E.g. how to use this repo and purpose of this repo.

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

No branches or pull requests

2 participants