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, focused on C, C++ and systems programming. My projects cover an HTTP server, a shell, an assembly renderer and a small graphics animation engine. I also use Next.js, React and Docker when a project needs a complete web interface and deployment.
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 care about what happens beneath the interface: processes, memory, networking, rendering, performance, and the operational constraints that shape reliable software.
Assembly and C projects where drawing, animation, coordinates and event handling are part of the implementation.
CURRENT FOCUS
I'm looking for my next C/C++ role. Web delivery remains a useful secondary skill, especially for small scoped projects.
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 short full-stack freelance projects when they fit my current focus.