Skip to content

Instantly share code, notes, and snippets.

View maxfierke's full-sized avatar
🌋
NoMethodError: undefined method `status' for #<ProfileInfo:0x00007fc2ffae9f38>

Max Fierke maxfierke

🌋
NoMethodError: undefined method `status' for #<ProfileInfo:0x00007fc2ffae9f38>
View GitHub Profile
@SonoSooS
SonoSooS / DMGCPU.MD
Last active March 21, 2025 09:58
Game Boy CPU internals

This document is intended to document certain inner workings of the CPU.

There have been efforts by emu-russia and gekkio to have the CPU decapped, and so we have the decode ROM accessible to us. This means, that we know exactly what each opcode does (besides some nuanced behavior related to HALT, STOP, and some state management related to interrupts and power saving which are hard to untangle).

Table of contents

@kconner
kconner / macOS Internals.md
Last active July 10, 2025 04:32
macOS Internals

macOS Internals

Understand your Mac and iPhone more deeply by tracing the evolution of Mac OS X from prelease to Swift. John Siracusa delivers the details.

Starting Points

How to use this gist

You've got two main options:

@mitchellh
mitchellh / merge_vs_rebase_vs_squash.md
Last active July 2, 2025 19:16
Merge vs. Rebase vs. Squash

I get asked pretty regularly what my opinion is on merge commits vs rebasing vs squashing. I've typed up this response so many times that I've decided to just put it in a gist so I can reference it whenever it comes up again.

I use merge, squash, rebase all situationally. I believe they all have their merits but their usage depends on the context. I think anyone who says any particular strategy is the right answer 100% of the time is wrong, but I think there is considerable acceptable leeway in when you use each. What follows is my personal and professional opinion:

@bdashrad
bdashrad / fizzbuzz.tf
Created May 14, 2024 15:18
a terrible idea
# fizzbuzz.tf
variable "start" {}
variable "end" {}
output "out_text" {
value = join(
"\n", [
for i in range(var.start, var.end):
i % 15 == 0 ? "FizzBuzz" :