QueryCase's answer
QueryCase started with a frustration I carried for years as a data analyst.
I dropped out of a software engineering degree after realising the coursework had no connection to anything real - Fibonacci sequences, phone book applications, abstract exercises with no stakes. I ended up in a data analyst role instead, which meant learning SQL properly and fast, on the job.
Seven years later I had built data pipelines, done data modelling, enabled self-serve analytics across multiple companies, and I kept seeing the same pattern. People trying to learn SQL hitting the same wall I had. Not because SQL is hard, but because every learning resource follows the same formula: a fake dataset, an isolated exercise, no reason to care about the answer.
The research backs this up. Information you actively generate is retained at nearly three times the rate of passive reading. Tutorials give you nothing to generate because there is nothing at stake.
I wanted to build something where the SQL had a reason behind it. Where getting the query right actually mattered. The detective investigation format came from that - give someone a case briefing, a real database, and a mystery to solve, and suddenly the JOIN has a purpose and the WHERE clause has stakes.
QueryCase is my first product launch. It is built by one person, designed around the learner I used to be, and focused on making SQL feel like something worth learning rather than something to endure.
Datacamp
Codecademy
SQLZOO
DataLemur
StrataScratch
LeetCode
HackerRank
The Odin Project
LiveEdu.tv
