While I don’t read the implementation of anything any more unless there’s a hard algorithmic problem, I do make an effort to read and document APIs thoroughly.
I have some questions.
Are you doing this for client-facing production code?
It seems you believe painting over APIs with some amount of documentation will guarantee the implementation is correct and well designed. Am I misreading that?
You say you still read code when code is « algorithmically hard ». How do you define that?
Software systems have requirements that are essential but not algorithmically hard. For instance, access control in a web application must be thorough and cover all REST resources. How do you know the implementation has the desired properties if you don’t read the code?
Do you have tests? How do you know they’re correct if you don’t read the code? Moreover, how do know if their coverage is sufficient if you don’t read the code?
Do you refactor code or is that not needed anymore?
I don’t understand your answer to the question of why anyone would publish a library if no one reads code anymore. « For the exact same reasons as before ». How so? This isn’t making sense.