2 ms·
The is a great suggestion. I’ve also learned a lot just from reading the already-merged code of projects I’m interested in, and stepping through git history to
by eyelidlessness 5y ago
The is a great suggestion. I’ve also learned a lot just from reading the already-merged code of projects I’m interested in, and stepping through git history to see how it evolved. I even frequently do this on my phone when I want time away from the desk.
For instance I’ve been super interested in SolidJS[1] for months. I learned from reading the source that a lot of the work is done by its underlying dom-expressions[2] compiler. And in reading its source, I learned enough about JS AST transformation that, when I had a need to do some AST transforms of my own for work, I knew enough to confidently timebox a proof of concept to two hours (and actually finished the work in that time!). All from reading code casually on my phone.
Sure, I front-loaded a lot of that work in my free time. But I did it because I was genuinely interested in the project I was learning from.
1: https://www.solidjs.com/ https://www.solidjs.com/
2: https://github.com/ryansolid/dom-expressions https://github.com/ryansolid/dom-expressions