Skip to content
View enesyesil's full-sized avatar

Highlights

  • Pro

Organizations

@Fisor-Analytics @young-professionals-canada

Block or report enesyesil

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
enesyesil/README.md

Hello, Friend 👋

Software Engineer — Backend / Platform

Distributed Systems · Cloud · Data Infrastructure · Agentic Workflows

Website

LinkedIn

Email

Profile views


Now

  • Building reliable backend systems with clear contracts, observable execution, and boring-by-design infrastructure
  • Interested in Platform engineering, Software & Cloud architecture, and Agentic automation that stays deterministic where it matters
  • Ship small → Validate → Harden

Building now

These are the projects I’m actively building and iterating on.

  • Design Cockpit — WIP workspace for making product/design decisions and turning them into clean plans.md + implementation contracts.md Repo → design-cockpit

  • Atlas Fabric — It explores whether we can systematically build a usable historical boundary dataset when none publicly exists Repo → atlas-fabric

  • IssueSight — GitHub issue context-bridge (LLM-assisted) to help juniors understand issues faster and reduce back-and-forth
    Repo → issuesight

  • Job Weaver — Go-based job discovery + digest system focused on startup/small-company opportunities
    Repo → job-weaver

  • Backenderer — lightweight deployment platform (infra-as-product) for shipping backends fast and reliably
    Repo → backenderer


How I build (so projects don’t rot)

My default build order:

  1. Interfaces first (APIs, schemas, minimal UI surface)
  2. Execution engine (workers, queues, schedulers)
  3. State + data (Postgres, Redis, object storage, Iceberg)
  4. Observability (metrics, logs, traces)
  5. Hardening (tests, rate limits, failure modes, CI/CD)

This keeps complexity contained and makes refactors survivable.


Tech Stack I actually use

Go TypeScript Next.js Python Postgres Redis Docker AWS Azure Hetzner Dokploy Dokploy Terraform Prometheus Grafana


Stats (lightweight)

Streak


Operating principles

  • I ship small, learn fast, and iterate.
  • Build → test → ship → improve.

Expect prototypes, experiments, and code that probably shouldn’t work (but sometimes does).

Pinned Loading

  1. fisor-builder fisor-builder Public

    A research/data pipeline module. It converts open-ended natural language questions into structured datasets

    Python

  2. iceberg iceberg Public

    Forked from apache/iceberg

    Apache Iceberg

    Java

  3. backenderer backenderer Public

    A lightweight, secure, and decentralized backend deploy kit for students and hobbyists. Deploy your backend app to your own cloud account in seconds - no servers to manage, no SSH needed.

    HCL

  4. docufier docufier Public

    A cross-platform desktop app that lets non-technical documentation maintainers easily create, open, and share portable Markdown-based documents.

    JavaScript

  5. issuesight issuesight Public

    IssueSight ingests GitHub issues and uses LLMs to generate "Context Bridges" from breaking down complex issues into junior-level prerequisites, architectural summaries, and implementation guides.

    Go

  6. ckm ckm Public

    A workload orchestration system I built to understand how kernel scheduling, memory management, and production infrastructure come together in real-world systems.

    Go