How to own a code

Knowing the architecture of an application is like passively knowing a foreign language. When you speak it - it's awkward. Here's how you go from passively to actively owning a code-base.

Have a feedback loop

"I believe we can quickly rise to the top if we never repeat the same mistake twice". I decided to test that. 4½ years later and many of my mistakes recorded where's what happened.

How to read a code

"Oh that's Steves code. He quit two years ago. We don't touch it. It just works and no-one knows how. Just let it be."

Overview mode

Sound familiar? You're 95% done some touching up then commit and run. And from nowhere that last little detail puts you back to square one.

Sider 1.0 - an ode to yak shaving

Why my greatest open source hit so far: sider almost never existed

Getting better at it

Want to get better at programming? Me too!