A hundred thousand guesses a second for a year straight and I wouldn't have come close ONCE to the reveal here

Show Post

Having finally identified the cause, you determine how to fix it. This could involve a small change to a specific component, or redesigning several components and their interactions from the ground up. This latter kind of work was some of the most satisfying to me.

Show Post

Having reproduced the bug, you then proceed to actually read the underlying code to understand what's going on. Code is at the end of the day structured text, and is usually organized into functionally differentiated components.

Show Post

Let's say you're fixing a bug in your software reported by a user, a huge part of the job. First, you spin up the app or whatever in a dev environment to reproduce the bug. You need to do this to determine that it's even real. This often involves painstakingly recreating the user's conditions.

Show Post

You think about how to make sure that other humans—including your future self—can read, understand, and thereby maintain your code. Mostly, you're reading code that other people wrote and trying to figure out if it's good or, if not, how to make it better.

Show Post