Cybersecurity · Backend Engineering · Networking · Systems
Building practical tools, exploring system behavior, and engineering more secure and reliable software.
I'm a developer interested in what happens beneath the surface of software and networks: how systems are designed, how components communicate, where failures emerge, and how to make applications more secure and reliable.
My work and learning connect four areas:
- Cybersecurity — security analysis, defensive tooling, web security, and threat behavior.
- Backend engineering — APIs, authentication, application architecture, and data-driven services.
- Networking and systems — protocols, traffic behavior, operating systems, and practical utilities.
- Developer tooling — automation and focused tools that make technical work easier.
Understand the system. Find the weakness. Build the defense.
I learn by building, testing, debugging, documenting, and iterating on real projects.
Metrics are supplied by third-party services and may load with a delay or be temporarily unavailable. Language charts reflect repository contents, not a proficiency ranking.
| Domain | Current interests |
|---|---|
| 🔐 Security engineering | Attack-surface awareness, secure design, defensive analysis, and practical security tools |
| 🧪 Malware research | Understanding execution and persistence behavior in controlled, authorized research environments |
| 🌐 Networking | Protocols, traffic inspection, network utilities, and communication between systems |
| ⚙️ Backend systems | REST APIs, authentication, validation, reliability, and maintainable architecture |
| 🧩 Systems programming | Operating-system concepts, system behavior, and tooling with Go |
| 🛠️ Automation | Utilities that reduce repetitive work and improve developer workflows |
Stack badges represent technologies I use or explore; they do not imply equal proficiency in every tool.
- Defensive security — turning security concepts into practical analysis and defensive tooling.
- Network behavior — understanding protocols, traffic, and communication between services.
- Go — building efficient command-line utilities and systems-oriented tools.
- TypeScript — writing clearer, safer application and backend code.
- Secure architecture — strengthening validation, authentication, configuration, and failure handling.
| Principle | How it shapes my work |
|---|---|
| Understand before optimizing | Learn how a system behaves before changing it. |
| Secure by design | Treat validation, permissions, and failure paths as core features. |
| Prefer useful simplicity | Build focused tools with clear responsibilities. |
| Test and document | Make behavior reproducible and easier for others to understand. |
| Keep improving | Treat debugging and feedback as part of the development process. |
When I'm away from a project, I enjoy exploring Linux, playing games, looking at the night sky, and following technical rabbit holes that turn into new experiments.
Learn continuously. Build deliberately. Secure what matters.



