tl;dr - My cheatsheet

Blog commit

If you've seen the last post before this, then you may have noticed that I have not been posting much content lately or at all.

Recently, I watched a video from KringleCon 2020. The video was a talk by one of my favorite podcasters Jack Rhysider from the podcast Darknet Diaries.

The title of his talk was "Give Yourself a Blog for Christmas". I didn't because I already had one. However, his talk encouraged me to write some more in this already existing blog.

"Blog commit" means that in the coming months or years you should see me be more active here, sharing with you what I've learned. I've added Disqus to this blog so people can comment, suggest, and correct my mistakes (There's going to be a lot of them, and thank you in advance).

I'll attempt to keep my writing here informal and playful as I do a lot of formal stuff during my day job.

Old notebooks
Photo by Charl Folscher / Unsplash

Cheatsheet

During the past year, I have been slowly transferring my old cheatsheet and writing a new sheet into my Github pages. Before I had the impression that your methodologies and cheatsheets are usually for your eyes only, then I saw this guy and that perception instantly changed. I guess everybody could have the same methodology and cheatsheet but it might be the knowledge and experience that would give you the edge. I believe everybody (even not in the cybersecurity field) should have their own cheatsheet. It's like jotting down your own notes even though your classmate would be willing to share or send his/her notes anyway. Also, it's just easier to access your notes without needing to login to your password manager everywhere you go just to access your private notes. So without further ado, my cheatsheet:

https://trojand.com/cheatsheet

If you have any comments, suggestions, or corrections, feel free to write them below in the comment section.