How can I read OSS source code and summarize them more efficiently?
I've been writing a series whose name is "How lit-html works" since days ago, which is one of my goals for 2020.
Writing posts everyday was harder than I expected. But it is also exciting and making me motivated.
Now I'm thinking that the way I'm doing is not efficient. That is, reading parts of source code everyday and write a post about them. In this way, I can't understand a part accurately at that time I read the part, because I don't know whole picture in advance.
I would like to hear your ideas or way to read source code, especially OSS.
Top comments (0)