3 ms·
It takes me 20 minutes and if it requires a minute longer then you're not a 10x savant like I am and you're slowing everyone down. You don't deserve to work her
by atleastoptimal 3y ago
It takes me 20 minutes and if it requires a minute longer then you're not a 10x savant like I am and you're slowing everyone down. You don't deserve to work here.
JK. IME the cycle is
1. Daunting, complete confusion
2. Find 1 or 2 subsections where I know 100% what is going on.
3. Do work in those subsections, it works, but then something messes up
4. In finding how it messes up I discover the weird edge cases and issues with the code, try to fix it
5. Doing so I begin to understand how it's all put together
Repeat 2-5 over a few weeks until it everything comes into place.
What's most important is finding small, definable areas where you can sink your mental "hooks" into the logical/semantic aims of the code, so you're not spending brain power aiming to compress information too noisy in scope at that point in your knowledge of it.