Founders

positioning rants 🚀; bringing you ✍️ /buildbetter, 🎙️ /artistspotlight and🎙️ /web3magic; De*** & open-source HW/SW enthusiast; https://nf.td/bfg

in a the fragmented industry that is web3, i actually disagree with adopting the “one thing well” position because its creates more fragmentation. People need composability which means you can just execute on your one part of the system

web3 is perfectly suited for doing just "one thing well" exactly because of its composability

as a dev, i would love to learn how folks have done composability over more than 2 systems well at scale.
I worked as a data engineer over an e2e supply chain and even that experience was less painful than building in web3. 

observably, latency, and complexity are huge pain points here