[{"content":"","date":null,"permalink":"https://etoile-bleu.github.io/matheo-blog/tags/at7-systeme/","section":"Tags","summary":"","title":"At7-Systeme"},{"content":"","date":"16 July 2026","permalink":"https://etoile-bleu.github.io/matheo-blog/posts/mensung-drug-interaction-checker/","section":"Posts","summary":"","title":"Checking drug interactions in places where the internet barely exists"},{"content":"","date":null,"permalink":"https://etoile-bleu.github.io/matheo-blog/tags/healthcare/","section":"Tags","summary":"","title":"Healthcare"},{"content":"I\u0026rsquo;m looking for a part-time developer role: two days a week, Thursdays and Fridays, September 13th 2026 through March 1st 2027. It\u0026rsquo;s built into third year at Epitech on purpose, so it\u0026rsquo;s a real structured commitment, not a maybe.\nI\u0026rsquo;m Mathéo. I build practical software that solves real problems, usually the systems and backend parts other people skip. If that\u0026rsquo;s what you need two days a week, reach out at matheo.delbarre@epitech.eu.\nAside from software development, I enjoy playing chess.\n","date":null,"permalink":"https://etoile-bleu.github.io/matheo-blog/","section":"Home","summary":"","title":"Home"},{"content":"","date":null,"permalink":"https://etoile-bleu.github.io/matheo-blog/tags/internship/","section":"Tags","summary":"","title":"Internship"},{"content":"","date":null,"permalink":"https://etoile-bleu.github.io/matheo-blog/tags/legacy-systems/","section":"Tags","summary":"","title":"Legacy-Systems"},{"content":"","date":null,"permalink":"https://etoile-bleu.github.io/matheo-blog/tags/mensung/","section":"Tags","summary":"","title":"Mensung"},{"content":"","date":null,"permalink":"https://etoile-bleu.github.io/matheo-blog/tags/open-source/","section":"Tags","summary":"","title":"Open-Source"},{"content":"","date":null,"permalink":"https://etoile-bleu.github.io/matheo-blog/tags/philosophy/","section":"Tags","summary":"","title":"Philosophy"},{"content":"","date":null,"permalink":"https://etoile-bleu.github.io/matheo-blog/posts/","section":"Posts","summary":"","title":"Posts"},{"content":"","date":null,"permalink":"https://etoile-bleu.github.io/matheo-blog/tags/react/","section":"Tags","summary":"","title":"React"},{"content":"","date":null,"permalink":"https://etoile-bleu.github.io/matheo-blog/tags/rust/","section":"Tags","summary":"","title":"Rust"},{"content":"","date":null,"permalink":"https://etoile-bleu.github.io/matheo-blog/tags/","section":"Tags","summary":"","title":"Tags"},{"content":"Here\u0026rsquo;s the constraint that started the whole project. AT7 Système, where I interned from August to December 2025, does industrial automation work, a lot of it on TotalEnergies\u0026rsquo; Carling petrochemical site. That site locks down every machine technicians touch. No unauthorized software installs, full stop. But TotalEnergies also requires intervention reports to be filed the same day, especially if something went wrong. AT7\u0026rsquo;s own internal software, the one that actually generates those reports, couldn\u0026rsquo;t be installed on-site. So for years, reports got written whenever the team made it back to a computer that could run it. Sometimes that was hours later. Sometimes it wasn\u0026rsquo;t the same day at all.\nMy mission was to fix that gap with a website. No install, works in whatever browser is already on the machine, same reports, same PDFs, generated on the spot.\nWhat actually shipped #It grew past the original scope pretty fast. By the end it covered intervention reports, a dashboard, timesheets, on-call schedules, leave requests, all pulling from the same data their 25-year-old internal tool already managed. Built in React, talking to a Node API, deployed as an actual replacement piece of their daily workflow, not a prototype that lives in a demo folder.\nThen we turned it on for real #It worked fine in testing, one or two people clicking around. Then we let the whole team use it at once, and the latency became unbearable. Click a button, wait. Submit a form, wait longer.\nThe cause took a while to track down. Their real data lives in an HFSQL database that only speaks the language of WinDev and WebDev, the proprietary stack AT7\u0026rsquo;s internal software was built on. My React app doesn\u0026rsquo;t speak that language either, so every request had to go through AT7\u0026rsquo;s existing WebDev API layer as a translator. And that translator, it turned out, had a hard concurrency cap. Not a technical limit. A deliberate one, the kind vendors set so you eventually pay to have it lifted. Fine when one or two people are testing. A wall the moment a whole team relies on it.\nTwo wrong answers before the right one #I needed a way to reach that database that didn\u0026rsquo;t go through the throttled translator.\nFirst attempt: ODBC, a generic database connector. It handled binary data cleanly, which mattered because report attachments and generated PDFs are binary. But it mangled every accented character. É, è, à, all garbled. Unacceptable when every report is written in French.\nSecond attempt: OLE DB. Handled French text perfectly. Fell over on binary data, the exact thing ODBC had been good at.\nThe answer was neither on its own. ODBC for binary, OLE DB for text, both wired together with small VBS scripts doing the handoff between them. Ugly on paper. In practice, the latency problem disappeared, and the site went from barely usable to something the team could run all day without noticing it was there, which is the actual goal of any internal tool.\nWhat I actually learned #Not React. I already knew React going in. What I didn\u0026rsquo;t know: how to sit across from two people, Christophe Fröliger and Lionel Sutkowski, who understood their 25-year-old system down to its edge cases but had never built a modern web app, and turn their explanations into something I could actually implement. A lot of the job was translation in both directions, not just between ODBC and OLE DB.\nI also had to prioritize hard. Five months sounds like a lot until you\u0026rsquo;re facing a system that\u0026rsquo;s been accumulating features for two decades. I used a rough 80/20 cut: reports and PDF generation first, because that\u0026rsquo;s the piece with a real compliance deadline attached, and the rest could follow once that actually worked.\nChristophe and Lionel gave me a lot of room to make real decisions, not just write code to a spec. That trust is the part of the internship I think about the most. It\u0026rsquo;s one thing to be told what to build. It\u0026rsquo;s another to be handed a real constraint and asked what you\u0026rsquo;d do about it.\nWhy this matters more than my side projects, honestly #ZamSync and MenSung are mine from the first line. I chose the architecture, I chose the constraints, nobody was depending on them before I shipped anything. AT7 was different. The database existed before me and will exist after me. The users were real people who needed their reports filed on time, not a demo audience. I didn\u0026rsquo;t get to pick the stack, the legacy quirks, or the vendor\u0026rsquo;s throttling.\nMost software running in the world looks more like AT7\u0026rsquo;s than like a greenfield side project. I\u0026rsquo;m glad the first real system I touched taught me that early.\n","date":"16 July 2026","permalink":"https://etoile-bleu.github.io/matheo-blog/posts/at7-systeme-internship/","section":"Posts","summary":"","title":"Their API was throttled on purpose, and I had to route around it"},{"content":"Picture a district hospital in Bhutan. Not a photo, not a headline. A real room, mountain light through a window nobody\u0026rsquo;s gotten around to washing, a nurse glancing at a screen that already knows what happened to a patient two valleys away, because the sync just went through, quietly, the way it\u0026rsquo;s supposed to. Nobody in that room is thinking about the code. That\u0026rsquo;s the whole point of writing it.\nI don\u0026rsquo;t know if that room exists yet. But I think about it more than almost anything else I\u0026rsquo;m building.\nI have two dreams. I\u0026rsquo;ve mentioned pieces of them before, in passing, tucked into the end of other posts, like I was a little embarrassed to say them plainly. I\u0026rsquo;m going to say them plainly now.\nThe first: ZamSync, but real #Right now, ZamSync is a project. A repository, 39 stars, a handful of pull requests, a demo I can run on my own laptop that proves it survives a cut connection and a dead battery. That\u0026rsquo;s not nothing. It\u0026rsquo;s just not the thing.\nThe thing is Bhutan\u0026rsquo;s Ministry of Health running ZamSync, or whatever ZamSync has become by then, as actual infrastructure. Not a pitch deck. Not a pilot that quietly dies once the grant money runs out. A real district hospital, a real Basic Health Unit up in the mountains, syncing real patient records over a real 2G link that drops every few hours, and it just working, the way it\u0026rsquo;s supposed to, because I built it to survive exactly that.\nI have no idea how a 19-year-old student gets a meeting with a Ministry of Health. I don\u0026rsquo;t have a plan for that part yet. I have working software and I\u0026rsquo;m not going anywhere.\nThe second: one roof, not two repositories #Right now, ZamSync and MenSung live in two separate places under my GitHub account, connected by nothing official, just the fact that I wrote both and keep repeating the same sentence about why.\nI want them under one roof. Not for the branding, though I won\u0026rsquo;t pretend a real name and a real identity isn\u0026rsquo;t appealing. For the discipline of it. An organization forces you to decide what belongs and what doesn\u0026rsquo;t, what the mission actually is, who else gets to build inside it. Right now that mission lives in my head and in a handful of blog posts. I want it to live somewhere that outlasts me getting busy, or distracted, or discouraged on a bad week.\nI haven\u0026rsquo;t landed on a name yet. I\u0026rsquo;d rather take the time and get it right than rush it and have to explain a rename later.\nWhy I\u0026rsquo;m saying this here #I dream about the hospital room where nobody thinks about my code. I dream about an organization that keeps building this kind of thing long after I\u0026rsquo;ve graduated, long after anyone remembers who wrote the first commit.\nNeither of these is guaranteed. Most dreams like this don\u0026rsquo;t happen the way you pictured them, if they happen at all. But I\u0026rsquo;d rather write it down and be wrong in public than keep it vague and safe in my head.\nThat\u0026rsquo;s the whole post. Not a plan. A direction, said out loud, so I have to mean it.\n","date":"16 July 2026","permalink":"https://etoile-bleu.github.io/matheo-blog/posts/two-dreams-i-havent-said-out-loud/","section":"Posts","summary":"","title":"Two dreams I haven't said out loud until now"},{"content":"I have one rule for what I build.\nIt has to be for someone who cannot buy their way out of the problem.\nNot \u0026ldquo;underserved.\u0026rdquo; Not \u0026ldquo;emerging markets.\u0026rdquo; A person. A nurse in a district clinic with no signal. A worker in a field hospital with no internet. A patient whose record just disappeared because the connection dropped mid-transfer, again.\nIf a company with money could already fix it, I don\u0026rsquo;t need to be there. Plenty of smart people are chasing those problems, and they\u0026rsquo;re better funded than I am. I want the empty corner of the map. The one with no market at the end of it. Just a person.\nWhere the rule came from #I didn\u0026rsquo;t choose this on purpose. I read, almost by accident, about a hospital in Bhutan that switched on a new patient records system and watched it fall over on day one. Not because anyone did anything wrong. Because the network genuinely could not carry the load, and nobody had built the system to survive that.\nI couldn\u0026rsquo;t stop thinking about it.\nSo I built ZamSync. A sync engine for clinics that lose their connection for hours, sometimes days, and lose power in the middle of a transfer without warning. Then I went looking for what else breaks in the same kind of place, and I found the next thing almost immediately: a nurse holding two drug names and no way to check if they\u0026rsquo;re safe together, because the tool for that lives on a website, and the website needs a connection she doesn\u0026rsquo;t have. So I built MenSung.\nNeither of these started as a business idea. They started as a sentence I read that I couldn\u0026rsquo;t put down.\nWhat \u0026ldquo;real\u0026rdquo; means to me #I get asked, sometimes, why I don\u0026rsquo;t build something more useful. Something more people would use.\nHere\u0026rsquo;s the test I actually apply. The people affected can\u0026rsquo;t just buy a commercial fix. The tools that exist are the wrong size, the wrong price, or built for a context that isn\u0026rsquo;t theirs. And the constraint is physical, not preference: no internet, no power, old hardware, a place too small or too poor to count as a market.\nThat last part matters most. \u0026ldquo;Not a market\u0026rdquo; is exactly why nobody else is building it. It is also exactly why I want to.\nThe part I\u0026rsquo;m less sure about #I\u0026rsquo;m not a great marketer. I\u0026rsquo;ve said that before and it\u0026rsquo;s still true. I don\u0026rsquo;t have a growth strategy. I have a GitHub account and an honest description of a problem, and so far, that has been enough.\nWhat keeps me going isn\u0026rsquo;t the stars, although the stars are nice. It\u0026rsquo;s the one message from a stranger who read about a clinic in the Himalayas he will probably never visit, and took thirty seconds to say the problem was real. I didn\u0026rsquo;t build ZamSync for him. But he\u0026rsquo;s the reason I kept building it on the nights I wanted to stop.\nThat\u0026rsquo;s the whole manifesto, really. Find the person the market forgot. Build the thing they actually need, not the thing that\u0026rsquo;s fun to build. Be honest about why. Everything else is details.\n","date":"16 July 2026","permalink":"https://etoile-bleu.github.io/matheo-blog/posts/why-i-only-build-for-people-who-need-it/","section":"Posts","summary":"","title":"Why I only build for people who actually need it"},{"content":"","date":null,"permalink":"https://etoile-bleu.github.io/matheo-blog/tags/zamsync/","section":"Tags","summary":"","title":"Zamsync"},{"content":"","date":null,"permalink":"https://etoile-bleu.github.io/matheo-blog/tags/meta/","section":"Tags","summary":"","title":"Meta"},{"content":"This is the beginning. This space is where I put into writing ideas that have been floating around in my head for too long.\nWhy a blog? #There is something particular about the act of writing. Not just to communicate, but to clarify. When you write, you discover what you actually think: vague ideas take shape, contradictions surface, gaps in reasoning become visible.\nThis blog isn\u0026rsquo;t here to impress anyone. It\u0026rsquo;s a thinking tool, public by choice.\nWhat I intend to explore #A few topics I\u0026rsquo;m interested in right now:\nWeb development: tools, patterns, what actually works in production Software architecture: how big decisions shape the long-term evolution of a project Hugo and static site generators: this blog runs on Hugo, and I find the approach genuinely compelling A note on format #I\u0026rsquo;ll aim for short, dense posts rather than exhaustive essays. If a topic deserves more depth, it probably deserves multiple posts.\nMore soon.\n","date":"24 June 2026","permalink":"https://etoile-bleu.github.io/matheo-blog/posts/welcome/","section":"Posts","summary":"","title":"Welcome to my blog"},{"content":"","date":null,"permalink":"https://etoile-bleu.github.io/matheo-blog/tags/writing/","section":"Tags","summary":"","title":"Writing"},{"content":"","date":null,"permalink":"https://etoile-bleu.github.io/matheo-blog/tags/building/","section":"Tags","summary":"","title":"Building"},{"content":"","date":null,"permalink":"https://etoile-bleu.github.io/matheo-blog/tags/indie/","section":"Tags","summary":"","title":"Indie"},{"content":"","date":null,"permalink":"https://etoile-bleu.github.io/matheo-blog/tags/product/","section":"Tags","summary":"","title":"Product"},{"content":"","date":"23 June 2026","permalink":"https://etoile-bleu.github.io/matheo-blog/posts/building-for-people-who-need-it/","section":"Posts","summary":"","title":"Show us what you're building: for people who actually need it"},{"content":"","date":"21 June 2026","permalink":"https://etoile-bleu.github.io/matheo-blog/posts/39-stars-first-contributor/","section":"Posts","summary":"","title":"39 stars, my first open source contributor, and a message I keep re-reading"},{"content":"","date":null,"permalink":"https://etoile-bleu.github.io/matheo-blog/tags/community/","section":"Tags","summary":"","title":"Community"},{"content":"","date":null,"permalink":"https://etoile-bleu.github.io/matheo-blog/tags/hugo/","section":"Tags","summary":"","title":"Hugo"},{"content":"","date":null,"permalink":"https://etoile-bleu.github.io/matheo-blog/tags/tools/","section":"Tags","summary":"","title":"Tools"},{"content":"","date":null,"permalink":"https://etoile-bleu.github.io/matheo-blog/tags/web/","section":"Tags","summary":"","title":"Web"},{"content":"Hugo is often described as the world\u0026rsquo;s fastest static site generator. That\u0026rsquo;s a marketing claim, but it rests on something real: Hugo is written in Go, and it compiles thousands of pages in seconds.\nThe static site landscape #The ecosystem has fragmented. Jekyll, Hugo, Gatsby, Eleventy, Astro, Next.js in export mode, each with its own philosophy.\nMy conclusion after trying several of them: complexity is the enemy of content. If the generator demands more attention than the articles, something is wrong.\nHugo has a steep initial learning curve. Go templates are disorienting at first, but once you understand the core concepts (layouts, front matter, taxonomies), everything fits together coherently.\nWhat I like about it #Speed. A hugo server that reloads in milliseconds is a daily pleasure.\nTaxonomies. Tags, categories, and other classifications are first-class citizens. No plugins required.\nSelf-contained. No Node.js, no node_modules. One Go binary, a directory of Markdown files, and that\u0026rsquo;s it.\nPortability. The output is plain HTML, CSS, and JavaScript. It will work on any host, forever.\nThe tradeoff #Go templates are verbose. And Hugo has historically moved fast, with breaking changes between major versions. The documentation can lag behind.\nFor a personal blog in 2026, it\u0026rsquo;s still the right call.\nThis blog runs on Hugo 0.163. Source is on GitHub.\n","date":"20 June 2026","permalink":"https://etoile-bleu.github.io/matheo-blog/posts/why-hugo/","section":"Posts","summary":"","title":"Why Hugo"},{"content":"","date":null,"permalink":"https://etoile-bleu.github.io/matheo-blog/tags/engineering/","section":"Tags","summary":"","title":"Engineering"},{"content":"","date":"15 June 2026","permalink":"https://etoile-bleu.github.io/matheo-blog/posts/zamsync-2g-sync-engine/","section":"Posts","summary":"","title":"I built a sync engine for clinics that run on 2G and lose power mid-transfer"},{"content":"Me #Hi there! I\u0026rsquo;m Mathéo, 19, a third-year computer science student at Epitech Nancy, France.\nI build software for places the industry usually skips: clinics with no reliable power, medical workers with no internet, situations where \u0026ldquo;just use the cloud\u0026rdquo; isn\u0026rsquo;t an option. It didn\u0026rsquo;t start as a plan. I read about a hospital in Bhutan whose new patient records system fell over on launch day because the network couldn\u0026rsquo;t take the load, and I couldn\u0026rsquo;t stop thinking about it. So I built ZamSync. Then I kept noticing the same kind of gap elsewhere and built MenSung. I\u0026rsquo;m not a great marketer and I don\u0026rsquo;t pretend to be one, I just try to build the thing and be honest about why.\nI\u0026rsquo;m looking for a part-time position, two days a week (Thursdays and Fridays), from September 13th 2026 through March 1st 2027. It\u0026rsquo;s a structured part of third year at Epitech, not a maybe. If you\u0026rsquo;re building something that matters and want a developer who cares about the whole stack, not just the parts that are fun, I\u0026rsquo;d like to hear from you at matheo.delbarre@epitech.eu.\nDownload my resume (PDF)\nOutside of code, I play chess, slowly, not particularly well, and I can\u0026rsquo;t seem to stop.\nWhat I\u0026rsquo;ve worked on professionally #Five months at AT7 Système (Aug to Dec 2025), porting a 25-year-old internal WinDev system to the web for technicians working on a locked-down industrial site where they couldn\u0026rsquo;t install anything. Real users, a legacy database, a vendor API throttled on purpose, and a same-day compliance deadline that didn\u0026rsquo;t care about any of that.\nRead the write-up: Their API was throttled on purpose, and I had to route around it\nSecurity #Top 5 out of 90 in Epitech\u0026rsquo;s binary exploitation CTF: stack and heap overflows, GOT overwrites, ROP-style chains, reverse engineering against custom challenges. Top 7 out of 149 across campuses on OWASP Juice Shop, 119 challenges solved: XSS, SQLi, broken access control, crypto, business logic flaws.\nWhat I\u0026rsquo;m building #Offline-first software for places where the internet, the hardware, or both, cannot be assumed: ZamSync, a sync engine for clinics in Bhutan that run on 2G and lose power mid-transfer, and MenSung, an offline medication interaction checker for medical workers in war zones, refugee camps, and rural clinics.\nSee the Projects page for demos and write-ups on both.\nThe blog #This is my personal blog where I share thoughts on software engineering, devops, and side projects.\nIt is built with Hugo and the Congo theme.\nContact #Here are the best ways to reach me:\nEmail: matheo.delbarre@epitech.eu GitHub: Etoile-Bleu LinkedIn: Mathéo Delbarre ","date":null,"permalink":"https://etoile-bleu.github.io/matheo-blog/about/","section":"Home","summary":"","title":"About"},{"content":"","date":null,"permalink":"https://etoile-bleu.github.io/matheo-blog/categories/","section":"Categories","summary":"","title":"Categories"},{"content":"Pull requests and issues on other people\u0026rsquo;s projects, not mine. My own stuff is on Projects.\n2026 SasanLabs/VulnerableApp, the OWASP VulnerableApp project. Replaced an insecure Base64-encoded session token with a signed, expiring JWT, plus a test proving tampered tokens get rejected. Then a second PR fixing the SAST scanner\u0026rsquo;s ground-truth mappings so its own vulnerability CSV actually pointed at the right lines.\nrazvandimescu/numa, a Rust DNS resolver. Added CLI toggles for blocking and DNSSEC, with unit tests.\nmmastrac/linktime, link-time initialization macros for Rust. Implemented symbol rooting using .ref assembly directives so it also works on AIX.\nGetting ZamSync in front of people who\u0026rsquo;d never see my repo otherwise: a write-up in This Week in Rust #656, an entry in awesome-rust, a listing on up-for-grabs.net, and entries in five different awesome-lists for local-first, distributed systems, and CRDTs.\nerenworld/technobot, a robotics tournament management system. Recurring contributor: Docker hot reload, a realtime PoC, mandatory API routes, and a handful of real bug fixes (a broken account-linking flow, an observation panel that stopped rendering).\nTinto57/ordalys_public_website, a friend\u0026rsquo;s project, private repo. Built out the admin dashboard, client, quote, and invoice management.\nlingdojo/kana-dojo and Hanzllasoomro/interview-prep-notes, small content contributions.\n2025 Tinto57/murmuresDAntan, a friend\u0026rsquo;s project, private repo. Fixed npm vulnerabilities and updated outdated frontend dependencies.\nAnomalie-Community, a community Garry\u0026rsquo;s Mod military gamemode, private repo. One of the more active contributors for a few weeks that spring.\n","date":null,"permalink":"https://etoile-bleu.github.io/matheo-blog/contributions/","section":"Home","summary":"","title":"Contributions"},{"content":"Last updated: July 2026, from Nancy, France.\nWhat I\u0026rsquo;m building #MenSung, an offline medication interaction checker in Rust for medical workers in war zones, refugee camps, and rural clinics. Just shipped v1.0.\nZamSync, a sync engine written in Rust for district health clinics in Bhutan that run on 2G and lose power mid-transfer, is stable and out in the world with its first outside contributors, which still feels unreal.\nWhat I\u0026rsquo;m studying #Third year at Epitech Nancy. The school is project-based and largely self-directed, which I find both exhausting and exactly right for how I learn.\nFrom September 13th 2026 through March 1st 2027, two days a week (Thursdays and Fridays), I\u0026rsquo;m looking for a part-time position. If you\u0026rsquo;re building something that matters and need a developer who cares about the whole stack, reach out.\nWhat I\u0026rsquo;m reading #Nothing specific right now, mostly technical papers and GitHub issues related to distributed systems and sync protocols.\nWhat I\u0026rsquo;m playing #Chess. Slow games, nothing impressive rating-wise, but I find the thinking process addictive.\nContact #matheo.delbarre@epitech.eu\nThis is a /now page. Inspired by Derek Sivers.\n","date":null,"permalink":"https://etoile-bleu.github.io/matheo-blog/now/","section":"Home","summary":"","title":"Now"},{"content":"Things I built myself, in the order I built them. Contributions to other people\u0026rsquo;s projects are on their own page.\n2026 Two projects I keep coming back to, both offline-first software for places where the internet, the hardware, or both, cannot be assumed.\nZamSync #A sync engine written in Rust for district health clinics in Bhutan that run on 2G and lose power mid-transfer. WAL replication with Hybrid Logical Clocks, Version Vectors, mTLS, and ChaCha20-Poly1305 encryption at rest, under 10 MB of RAM.\nCode: github.com/Etoile-Bleu/ZamSync Read more: Building software for places where the internet barely exists MenSung #An offline medication interaction checker in Rust, built for medical workers in war zones, refugee camps, and rural clinics with no internet access. One static binary, one database file, every lookup fully local.\nCode: github.com/Etoile-Bleu/MenSung Read more: Checking drug interactions in places where the internet barely exists Scriptable mode, two drugs, a known contraindication:\nSame check, a different pair:\nThe interactive terminal interface, looking up a single drug\u0026rsquo;s own facts with Alt+I:\ngenerals-forge #A community dedicated server in Rust, hexagonal architecture, for Command \u0026amp; Conquer: Generals Zero Hour. A twenty year old RTS with a fan base that still wants to play it online.\nCode: github.com/Etoile-Bleu/generals-forge druk-lang #An LLVM-backed compiled language written in C++. Custom front-end, parser, static type system, IR generation pipeline supporting both JIT and AOT execution.\nCode: github.com/Etoile-Bleu/druk-lang 2025 AT7 Système, my internship, five months porting a legacy WinDev system to the web for technicians on a locked-down industrial site. Full write-up.\n2019 GuardMinecraftFR, my first project, ever. I was 13. A Skript script called \u0026ldquo;Guard\u0026rdquo; for a Minecraft server: anti-spam, chat mute and clear, broadcasts, spawn point management. The original README still says, in my own words at the time: \u0026ldquo;Je suis un jeune de 13 ans qui ai fait ce script\u0026rdquo;, I\u0026rsquo;m a 13 year old who made this script. I asked people to email me the bugs they found. I still would.\nOther work #Compilers, raytracers, distributed systems, CTF write-ups, the smaller stuff. All of it is on my GitHub, and the full list with context is on my resume.\n","date":null,"permalink":"https://etoile-bleu.github.io/matheo-blog/projects/","section":"Home","summary":"","title":"Projects"}]