$ booting lumma.dev

mounting sections…

ready_

Available for work

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. Right now most of that energy goes into MU — the project below I keep coming back to.

View Projects Contact
lumma@localhost

$ whoami

lumma

$ ls interests

backendcybersecurity linuxnetworking systems

$ status

available, building MU_

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 genuine pull toward backend development, Linux, systems, and security — the layers most people never have to think about, which is exactly why I can't stop thinking about them.

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 — and it's the whole reason a project like MU exists instead of me just using something off the shelf.

~/focus

Backend

APIs, services, the logic underneath the interface.

Systems

How the machine actually runs the code I write.

Security

Learning how things break so I can build them sturdier.

Linux

Daily driver, lab environment, and default assumption.

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.

Languages

09
C++ logo

C++

Comfortable

Native programming, performance work, and getting closer to how the machine actually sees things.

C logo

C

Comfortable

Where I go when I want to understand memory instead of trusting it.

Python logo

Python

Comfortable

Automation, scripting, quick APIs, and most of my tooling.

JavaScript logo

JavaScript

Working with

Frontend logic and small tools, this site included.

Go logo

Go

Working with

Command-line tools and small, lightweight services.

C# logo

C#

Learning

New territory for me — working through it one small project at a time.

Bash logo

Bash

Comfortable

Most of what I do day-to-day starts and ends in a shell.

HTML logo

HTML

Comfortable

Structure first, always. This whole site is hand-built on it.

CSS logo

CSS

Comfortable

I'd rather write it by hand than fight a framework's defaults.

Tools

02
Git logo

Git

Comfortable

Branches, rebases, and the occasional reflog rescue.

Docker logo

Docker

Working with

Mostly for spinning up isolated environments and labs.

Operating Systems

01
Linux logo

Linux

Comfortable

Terminal workflows, system configuration, and a lot of trial and error.

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
lab-vm — isolated

$ 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.

One project I'm actually putting real hours into, and a few smaller things around it.

Featured Project

MU In Development

A one-sentence pitch for MU — what it is and why it exists instead of something off the shelf — goes here.

BackendCLILinuxSystems

01 Overview

This is where the real pitch goes: what MU actually does, the problem it solves, and why it's worth building instead of reaching for something that already exists. Write it like you're explaining it to another engineer over coffee — specific about the "what" and the "why," light on the marketing.

02 Tech Stack

Swap these for the real stack once it's locked in — the chips above are a start.

  • — Language: add yours
  • — Interface: CLI, API, etc.
  • — Storage: add yours
  • — Platform: Linux

03 Current Progress

Currently in the core build phase. Move the marker as MU progresses, and use this line for the honest one-sentence status.

04 Features

  • Replace with what's actually working today
  • Core functionality, end to end
  • Basic error handling & logging

05 Planned Features

  • The next big feature on the list
  • Configuration / settings support
  • Tests, and eventually CI

06 Architecture

A rough sketch — replace with MU's real components and how data actually moves between them.

┌──────────────┐ │ Interface │ CLI / API — however you talk to it └──────┬───────┘ │ ┌──────▼───────┐ │ Core │ the actual logic └──────┬───────┘ │ ┌──────▼───────┐ │ Storage │ files, a database, whatever persists └──────────────┘

07 Screenshots

Screenshot placeholder
swap in real output when ready
Screenshot placeholder
swap in real output when ready
Screenshot placeholder
swap in real output when ready

Also around

Systems

Linux Configuration

A living collection of configs — window manager setup, shell environment, and dotfiles. Less about a particular look and more about a machine that gets out of my way: keyboard-driven, scriptable, and set up so I can rebuild it from scratch in minutes if I ever need to.

LinuxBashDotfiles
Security

Networking & Security Labs

An isolated home lab I use to actually break things safely — running scans, capturing traffic, and working through vulnerable machines to understand how systems fail before I need to know it for real. Everything here stays inside the lab network.

NetworkingLinuxIsolated Labs
Development

Portfolio Website

This site. Hand-built with plain HTML, CSS, and JavaScript — no framework, no build step. Partly a place to point people, partly an excuse to get the small details right — spacing, motion, type — without anything else making decisions for me.

HTMLCSSJavaScript

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.

Email lumma.support@gmail.com GitHub github.com/lumma Discord lumma#0000 X / Twitter @lumma