> 1. In your engineering careers how often do you have to deal with shit code other people wrote? Almost as often as I have to deal with shit code I wrote :)

> 1. In your engineering careers how often do you have to deal with shit code other people wrote? Almost as often as I have to deal with shit code I wrote :) > I'm in the process of fixing bugs (and learning about the code altogether). This is exactly the way to deal with this situation. Until you understand the project's architecture you can't make an objective decision on how to improve things. As you go along make sure that you're adding in relevant tests so that when you are in a position to make an objective change you can make sure you don't break the actual business logic of the project.