[Wakagawa Vision x Source Code Co-reading] Introduction to learning 200 lines of source code co-reading activities every week

Source code common reading preface

In order to help more students who are interested in source code, want to learn to read source code, and improve their writing and front-end technical abilities. Help readers consolidate the foundation, check for leaks and fill gaps, broaden their horizons, broaden their horizons, and know why they are.

I did my best to organize a weekly source code reading activity of about 200 lines. I have written more than 20 articles in the "Learning Source Code Overall Architecture Series" .

Welcome (jia) I WeChat  ruochuan12 to  communicate and participate in  the source code reading  activity. Every week, everyone learns about 200 lines of source code and makes progress together. You can continue to follow me @ Ruo Chuan .

Submit Notes

In order to benefit everyone, and to bring more readings to everyone's articles and facilitate search, from March 27, 2022, notes can be directly published in the Nuggets, in the "[Wakakawa Vision x Source Code Reading Together]" section Several Issues | Title Naming" The first sentence at the beginning of the article added: This article participated in the weekly source code reading activity initiated by the public account @ Ruo Chuan Vision, click for details to participate together.

After writing your notes, go to the article comment area of ​​the current event to leave a message about your article and note features. It is convenient for everyone to read, learn, exchange and discuss.

All previous notes are stored in the Yuque discussion area .

common problem

Q: My working years are relatively short, can I participate in the activities? Will it be more laborious?

A: Yes. The 23rd class (currently junior) has written notes 7 times. It is generally recommended to read Vue3 tool functions first, which is relatively easy. If you have any questions, you can discuss them.

Q: I currently do not know vue, no vue3, no react, no Node.js, can I participate?

A: Yes. It is not strongly related to the technology stack, mainly native JS and Node.js. Node.js is basically a must-learn for every front-end, and you can check while learning. Feel free to ask questions in the group if you don't understand anything.

Q: I'm busy right now and don't have time to participate. Is there a time limit for submitting notes?

A: There are currently no restrictions.

Q: Do I have to submit notes?

A: It is not necessary at present, but I recommend reading one issue and taking notes. Write down your gains, summaries, and feelings at the time.

Q: Is there a fee for the event? Is there a penalty?

A: There is currently no charge. There is currently no penalty, and in the future, each person may be required to submit at least the first note within half a month after joining the group .

Recommended learning order from easy to difficult

In order to reduce the difficulty and promote everyone's learning. We rearranged the learning order from easy to difficult .

It is recommended that you study step by step in order, check for leaks and fill in gaps, and consolidate the foundation. Improve the ability to read source code and improve front-end technical capabilities. If you don't know how to debug, read this article : Beginners: Front-end programmers must learn basic skills - debugging JS code

  1. Issue 24 [vue2 shared] Practical basic tool functions in Vue2 source code that beginners can understand
  2. Issue 19 [axios/utils] More than 10 utility functions in axios source code
  3. Issue 23 [vue-this] Why Vue2 this can directly get data and methods, source code revealed
  4. Issue 16 [only-allow]: From the vue3 and vite source code, I learned a line of code to unify the artifact of standardizing the team package manager
  5. 第7期【validate-npm-package-name】: validate-npm-package-name
  6. Issue 2 [@vuejs/shared]: Practical basic tool functions in Vue3 source code that beginners can understand
  7. 第22期【dotenv】面试官:项目中常用的 .env 文件原理是什么?如何实现?

等等

流程图一览

简单说就是四步:

  1. 按照顺序选择其中一期开始,看任务。
  2. 看辅助文章、看源码。
  3. 微信群交流讨论,写笔记,写总结、收获。
  4. 语雀讨论区提交笔记。

Rule icon


读者评价

简单选择了三个笔记中的感想。

评价一

川哥组织的这个活动,给我最大的影响就是我对待源码的态度发生了转变。以前源码给我的感觉是“可远观而不可亵玩焉”,但是其实只要你认真读过一期,源码就会变成良师益友。你可以坐下来倾听他的思想,并从中受益良多,甚至可以和他交流,提出自己的想法,直至参与共建让源码更好。

评价二

川哥举办的源码调试给我带来了什么?

  1. 开始尝试写笔记
    a. 源码我都懂,让我说出来或者写出来,蒙了。
  2. 更注重细节
    a. 以前看源码就囫囵吞枣的过一遍
  3. 更注重应用场景
    a. 以前:原来这个方法是这样实现的啊
    b. 现在:看下测试用例,都是怎么使用的,某个判断是为了解决什么问题
    总之
    是一个老手,那么现在川哥给了你一个交流讨论的机会,去温故而知新。
    是一个新手,千里之行始于足下,有群里川哥和大佬们的帮助,勇敢迈出第一步。
    写笔记真是一个令人头疼的东西。

评价三

我最近看了几篇,川哥选的库都很精妙啊,老手可以梳理体系,新手可以了解现代工程化,进阶架构师必经之路啊。
特别是这几篇 create-vue、koa-compose、co、vue-dev-server,我都是熬夜看的,太起劲了


This article is continuously updated .

Guess you like

Origin juejin.im/post/7079706017579139102