3 ms·
It comes down to your distance from a specific 'tool' or system. You aren't writing x86 assembler. You are presumably writing some other, higher-level language
by lsaferite 6y ago
It comes down to your distance from a specific 'tool' or system.
You aren't writing x86 assembler. You are presumably writing some other, higher-level language. I would fully expect you to know that language in detail and even better to understand the performance implications of the choices you make in that language. Knowing the lower level details helps there, but it's not 100% required.
With git, it's something you _directly_ interact with so I would expect you to understand it in great detail.
- rmtech 6y ago> With git, it's something you _directly_ interact with so I would expect you to understand it in great detail. Yes, you are describing what is broken about git: its abstractions are leaking too much so people who touch it have to know all its internals. I touch x86 assembler every time I run high-level code, it's just that other kind folks have gone to a lot of effort to make it so that I don't have know how the internals of that low-level stuff work. Abstractions allow people to be productive without knowing in great detail how absolutely everything in the universe works. A good tool has simple, non-leaky abstractions with a simple interface. Git is not a good tool.