15 karma · joined March 29, 2019
People think it's a good idea because it will save them time and I get many messages about different questions, use cases and support but the reality is you trade convenience for risk that something will be missing. What most people really want is a boilerplate for the SaaS, some building blocks for their UI and to not think about deployments.
VCs love this too, and many reach out, especially a couple of years ago. Maybe they know something I don't, maybe it was just phase.
reason: people like it (but also drives traffic)
Torvalds sarcastically quipped about the name git (which means "unpleasant person" in British English slang): "I'm an egotistical bastard, and I name all my projects after myself. First 'Linux', now 'git'."
Link: https://youtube.com/playlist?list=PLWTCD_J8kOHOeW1u3MH0CyTPT...
There’s also this great tutorial making a uniswap clone that goes through the hardest aspects of onchain development.
Link: https://medium.com/coinmonks/programming-defi-uniswap-part-1...
I also building Diagram (https://www.ondiagram.com), a way to build APIs with nocode and MongoDB
The thing was to have a no-boilerplate library for state management that is compatible with redux. Then, when complex reducers or sagas are needed I can just replace it with redux with out re-writing all state management code.
Codesandbox: https://codesandbox.io/s/simple-redux-js-ubnnc
The whole thing is 40 lines of code -> https://github.com/LiveDuo/simple-redux/blob/master/src/inde...