loading...

How can I read source code and summarize them more efficiently?

nozomuikuta profile image Nozomu Ikuta ・1 min read

My Dev Journal of 2020 (9 Part Series)

1) Hello, DEV 2) Study Plan for 2020 3 ... 7 3) How can I read source code and summarize them more efficiently? 4) Change on study plan 5) Study Log: Reading Vue's RFCs 6) Study Log: Reading Vue's RFCs (2) 7) Study Log: Reading Vue's RFCs (3) 8) What I learned so far by writing 14 posts everyday 9) Change on study plan (2)

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.

Discussion

markdown guide