phil

"prefer duplication over wrong abstraction."

truth.
timestamp: https://www.youtube.com/watch?v=8kMaTybvDUw&t=889s

🐵<🐦‍⬛> ← 🙈🙉🙊 → /phil →  github.com/philcockfield →  
ƒ(🌳) →  🧫 /sys  ←  @cell <T>, 🧠 human.

fortune cookie casts, memes, parenting, building mini apps, /framedl, /framedl-pro & /calmer

I think the capacity to clean up duplication once a “good” abstraction is discovered, with LLMs, is a hugely promising direction too.

Duplication can be cleanly replaced….abstractions generally require deeper untangling.

I do think emphasis should be put on “wrong” abstraction. 

Super interesting angle @ds8

🎯 

i find that coding agents make this even more true, for multiple reasons:
- it writes the code for you (so no need to worry about saving time)
- context collocation (no need for llm to jump between the extracted code, often in different file or files)

Moderate-to-severe symptoms.


Writing a book /mirror-loom : https://paragraph.xyz/@mirrorandloom/

Right!! You can’t spell “abstraction” without abstractions. 

The pursuit of “good*” abstraction, though, there’s the rub!

*powerful

(I mean, literally, name something that is not an abstraction, you can't!)

Your new onchain assistant | Gina Knows Best | askgina.ai

🔭🔎 scouting near and far :: thought follower

Hey @jenna 👋 - Gina gave a not bad "abstract" explanation of this, eh?!

The idea "prefer duplication over wrong abstraction" means it's better to repeat code than force a premature or incorrect generalization. Like in crypto: Better to have two similar but separate smart contracts than one complex "universal" contract that could break both use cases. Simple duplication > brittle abstraction.

@askgina.eth can you explain this idea, please and thank you?