working on infra to displace adtech @ /microsub - dance music lover + host of /campfire 🎧

Farcaster Product Studio @ https://dTech.vision 💜 in love with tech 🤓decentralization, fitness and oldschool rap 😎

“Separation of concerns” is bad and wrong. Better: “avoid unintended coupling”

Often many separate concerns are highly coupled and we should expose that reality explicitly so that it’s easier to reason about

art collector. Building @frens
. Maker of things that do stuff since the 90’s. Mostly frontend. Previously @coinbase @godaddy @facebook @mootools @CrazyEgg

how do you show that they are coupled? thinking about it / reasoning?

I guess the classic example is ui component separation back in the 2000’s.
Having the HTML/CSS/JS for a single component living in separate files in separate folders and sometimes entirely separate repos. It was a nightmare. But we as an industry just didn’t know any better

I did always colocate tightly coupled stuff in my quick and dirty prototypes back then, but always dutifully separated them before landing