Skip to content
View teyfix's full-sized avatar
  • Istanbul, Turkey
  • 14:30 (UTC +03:00)
  • LinkedIn in/teyfik

Block or report teyfix

Block user

Prevent this user from interacting with your repositories and sending you notifications. Learn more about blocking users.

You must be logged in to block users.

Maximum 250 characters. Please don't include any personal information such as legal names or email addresses. Markdown supported. This note will be visible to only you.
Report abuse

Contact GitHub support about this user’s behavior. Learn more about reporting abuse.

Report abuse
teyfix/README.md

Hi, I’m Halil 👋

Expand Table of Contents

Table of Contents

Senior Full-Stack Engineer · Systems Architect · Performance Nerd

I build high-scale, performance-critical systems that stay boring in production.
10+ years of experience designing and shipping cloud platforms used by hundreds of thousands of users across multiple regions.

My work usually lives at the intersection of backend systems, data, and infrastructure—with enough frontend fluency to keep products fast and humane.

🧠 What I Focus On

Distributed systems & data pipelines

High-throughput ingestion, event-driven architectures, batching, deduplication, and cost-aware scaling.

Performance engineering

Turning 10-second queries into sub-200ms paths. Measuring first, fixing second, bragging never.

Production reliability

Zero-data-loss pipelines, idempotency, graceful degradation, and observability-first design.

Pragmatic architecture

Choosing the right tool, not the fashionable one. PostgreSQL + ClickHouse beats magic every time.

🛠 Tech I Use Daily

Languages

TypeScript, JavaScript, SQL, Node.js, Lua, Python

Backend & Data

Node.js, Bun, NestJS, Kafka, PostgreSQL, TimescaleDB, ClickHouse, Redis, MongoDB

Frontend

React, Next.js, TypeScript, TailwindCSS, shadcn/ui

Infrastructure

AWS, GCP, Docker, Kubernetes, Terraform, GitHub Actions, Rancher, Traefik

Patterns & Practices

Event-driven architecture, microservices, batching, schema validation, CI/CD, TDD

🧭 How I Think About Engineering

  • Make the database do the work
  • Measure before optimizing
  • Prefer boring, explainable systems
  • Build tooling that helps the next engineer
  • Optimize for long-term operability, not short-term cleverness

I care deeply about systems behaving correctly under pressure—even if users never know my name.

📚 Background

I started programming at age 9 trying (and failing) to build games.
I never stopped being curious about how things work, only the scale got bigger.

Over time, I’ve worked across frontend, backend, and infrastructure—which helps me design systems that are both technically sound and practical to maintain.

Lately, I’ve been especially interested in AI-assisted systems, embeddings, and data-driven product behavior—where correctness and scale really matter.

📬 Get in Touch

I enjoy building systems that stay quiet at 3 a.m. That’s usually a good sign.

Pinned Loading

  1. postgres postgres Public

    Daily PostgreSQL builds including TimescaleDB with PGRX extensions including Supabase Wrappers (ClickHouse FDW)

    Dockerfile

  2. traefik traefik Public

    Local HTTPS development environment using Traefik reverse proxy and Step CA for automatic TLS certificate management via ACME

    2

  3. rancher rancher Public

    Automated k3s install with Rancher

    Shell 1

  4. next-template next-template Public

    Next.js App Router starter template with localization, theming, React Query, and dashboard layout for quick project bootstrapping.

    TypeScript

  5. nats-docker-compose-recipe nats-docker-compose-recipe Public

    Docker Compose recipe for running NATS with JWT authentication, NSC bootstrap, JetStream, and WebSocket support.

    TypeScript