Skip to content
Emre.dev — home
Emre.dev

Adana, Türkiye · GMT+3

About Emre

Nineteen. Self-taught, two years in, no computer science degree. The early work happened around 01:30 bakery shifts and high-school exams — that is part of the record, but it is not the interesting part.

The interesting part is what the code does. Eight projects, six of them under version control, a little over a thousand commits between April and August 2026. Two are live on the public internet, one is an approved production release, and one was deliberately never shipped.

The through-line is narrow and on purpose: probabilistic systems constrained by deterministic ones. A hardcoded emergency check that runs before the model. A scheduling engine the framework is not allowed to touch. A simulation core that knows nothing about its renderer.

  • Full-Stack Developer
  • AI Developer
  • Indie Hacker

Principles

What I refuse to compromise

Four positions that decide the architecture before the first file is written.

  1. Production-first

    Every system is designed for real users from day one. No prototypes wearing the costume of products.

  2. Reproducible or it does not exist

    If it cannot be re-created from a repository, I do not consider it built. Infrastructure in code, decisions written down, gates that must be green before work continues.

  3. Cost-aware engineering

    Every architectural decision considers what it costs per request. At scale those choices compound faster than feature velocity does.

  4. AI as leverage, never as authority

    Augment with AI; never replace engineering rigour. Models hallucinate. Types and tests do not.

Capabilities

What I build

No percentage bars. Each area names the technologies actually used in the projects listed below it.

  • Product engineering

    End-to-end products rather than front ends: authentication, metered billing, scanning engines, observability, and authorization derived from the token rather than trusted from the client. Four of the eight projects here went from an empty repository to something a stranger could use.

    • Next.js
    • React
    • TypeScript
    • PostgreSQL
    • Supabase
  • AI systems

    Orchestration where the model is bounded by design: structured output validated against a schema, confidence floors that resolve to "not enough information", deterministic overrides that execute before inference, and remediation produced by playbooks rather than generation.

    • Claude
    • Gemini
    • ML Kit
    • Zod
  • Mobile engineering

    Flutter applications shipped to production release tracks: on-device machine vision, row-level-secured backends, subscription entitlement mirrored server-side, and paths that still work when the network does not.

    • Flutter
    • Dart
    • Riverpod
    • ML Kit
  • Cloud and delivery

    Production resources provisioned in Terraform, edge functions, object storage, and CI that gates on lint, types, tests, accessibility and performance budgets before anything reaches a branch.

    • Terraform
    • AWS
    • Cloudflare R2
    • Vercel
    • Playwright

Experience

What happened, in order

Dates are taken from git history rather than from memory, and every entry carries something checkable. Six of the eight projects are under version control; those are the six here.

  1. Apr — Aug 2026

    FormAI — read the case study

    On-device vision · 604 commits

    The largest codebase here: roughly 61,000 lines of Dart across 177 files, eight pose analyzers, all inference on the device. Reached a closed testing track. Its most telling commit corrects the privacy policy the moment a feature started uploading photographs.

    • 604 commits
    • Build 1.0.0+40
  2. May 2026

    Lumina — read the case study

    Eleven phases · performance as a build gate

    A Next.js monorepo where every route carries its own first-load JavaScript budget and a script fails the build when one is exceeded. Thirty-five routes, three locales, and an editorial workflow that refuses to publish an uncited chapter.

    • 35 routes
    • 3 locales
  3. May 2026

    FormAI Web — read the case study

    Five days, first commit to live

    The product site for FormAI. Notable less for the stack than for the process: a written audit scored version one at 6.2 out of 10 against explicit criteria, and the phased rewrite that followed came from those findings rather than from taste.

    • 56 commits
    • Live in 5 days
  4. May 2026 — present

    PawDoc — read the case study

    Safety-critical AI · production release

    A pet-health triage product where a false negative is the primary business risk, so the emergency path is hardcoded, mirrored on-device for offline use, and kept in parity across three languages by a test. Reached an approved production release build in August.

    • 109 commits
    • Release 1.0.0+8
  5. Jul — Aug 2026

    Ehliyet Akademi — read the case study

    Monorepo platform · live in 28 days

    A Turborepo platform with a framework-free spaced-repetition engine as its own tested package, taken from first commit to a live production domain in under a month, with architecture decision records kept in-repo throughout.

    • 238 commits
    • Live at ehliyetegitim.com
  6. Aug 2026

    Evolutionary Tycoon — read the case study

    Deterministic simulation · paused at a gate

    A browser game whose simulation core imports nothing from its renderer, which is what makes the economy verifiable without a browser and a bug reproducible from a seed. Stopped at phase 4 of 25 deliberately, at a gate, rather than drifting.

    • 26k lines
    • 110 test files

Credentials

Verifiable, and not yet held

No third-party certification is held today. Two AWS exams are planned and are labelled as targets. The rest is work a stranger can open and check, which is the stronger claim anyway.

  • Shipped

    Ehliyet Akademi — live platform

    Self-issued · independently verifiable · Aug 2026

    A learning platform taken from first commit to a live production domain in twenty-eight days. Open it and check.

    See it (opens in a new tab)
  • Shipped

    PawDoc — production release build

    Self-issued · source publicly auditable · Aug 2026

    A safety-critical mobile product at approved production release 1.0.0+8, with the full source open for inspection.

    See it (opens in a new tab)
  • Target — not held

    AWS Certified Solutions Architect

    Amazon Web Services · Target · Q3 2026

    Associate. Planned, not held — to formalise architecture already running in production. No certificate exists yet and none is implied.

    Exam details (opens in a new tab)
  • Target — not held

    AWS Certified DevOps Engineer

    Amazon Web Services · Target · Q1 2027

    Professional. Follows the Associate exam; covers the Terraform, CI and release practice already in use. Also not held.

    Exam details (opens in a new tab)

Next

Have something to build?

Open to freelance work, collaboration and full-time roles.