HN user

kolpa

752 karma
Posts0
Comments358
View on HN
No posts found.

You don't need to undo the abstraction, just opt out: Fork the shared artifact and modify or rewrite the copy (prune useless parts) as you need.

People often forget "copy-on-write". Coupling doesn't have to be permanent. If refactor to create a sahred component, and then you want to modify a shared component to help one client, you can fork it -- it's not worse than simply not having created the shared component in the first place.

Insurers are paid in premiums, not health outcomes. An insurance company is incentivized to help avoid costly claims, but if you are likely to make costly claims, and they can't drop you, they are incentivized toward healthcare choices that kill you before you need long-expensive term care.

"Yak shaving" is for things that seem ridiculous at first glance but turn out to be necessary or optimal due to unexpected constraints and requirement -- washing your car requires you to shave a yak to get the wool to build a sponge.

"Tying your shoes" is for mundane but necessary tasks. "Sharpening your saw" is for tangential work that indirectly makes your output better.