MODULE DOCUMENTATIONS
I am doing the named entity recognition of our data at the moment. It allows us to collect the useful information such as which character is mentioned the most in the portion of text and where the action is taking place. I am using SpaCy to accomplish this task. SpaCy was recently updated to version 3.x.x which brought a lot of changes. Since I am working alone all the time, I have to depend on online communities such as StackOveflow whenever I have any issue. Whenever I have an issue with SpaCy and look it up online, I always have to figure out what version the person is using, then figure out how to convert it to the version I am using.
This process taught me to rely more about how to read module documentations, and to rely more on them rather than just copying and pasting code portions online. Reading the documentation gives me the most accurate information about the latest version and a detailed explanation of each of the syntaxes. This allows me to actually understand how the module works under the hood and makes the work smother should I use it again in the future. I am still bad at understanding module documentations. However, what I am doing right now is find code portions online, put the code portions and the module documentation side to side, then I read the code portion, then go to the documentation to check out each of the keywords I do not understand. The advantage of this is that I have the opportunity to understand the module without having to look at the documentations, and it allows me to only look up the most important part instead of reading the full documentation.
Comments
Post a Comment