Mohamed Badr Elwardi

I'm Mohamed Badr Elwardi — a software engineer who builds systems-level software and modern web applications. My work sits at the intersection of low-level computing and full-stack development, and I spend most of my time thinking about how things actually work under the hood.

I'm drawn to complexity. Not complexity for its own sake, but the kind that forces you to understand computing from first principles — memory, processes, networking, architecture. That foundation shapes how I write every line of code.

I started with C. Not frameworks, not tutorials — raw C, pointers, memory management, and algorithms. Learning to reason about what happens at the hardware level before ever touching a high-level abstraction gave me a perspective most developers don't get early on.

From there I moved into C++ and system architecture, then expanded into backend and web systems. The path wasn't linear, but it was deliberate — each step built on a real understanding of what came before it.

I'm most engaged when working on things that are technically demanding. Custom HTTP servers, real-time systems, backend infrastructure, performance-sensitive software — problems where the implementation details actually matter.

Some things I've built: an HTTP server from scratch, a raycasting engine, C libraries, systems handling CGI execution and request parsing. I've also worked on full-stack web applications and automation tooling. The common thread is building from the ground up rather than relying on black boxes.

Algorithms and data structures, systems programming, networking fundamentals, server architecture, low-level memory management, performance optimization. These aren't just things I've studied — they're areas I actively explore and apply.

I find that the engineers who build the most reliable software are usually the ones who understand what's happening a few layers below their code. That's the standard I hold myself to.

When I learn something new, I implement it myself. Reading about how an HTTP server works is useful. Building one teaches you everything the documentation leaves out.

I write clean, deliberate code. I break complex problems into well-understood components. I don't reach for a library until I understand what the library is doing — and sometimes I just write it myself.

Right now I'm deepening my C++ knowledge, studying advanced algorithms, and continuing to build backend systems. I'm also exploring performance optimization at the systems level — profiling, bottlenecks, and the decisions that make software fast.

I'm always working on something that pushes my understanding further. That's the point.