“In order to understand something, you must be willing to take it apart.”
I like to learn about engines, but I don’t own one — so instead, I learn about computers.
I'm more into understanding how systems work than building flashy projects. If it crashes, panics, or dumps core, that’s when it gets interesting. I wouldn’t call myself a developer — more like a reverse engineer in training who treats every stack trace like a mystery novel.
- Python
- Bash
- C / C++ (to remind myself I am not a developer)
- Networking (TCP/IP, DNS, VPNs, proxies, firewalls)
- Hosting & DevOps (Nginx, Docker, systemd, SSH)
- Tools: Linux, Git, Wireshark, GDB, curl, nmap, tmux, rsync, you name it
- Myself
- Operating system internals
- Cybersecurity (offensive & defensive)
- Building self-hosted setups & secure infra
- Using encryption properly (and actually understanding it)
 Clannad |
 Serial Experiments Lain |
 Gintama |
 Discourses |
 Beyond good and evil |
- Self-hosting stuff to find out later it broke
- Setting up monitoring for servers no one asked me to monitor
- Digging into packet captures like it's detective work
- Building a local CTF lab and locking myself out of it
- Explaining DNS like it's magic (because it kind of is)
"If you want to understand a system, break it and then Google your way back."
All love Lain.