| ▲ | watermelon0 3 hours ago |
| You can use it without understanding, but this won't help you actually understand how it behaves. |
|
| ▲ | rco8786 3 hours ago | parent [-] |
| I believe I can understand how a library behaves from the README and docs. I do this all the time. We all do. |
| |
| ▲ | kevinh 3 hours ago | parent [-] | | You haven't run into cases where the documentation is missing or incomplete? You must be dealing with different libraries than I am. | | |
| ▲ | rco8786 3 hours ago | parent [-] | | Of course. And then we fix the problem. It's no different here. The point is that reading the code first is absolutely not a requirement when adopting a new library. | | |
| ▲ | skydhash 36 minutes ago | parent [-] | | It is not. But there’s an element of trust being involved. Something like libflac or libcurl, I don’t read the code. I read the doc which does outline the behavior of each function and the conceptual model. If something break, it’s quite often my code. Why? because their code is battle tested. Which is quite different from AI generated code. |
|
|
|
