By Berkan Y. —

Welcome to Berkan’s Notepad

Welcome to Berkan’s Notepad
Photo by Slejven Djurakovic / Unsplash

This website is my notepad.

Not a blog. Not a learning platform. Not a “journey”.
A dumping ground for things I reverse engineer when documentation lies, abstractions leak, and systems behave like they were designed at 3 a.m. by someone who already quit.

If you’re looking for clean tutorials, inspirational posts, or “ethical hacking” LinkedIn energy — close the tab now. This site will actively waste your time if you don’t already know what you’re doing.

What this site is

Berkan’s Notepad is a public autopsy report of modern software.

I tear things apart and write down what falls out:

  • Windows internals that “shouldn’t matter” but absolutely do
  • Hyper-V, VMX, EPT, timing garbage, and virtualization footguns
  • Firmware, UEFI, pre-boot nonsense nobody documents
  • Anti-cheat internals that trust way too much
  • Exploit primitives, broken invariants, and design sins

These are notes, not lessons. Expect missing context, jumps straight to conclusions, and assumptions you’re expected to keep up with. If you don’t understand something, that’s not a bug — that’s the admission test.

What this site is not

Let’s be clear:

  • Not beginner friendly
  • Not sanitized
  • Not moralized
  • Not “here’s how to hack XYZ in 5 minutes”
  • Not responsible for your bluescreens

If a post ends with “this is cursed”, that means I spent hours on it and decided the system deserves no further respect.

Why this exists

Because:

  • I’m tired of rediscovering the same undocumented bullshit every six months
  • Writing things down prevents future me from hating past me
  • Some knowledge deserves to escape private folders and Discord DMs

Also, because watching people confidently explain how something should work is funny when you already know how it actually works.

What you’ll find here

  • Code with zero hand-holding
  • Offsets without apologies
  • Hypotheses that age badly
  • Observations that contradict official docs
  • Occasional rants when abstractions pretend too hard

You may also find mistakes. Congratulations, that means you’re paying attention.

What you won’t find

  • SEO
  • Buzzwords
  • “Best practices”
  • Inspirational conclusions
  • Respect for systems that lie

Final warning

Everything here comes from real experimentation.
Things crash. Things break. Assumptions die.

If you believe documentation is truth, APIs are contracts, and virtualization is “clean” — this site will annoy you.

If you enjoy watching carefully constructed abstractions collapse under a debugger — welcome.

— Berkan