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

This is the alt account of Sister Hazel. Writings at https://powerlaw.systems. Curating https://protocol-particles.github.io.

imho we have to challenge this narrative. 

for blockchain to have pmf developers shouldn’t have to make these drastic trade offs. 
if i want to use blockchain for coordination, i should be able to do that without compromising features or using 5+ different tools. 

not just complaining here, im actively working on the fix for this problem.

Coming from an infrastructure background, smart contracts are just another class of micro services.

If you care about latency, then you are either not using smart contracts for writes, or use caches for reads.

Your observability stack is always a separate component anyway, which integrates across all layers via push or pull based collector patterns.

I don't understand your question well and I am just rambling here. If you like we can chat some more!