muozez@systems:~$whoami

_

Muhammet Yılmaz - Mechanical Engineering Student & Cloud/DevOps Enthusiast. Transforming coffee into code and distributed systems.

GitHubLinkedInBuild in Public
scroll

./about

My primary language is JavaScript/TypeScript, but I speak fluent Bash. Currently bridging the gap between Mechanical Engineering and Cloud Architecture.

I build complex systems primarily to learn how spectacularly they can fail. Nothing teaches you quite like a production incident at 3 AM when you're the only one awake.

Background

Previously co-founded a startup (Bakbul), now fully focused on mastering Cloud Native technologies and finishing my engineering degree.

Focus Areas

Cloud Architecture
DevOps
Microservices

Philosophy

Systems ThinkingLearn by Breaking
$cat current_status.txt

Education: Mechanical Engineering Student

Focus: Cloud/DevOps Engineering

Status: Building & Learning

./projects

A collection of things I've built, broken, and occasionally fixed. One showcase project, one spectacular learning experience (read: failure).

Oturum

Polyglot Microservices Event Management System

Showcase Project

A complex event management platform architected as microservices to handle high concurrency. It's not just a monolith; it's a distributed system designed to scale.

Architecture

Auth Service
Python
Identity & Security
Session Service
TypeScript
Event Logic
Attendee Service
TypeScript
User Management
Admin Dashboard
TypeScript
Frontend Control
Honest Take

This is where I apply everything I've learned about distributed systems. Each service has a purpose, a language best suited for it, and clear boundaries.

Node.jsBunTypeScriptPythonDockerRedisPostgreSQL

What I Learned

  • >Polyglot architectures require strict API contracts
  • >Service boundaries matter more than language choice
  • >Docker Compose is your best friend in development
Source

EnvZilla

Ephemeral Preview Environments (Post-Mortem)

Post-Mortem Mode

Wanting to solve 'works on my machine', I created a monster. Mixed logic, infra, and networking into a monolithic soup. Lesson learned: KISS is king.

Honest Take

The irony wasn't lost on me. The prototype could spin up environments, but the setup was so complex only I could operate it. A humbling experience.

GoDockerMakefiles

What I Learned

  • >Separation of concerns isn't optional
  • >Document as you build, not after
  • >MVP means minimal, not maximally complex
// archived

./tech-stack

The tools I use to transform caffeine into distributed systems (and occasionally working code).

$ls~/daily-drivers
TypeScriptPythonNode.jsBash Scripting
$ls~/infrastructure-cloud
DockerKubernetesTerraformHelmNginxLinux
$ls~/learning-exploring
AWSGolangIstio
$ls~/data
PostgreSQLRedisMongoDB
$which editor
vim// and yes, I can exit it

./contact

Want to discuss why your microservices are secretly a distributed monolith, or swap 3 AM debugging war stories? Let's connect.

Email

muhammetylmaz128@gmail.com

GitHub

@muozez

LinkedIn

muozez

YouTube

Build in Public

$ echo "Let's build something that doesn't break"