01
Currently building
Lumma.
Software, systems.
Curiosity without shortcuts.
I'm Lumma. I write code, poke around inside systems more than is probably necessary, and spend a lot of my free time learning how software actually works once you get past the parts that are meant to be seen.
$ whoami
lumma
$ ls interests
codingcybersecurity linuxnetworking systems
$ status
building_
About
Curious by default.
I got into programming the normal way — by wanting to build one specific thing, then getting distracted by everything underneath it. That distraction never really stopped. These days it's turned into a general interest in operating systems, networking, Linux, and cybersecurity, on top of the actual software I set out to build in the first place.
I like knowing why something works, not just that it works. That means I spend a fair amount of time in the terminal, reading source instead of docs when the docs run out, and rebuilding things I already have working versions of, just to understand them properly. It's a slower way to learn. It also tends to stick.
01
Build
Turn ideas into working software.
02
Analyze
Understand how systems and software behave.
03
Learn
Explore unfamiliar technologies and concepts.
What I know
Tools I actually reach for.
No made-up percentages here — just what I'm comfortable with, what I use regularly, and what I'm still figuring out.
C++
ComfortableNative programming, performance work, and getting closer to how the machine actually sees things.
C
ComfortableWhere I go when I want to understand memory instead of trusting it.
Python
ComfortableAutomation, scripting, quick APIs, and most of my tooling.
JavaScript
Working withFrontend logic and small tools, this site included.
Go
Working withCommand-line tools and small, lightweight services.
C#
LearningNew territory for me — working through it one small project at a time.
Bash
ComfortableMost of what I do day-to-day starts and ends in a shell.
HTML
ComfortableStructure first, always. This whole site is hand-built on it.
CSS
ComfortableI'd rather write it by hand than fight a framework's defaults.
Linux
ComfortableTerminal workflows, system configuration, and a lot of trial and error.
Git
ComfortableBranches, rebases, and the occasional reflog rescue.
Docker
Working withMostly for spinning up isolated environments and labs.
Cybersecurity
Learning how things break.
I got into security the same way I get into most things — by wanting to understand what's actually happening under a system, not just what it's supposed to do. That's led me toward networking fundamentals, Linux internals, and the basics of how software gets analyzed and defended.
Right now that mostly looks like reading, running things in isolated VMs so I can't break anything that matters, and slowly working through the fundamentals: how traffic actually moves across a network, what malware analysis looks like at a conceptual level, some early reverse engineering, and defensive security practices in general. I'm early in this, and I'm fine saying that.
- Security fundamentals
- Networking
- Linux & system internals
- Malware analysis concepts
- Defensive security
- Reverse engineering concepts
- Isolated labs & virtual machines
$ ip -brief addr
eth0 UP 10.0.13.4/24
$ nmap -sV 10.0.13.0/24
scanning host range...
22/tcp open ssh
80/tcp open http
$ tail -f auth.log
watching for anomalies_
Projects
Some of what I've built.
A few things worth showing. Placeholders for now — swap in your real work.
Progress, not resume
Currently learning.
No professional roles to list yet, so here's the honest version — what I've been working through, in roughly the order I picked it up.
Programming
Where it started. Still where most of my time goes.
Linux & systems
Moved off the beaten path and started actually configuring things myself.
Networking
Learning how machines actually talk to each other, not just that they do.
Cybersecurity
The current focus — fundamentals first, tools second.
Low-level concepts
What I'm chipping away at right now, slowly and on purpose.
“The interesting part isn't just using technology.
It's understanding what happens underneath.”
Contact
Let's build something interesting.
Best way to reach me is email — I check it far more than anything else here.