11 — Tools Setup¶
The goal of Day 1 setup is to reduce the activation energy for practice to zero. Every time you sit down to solve a problem, you should be solving within 60 seconds of opening your laptop — not hunting for the right file, configuring a compiler, or wondering where your notes went.
Friction is the enemy of a 10-15 hour/week schedule. When you have 45 free minutes on a Tuesday evening, cognitive overhead from a poorly set up environment is enough to turn “I’ll solve one problem” into “maybe tomorrow.” Remove the overhead once, on Day 1, and it stays removed.
This section is not about finding the perfect setup. It’s about finding a good-enough setup that you will not need to reconfigure for 9 months. Resist the urge to optimize your tools instead of using them. A competitive programmer who submits on Notepad++ beats one who spends Sunday afternoons configuring Neovim LSP.
Contents¶
01_ide_and_environment.md — VS Code, language choice, environment setup
02_problem_tracking.md — Logging solved problems and patterns
03_competitive_programming_setup.md — CP-specific tooling
04_day1_checklist.md — The exact Day 1 (July 27, 2026) action list
Navigation: ← Communities | → Main README