3 ms·
If you don't see the purpose of something adding complexity or abstraction layers, you most likely don't need it and shouldn't adopt it (yet). With the hopefull
by 3np 5y ago
If you don't see the purpose of something adding complexity or abstraction layers, you most likely don't need it and shouldn't adopt it (yet). With the hopefully obvious caveat of some things relating to security, like firewalls and scoping capabilities. Start simple and look for solutions only once certain things become painpoints.
- tomatowurst 5y agovery very good principle. i have favorited. in case next time i feel like im drinking the koolaid. also applies to the whole blockchain space.
- 3np 5y agoAnd as always - just because it is not the right choice for you right now does not mean it is "bad". On the flip side, consider a small team spending hours every week doing fully manual deployments instead of automating at least parts of that. Different people and orgs have different needs, and those can change over time. Learning to strike that balance and timing right is a hallmark of a great engineer IMO. > also applies to the whole blockchain space. It applies to everything. Blockchain can serve a purpose w.r.t. the security I alluded to above. Security in general is a tricky one as once you realize it's a problem, it may be too late to reconsider.
- zaphirplane 5y agoThere was an post a few days ago about https://en.m.wikipedia.org/wiki/Wikipedia:Chesterton's_fence https://en.m.wikipedia.org/wiki/Wikipedia:Chesterton's_fence Which boils down to if you don’t understand why then don’t replace it