Network & Security
I decide where the packets go.
From networking and security to virtualization, databases and automation: the tools I use in the engine room of infrastructure.
I decide where the packets go.
From physical to virtual, from virtual to containers.
The goal: replicas in sync, backups tested.
Do it twice, and the third time it becomes a script.
Tool list ≠ project experience: not every tool was used to the same depth. For real-world usage, see the projects page.
Every critical layer is designed with redundancy (HA).
Any operation done manually twice becomes a Bash or PowerShell script the third time.
An untested backup is not a backup (MinIO S3 + automated verification).
Packets go only where they need to go, and only as far as they need to.
AI speeds things up, but responsibility stays with people: generated code and commands are reviewed first, tested next, and only then go live.
prompt → review → test → deploy. The order never changes. Claude writes and refactors, ChatGPT gives a second opinion; a human approves, measures and owns the result.
Between July and October 2026, 19 internal tools were built with Claude Code. Details on the projects page.
İsmail is a technology professional who one day works out from query statistics why PostgreSQL is burning CPU, the next day designs Kubernetes RBAC, another day builds an admin tool in PowerShell, and in between retires unnecessary infrastructure before it is even built by asking "do we really need this?". In his world, a working system is good, an automated system is better, and a secure, documented, automated system is simply how it should be.
Email is the fastest way. If I'm on the road, I'll reply from the next Wi-Fi.