# 🚨 I Lost My Entire Backend Code 2 Days Before Submission (A Fresher’s Mistake)
Hi connections,
As freshers, we face different types of failures and successes. In that process, we do many activities, and all of them give us some learning and warnings. In my journey as a fresher, an incident also occurred recently.
💻 The Incident
The incident is like this: for my college project, I had been working on developing the backend system for my project ArogyaNaxa for around 2 months. It is based on microservices architecture and has 14 APIs, along with a Gateway, Auth service, and business logic APIs.
When it was built around 70%, I made a copy of that backend system to move further with new changes until 100% completion. When it became 100% successful along with API testing, at that stage I had all 14 microservices including Kafka, Redis, and a single entry point as a gateway.
For all this work, I was using Git and GitHub for code review and code storage.
🔄 Integration Phase
Now, the next step was to integrate the backend with the frontend. I am a person who has more interest in developing backend systems rather than frontend and integration work, so I used Kiro for integration work.
I gave a detailed prompt to Kiro to integrate the frontend and backend. Then the agent started analyzing my 14 APIs code with the frontend structure. It takes time, so I thought to push the backend code to the repository.
I tried to push, but I got an error because the repository already had frontend code, and one or two APIs were the same as those used in my previous project, which were already pushed to that repo.
⚠️ The Mistake
So, I copied those errors and pasted them into GPT, and it suggested removing the .git folder, reinitializing it, and pushing the code again.
I deleted and reinitialized it and pushed the code.
When I checked, I found my code was corrupted, and many APIs had lost their business logic.
😨 What Went Wrong
When I investigated, I found that my 14 APIs were very large, and analyzing and integrating them took more time and exceeded the context limit of the agent, so it deleted out-of-context code.
At that time, I was not aware of that.
I tried my best to retrieve my code, thinking that since I was using Git, git log would help me reset my working directory. But I had already made a mistake.
Deleting the .git folder deleted all the commit history, and the git log command did not help me.
That gave me a big shock at that time; it was around 4:30 AM IST.
All this happened when my project submission was just 2 days away. Thinking about all this, I couldn’t sleep till 7 AM IST.
When I woke up, my project members called me to verify the project report at 10 AM. They were busy doing all that work, and I kept thinking that if they knew about the current situation of our project, they would scold me badly.
🔥 The Comeback
After finishing the project report work, I came back to my hostel and started preparing to build the backend system again with some minor changes.
At that time, instead of following microservices architecture, I followed monolithic architecture. Earlier, I was trying to make my APIs enterprise standard and ready to deploy on AWS, but now they were only compatible for my local server to build the system.
From that day, I did not sleep for nearly 2 days and, without taking any break, just focused on building the backend and integrating it with the frontend.
On the day of submission at 7 AM, I was confident that now all the functionalities were working, and we were able to present our project.
📌 Moral of the Incident
- Never delete your
.gitfolder; find other ways even if AI suggests it. - Never use forceful Git commands like
--forceor--hardwithout understanding them, because they can delete commit history, and without history,git logbecomes useless. - Building microservices-based projects is time-consuming.
- Building monolithic architecture-based projects is simpler, easier, and takes less time.
- Test cases are the backbone of any codebase. If your test cases run perfectly, your APIs will work smoothly. If you do not use test cases, you have to manually check every feature or endpoint. Writing test cases for every feature will save time and remove doubts about whether your system is working properly or not.
📊 Below is my backend system architecture figure.
🚀 I will share my working project in the next post.
Thanks for reading.
I know it’s a silly mistake, but how much maturity can you expect from a fresher?
Writer
Shivam Sharma
Java Backend developer
LinkedIn : www.linkedin.com/in/shivamsharma117