LeakLens
Your Valgrind log,
untangled.
- Valgrind
- Memory debugging
- Browser-based analysis
Inspect a log. Follow the stack. Compare runs. ↗
Hello! I’m
My background connects mathematics and computer science with hands-on software development. At 1337, I learn through projects, peer review and collaborative work.
I’ve worked on parsing, processes, memory management and containerized services. I’m looking for opportunities to apply that foundation, keep learning and contribute to a team.
Software Engineering Program
Degree in Mathematics and Computer Science
C · C++ · Python · Docker · Git · Valgrind
Arabic · English · French
42 projects and independent developer tools.
Your Valgrind log,
untangled.
Inspect a log. Follow the stack. Compare runs. ↗
A closer look at what happens
after you press Enter.
Command execution, built-ins, quoting, environment variables, pipes, redirections and signals. The project also includes memory checks with Valgrind.
hamza $ ls -l | grep ".c" > files.txt
A sample pipeline, from input to execution.
Separate services.
A working whole.
Custom Dockerfiles, an isolated bridge network, persistent volumes and Docker Secrets. The repository also includes Redis caching, Adminer and a static showcase site.
Click a service to inspect its ports and storage.
Small, interactive models of systems ideas.
Enter numbers. Watch two stacks turn a constraint into a sorted result.
JavaScript minimum-first model using valid stack operations. The C repository uses a cost-based strategy; these move counts are separate.
See the C implementation and measured benchmark →Shared forks, competing workers. Change the timings and watch starvation emerge.
Deterministic JavaScript simulation with atomic two-fork acquisition. It illustrates contention; the C project uses real threads and mutexes.
Read the concurrency study →I’d like to hear about C/C++ and systems engineering roles and internships.
LinkedIn