Ayach Youssef

ship.log — 18entries

Ship Log

Engineering notes with one rule: every entry is something I shipped, or something I learned shipping it. No filler. Subscribe via RSS.

Privacy by schema: when the column does not exist

Lantern Analytics promises no cookies, no stored IPs and no fingerprints. The way to make that promise checkable is to give the database nowhere to put them, test that, and then find out what the tests still cannot see: a chart blanked by its own security policy.

497 green tests, and a hospital perpendicular to its insurers

Site Kit builds 60 business websites in French and Arabic, with a test suite that covers every one of them. A full read of the Arabic still found 65 errors, including one that changed what a hospital was telling its patients. What tests can't see, and what I changed.

A photo for every demo site, and the batch that was a file late

The CeoJoe showcase needed a distinct photograph for every demo site. Generating them was the easy part. Getting each one attached to the right business was where it went wrong, and a contact sheet is what caught it.

A government changed a timezone and broke my tests

A failing test in a booking app's CI looked like an environment bug. Three machines gave three different answers before I found the actual cause: Morocco abolished its seasonal clock change three weeks earlier, and nobody told my test fixtures.

A security checklist on a finished app: three real fixes

ci-pulse was feature-complete and already hardened when I ran a full security checklist over it. It still found a critical dependency advisory, a config bug that failed mid-request, and a cron check that would have accepted 'Bearer undefined'.

Why the poller is not on Vercel Cron

ci-pulse needs to check GitHub every five to fifteen minutes. Vercel's free tier runs cron once a day. The fix is a secret-guarded endpoint that any scheduler can call, and a few rules about how it behaves when it is called.

Learning Go by scratching a real itch: ci-status

A tiny Go CLI that checks GitHub Actions status across several repos at once — my first project in a new language, and the byte-vs-rune bug it taught me on day one.

Terraform without a cloud account: do-vm-terraform

A DigitalOcean droplet+firewall+DNS module, fully validated and tested against a mocked provider — and the Terraform `set` block bug that cost me an hour.

Building auth from scratch instead of installing it: auth-service

A standalone JWT auth microservice built against an explicit OWASP checklist — refresh-token rotation with reuse detection, argon2id, and timing-safe login failures, all decisions I can defend one by one.

Building a CI/CD + IaC pipeline from nothing: deploy-pipeline

A minimal link-shortener is the vehicle; the real project is the pipeline around it — GitHub Actions, Ansible-provisioned VPS, and nginx, wired end to end.

Real-time without a framework: live-room

A live poll room over WebSockets — vote counts and presence updating instantly for everyone in the room, with no page refresh and no polling.

Provisioning-as-code for monitoring: observability-stack

Prometheus and Grafana monitoring task-api-hardened, with the dashboard itself checked into git instead of clicked together — plus the honest story of adapting scope when a VPS wasn't there yet.

Extracting a library from my own repetition: strict-env

Every backend service this sprint hand-rolled the same env-var validation block. strict-env factors it out — zero dependencies, dual ESM/CJS, and reports every config problem at once instead of one restart at a time.

Hardening a toy CRUD API into something production-shaped

task-api-hardened takes a five-endpoint task list and wraps it in Redis-backed rate limiting, cache invalidation, and structured logging — the unglamorous layer that separates a demo from a service.

The fun slot: termdle

A Wordle clone that runs entirely in the terminal — this sprint's unserious project, and the one classic edge case (duplicate letters) it still had to get right.

Building something that acts without being asked: weather-pulse

A cron-scheduled service that snapshots real weather data into Postgres every 15 minutes, rendered through a dashboard with zero client-side JavaScript.

MCP servers in production: giving an AI agent hands, safely

OneBotAds' chatbot launches real ad campaigns through Model Context Protocol servers spawned per request. Here's the architecture, why we spawn instead of keeping processes alive, and what I'd tell anyone wiring an LLM to real APIs.

From mockup to production in three months: a PFE postmortem

My final-year internship brief was a React mockup with nothing behind it. Three months later it was a live SaaS with six ad-platform integrations. What went right, what bit me, and what I'd do differently.