[halayli]

> Consider time_saved to represent the time you may have spent developing your own solution

Developing your own solution is one thing, and developing your own solution that's as battle tested as a popular library is another.

Baking your own solution helps you understand the core problem that a library you could have used tried to solve. But generally speaking developers that tend to do that have difficulty learning top to bottom and favor bottom up approach which leads them to developing things from scratch. That's just a personal anecdote though.

There are cases were a developer has been using a library for a while and is experienced enough to come up with better solution and cleaner APIs but I'd argue that's not the common case.

Understanding other people's code/libraries is a skill worth mastering.

[tomelders]

As far as libraries generally go, Redux is tiny.

https://github.com/reactjs/redux/tree/master/src

The largest and most important part is CreateStore, but at 250 lines long (mainly comments), it's shockingly simple when you take a look at it.

[always_good]

> But generally speaking developers that tend to do that have difficulty learning top to bottom and favor bottom up approach which leads them to developing things from scratch.

Damn, that was a hard pill for me to swallow just now.

[hliyan]

I'm afraid I'm guilty of this type of re-invention myself. Having built a very large project using Redux, I decided to develop my own alternative, not just to Redux, but to Flux itself:

https://hackernoon.com/transmission-tx-a-flux-alternative-fe...

I'm convinced it's better and simpler, but then again, I'm arguably biased.