go-patterns
go-patterns copied to clipboard
tmrts
How should one use this?
Should one do a go get or should one copy and modify the code in the personal projects
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 What about adding this to the README? E.g. how to use this repo and purpose of this repo.