👋 About Me

I'm a self-taught full-stack software engineer and independent developer who enjoys building complete software systems — from frontend interfaces and APIs to databases, infrastructure, networking, and deployment.

My current journey is also taking me deeper into systems programming and infrastructure, with a particular interest in Rust, Linux, networking, concurrency, and distributed systems.

• 💻 Full-Stack Development: Building complete web applications from frontend to backend and infrastructure
• 🧩 Backend Engineering: APIs, services, databases, authentication, background jobs, and integrations
• ⚛️ Frontend Engineering: React, Next.js, and modern TypeScript applications
• 🐘 PHP Development: PHP and Laravel applications and APIs
• 🐍 Python Development: Python and FastAPI for backend services and tooling
• 🦀 Currently Learning: Rust and systems programming
• 🌐 Exploring: Networking, distributed systems, Linux, and infrastructure
• 📦 Open Source: Building and maintaining developer tools and libraries

🧠 My Engineering Direction

I work across multiple layers of software:

┌─────────────────────────────────────┐ │ User Interfaces │ │ React / Next.js / JS │ ├─────────────────────────────────────┤ │ Application Layer │ │ TypeScript / PHP / Python │ ├─────────────────────────────────────┤ │ Backend │ │ Laravel / FastAPI / Node.js / APIs │ ├─────────────────────────────────────┤ │ Infrastructure │ │ Docker / Linux / Deployment │ ├─────────────────────────────────────┤ │ Systems & Networking │ │ Rust / TCP / HTTP / IPC / Protocols │ ├─────────────────────────────────────┤ │ Distributed Architecture │ │ Services / Relays / Concurrency │ └─────────────────────────────────────┘

I enjoy understanding how these layers connect rather than working with any single layer in isolation.

🛠️ Technical Stack

💻 Languages

⚙️ Backend

🐧 Infrastructure & Tooling

🦀 Systems Programming

I'm currently expanding beyond application-level development into lower-level software engineering.

Rust

Currently learning and exploring:

• Ownership & Borrowing
• Memory Safety
• Lifetimes
• Concurrency
• Async Programming
• Networking
• Processes & Threads
• Systems Programming
• Runtime Architecture
• Performance-Oriented Software

🌐 Networking

I'm interested in understanding how systems communicate at the protocol level.

Areas I'm exploring:

• TCP/IP
• UDP
• HTTP/1.1
• HTTP/2
• HTTP/3
• QUIC
• TLS
• DNS
• WebSockets
• Persistent Connections
• NAT Traversal
• Relays
• Proxies
• Client-Server Architecture
• Network Protocols

⚙️ Distributed Systems

I'm exploring architectures where multiple processes, services, and machines communicate as a larger system.

Areas of interest:

• Distributed communication
• Message passing
• Event-driven systems
• Concurrency
• Fault tolerance
• Process supervision
• Service discovery
• Queues & workers
• State management
• Failure recovery
• Horizontal scaling
• Remote execution

🐧 Linux & Systems

Linux is an important part of my deeper engineering journey.

I'm exploring:

• Processes & Threads
• Signals
• IPC
• Filesystems
• Sockets
• Permissions
• System Calls
• Memory Management
• Linux Networking
• Services & Daemons
• Containers
• System Administration

🔓 Open Source

I believe building in public and contributing to open source is one of the best ways to learn real-world software engineering.

My open-source interests include:

• Developer tools
• Web frameworks & libraries
• Systems software
• Networking tools
• Infrastructure
• CLI applications
• Runtime tooling
• Developer productivity

🔬 Current Learning

FULL-STACK ENGINEERING │ ├── Frontend │ ├── React │ └── Next.js │ ├── Backend │ ├── Laravel │ ├── FastAPI │ └── Node.js │ ├── Systems │ └── Rust │ ├── Infrastructure │ ├── Linux │ ├── Docker │ └── Kubernetes │ └── Networking ├── TCP/IP ├── HTTP ├── QUIC └── Distributed Systems

📊 GitHub

🌐 Connect With Me

Building software across the stack — from web applications to systems and infrastructure. ⚙️🦀