17 ms·
Thank you. I will add that the title is intentionally provocative. However, I want to encourage developers to think of an abstraction as something you pay a s
by pclmulqdq 4y ago
Thank you. I will add that the title is intentionally provocative. However, I want to encourage developers to think of an abstraction as something you pay a significant cost for rather than something you get for free, and use that logic to make good choices.
In a sense, you hire abstractions a little like you hire employees. Interview them and make sure your values match.
- danielmarkbruce 4y ago"abstraction in expensive" makes people think you are implying one shouldn't use abstraction. It's all well and good that the content doesn't say that, but as journalists say: "don't bury the lede".
- lll-o-lll 4y agoNah, it’s perfect. Provocative, technically true, and when you come back to the title it’s “I have a new insight into this now”.
- danielmarkbruce 4y agoAn aside - if you haven't read any Michael Porter, you might find it interesting. https://iqfystage.blob.core.windows.net/files/CUE8taE5QUKZf8ujfYlS_Reading+1.4.pdf https://iqfystage.blob.core.windows.net/files/CUE8taE5QUKZf8... Slightly different concept, but similar ideas around consistency given a set of explicit choices/constraints.