Building things that probably shouldn't work, then spending 14 hours figuring out why they do.
I'm a developer interested in reverse engineering, low-level programming, security research and generally making complicated things more complicated than they need to be.
I like taking things apart, figuring out how they work, and occasionally putting them back together in a slightly worse state.
Most of my projects start with:
"I wonder if this is possible."
and end with:
"damn, that does in fact work somehow."
- Reverse engineering & binary analysis
- Windows internals
- C / C++
- Python tooling & automation
- Malware analysis & PoCs
- Software protection & obfuscation
- Game / application internals
- API & infrastructure development
- Building tools nobody asked for
- And womens.
Windows security research / UAC bypass research project.
To make it short, its becoming Terry A. Davis on your computer.
Research PoC exploring Windows GDI internals and techniques commonly encountered during malware analysis.
To make it a bit short, its a lot of color on your screen and your pc go boom boom.
Using Discord's Custom Rich Presence to show that you are a professional engineer in IDA.
To make it very short, its just visuals on Discord.
if (it works)
{
don't touch it;
}
if (it doesn't work)
{
blame Windows;
}
if (Windows isn't involved)
{
blame the compiler;
}
I don't necessarily write good software.
I write software that eventually becomes someone else's problem.
- I enjoy reverse engineering things I probably shouldn't have opened in the first place.
- I make projects that take significantly longer than they should.
- I have a questionable relationship with documentation.
printf()has solved more problems than it reasonably should have.- I occasionally remember that Git has a commit history.
- I like women.
- I probably should have stopped coding three hours ago.

