Calmly, line by line, character by character. No rush.
I’ve been tasked with making pretty significant changes to a core piece of Urbit software. That’s really cool, and I’d love to become The Guy Who Made The Thing, but I can’t just jump in and get to work. Not if I’m aiming to bring forth a sturdy result, that is. Doing big work on something I only half understand doesn’t sound like the most productive effort, now does it?
And so I set off to learn. It helps that I’ve touched some parts of the code already, so there’s some familiarity here and there. There’s many more parts though that I’ve just skipped over when I last saw them, either because they were irrelevant or they seemed too complex.
Now that I’m actually sitting myself down and working through the thing line by line though, it’s starting to make a lot more sense. Having “I just want to implement x” in the back of your head rushes you towards finding a solution quick. That can be perfectly fine, but it often pushes you to skip on thorough understanding. Chances are that’ll come back to bite you, too.
Things are now starting to click into place though, slowly but surely!