{ "@context": "https://schema.org", "@id": "https://aggr.aymericbeaumet.com/items/computerenhance-com/2026-06-22-let-s-decode-the-mystery-bytes/#webpage", "@type": [ "WebPage", "ArchiveComponent" ], "articleBody": "Last month, I posted *[Let’s Answer Ray’s Question!](https://www.computerenhance.com/p/lets-answer-rays-question)* - a video where we looked at the memory behavior of two different compilations of the same program. I ended that video by saying that if you could read assembly language (like you can if you did [Part I of the](https://www.computerenhance.com/i/99218768/performance-aware-programming-series) *[Performance Aware Programming](https://www.computerenhance.com/i/99218768/performance-aware-programming-series)*[course](https://www.computerenhance.com/i/99218768/performance-aware-programming-series) !), you could go much further and determine even more specifics.\n\nIn this video, we do exactly that. Using disassembly, memory view, and heap debugging, we zero in on exactly who is setting the magic eight bytes we saw next to Ray’s allocations in the first video - and we figure the convoluted way those bytes are encoded.\n\n*If you’d like to be emailed when the third and final video is posted, you can subscribe your email address to either our free or paid tiers using the button below.*\n", "authors": [ "Casey Muratori" ], "captured_at": "2026-09-19T21:30:23.395188495+00:00", "category": "programming", "content_html": "

Last month, I posted Let’s Answer Ray’s Question! - a video where we looked at the memory behavior of two different compilations of the same program. I ended that video by saying that if you could read assembly language (like you can if you did Part I of the Performance Aware Programmingcourse !), you could go much further and determine even more specifics.

\n

In this video, we do exactly that. Using disassembly, memory view, and heap debugging, we zero in on exactly who is setting the magic eight bytes we saw next to Ray’s allocations in the first video - and we figure the convoluted way those bytes are encoded.

\n

If you’d like to be emailed when the third and final video is posted, you can subscribe your email address to either our free or paid tiers using the button below.

\n", "content_markdown": "Last month, I posted *[Let’s Answer Ray’s Question!](https://www.computerenhance.com/p/lets-answer-rays-question)* - a video where we looked at the memory behavior of two different compilations of the same program. I ended that video by saying that if you could read assembly language (like you can if you did [Part I of the](https://www.computerenhance.com/i/99218768/performance-aware-programming-series) *[Performance Aware Programming](https://www.computerenhance.com/i/99218768/performance-aware-programming-series)*[course](https://www.computerenhance.com/i/99218768/performance-aware-programming-series) !), you could go much further and determine even more specifics.\n\nIn this video, we do exactly that. Using disassembly, memory view, and heap debugging, we zero in on exactly who is setting the magic eight bytes we saw next to Ray’s allocations in the first video - and we figure the convoluted way those bytes are encoded.\n\n*If you’d like to be emailed when the third and final video is posted, you can subscribe your email address to either our free or paid tiers using the button below.*\n", "dateCreated": "2026-09-19T21:30:23.395188495+00:00", "date_created": "2026-06-22T17:48:57+00:00", "date_modified": "2026-06-22T17:48:57+00:00", "date_published": "2026-06-22T17:48:57+00:00", "description": "In this follow-up to \"Let's Answer Ray's Question!\", we go all the way down the rabbit hole to decode the mysterious eight bytes that kept showing up in-between Ray's allocations.", "external_url": "https://www.computerenhance.com/p/lets-decode-the-mystery-bytes", "git": { "commit": "ebb0941c5c06a2ab2377342d607535262a3e969e", "path": "items/computerenhance-com/2026/06/2026-06-22-let-s-decode-the-mystery-bytes.md", "permalink": "https://github.com/aymericbeaumet/aggr-instance/blob/ebb0941c5c06a2ab2377342d607535262a3e969e/items/computerenhance-com/2026/06/2026-06-22-let-s-decode-the-mystery-bytes.md" }, "id": "urn:aggr:item:8c4f3d6cea60bd97c0c26fdb2de6439d2e483b38", "isBasedOn": { "@id": "https://www.computerenhance.com/p/lets-decode-the-mystery-bytes" }, "mainEntity": { "@id": "https://www.computerenhance.com/p/lets-decode-the-mystery-bytes", "@type": "CreativeWork", "archivedAt": { "@id": "https://aggr.aymericbeaumet.com/items/computerenhance-com/2026-06-22-let-s-decode-the-mystery-bytes/#webpage" }, "author": [ { "@type": "Person", "name": "Casey Muratori" } ], "dateModified": "2026-06-22T17:48:57+00:00", "datePublished": "2026-06-22T17:48:57+00:00", "headline": "Let's Decode the Mystery Bytes!", "timeRequired": "PT1M", "url": "https://www.computerenhance.com/p/lets-decode-the-mystery-bytes", "wordCount": 138 }, "name": "Archived snapshot: Let's Decode the Mystery Bytes!", "preview": null, "reading_minutes": 1, "replicated_at": null, "source": "computerenhance-com", "source_name": "Computer, Enhance!", "summary": "In this follow-up to \"Let's Answer Ray's Question!\", we go all the way down the rabbit hole to decode the mysterious eight bytes that kept showing up in-between Ray's allocations.", "tags": [], "temporalCoverage": "2026-09-19T21:30:23.395188495+00:00", "title": "Let's Decode the Mystery Bytes!", "url": "https://aggr.aymericbeaumet.com/items/computerenhance-com/2026-06-22-let-s-decode-the-mystery-bytes/", "word_count": 138 }