Fits in well with an important piece of my professional philosophy: aggressively fight to strip magic away from my dependency tree.
Conversation
Yes. From the dependency tree, and from all things that it can reasonably be stripped, really.
2
1
The difference between thinking of a library as “hiding the hard bits” vs “automating the hard bits you already understand.”
2
7
22
Doesn’t that depend on the subject at hand? Graphics programming, sure. Encryption/Compression libraries..?
1
No, those, too. Just a question of priority. If they're central to my project, I'd want to understand them 100%.
2
1
eg graphics technologies are central to most app developers, so they'd better understand them deeply!
4
Let’s take UIKit physics for example. most iOS devs won’t be able to write their own engine. Should they be able to?
1
Replying to
Depends on whether they're using it for subtle, incremental enhancement or whether it's central to their app.