GlitchedPanda here—hello, world. I’m a self-taught systems developer from Norway, and I build fast tooling for performance-sensitive work. My focus sits in the low-level layer: graphics tooling, emulation, systems utilities, and efficient developer tools that feel responsive from the first compile to the final frame.
Low-level by default
When I say “systems developer,” I mean it. I like projects where details matter: memory behavior, runtime cost, and predictable performance. That mindset guides how I structure tools, how I choose data layouts, and how I chase improvements without adding unnecessary complexity.
Rust for speed and safety
Rust is one of my main languages because it helps me write performance-oriented code without giving up safety. I use it when I want tight control and reliable correctness, especially in projects where small mistakes can create big debugging headaches. It also fits well with the kind of tooling I enjoy building—fast, practical utilities that are easy to iterate on.
C++ for performance-critical tooling
For performance-critical native code, I reach for C++. Whether I’m working on emulation-adjacent components, low-level utilities, or graphics-related systems, C++ gives me the control I need. It’s the tool of choice when I’m optimizing hot paths and building components that must squeeze every millisecond out of the pipeline.
Python for flexible workflows
Python rounds things out by making the workflow flexible. I use it for scripting, automation, and glue code across projects—so experiments move quickly and repetitive tasks don’t steal time. In practice, this means faster iteration cycles: prototype with Python, validate the idea, then drop into Rust or C++ where performance matters most.
A daily workflow that keeps momentum
My day-to-day setup is built for speed and clarity: Arch Linux for a lightweight environment, Neovim for keyboard-driven editing, and Git for versioned workflows. That combination keeps builds smooth, changes trackable, and iteration tight—exactly what you want when you’re developing systems-level software.
If you want to see more about how GlitchedPanda works and what projects are in motion, you can start at glitchedpanda.dev.
In the end, GlitchedPanda is about building tools that perform, tooling that stays dependable, and experiments that turn into useful systems—thank you for reading.
See you in the next build.
