Parantaj
OngoingOwner
A personal and corporate financial management platform. It offers income-expense tracking, budget planning, detailed reporting, and multi-account management.
Polyglot Developer & System Architect
I have been building software since 2008; in recent years my focus is the architecture of high-traffic systems. Here I share the reasoning behind decisions and the lessons drawn from real projects.
In brief
I have been building software since 2008. Today I work as a Staff Engineer at a technology company, designing the microservice and event-driven architecture of high-traffic systems. I work across the PHP, Go, Python and JavaScript ecosystems as a developer who focuses on the problem rather than the language. I act as a technical compass for teams on scalability and maintainability decisions, and in my remaining time I maintain my own SaaS products and open-source projects.
At the center of my interests are scalable system architecture, clean API design and testable code. I enjoy sharing what I learn, contributing to open source, and turning ideas into working products.
Portfolio
A selection of products and projects I build and maintain.
Owner
A personal and corporate financial management platform. It offers income-expense tracking, budget planning, detailed reporting, and multi-account management.
Founder & Developer
BabelQueue is a language-agnostic message queue standard that lets services written in different languages share the same queue without getting trapped by serialization lock-in. Instead of language-specific formats like PHP's serialize(), it defines a strict JSON envelope — frozen at schema_version 1 — that every language can read natively. It runs on Redis and RabbitMQ with no sidecar or broker plugin, adding under 2% overhead.
Founder & Developer
CommitBrief is a provider-agnostic Go CLI tool that performs LLM-powered local code review on git diffs. It reviews any scope — from staged/unstaged changes to a single commit to PR-style three-dot ranges — without leaving the terminal, without leaking the diff, and with customizable project rules.
Career
Highlights from my professional software journey.
Bulutklinik Teknoloji Istanbul, Türkiye
As a Staff Developer, I design Bulutklinik’s high-traffic healthcare platform using microservice and event-driven architecture, serving as the technical compass for critical design decisions. Grounded in domain-driven design, test-driven development, and performance optimization principles, I continuously improve teams’ code quality and delivery speed while aligning product strategy with technology vision. This approach sustainably enhances the platform’s reliability and flexibility.
Bulutklinik Teknoloji Istanbul, Türkiye
As a Senior Developer, I took end-to-end technical ownership of the microservice architecture, automatic scalability, and integration layers of a cloud-based HIS (Hospital Information System) & Telemedicine platform. By re-architecting internal services with secure OAuth 2 flows, I reduced prescription and data synchronization errors by 95% and raised system availability to 99.95%. I also mentored a team of 4–6 people in TDD/DDD and authored a comprehensive code-review guide, shortening the PR feedback loop and significantly expanding test coverage.
Biliver Istanbul, Türkiye
As a Back-end Developer, I managed the real-time query performance and large-scale data processing layers within the core R&D team of a vertical search engine spanning 40M+ documents. While designing the PHP/Python-based pipeline that crawled 1M URLs per hour and seamlessly indexed 5 GB of data daily, the hybrid MySQL-Redis caching layer I built reduced query latency from 1,500 ms to roughly 140 ms. By partitioning the database and cache clusters, I cut the total DB load by 80% and ensured the system’s high availability.
Blog
My latest writing on software, architecture and product development.
The problems we used to solve with JavaScript and preprocessors now have native CSS answers: container queries, :has(), and native nesting.
Two workers produced the same invoice number in production. A log of how I resolved the race condition vs. legal gap dilemma in a real project.
Three months ago I built a tool to audit my own diffs. This post is not about the 'why' but the 'how much': which workflow layers it plugs into, the numbers behind the speedup, the bug patterns it keeps catching — and where it hits its limits.