Is It Worth Reading This Blog?
The aim of this blog is simply to show my setup and give a brief preview of how it’s done.
[TL;DR]
This is my repo with my basic setup.
You can try it out in two ways:
- By clicking the "Open in GitHub Codespaces" button in the README.
- By cloning the repository and opening the folder in a dev container.
Why
As the title suggests, this is another blog about a setup for competitive programming.
For several reasons, I often find myself using a machine that doesn’t have the basic tools for competitive programming, such as g++ and python3. Every time, I get frustrated having to install everything from scratch and configure it the way I like.
To solve this problem, I decided once and for all to set everything up properly and reuse the entire setup every time I need it.
How Did I Do It?
To achieve this goal, I used the following technologies:
Docker is used to specify the required tools (git, python3, g++, etc.) and to guarantee that my working environment is always the same.
Visual Studio Code is used to specify which extensions I prefer and to set the configuration parameters.
The Dev Containers extension allows easy integration between Visual Studio Code and Docker.
In the [TL;DR] section, I linked the repository with a working configuration.
How to Compete?
Once everything is set up, it’s just like using Visual Studio Code as usual—nothing more.
Is It Worth?
If you’re wondering whether the dev container will slow you down during a contest, I haven’t noticed any slowdown while programming.
You can also launch it via GitHub Codespaces, so you don’t even need to install Docker or other dependencies.
Is It Overkill?
YES.
What About You?
How do you save your setup? Do you install everything over and over again?
Did you already know about these applications of this technology?
