soldier of Good. 🪖🥰 
producer × DJ. 🎧 🪩 
working on /campfire. 🫴🪵🔥
host of /downshift ⚙️ + /dww 🎧 +  /gtd 🛠️.
https://linktr.ee/0xdownshift

Farcaster Development Boutique @ 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?

Personally, I code by gut instinct aka “intuition” aka “Feelings”. 

But if I were to train an ai to objectively measure it, I would look for files consistently mutated simultaneously.

If you need to change two files to make one change, maybe they should be in the same file.

But smart people have better objective evaluations. I’d probably consult the experts before building my own thing

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