3 ms·
This may also be a contributor to the fact that a lot of devs these days seem to make a clear distinction between the type of code they allow themselves to writ
by maxxxxx 9y ago
This may also be a contributor to the fact that a lot of devs these days seem to make a clear distinction between the type of code they allow themselves to write and code they won't write. A lot of people stay within a narrow range of what their chosen framework allows and don't really experiment with doing complex stuff themselves. In my view someone who has worked with React or Node (example) for a while should have a fairly good idea how they are imlemented but it seems many people accept it as "magic" and don't look behind the scenes.
To me reading source of these frameworks helps realizing that whoever developed them are just human beings like the rest of us and write regular code that's really not special.
- kerkeslager 9y agoMore than that, reading framework source often reveals that the code is very, very bad.
- maxxxxx 9y agoBecause a lot of working code is very bad. Reading other people's code is a good to way calibrate expectations for code quality.
- kerkeslager 9y agoIt's ambiguous what you mean there, expectations could be beliefs ("I expect code to be bad generally, so I don't assume anything") or what you'll accept ("I expect code in my system to be good, so I rejected the PR that added that garbage library").