Code I can come back to
If I have to reopen a project six months later, I want to understand it without a guided tour.
I'm a student at 42. Most of my work is in C and C++: an HTTP server, a shell, an assembly renderer, and a small graphics animation engine. I use Next.js, React and Docker too, mostly when I need to ship something with a real UI.
If I have to reopen a project six months later, I want to understand it without a guided tour.
I start with what the project already has. A new dependency needs to earn its place.
I measure before optimizing. The interesting part is finding the real bottleneck, not guessing at it.
I like understanding what is happening under the UI: processes, memory, sockets, rendering, latency, and the awkward details that make software real.
Small Assembly and C projects where drawing pixels, moving things around and handling events are the actual subject.
CURRENT FOCUS
I'm looking for a C/C++ role. I still like web work, especially when it gives a technical project a usable interface.
SOLO
Assembly renderer
I wrote a Mandelbrot renderer in assembly as a solo project. It was a good excuse to handle the maths, memory and display loop without much hiding underneath.
DUO
C / Shell
A shell built by two people at 42. I worked on turning command lines into an AST, then executing them with behaviour close to a real shell.
TEAM OF 5
Tech lead
The final common-core project at 42, built by a team of five. The README lists me as tech lead, responsible for architecture decisions, the NestJS User Service and frontend work shared with jramiro.
I'm looking for a C/C++ role. I also take on small full-stack freelance projects when the scope is sane and the work fits.