Handy Tools — the project that made us “real”

The assignment that refused to stay small

Handy Tools began life as the final project of our second semester in the Diploma in Information Technology — my brother Muhammad Hassan Qureshi and I, studying side by side at Government College of Commerce & Management Sciences, Ring Road Peshawar, submitted to the Khyber Pakhtunkhwa Board of Technical and Commerce Education. We could have built the conventional project everyone expects — a few static pages, a screenshot in a report, done. Instead we asked a hungrier question: what if our submission was a real, live website that examiners, teachers and the public could actually visit from anywhere in the world?

That single decision multiplied the difficulty — and the learning — by ten. Suddenly it wasn’t just about writing the tools. It was about hosting, domains, deployment pipelines and everything nobody teaches you in a semester. We dedicated the project report to our parents and teachers, whose support carried us through it — and then we went hunting for a way to put it on the internet.

Two platforms failed us first — and that was the gift

Our first stop was the classic free-hosting route: InfinityFree. Then Pantheon. Both taught us the same lesson the hard way — restrictive limits, forced setups, and walls between you and a genuinely professional result. Every dead end pushed us to research harder, and that research uncovered the thing that changed our developer lives: the modern workflow of Git + GitHub for version control, wired to Vercel for automated deployment. Push your code, and the site updates itself. We created our accounts, moved the project into a proper repository, and imported it into Vercel.

Then came the night we’ll never forget. The first deployment went live — and every page except the homepage screamed 404_NOT_FOUND. Our stylesheets were gone, our scripts were gone; the site was a skeleton. For a beginner, that’s the moment you quit. Instead, we debugged it like engineers: the culprit was relative path references — files inside the Pages folder were looking for /Styles/styles.css at the wrong root. One character — adding ./ — separated a broken site from a working one.

We restructured the whole repository into clean Pages, Styles, Scripts and Media folders, corrected every path, and pushed again. Vercel rebuilt automatically. The site loaded perfectly. Watching that deployment turn green taught us more about real-world web development than any tutorial ever had — the kind of lesson you can only buy with a genuine failure.

Small tools, serious standards

We made a deliberate philosophy call: no tool gets published until it deserves to exist. Every tool had to load instantly, work on a slow phone connection, look clean on any screen, and do exactly one thing well. The length converter handles every unit a student meets, from millimetres to miles. The BMI calculator gives a clear, WHO-standard category, not just a number. The word counter counts the way writers actually think, and the ToDo list remembers your tasks between visits using browser storage.

The final build: 9 HTML pages, 9 JavaScript modules, 1 unified stylesheet, 21 media assets — every line written by hand in Visual Studio Code, tested across screen sizes, and shipped through the Git-to-Vercel pipeline we’d bled to learn. Building as brothers meant every decision passed two very different brains — I obsessed over code structure; Hassan guarded the user’s eye view. The tools are better for every one of those arguments.