§ 00 / Index—41.0°N 29.0°E

Muhammed Said Çakır

I build software systems that turn complex ideas into working products.

Software developer working across backend platforms, mobile products, artificial intelligence, computer vision, and connected devices.

Explore my work Contact me
Base
Türkiye
Role
Software Developer
Domains
Backend / AI / Mobile / IoT
Status
Available for selected collaborations
§ 01 / Work

Selected work

Four records from the archive. Each entry documents the problem, my role, and the decision that mattered.

PRJ-001WEB + MOBILE PLATFORM PRODUCTION

Qbitmap AI

Generating images with AI is easy once; making it a product is not. Qbitmap AI is a generative-image platform for web and mobile with templates, public galleries, favorites, credit management, sharing, and search that stays fast as the gallery grows.

View case study
Role
Product creator, full-stack developer
Stack
Laravel · Livewire · Alpine.js · Tailwind · PostgreSQL · Redis · Elasticsearch
Highlight
Elasticsearch-backed gallery search with Redis-cached credit accounting on the generation path
Build
[ date — placeholder ]
Role
Backend & computer-vision developer
Stack
.NET · ABP Framework · Neurotechnology SDK · Firebase · blob storage · background processing
Highlight
Recognition runs off the request path: frames queue into background workers, operators get notified on match
Build
[ date — placeholder ]
PRJ-002COMPUTER VISION PRODUCTION

Reeve

Real-time surveillance workflows fail on latency, not on model accuracy. Reeve handles biometric identification, face-attribute extraction, blacklist management, and operator notification as one pipeline an operator can actually watch.

View case study
PRJ-003LOGISTICS PLATFORM ACTIVE

EFSO

A logistics marketplace touches companies, drivers, vehicles, identity, onboarding and reference data at once. EFSO keeps those as separate modules inside one deployable system, with mobile clients on the same contracts.

View case study
Role
Software developer — architecture, backend, mobile integration
Stack
.NET · modular monolith · CQRS · DDD · PostgreSQL · React Native
Highlight
Module boundaries drawn around domains, not tables — commands and queries separated where the read shape diverged
Build
[ date — placeholder ]
Role
Designer, programmer, hardware builder
Stack
ESP32 · ESP-IDF · C · BME280 · OLED · capacitive soil sensors · REST · battery + solar
Highlight
Duty-cycled sampling and deep sleep sized against the panel, so the node survives cloudy days
Build
[ date — placeholder ]
PRJ-004CONNECTED DEVICE RESEARCH

Connected Garden Monitor

A solar-powered ESP32 node in a garden, reporting temperature, humidity, soil moisture, Wi-Fi state and its own health. Built to find out what breaks when a device has to run unattended on a small panel.

View case study
§ 02 / Capability

What I can build

C-01

Backend Systems

Scalable APIs, modular business platforms, authentication, search, caching, background processing, third-party integrations.

.NET · Laravel · PostgreSQL · Redis · Elasticsearch

C-02

Product Engineering

Turning product requirements into complete web and mobile experiences, from first prototype to release.

Livewire · Alpine.js · Tailwind · React Native

C-03

AI & Computer Vision

Generative media, biometric identification, image processing, face analysis, applied AI integrations.

Neurotechnology SDK · image pipelines · queues

C-04

Mobile Applications

Cross-platform applications, authentication, location services, push notifications, release workflows.

React Native · Firebase · store pipelines

C-05

Connected Devices

ESP32 development, environmental sensors, REST-connected devices, displays, battery and solar-powered prototypes.

ESP-IDF · C · I²C sensors · power budgeting

C-06

Architecture & Infrastructure

Domain-driven design, CQRS, modular monoliths, relational databases, caching, containers, deployment automation.

DDD · CQRS · Docker · Linux · CI/CD

§ 03 / Lab

Experiments / Things I’m exploring

Notebook entries, not products. Unfinished by design — kept here so the thinking stays visible.

  1. EXP-014 · [ date ]

    Smart-garden control loop

    RUNNING

    OBJECTIVEClose the loop between soil-moisture readings and watering, without a cloud dependency.

    LEARNEDCapacitive sensors drift with temperature; readings need compensation before any threshold logic is trustworthy.

    ESP32 · ESP-IDF · BME280

  2. EXP-011 · [ date ]

    Generative media tooling

    RUNNING

    OBJECTIVETemplating and reproducibility for image generation, so a result can be regenerated intentionally.

    LEARNEDStoring the full generation parameter set is worth more to users than any single output.

    Laravel · queues · object storage

  3. EXP-008 · [ date ]

    Acoustic & signal experiments

    PAUSED

    OBJECTIVEDetect meaningful events in a noisy environment from cheap microphones alone.

    LEARNEDMost of the difficulty is in framing and windowing, long before any classifier is involved.

    Signal processing · Python

  4. EXP-005 · [ date ]

    Logistics route optimisation

    ARCHIVED

    OBJECTIVETest whether simple heuristics get close enough to a solver for real dispatch decisions.

    LEARNEDData quality on addresses and vehicle availability dominates any algorithmic gain.

    .NET · PostgreSQL

  5. EXP-003 · [ date ]

    Face-recognition research notes

    RUNNING

    OBJECTIVEUnderstand where recognition confidence degrades: angle, lighting, resolution, or enrolment quality.

    LEARNEDEnrolment quality decides more than the matching threshold does.

    Neurotechnology SDK · .NET

§ 04 / Method

How I work

SPEC / REV. 2026-09

  1. 1.0I start by understanding the actual problem.

    Before scope, before stack. The stated request and the real problem are rarely identical.

  2. 2.0I prefer clear systems over unnecessary complexity.

    A boundary that a new developer can explain is worth more than a clever one.

  3. 3.0I prototype quickly when uncertainty is high.

    Cheap answers first; the prototype is allowed to be thrown away.

  4. 4.0I strengthen the architecture as the product becomes clearer.

    Structure arrives when it is earned, not as an opening move.

  5. 5.0I make important technical decisions explicit.

    Written down with the trade-off, so the next person inherits reasoning, not folklore.

  6. 6.0I care about maintainability, observability, and real-world behaviour.

    A system you cannot observe is a system you are guessing about.

  7. 7.0I enjoy working where software, hardware, and product thinking overlap.

    That overlap is where most of my experiments start.

§ 05 / About

About me

I’m Muhammed Said Çakır, a software developer based in Türkiye. My work spans backend platforms, mobile applications, artificial intelligence, computer vision, blockchain systems, DevOps, and connected-device experiments.

I enjoy taking complicated requirements, finding the real engineering problem, and turning it into a system that people can actually use. Alongside production software, I build personal experiments involving sensors, embedded devices, generative media, acoustics, and other technologies that make me curious.

For me, software development is not limited to writing code. It includes understanding the product, questioning assumptions, designing maintainable architecture, measuring real behaviour, and continuing to improve what has been built.

[ portrait — drop a photo here ]
FIG.02 — M.S.Ç. / Türkiye
§ 06 / Track

Career track

Dates, employers and titles are placeholders — fill in from CV.

  1. [ period ]PHP & Laravel development[ employer / context ]
  2. [ period ]Full-stack product development[ employer / context ]
  3. [ period ]Blockchain payment infrastructure[ employer / context ]
  4. [ period ].NET backend systems[ employer / context ]
  5. [ period ]Computer vision & biometric systems[ employer / context ]
  6. [ period ]AI & generative media[ employer / context ]
  7. [ period ]Logistics platforms & React Native mobile[ employer / context ]
  8. ongoingESP32 & embedded experimentspersonal
§ 07 / Notes

Technical notes

JOURNAL — 0 ENTRIES PUBLISHED

Nothing published yet.

The first notes will come out of work already in progress: recognition pipelines, modular monolith boundaries, and power budgeting on battery-run devices.

Tell me what you’d like me to write about →
  • Backend architecture—
  • .NET—
  • Laravel—
  • Computer vision—
  • Mobile development—
  • ESP32—
  • Linux & infrastructure—
  • Product experiments—
§ 08 / Contact

Have an interesting problem to solve?

I’m open to selected projects, technical collaborations, and conversations about software products, backend architecture, applied AI, and unusual engineering challenges.

Location
Türkiye
Status
Available for selected collaborations

Inquiry