Mohit Yadav

First of all committing and pushing after 1st July in submitted repo is unfairrrr!!!! Second, the changes were nowhere near to small, it had 55 file changes with 5k+ additions after 1st July. If you wanted to make changes for the sake of using yourself, you could've done it in a local or private repo and not submit in the blog. I do not think others are fool who try to finish everything (from UI to code with all bugs fixed) before hackathon ends. Your app is interesting and useful, but man you lost my respect! Even I could have added a ton of features in my project but I'm doing so in a private repo. I believe everyone should wait till the results are announced before making any changes to their repository.

Rounak Singh I understand your concern. I've fully made sure to not change any noticeable functionality of the application.

Just that I wanted to track the clicks I was getting, so I added analytics. Some people reported some typos, so I changed some text. Just had a few complaints of errors not showing up if progress is struck, fixed that. Most of them because I went with JavaScript for this project, not TypeScript. You could even see the commit messages and have a look at the changes, they're mostly silly typos or updating mundane-stuff.

I believe I do not stand an unfair chance with making any of the changes, and besides, these commits contribute to less than 1% of the code (the 5k+ additions is git's problem that it does not differentiate renames with changes. Like if I change the name of the src file to source, it would show 99% lines added, 99% deleted. These changes show because I renamed a template from fancy presentation to angular presentation to make it sound more descriptive, and also renamed some SVG files). If you do not agree, you're free to go back to the commit on 30th June and report any noticeable changes you find you feel are unfair to submit after the deadline.

This does not change the fact that the project was full functional, completed and submitted even a few days before the deadline. As I said before, feel free to go back to any commit you feel makes a significant change in my project's marking. Git is a very transparent technology, and it's up to the judges to decide which codebase to consider. I do not agree with how altering less than a few typos and minor stuff could result in respect changes when the project is so huge 😃. Thanks!

Rounak Singh He actually booked a slot. The entire article was blank by the deadline.