4 ms·
I wish I had a better answer, but I honestly just stumble around it. I typically start by trying to understand how they structured their files, then I'll start
by Sakes 11y ago
I wish I had a better answer, but I honestly just stumble around it. I typically start by trying to understand how they structured their files, then I'll start diving into the code. I wouldn't try to "understand" it completely. Just look over it until you feel comfortable enough to try to make some modifications.
Michael's code looks clean and well organized. Shouldn't be terribly difficult for someone proficient at JS.
- amorphid 11y agoGlad I'm not the only one who stumbles around :) Another thing I do is try and replicate one core feature of the thing I'm trying to understand. Like others have suggested, I like using debuggers. Recently, I wondered how debuggers work. So I built the following to find out. https://github.com/amorphid/rails-debugger_example https://github.com/amorphid/rails-debugger_example