You look at the involved components and how they interact, and try to discern what could cause the bug. Depending on the complexity of the bug and the software, at this point you're anything between 10 minutes and several days into the process.

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

We got Andre 3000. #halloween

Show Post

I love the dynamic when a federal judge says something that sounds mildly salty and all the lawyers on here are like: “omg” “HOLYYYY SHIIITT!!” “I would just quit right then in shame. Give up law and open a show shop” “federal judges only say this when they are extremely stressed”

Show Post