<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Knowledge on Fabrice's Blog</title><link>https://blog.redteamshell.com/tags/knowledge/</link><description>Recent content in Knowledge on Fabrice's Blog</description><generator>Hugo</generator><language>en</language><copyright>&lt;a href="https://creativecommons.org/licenses/by-nc/4.0/" target="_blank" rel="noopener">CC BY-NC 4.0&lt;/a></copyright><lastBuildDate>Sun, 25 Jan 2026 08:17:44 -0500</lastBuildDate><atom:link href="https://blog.redteamshell.com/tags/knowledge/index.xml" rel="self" type="application/rss+xml"/><item><title>The 2026 Deep Dive</title><link>https://blog.redteamshell.com/posts/2026/01/the-2026-deep-dive/</link><pubDate>Sun, 25 Jan 2026 08:17:44 -0500</pubDate><guid>https://blog.redteamshell.com/posts/2026/01/the-2026-deep-dive/</guid><description>&lt;p>&lt;img src="https://blog.redteamshell.com/images/2026_hero_image.jpg" alt="Hero Image">&lt;/p>
&lt;h3 id="going-deeper-into-code-review-reverse-engineering-and-web-exploitation">Going Deeper into Code Review, Reverse Engineering, and Web Exploitation&lt;/h3>
&lt;p>I keep coming back to the same itch: I want to know what&amp;rsquo;s actually happening under the hood. Not &amp;ldquo;the scanner flagged it,&amp;rdquo; not &amp;ldquo;the payload worked&amp;rdquo; — &lt;em>why&lt;/em> it worked, what the bytes were doing, where the bug actually lives in the code. There&amp;rsquo;s no career milestone forcing this. I just can&amp;rsquo;t leave it alone.&lt;/p>
&lt;p>So this year goes deep in three directions: code review, reverse engineering, and web exploitation. I&amp;rsquo;ve already bought the materials, which for me is the part that makes it real — money down, no graceful exit.&lt;/p></description></item></channel></rss>