DEV Community πŸ‘©β€πŸ’»πŸ‘¨β€πŸ’»

decker
decker

Posted on

Think First, Code Second

From time to time I see code from colleges or other people, that seems to be to complicated or architectures that consists of many parts, more than I would add.

My questions: Why is that?

I think they simply follow a known pattern read or seen anywhere.

They do not think about it first, is something really needed or who needs it.

Adding a statemanagement library like Pine, adding Axios for the REST API, MinIO for Object Store, Elastic Search and so on. And sometimes it is even more strange, when the framework itself has a solution for this and you do not have to add another one.

I would suppose: Think first, start lean and simple, use interfaces to hide implementation details and only switch to bigger players when really needed.

What do you think? How would you start a project?

Top comments (0)

Take Your Github Repository To The Next Level

>> Check out this classic DEV post <<