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

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

Farcaster Development Boutique @ dTech.vision 💜 prev pentester & CS at @ ETH Zurich | In love with tech 🤓 decentralization, fitness and oldschool rap 😎

SKYCASTLE

dang, I am a overprescribing medicine taking coder then :D

“DRY” (don’t repeat yourself) is way over-prescribed 

it is better to repeat boilerplate code than abstract it UNLESS the boilerplate frequently causes bugs…. then, abstract 

(h/t @subtlegradient)

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

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

“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