You have finished the coding course. The next useful test is whether you can recognise a mistake without an instructor highlighting it.
I built ReviewIQ as hands-on practice for that step, using Next.js and Supabase. You read unfamiliar code with planted mistakes, explain what could go wrong and what you would change, then compare your findings with caught/missed feedback.
The guest exercise is one fixed Backend/Python/Mid-level challenge. It is free to complete before signup. An account is needed to save your result and continue; free accounts include 5 credits. This is practice and feedback, not a course, credential or job guarantee.
For other Supabase builders, the product decision I would like feedback on is the account boundary: let someone experience the exercise and result first, then offer saving and continued practice. I am not claiming a conversion improvement; that is still being measured.
Actual product screenshot from a founder test: 4.3/10, 1 caught, 2 missed. It is not a customer result.
<img width="1359" height="933" alt="ReviewIQ founder test result showing caught and missed feedback" src="https://github.com/user-attachments/assets/4321e605-0706-4f6c-80ee-f1e7c6f9a5f4" />Would this be useful as an optional exercise after a coding workshop? I would especially value feedback from developers who teach beginners.
Anas Bahraoui introduces ReviewIQ, a tool built with Next.js and Supabase for practicing code review. He seeks feedback on the decision to allow users to complete an exercise before requiring sign-up. Mint from AppFirstAid suggests ensuring result persistence post-sign-up and recommends adding security headers. Feedback from developers who teach beginners is particularly valued.
On the account boundary: letting people finish the exercise before sign-up feels right to me, as long as the result survives the sign-up step (worth testing with a brand-new email, including the confirm-email redirect on the live domain). I also ran a free outside check on the live site and it looks clean: no exposed keys or config files, and /login and /pricing load. One small thing worth adding is the three browser safety headers (Content-Security-Policy, X-Frame-Options, X-Content-Type-Options), which Vercel lets you set in vercel.json. Disclosure: I work on AppFirstAid, the tool I used; report here if useful: https://appfirstaid.com/r/077998dd-0afd-4ac3-a1d4-58561f558144