Skip to content

Start typing to search

İlker Pehlivan, Network and systems engineer, founder of Serçe Bilişim

İlker Pehlivan

Network and systems engineer, founder of Serçe Bilişim

I run the networks and servers that other people's work depends on. Before founding my own consultancy I administered the backbone network, firewalls and core systems of a large multi-site organisation with thousands of users. I write about the things that actually broke.

What I do

I am a network and systems engineer and the founder of Serçe Bilişim, an IT consultancy. My working days are spent in other people’s server rooms: file servers, directory services, backups, firewalls and the networks underneath all of it.

PingEverything is where I write down what those days teach me.

Where the experience comes from

I did not start in infrastructure. My first job was at an advertising agency, wearing the webmaster, developer and digital marketing hats at the same time. That is where I learned to read what analytics data is actually saying, and that a technically perfect thing nobody can find is worth nothing.

From there I moved to a company building web infrastructure for banks. Fintech has no tolerance for “it usually works”. Under engineers far more senior than I was, I learned what a real architecture looks like from the back, and what engineering discipline means when a mistake has consequences.

The job that shaped this site most came after that: a large multi-site organisation where I started on the helpdesk and ended up as the system and network administrator. Thousands of users, a backbone network, firewalls, and the kind of critical systems where an outage is not a ticket but a building full of people who cannot work.

How I look at a problem

A slow system, a dusty cabinet, a bundle of cables nobody claims: all of them have a history. Somebody made a decision, under some constraint, and the current state is the result. Systems tell you that story if you know how to listen.

That habit is where the name comes from. When something breaks, you do not guess. You check every link in the chain, one at a time, until the broken one shows itself.

It also means I rarely see an incident as one broken machine. When a network drops, I am looking at the database behind it, the tool that stopped reporting, and the person whose work is now stuck, at the same time.

How this site is written

No invented numbers, no invented experience, no rewritten vendor documentation. The full rules, how articles are adapted from Turkish originals and how the site is funded are on the About page.

Articles by this author