How I organize my competitive programming solutions

Revision en3, by TomDev, 2026-02-17 18:16:13

Hello Codeforces!

As my collection of solved problems grew across multiple Online Judges (Codeforces, CSES, MarisaOJ, etc.), I realized that just solving and then forgetting the problem wasn't enough. I needed a way to track my progress, improve my coding style, and save my thoughts.

Today, I want to share the repository I’ve built to manage my source files and other resources: CP-Archive.

The System

My goal was to create a clean coding environment for competitive programming. Here is how I organized it:

  • Categorization: Solutions are sorted by name and categorized by OJs. This makes it easy to review when needed.

  • Embedded Editorials: For recent problems, I’ve included a "Short Editorial" section right in the C++ source files. This captures the main idea and the moment of clarity instead of just providing the raw code.

  • Living Documentation: The README.md serves as a dynamic dashboard to track which topics I’ve mastered and which ones I still need to work on.

Why share this?

I believe that seeing how others organize their work can help those starting their own journey. If you’re stuck on a problem or looking for a different way to implement a solution, feel free to check out my vault.

  • A note on English: As I’m still working on my English skills, some explanations may be a bit rough. If anything is confusing or if you have suggestions for clearer details, please open an Issue or leave a comment! I update and refine this repo daily.

My Philosophy on Learning

To protect your own growth and critical thinking:

  1. Only check my code/editorial when you are absolutely stuck after hours of thinking.

  2. Use it to compare implementations after you have already got "Accepted".

  3. Disclaimer: This is a personal progress tracker, not a formal encyclopedia. Read at your own risk!

Quick Links:

Happy coding, made by TomDev with joy.

Repo preview

Tags solutions, guide, repository, personal, cpp, learning-resource, editorial, archive

History

 
 
 
 
Revisions
 
 
  Rev. Lang. By When Δ Comment
en4 English TomDev 2026-02-19 13:58:55 1793
en3 English TomDev 2026-02-17 18:16:13 29
en2 English TomDev 2026-02-12 20:27:11 783 Tiny change: 'ks:\n\n- [All OJ Solutions](https://' -> 'ks:\n\n- [My whole library](https://' (published)
en1 English TomDev 2026-02-12 20:02:09 2098 Initial revision (saved to drafts)