I’m a software engineer

who specializes in low-level programming. For me, that means two things:

1. Understanding how a piece of software works - whether that means running it, reading the source code, or staring at the compiled bytecode.
2. Coming up with creative solutions to problems caused by the constraints of the environment.

This may seem vague, but that’s because it’s not about a specific technology; it’s about having to dive deep and do things no one else has done before. I learn how Go stack resizing works one day and think of ways around Macos memory permissions the next, and I love it.