I am a proficient power-user of the terminal. The high majority of my terminal knowledge is in Mac and Ubuntu, so I don't believe that I know that much in Windows. I know a lot of the commands are similar but don't know the differences between the operating systems. WSL somewhat compensates for that, however, I much prefer to do my development on a Mac.

To varying degrees, I can use the terminal for package management with tools like 'brew', 'pip', 'pyenv', 'pipenv', 'conda', 'npm', and 'poetry'.

I can create some shell scripts to automate some frequently repeated processes.

I build all of my project's development environments using Docker within the terminal. Other than 'build', 'up', and 'down', the majority of commands you're likely to need to manage a project in Docker can be found here.

I can build 'docker-compose' files to automate the build and setup process for my Django projects. This includes services for Django itself, Postgres, Celery, CeleryBeat, and Redis.

I have tested a lot of Python images and eventually found that some of the recommended lighter packages such as 'alpine' is actually more hassle than its worth. This is because you need to add/remove dependencies to get the images to build all for the sake of the overall build being that bit smaller. I have settled on the 'Buster' version which works for my projects.

I am proficient in the command line for most of the basic Git commands required to manage a project such as add, remove, commit, push, pull, branch, merge, status, diff, log. I would need to research some of the lesser used commands

I have a good knowledge of managing a project using GitHub issues and projects.

I have made a few contributions to open source projects. These have mainly been in improving the documentation and testing coverage (tox/travis).

I would like to learn more about GitHub actions as this seems like the next progression in CI/CD since it is so closely coupled with GitHub. I haven't found a need to use this yet as my deployment strategy is using Heroku which, after the first deployment, is relatively simple when compared to deploying to a Linux server such as Linode or Digital Ocean.