Hello Codeforces!

As my collection of solved problems grew across multiple Online Judges (Codeforces, CSES, MarisaOJ, etc.), I realized that just "solving and forgetting" wasn't enough. I needed a systematic way to track my progress, refine my implementation style, and archive my thought processes.

Today, I want to share the repository I’ve built to manage this journey: **CP-Archive.

The System

My goal was to create a "Clean Code" environment for competitive programming. Here is how I organized it:

Categorization: Solutions are structured by OJ and difficulty, making it easy to look back at specific contest histories.

Embedded Editorials: For recent problems, I’ve started including a "Short Editorial" section directly inside the C++ source files. This records the core idea and the "Aha!" moment instead of just the raw code.

Living Documentation: The README.md acts as a dynamic dashboard to track which topics I've mastered and which ones still need work.

Why share this? I believe that seeing how others organize their workspace can be helpful for those starting their own journey. If you're stuck on a problem or looking for a different implementation perspective, you're welcome to explore my vault.

A note on English: Since I am still improving my English, some explanations might be a bit "raw." If you find anything confusing or have suggestions for better complexity, feel free to 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:

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

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

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

Quick Links:

All OJ Solutions

My Codeforces Archive

Happy coding, TomDev Refining logic, one problem at a time.