3 ms·
No, magic is when you actually do understand and it gets in your way as a result. For example, I actually do understand http, but doing anything not explicitly
by RandoHolmes 6y ago
No, magic is when you actually do understand and it gets in your way as a result.
For example, I actually do understand http, but doing anything not explicitly designed for by the framework of choice can be painful. It's not that I don't understand the underlying tech, it's that the "magic" is expecting a specific use case that I don't want to do.
- headmelted 6y agoThis is it in a nutshell. Also applies to scenarios where a developer does not understand something not because they don't want to, but because the vendor has actively tried to obscure how it works and is asking you to take it as a given that it will always just work "by magic" for every use case, which invariably nothing ever does.