Production & pricing system
Hazelnut production, contracts and CRM in one Go service, with a cost model unit-tested against the spreadsheet it replaced.
- Go
- PostgreSQL
- SSE
- Claude API
I lead digital transformation at a logistics group in İstanbul, from architecture through to deployment, on every internal web and mobile system. Trained at École 42 on C, sockets and containers, which is still how I prefer to think about a problem: from the layer underneath it.
The remit
One developer, a logistics group, and every internal system it runs on.
Off paper
Vehicle maintenance and technical service, moved into a Flutter app wired straight into the ERP.
Out of the spreadsheet
A pricing model that lived in Excel, rebuilt as a Go service, unit-tested against the file it replaced.
Grounded answers
A retrieval-augmented assistant that answers from what the company actually wrote down.
Hazelnut production, contracts and CRM in one Go service, with a cost model unit-tested against the spreadsheet it replaced.
Vehicle maintenance and technical service on mobile, synchronised with Movetech ERP over REST.
Feature work inside the ERP the fleet runs on, rather than around it.
Reaching drivers on the app they already use, instead of asking a fleet to adopt a new one.
Corporate documentation ingested into a vector store, answers grounded in the source.
Real-time game state and chat over WebSockets, JWT two-factor auth, the whole stack in Compose.
Written from scratch in C++, speaking the protocol well enough for real HexChat clients.
Multi-node K3s provisioned with Vagrant, deployments synchronised from Git through ArgoCD.
Two curricula, 26 months overlapping
I took a Computer Programming degree at Karabük Üniversitesi and went through the Common Core at École 42 Kocaeli at the same time: two full curricula running in parallel for most of their length. That is where the discipline came from, and the habit of scheduling work against a deadline I did not set.
42 has no lectures and no teachers: you read unfamiliar systems until they make sense, then defend the result in peer review. I still work that way. Give me a problem and I will take it end to end: architecture, implementation, database, deployment. I would rather own the whole path than wait to be handed a spec for part of it.
2021 – present
Associate, Computer Programming
Common Core
Software Development, İstanbul
↑ 26 months of both at once
Enco Lojistik · 12/2024 to present, İstanbul
Enco Lojistik · İstanbul
École 42 · 2022 to 2024
ft_transcendence
ft_irc
Kubernetes track
Grouped by where it sits in the stack
Open to conversation about backend, infrastructure and data work. References available on request.
Download CV↓