[olingern]

- Read some recent PR's on an area of the codebase you'll be in. See if you can come up with some questions if you can't figure out why something was done. It would impress me if someone came to me with great questions or was just interested in learning.

- Be aware of your time. Sometimes, devs can be pulled in many different directions that distract them from what matters.

- Learn and research your company's tools and practices, i.e. Github/Bitbucket, Trello/Asana, scrum/okr's, etc.

- Get your dev environment running. If there are bugs or issues in the documentation, see if you can make a PR and fix it for the next person.

edit: PR stands for "pull request." Adding, since I would not have known this just out of college.