I am an independent developer and a computer science student. I work on software, infrastructure, automation and systems, and I publish most of it as open source.
My rule is simple: technology should be accessible. My projects are free to use, can be rebuilt from a clean machine, and are documented well enough for a beginner to follow without guessing.
Current focus: Cloud-Project-K3s, a private cloud lab on a two node K3s cluster.
Every project below is public. Documentation is in English unless stated otherwise. Cloud-Project-K3s, parfum-empire and SQL_Server_project are documented in French.
| Project | Description | Stack |
|---|---|---|
| Cloud-Project-K3s In progress |
A private cloud lab for a fictional company. Two Ubuntu Server virtual machines run a K3s cluster with a helpdesk application and PostgreSQL. The work covers deployment, data persistence, access control, updates, backup and recovery. School project. | K3s Kubernetes PostgreSQL VirtualBox Bash |
| mc-server-template | A GitHub template that sets up a PaperMC Minecraft server in a Codespace: Java 21, the Crafty Controller panel, a Playit.gg tunnel, hourly backups and a startup script. | PaperMC Codespaces Bash |
| Minecraft-Server Guide, scripts pending |
A step by step guide to hosting a free PaperMC server on GitHub Codespaces, available in 8 languages. | PaperMC Codespaces |
| Project | Description | Stack |
|---|---|---|
| verified-by-default | A written workflow for keeping commits made with AI coding assistants signed and shown as Verified on GitHub, whether the agent runs locally or in the cloud. | Git SSH GPG |
| git-signed-commits-windows | A beginner guide to signing Git commits with an SSH key on Windows so that GitHub shows the Verified badge. | Git SSH |
| Jouer-aux-anciens-jeux-Flash | A guide to playing old Flash games without Adobe Flash Player, using the Ruffle emulator on Windows, macOS and Linux. | Ruffle |
| CouteauSuisse Steganography tool in progress |
A Windows console toolkit with a French interface. It converts text to Morse code with audio playback and converts numbers between bases. | C# .NET 9 |
| Project | Description | Stack |
|---|---|---|
| parfum-empire In development |
A 2D management game in the browser. You harvest ingredients, formulate perfumes, sell them and expand a perfume house over several floors. Progress is saved locally, with no accounts or multiplayer yet. | TypeScript Vite Vitest |
| Code_Quest | A console RPG where you fight bugs, malware and hackers by answering computer science questions. Runs on Windows. | C# .NET 8 |
| Project | Description | Stack |
|---|---|---|
| SQL_Server_project | Mission SQL Cinéma, a school project made for an open day. A Flask application on SQL Server offers guided challenges on joins, grouping and date analysis, with a generator aiming for 10 million synthetic bookings. | SQL Server Python Flask |
| chococoa-web | A static chocolate shop website built to practise HTML, CSS and JavaScript without any framework. It includes a shop, news, a quiz, a VIP area and a newsletter page. | HTML CSS JavaScript |
These are the technologies used in the projects above.
| Area | Technologies |
|---|---|
| Languages |           |
| Frameworks and runtimes |      |
| Databases |   |
| Infrastructure and cloud |      |
| Development tools |    |
- Free to use. I prefer tools that do not hide essential features behind a subscription or a trial, and I state costs and limits openly.
- Reproducible. A result should be rebuildable from a clean environment.
- Documented. I explain why a step matters, not only which command to run.
- Honest. Limits, bugs and approaches that failed belong in the documentation too.
- Open source first. Open standards and free and open source tools come first whenever practical.
- Accessible. I do not assume the reader already knows the technology.
Many of my repositories are guides rather than conventional software. Examples are Git SSH signing on Windows, playing Flash games with Ruffle and hosting a Minecraft server on Codespaces. A guide is finished when a beginner can follow it on a clean machine and get the same result.
To get there, each guide aims to:
- Start from a clean machine, or state the exact starting point.
- List prerequisites and link the official downloads.
- Give exact commands together with the expected output.
- Explain each important configuration choice.
- Cover common errors and how to fix them.
- State costs, limits and security implications, and offer free alternatives where practical.
- Stay maintainable as the tools change.
Documentation is part of the project, not an afterthought.
Issues and pull requests are welcome on any of my repositories.
- Report a bug. Open an issue on the repository concerned, with clear steps to reproduce it.
- Suggest an improvement. Explain what could be better and why.
- Request a guide. Open an issue on this repository titled
Guide request: [topic]and describe what you want to accomplish. - Send a fix. Fork the repository, create a branch with
git switch -c fix/short-name, commit with a clear message and open a pull request.
GitHub is the best place to reach me. I keep technical discussions there so that useful answers stay searchable for everyone.
