Zohaib AliSoftwareEngineer

Birmingham's bin strikes left waste sitting on the street for weeks, and residents had no reliable way to say where it was or whether anyone had dealt with it. CommunityClean was my dissertation answer: a map where anyone can drop a report with a photo, a location and a severity rating, see what has already been logged nearby, and organise a clean-up around it. Reports move through a full lifecycle, from submitted to scheduled to cleaned and finally verified with photographic proof, with admin moderation sitting behind the whole thing.

Access control lives in Postgres as Row-Level Security rather than in the application layer, with Zod validating at the edge. The cost is that the policy sits further from the code that reads it. The payoff is a report staying unreadable even when a query is wrong.

Most habit trackers stop at the tick of the task. Divergence records the day as well: you check off what you actually did, log a mood and a rating, and the dashboard puts the two next to each other, with streaks and completion over time set against the days you marked as good ones. The idea is to work out which habits are genuinely doing something for you rather than just collecting green squares.

Next.js Server Components and Server Actions read and write Supabase Postgres directly, so there is no separate API tier to keep in sync. The trade is a data layer only as portable as the framework. Writes upsert on natural unique keys, so a retried submit cannot double-count a habit. Streak, date and completion maths sits in a pure, dependency-free module under Vitest, because an off-by-one there is invisible right up until someone loses an eleven-day run.