3 ms·
> In particular, the desire to cram increasingly diverse and rich interfaces into 70s file IO is a strange sacrament Long time ago I asked my karate sensei how
by jjav 3y ago
> In particular, the desire to cram increasingly diverse and rich interfaces into 70s file IO is a strange sacrament
Long time ago I asked my karate sensei how come I see some of the black belts doing katas in a different way. His answer was that to improve on something one must first have deep mastery of how it is done.
(i.e. "Shut up and do the katas correctly. If you ever get to black belt then you can improvise.")
Always found that answer to apply to everything. In particular it applies to a lot of the poor quality libraries and code we see today as a direct consequence of not understanding the past and what has been tried and failed and why.
The fact that we're talking in 2024 about using the file abstractions of Unix created in the 70s is proof of how extremely powerful they are. Nothing is perfect, but that's quite an achievement.
- galaxyLogic 3y agoA mistake we often make I believe is to focus on code-quality, rather than code-content-quality. Code is basically mathematics. Is it good math or bad that is the question. Does it do something useful, in an economical way. To write great code, I believe, means you have to be a domain expert of the domain for which your code solves problems.