I build the kind of software that has to keep running when nobody is watching it.
Most of my work is monitoring and alerting. A service monitor for a production Linux estate, written against the JDK with no third-party dependency: thirteen protocol-aware checks, an alert engine whose hard part is suppression rather than detection, and ownership resolved from the machine's own Linux groups. It runs as the local monitoring service for that estate at 71 MB resident, 35 OS threads, no swap.
The rest splits between security tooling, wire protocols I would rather implement than import, and tools I actually use. A PostgreSQL client that speaks the frontend/backend protocol directly, SCRAM-SHA-256 included, because taking a driver would have ended the no-dependency claim. An offline client for my school's results portal that implements the evaluation règlement from the official text.
I am a third-year engineering student at ENSAM Meknès, in Electromechanical Engineering, Industrial Digitalization option, which is where the industrial-software half of the degree lives. My most recent internship was at COD Partner, where the monitoring work below was built. Earlier work on SMT production lines and AOI systems is where the defect-analysis dashboard comes from.
Most of what I would want to show is not public, for four separate reasons. Some is covered by a confidentiality agreement: the monitoring work was built inside a company, against its estate, and the configuration alone is a map of an internal network and of who is on call for each part of it. Some is running in production right now, on machines that belong to someone else. Some is a product rather than a demonstration. And a good deal of it I simply use every day, which means it carries my data, my notes and my habits.
So the fair way to judge the private half is by what it does and what it is built from.
An estate of 300 services throws off roughly 20 events a second. A team reads maybe ten messages a day before it starts ignoring the channel, and squeezing the first number down to the second is the whole job. Ownership resolves from the machine's own Linux groups.
Java (JDK only) · systemd · Prometheus · Grafana · Loki · PostgreSQL wire protocol
Not publicA capture-the-flag event end to end: scoring, phase control, per-player DNS accounting, an AI-domain firewall, and the ten challenges that run on it.
Rust · Ratatui · HTTP API · iptables
Not publicOffline CLI for the ENSAM results portal. Local store, watch mode with snapshot diffing, and the evaluation règlement implemented from the official text. One store behind a CLI, an HTTP API, Android and KDE clients.
Python · SQLite · Android · KDE Plasma
SourceDashboard for in-circuit-test defects on an SMT line. Per-component failure rate and reliability, an SPC control chart, heatmaps, and a resolution workflow with live updates.
TypeScript · Next.js · SPC · Charting
SourceThree of them, for Java, Rust and Git. Problem banks, hidden test suites, sandboxed repositories, and progress that survives syncing between two machines.
Java · Rust · Python · PostgreSQL · Git plumbing
Not publicJournal, notes, habit and health tracking, daily reports. State kept as text so two laptops can merge it by union instead of conflicting.
Python · Text-as-database · Syncthing
Not publicOrganises a course calendar into Google Calendar: colour assignment, validation with row numbers, statistics and splitting.
Python · Google Calendar API
SourceA terminal game in C++ that teaches eleven language features, one per room, in French.
C++ · Terminal UI
SourceA free-return lunar flyby in two dimensions. The trajectory is the easy half: the interesting stretch is the one where the Moon sits between the spacecraft and the only antenna that can hear it, so occultation is decided by point-to-line geometry rather than by eye. The model is held against real AROW telemetry and JPL Horizons ephemerides.
Python · Matplotlib · JPL Horizons · Streamlit
SourceJava · Rust · Python · C · C++ · TypeScript
Linux · systemd · Docker · Prometheus · Grafana · Loki
PostgreSQL · SQLite · Wire protocols · Text-as-database
Next.js · React · Tailwind · Node
AOI systems · Computer vision · SPC · Defect classification
Git · Bash · Neovim · LaTeX · Obsidian
Happy to talk about monitoring, systems work, or anything below. Mail is the fastest way to reach me.