$ whoami
i build software from the first architecture sketch to production — backend systems, interfaces, real-time applications, and the infrastructure that keeps them running.
i'm Ege, a software engineer working across backend and full-stack development. i care about systems that are understandable, maintainable, and useful after the first release.
my work spans Java and Spring Boot services, TypeScript applications, real-time communication, databases, and cloud deployments. i like owning the whole problem: understanding it, choosing the right trade-offs, shipping it, and keeping it working.
i'm not particularly loyal to frameworks. the problem comes first; the tools follow.
3rd dan black belt in taekwondo.
the discipline carries over.
selected things i've worked on professionally. these are company projects, not personal open-source work.
building backend services for a social food discovery platform: real-time messaging, asynchronous media processing, subscriptions, and cloud-native deployments. also contributed to rezfinders , a Next.js and Go web product.
owned architecture and development of XMS, a venue management platform connecting web apps, backend services, and MQTT-based kiosks. also worked on real-time unmanned vessel control, industrial IoT monitoring, and production web deployments.
leading technical recruitment for the software engineering track and mentoring engineers through architecture, code quality, CI/CD, and real-world product development.
side projects born from specific problems, not from a need to fill a portfolio.
break your api before your users do.
a Rust CLI for HTTP load testing, with constant traffic, ramps, spikes, and limit-finding runs. reports latency percentiles, throughput, and error rates; works in a terminal or CI.
a workaround built for the pi on my desk.
a C-based SOCKS5 proxy that fragments TLS ClientHello messages to work around basic SNI-based filtering, alongside DNS resolution safeguards. built for Raspberry Pi OS when available tools didn't fit.
talk is cheap. show me the code.
simplicity is prerequisite for reliability.
programs must be written for people to read, and only incidentally for machines to execute.
$ find me elsewhere