Systems project
Raytracer
C++17 OOP raytracer. Primitives and lights as runtime plugins (.so), scenes in libconfig, Google Test suite.
C++17
Plugins
libconfig
Google Test
Makefile
Karma makes useful things
Karma — I make computers do unreasonably useful things
Low-level C++, a Proxmox rack that stays up, and tools that leave the prototype stage. The background is my C++ raytracer — rendering live. Move your mouse to steer the lights.
RENDERING…
TILES —/— · 0 SPP · STATIC
GLSL PORT OF MY C++ RAYTRACER
Selected mischief
Things that escaped the idea folder.
Scroll the stage — it pins under the header while projects step. Or tap a chip.
Under the hood
One lab. A lot of moving parts.
Scroll the console — it pins under the header while parts step. Or tap a blob.
Pinned — scroll to step
Compute / active
Proxmox is the foundation.
The main host runs isolated workloads as LXCs and VMs, keeping services independent without turning the lab into a maze.
- Proxmox
- Linux
- LXC / VM
Tools currently making noise
RustCC++PythonDartTypeScriptJavaScriptReactFlutterNext.jsTailwind CSSHTMLCSSFlaskPlaywrightAnsible
How my brain works
About
Curious enough to break it. Patient enough to fix it. Three rules that keep the experiments useful.
01
Own the failure path.
The useful question is not whether a system can run. It is whether I can explain, observe, and recover it when it stops.
02
Automate the second time.
One manual pass teaches the shape of the problem. Repetition is a signal that the process deserves code.
03
Ship observable work.
Tests, health checks, logs, and real output turn an implementation into something other people can trust.
- Forgejo repos
- 15
- Base
- Lyon, FR
- Focus
- Systems & homelab
- Status
- Open to work
Your move
Say hi.
Bring me the idea that keeps interrupting your sleep — an infra knot, a useful tool, or something too odd for a job title.