There is a pretty simple order of operation you can target if you want: 1) As you onboard and get your environment setup simultaneously write a Vagrantfile so

There is a pretty simple order of operation you can target if you want: 1) As you onboard and get your environment setup simultaneously write a Vagrantfile so that you can provision a local dev environment in an automatic fashion. 2) Set up an automatic monitoring solution. This shouldn't take longer than 30 mins but will be all it takes to provide proof that lack of tests and deploys directly from local to prod are endangering the stability. It will also allow you to pinpoint outages coinciding with deploys. 3) Write an extremely basic test script. Even if it is nothing but a bash script that uses curl commands to do auth, the top 5 transactions, and that's it it will still be better than nothing. You don't need 100% coverage for tests to be useful. Most of the time there are a key ten to twenty tests that can cover 80% of the core stuff that you don't want to break. 4) Any time you figure out how an endpoint works, or have to ask one of the other engineers something take 5 minutes to commit this meatspace knowledge you just learned to a bitspace markdown file somewhere in your repo. The nice thing is that these are all things that take minimal time, but have a huge multiplicative effect on your productivity and that of others. You should be able write better code faster than your coworkers and the results will speak for themselves.