Replies: 1 comment 3 replies
-
Yes, I quite agree with what you said. Most of the tools we are using today are quite opinionated. However, I think design patterns can be useful not for structuring the whole codebase but for example in a certain part of the codebase to tackle a specific issue. What do you think? |
Beta Was this translation helpful? Give feedback.
3 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
@zxenonx
I think design patterns are overrated. Today, you never start from scratch. You eigther have a database (for example potsgresql) or you have an API. The services you work with define their usage pattern.
A lot of design patterns are about native GUI applications. And today your mostly write http request handlers. At least in my context. The http request comes in, your code contacts a DB, API or uses a library, and then returns the result.
In this context you hardly need design patterns. I read a book about design patterns 20 years ago, and I have never used it. Maybe this pattern of stateless http request handling is a design pattern. I don't know.
Beta Was this translation helpful? Give feedback.
All reactions