The First 30 Days of a New Dev Job

In a new job, I want to get the project running and make one small change as early as possible. It gives the setup instructions and release process some context.

I also keep a list of names, terms and questions. There's too much to remember in the first week, and some things only make sense after I've seen them used. I try to understand why the code looks the way it does before suggesting how I'd rearrange it.