About

I am a software and IT specialist, and a computer engineering graduate. I take end-to-end ownership of software systems: commerce platforms, SaaS products, and the mobile apps that sit on top of them. I build products of my own, systems for clients, and I consult when someone needs to decide what to build before spending on building it.

What makes that different from hiring any senior developer is a habit I have made structural. In the systems I build, correctness is enforced by the system rather than by anyone remembering: the ledger is append-only, the duplicate is rejected by a unique key, the tenant boundary lives in the database, and a job that gives up tells a human it gave up. The alternative is software that reports success and does nothing, which nobody finds out about until a customer does.

In practice that has meant being Kremi's software consultant since August 2025 and taking freelance engagements from clients abroad since 2026; the experience below is the short version, the log after it is the long one. Alongside that, my own products: a prompt library, a link platform, a tag layer for Google Drive built with Erkut Yıldırım, a points engine, and the agent system I run my own work on.

I work remotely, written-first: updates at the end of each working block, decisions kept in version control, and a call whenever it helps more than writing.

Experience

  1. 2025 – present

    Software consultant

    Kremi, cosmetics e-commerce

    • A storefront in Turkish and English: custom sections written inside a paid Shopify theme, with the content edited in the theme editor.
    • A Flutter shopping app on the App Store and Google Play, built since January 2026.
    • Order operations: orders from the online store and three marketplaces in a single queue where a failure raises an alert, and an internal panel for orders, stock counts and shipping labels.

    See the Kremi case

  2. 2026 – present

    Freelance engineer

    Clients abroad, remote

    • A restaurant discovery and booking platform taken over from a previous team in January 2026: a Flutter app, an Express backend and a Next.js panel, with bug fixing and a MongoDB-to-PostgreSQL migration that ran to June.
    • Payment providers in the stack: Stripe and Mollie.
    • Registered as a Shopify Partner in September 2026, for client store work.

    See the case

  3. 2025 – present

    Independent practice

    Own products and client work

    • Products: PromptLikeEngineer (version control for prompts, on web, CLI and MCP), LinkZae (link pages and digital cards, started with a friend) and FolderPls (tags for Google Drive, built with Erkut Yıldırım).
    • Client work: a Shopify store built from scratch with a migration from a local e-commerce platform, a Next.js site for a fishing-tourism business, and personal sites on a white-label platform I built.
    • Open source: promptlike (a CLI) and promptlike-mcp (an MCP server), both MIT-licensed on npm.

    See the work

  4. 2020 – 2024

    B.Sc. Computer Engineering

    Kocaeli University

    • Part-time developer at the university, June 2022 to March 2023: .NET Core MVC, Entity Framework and MSSQL, plus React.
    • Internship at UPT, a payment and electronic-money company, December 2023: banking transaction data, on Kubernetes, Elastic, MongoDB and MSSQL.
    • Internship at the university, February to March 2024: real-time EEG with an Emotiv Epoc+ headset and a Next.js interface.

How I work

Written, async

Default communication is written, so time zones matter less than clarity.

Remote, UTC+3

I work Monday to Saturday and usually reply within 12 hours.

A look before a quote

For inherited systems, I ask for a short technical look before quoting scope.

I don't claim what isn't measured

If I state a result, it's measured; if it isn't, I say so.

The log

2026
  • SEPShopify client work: registered as a Shopify Partner, freelance engagements with clients abroad, a new store build underway.
  • AUGOngoing consulting: the work with Kremi continues on a monthly retainer, and white-label tiers designed for magazine and education sites.
  • JULData that cannot drift: a loyalty platform started on an append-only ledger, with a shared Dart core and a marketplace app; my agent system got a desktop companion; the PromptLikeEngineer CLI published on npm.
  • JUNMulti-tenant SaaS: PromptLikeEngineer launched, tenant isolation enforced in the database; my agent system moved into its own repository.
  • MAYSmall-business sites: a Next.js site delivered for a fishing-tourism business.
  • APRMigration without loss: a store moved from a local e-commerce platform onto Shopify, products and content intact.
  • FEBClient operations that fail loudly: Kremi's marketplace orders brought into a single queue, failures raised as alerts, and an operations dashboard alongside.
  • FEBMeeting developers where they work: a Chrome extension for the prompt library, to be released soon.
  • JANMobile shipping: work starts on Kremi's Flutter shopping app, now live on the App Store and Google Play.
  • JANInherited systems: took over a live restaurant platform and moved it from MongoDB to PostgreSQL while it stayed online, a migration that finished in June.
2025
  • NOVFull store builds: a Shopify store built from scratch for a client, with a migration from a local platform that finished the following April.
  • AUGConsulting begins: work starts on Kremi's Shopify storefront, the first step of an engagement that is still going.
  • JULRunning my work as a system: a private, versioned knowledge and planning vault for everything I run.
  • MARAutomating repeated work: scheduled update-and-email pipelines, file tooling, a reusable web template.
  • JANLLMs in practical tools: a packaged desktop app translating Markdown knowledge bases from German to English.
2024
  • JUNFinishing the foundations: graduated with a B.Sc. in Computer Engineering, Kocaeli University.
  • MAYApplied research: an emotion-based movie recommender, EEG signals feeding a content-based model.
  • MARMeasurement discipline: real-time EEG tooling on an Emotiv headset, the academic thread where I learned it.
2022–23
  • Software fundamentals: object-oriented design, software architecture patterns and computer architecture, built alongside coursework.
  • Typed, structured backends: .NET practice with services and data layers.
  • Learning in public: opened Software Developer Archive, a social account where I shared what I was learning; teaching was my way of learning.
  • Building to learn: a plane-traffic sim, a smart-home controller, a bank management system, an e-commerce scraper, an Android card game.