Скачать или смотреть Online Judge

copy this url
Github repo:- https://github.com/shrey209/Algomania-judge

My Journey with Algomania

Embarking on the journey to create Algomania was a challenging yet rewarding experience. It all started in my 3rd semester when I first explored Spring Boot and learned how to build APIs. I created a small code execution system that ran scripts using the command line. This initial project sparked the idea of creating my very own version of LeetCode.

During my summer vacations, I began building Algomania in earnest. Progress was steady, but then I stumbled upon videos suggesting the use of Docker for containerization. Intrigued, I delved into Docker and integrated it into my project. My learning curve didn’t stop there; to ensure reliable service for users, I explored Kafka for message queues.

The biggest challenge I faced was developing the remote code execution (RCE) engine. I spent about a week refining it, striving to make it functional. Although it is not yet perfect, I am continually working to improve it. Currently, the RCE engine doesn't run in parallel and lacks CPU limits. To address these issues, I am learning Kubernetes, even though it might take some time as I am still a beginner. Nevertheless, I am determined to make it work.

Throughout this journey, I built every aspect of the project myself, from API gateways to authentication filters. I made various trade-offs in designing the database schema and, while I am not certain how well it will perform under heavy load, I am confident that problem searching will be fast based on my current knowledge.

Creating Algomania has been an incredible learning experience. Here are a few key lessons I've learned along the way:

1. *Managing projects is tougher than it seems:* The intricacies and scale of Algomania taught me the importance of meticulous documentation. Without it, keeping track of progress and ensuring consistency becomes a daunting task.

2. *The art of error management:* I learned that bad code isn't just a nuisance; it can be a showstopper. Effective error management became my lifeline, ensuring that the project remained stable and functional.

3. *The nature of trade-offs in software development:* I discovered that every decision comes with its own set of sacrifices. In the software industry, you must often choose one path at the expense of another, balancing benefits and drawbacks.

4. *Facing and conquering challenges:* Building Algomania was often an overwhelming workload. There were moments when the urge to give up was strong, but I learned that perseverance and determination are key. Overcoming those lazy thoughts and pushing forward was crucial to my progress.

This project is a testament to my journey of growth and determination in the world of software development.