QueryForge Initial Ship
TL;DR
Initial ship of QueryForge on May 25, 2025 with the core database query experience and the first challenge list in place.
Benjamin Hyde
Education Leader & AI Builder
QueryForge officially started on May 20, 2025, and the first version shipped on May 25, 2025. The goal of that initial release was simple: get the core loop working so students could write SQL against a real database and work through a visible list of challenges.
That first ship focused on the two things the project absolutely needed. First, the database query functionality had to work reliably so students could actually run and test SQL. Second, there needed to be a challenge list so the tool felt structured from the start rather than just being an empty query box.
What shipped first
The first release included the basic database functionality required to let users run queries against the project dataset. That mattered because QueryForge only makes sense if students can work with a real relational structure rather than learning SQL as abstract theory.
Alongside that, I shipped the initial list of challenges. This immediately gave the platform a sense of progression. Even in an early state, students could see that the tool was built around solving actual tasks rather than experimenting blindly with syntax.
Why this was the right starting point
The temptation with a project like this is to build dashboards, polish, tracking, and teacher tools before the core student workflow is solid. I wanted to avoid that. If the query engine and challenge structure were not working, everything else would have been premature.
By shipping the database interaction layer and the challenge list first, the project had a usable foundation. There was something real to test, iterate on, and improve rather than just a good idea sitting in code.
Screenshots
Build Notes
Approach
Start with the smallest usable version of QueryForge: a working SQL query experience connected to a database, plus a visible list of challenges to give students structure.
Tools Used
Next.js, TypeScript, Prisma, SQLite
What Worked
The core learning loop was established early. Query execution and the challenge list gave the project an immediate educational shape.
What Failed
The first version was intentionally narrow, so many of the richer teacher-facing and progress-tracking features were still absent at this point.
What's Next
Expand the challenge system, improve the student workflow, and start building the supporting features that make QueryForge more useful in class.