Hello, self
Hello. Let me start with an introduction.
I go by thefueley. I’ve been in the Computer Science world for many years, both as a student and a SysAd, and the part of the field that keeps pulling me back is the low-level end: reverse engineering, and malware in particular. There’s something satisfying about taking a program you were never meant to read and working out exactly what it does anyway.
Why this blog
The honest reason is that I want to relearn this material properly, and writing it down in public is the most reliable way I know to do that. Explaining something forces you to actually understand it, and a half-finished explanation is easy to spot. If no one else catches it, my future self will. That’s really who these posts are for, which is where the title comes from.
So this is a learning journal more than a set of tutorials. I’ll be refreshing and rebuilding my own knowledge across reverse engineering, hacking, and malware analysis, and posting the notes as I go. Nothing here is meant to be authoritative. It’s me working through material and recording what stuck.
What I plan to cover
A running list, in no particular order:
- Software engineering
- Software reverse engineering
- Hacking and offensive security
- Embedded systems
- Linux security
- Programming languages (assembly, C, Go, and whatever a given problem demands)
- Digital forensics
- Network security
- Malware analysis
And, every so often, things with no connection to any of the above: food, and the foreign languages I’m studying. Consider those the B-sides.
What the posts will look like
Expect disassembly listings, annotated C, hex dumps, and the occasional terminal session. That’s the raw material of the work, and I would rather keep it close to the surface than smooth it over. When I get something wrong, I’ll try to leave the wrong turn visible instead of quietly editing it out. The mistakes are usually where the learning is.
That’s the plan. First real post soon.