About
One person, start to finish.
I'm Yameen, in Greater Manchester. I design the interface, model the data behind it, write the pipeline that ships it and operate the thing once it is live — for a masjid with an app on Google Play, a product of my own, and a handful of businesses. Working alone means there is nowhere to hand a problem on to, which is the part I have learned most from.
What I build
- Interfaces
- Static sites in Astro and Next.js, PWAs with service workers and offline behaviour, and a React Native app. Accessibility checked in CI, not at the end.
- Software
- Multi-tenant Postgres on Supabase with row level security, SECURITY DEFINER functions, scheduled jobs and edge functions. Stripe for payments, webhooks included.
- Delivery
- GitHub Actions across seven workflows — build, smoke, release gating, worker deploys. Static output to GitHub Pages on custom domains; Cloudflare Workers where compute is unavoidable.
The detail, with the workflow files and migrations behind each claim, is on the engineering page.
Certifications
Held
AZ-900
Microsoft Azure Fundamentals
Booked
AZ-104
Microsoft Azure Administrator
Exam booked, not yet sat — a plan rather than a qualification.
A fundamentals certificate is not production experience and this page does not pretend otherwise — what I have actually run is below.
How I work
- The check has to be able to fail
- A CI job that cannot catch the thing it exists for is worse than no job, because it buys confidence. I have shipped that mistake, and it is why my release workflow now refuses to build a bundle no device has opened.
- Write down why, not what
- The diff shows what changed. The commit message is for whoever finds this in a year and needs to know which constraint made it the right call — and whether that constraint still holds.
- Say what is not built
- Every project here states what is finished, what is staged and what is blocked. Overstating readiness costs more than admitting a gap, and it is the error I have had to correct most often.
- Put the rule where it cannot be bypassed
- Hiding a row in the interface is not access control. If it matters it belongs in the database, behind a grant and a policy, so editing the JavaScript in a browser gets you nothing.
What I'm looking for
- Roles
- Platform, DevOps or infrastructure engineering. I am most useful where delivery is the problem — pipelines that do not catch what they should, environments that drift, deploys nobody trusts.
- Where
- Greater Manchester, or remote. The work above has gone to London, Birmingham, Coventry and Nuneaton without me being in the room.
- Honestly
- The certificate above is Azure; the systems are not. What I have run in production is Cloudflare, Supabase, GitHub Actions and Render. The concepts carry — tenancy, least privilege, build gating, webhook idempotency, deploy verification — but I would rather be straight about which consoles I have actually operated in than let a fundamentals exam imply more than it is.
Get in touch
Hiring, or want to talk through any of the work above? Either route below reaches me. Still taking freelance builds alongside this —process and prices here.