Web
Frontends that hold up after a year in production. Strong types, careful state, and the parts users don't notice but a team does.
- TypeScript
- React
- Next.js
- Tailwind CSS
- Motion
- Vite
- Astro
- Web Performance
Working notes
— From a desk in southeast Türkiye. —
Software engineer in Mardin. Mostly remote, across Kurdish, Arabic, and English environments. Marketplaces, exchange tools, automation, the slow-running parts of online infrastructure. Decisions made early are usually the ones that ruin a system later. The rest is mostly maintenance.

Field
Software engineering
Builds
Web · Mobile · Backend
Languages
EN · TR · AR
Method
Remote, async
II — Stack
Grouped by where it sits in the stack. Names I open every week — nothing here for the trophy shelf.
Frontends that hold up after a year in production. Strong types, careful state, and the parts users don't notice but a team does.
iOS and Android. Swift and Kotlin where the platform asks for it. Accessibility, gestures, battery — not afterthoughts.
APIs, schemas, queues, the slow-running parts. Built so on-call is short and the page rarely wakes anyone.
Around the code: CI, design tokens, code review, written records. The boring parts that decide whether a project survives the second year.

III — Work
Built end to end. Handed over. Still running.

A marketplace for Syria. Listings, paid promotion, and the contact path between buyer and seller.
Bayzo is the marketplace I built for the Syrian market. It does three things at once — listings, paid promotion, and a clean handoff between buyer and seller — without becoming a flea market. Most marketplace work is content moderation and search relevance, not pretty product pages. I built around what breaks under load.

Listings and project pages for a real estate and construction firm in Mersin.
GELLO is a real estate and construction firm in Mersin with a long local presence. The brief was simple: move the firm's offline reputation online without making the site feel like a fresh startup. Bilingual listings (TR/EN), pages for finished and active builds, and contact paths that route serious leads to the right person.
IV — Certificates
Mostly for myself. The work is the real proof; these are receipts.
Foundational Google course on prompt structure and output evaluation. Useful for setting realistic limits on what generative AI is good for — and what it isn't.
Practical Google course on AI as a junior assistant for everyday writing, brainstorming, and document work. A tool, not a replacement.
IBM SkillsBuild credential on AI systems, ethics, and the machine learning underneath them. Mostly useful for separating marketing claims from what these systems actually do in production.

V — Notes
Borrowed from people who shipped real systems. Useful on the bad days.
Simplicity is prerequisite for reliability.
Edsger W. Dijkstra
EWD498, 1975
Programs must be written for people to read, and only incidentally for machines to execute.
Harold Abelson
Structure and Interpretation of Computer Programs
Perfection is achieved, not when there is nothing more to add, but when there is nothing left to take away.
Antoine de Saint-Exupéry
Terre des hommes, 1939
Premature optimization is the root of all evil.
Donald E. Knuth
Structured Programming with go to Statements, 1974
The function of good software is to make the complex appear to be simple.
Grady Booch
VI — Contact
I read every message. Short and specific helps. Tell me what you're building and what's missing.

Working with
Mostly remote. Türkiye-wide — Istanbul, Ankara, İzmir, Bursa, Antalya, Mersin, Mardin, Gaziantep, Diyarbakır — and clients abroad. Kurdish, Arabic, English. The brief matters more than the city.