Malik Ammar F.

I write software for systems that have to keep working after I hand them over. Right now I'm a software engineer at Virtual.Blue, writing C for a Wayland compositor and Go for the backend service behind it. Before that I was a backend developer at baytonia, where I built internal tools and a scraping/ETL pipeline running against Postgres. Both were existing codebases when I arrived, which is most of what I do: read a system carefully, work out why it's shaped the way it is, and extend it without rewriting the parts that already work. What I work with: • Frontend/app — TypeScript, React, Next.js • Backend — Python, Go, Node.js, C, REST APIs • Data — PostgreSQL, schema design and migrations, Prefect ETL jobs, concurrent scrapers in Python and Node.js • Infra — Docker, Git/GitHub, CI pipelines Outside of client work I build sahl, my own programming language — a compiler frontend in Rust and a bytecode VM in C. I've also contributed to GHC (the Haskell compiler) and SerenityOS. That work isn't directly billable, but it's why I'm comfortable debugging things at a level most web developers stop at, and why an unfamiliar codebase doesn't intimidate me. How I work: I ask questions before making assumptions, tell you early when something is blocked or ambiguous rather than quietly guessing, and leave the tests passing. If I think your approach has a problem, I'll say so once, clearly, and then do it your way if you still want it. I've been freelancing here since 2022. Tell me what you're building and what's currently in your way — I'm happy to give you an honest read on scope before either of us commits to anything.