GARDENER / SYSTEM_OPERATOR

Information engineering student in Padova, learning Linux and systems from the inside, in public.

          .
       .      .
    .      .      .
        \  |  /
         \ | /
      --- ( ) ---
         / | \
        /  |  \
    .      .      .
       .      .
          .

      _(_)_                          _(_)_
     (_)@(_)       _(_)_            (_)@(_)
       (_)_(_)    (_)@(_)             (_)_(_)
         |          (_)_(_)             |
      \|/|/           |              \|/|/
   \\\|//|/\\\      \|/|/           \\\|//|/\\\
    ^^^^^^^^^^^  \\\|//|/\\\        ^^^^^^^^^^^
                  ^^^^^^^^^^^

What I'm doing here

This site is part a workbench part a digital garden. Currently I have solid foundations in math and signal processing, I'm at home in a Linux terminal, and navigate any linux system. The interesting work is still ahead of me, and I would rather show that arc as it happens than wait until it looks finished.

The plan, roughly, is to spend the next six to twelve months getting production-competent in the things I actually care about — computational analysis, low-level and systems programming, the tooling adjacent to HPC, embedded work where the constraints push back. I am drawn to code that has modles complex systems and their relationship with agents.

What I work on

Linux as a daily driver and a study object. I run Arch with Hyprland on an HP ProBook 430 with eight gigabytes of RAM. With my old hardware i learned that there cant be room to hide a sloppy script behind, and that pressure has taught me more about resource use than any textbook.

Most of what I learn ends up documented in small tools and configuration notes: notification scripts, status modules, and the kind of plumbing that exists to make an arch server on 1GB RAM alive.

FOSS, on principle. Tool ownership and open infrastructure decide a lot about who gets to think clearly in public, and I would like to keep that decision close to home. So I self-host where I can, run no analytics, and keep things in plain text whenever plain text will hold them.

Notes as a thinking tool. I keep a Zettelkasten-style Obsidian vault for coursework and projects, and the vault has become its own ongoing project. I write while I work because I can't think at the pace of a problem otherwise. The notebook is where the thinking actually happens; the code is what falls out of it.

Build the smallest thing that's honest. Then make it right. Then, if it matters, make it fast.

Outside the terminal

I work part-time at McDonald's, which keeps the abstraction-leak problem grounded in something other than software. There is a particular kind of clarity that comes from finishing a six-hour shift on your feet and then sitting down to debug a kernel module.

Get in touch

I read every message and reply to most of them.