Some notes, tools, and techniques for reverse engineering macOS binaries.
Discover gists
| --- | |
| name: frontend-design | |
| description: Create distinctive, production-grade frontend interfaces with high design quality. Use this skill when the user asks to build web components, pages, or applications. Generates creative, polished code that avoids generic AI aesthetics. | |
| license: Complete terms in LICENSE.txt | |
| --- | |
| This skill guides creation of distinctive, production-grade frontend interfaces that avoid generic "AI slop" aesthetics. Implement real working code with exceptional attention to aesthetic details and creative choices. | |
| The user provides frontend requirements: a component, page, application, or interface to build. They may include context about the purpose, audience, or technical constraints. |
This is a collections of script, patches and procedures to mod Mobile and Desktop Spotify Applications.
If you know about something that isn't listed here and you would like it to be feel free to tell me about it in the comments or send an e-mail to [email protected]
| Product Year Version Product Keys | |
| Visual Studio 2022 2021 17.x Professional: | |
| TD244-P4NB7-YQ6XK-Y8MMM-YWV2J | |
| Enterprise: | |
| VHF9H-NXBBB-638P6-6JHCY-88JWH | |
| Visual Studio 2019 2019 16.x Professional: | |
| NYWVH-HT4XC-R2WYW-9Y3CM-X4V3Y | |
| Enterprise: |
Go provides file-opening flags represented by constants defined in the os package. These flags determine the behavior of file operations, such as opening, creating, and truncating files. The following is a list of the flags and what they do.
-
os.O_RDONLY: Opens the file as read-only. The file must exist. -
os.O_WRONLY: Opens the file as write-only. If the file exists, its contents are truncated. If it doesn't exist, a new file is created. -
os.O_RDWR: Opens the file for reading and writing. If the file exists, its contents are truncated. If it doesn't exist, a new file is created.
This style guide was generated by Claude Code through deep analysis of the Fizzy codebase - 37signals' open-source project management tool.
Why Fizzy matters: While 37signals has long advocated for "vanilla Rails" and opinionated software design, their production codebases (Basecamp, HEY, etc.) have historically been closed source. Fizzy changes that. For the first time, developers can study a real 37signals/DHH-style Rails application - not just blog posts and conference talks, but actual production code with all its patterns, trade-offs, and deliberate omissions.
How this was created: Claude Code analyzed the entire codebase - routes, controllers, models, concerns, views, JavaScript, CSS, tests, and configuration. The goal was to extract not just what patterns are used, but why - inferring philosophy from implementation choices.
| #include <Arduino.h> | |
| #include <TimerOne.h> | |
| // Diagram --------------------------------------------------------- | |
| // Logic Voltage (5V/3.3V)--------[resistor]----+----[Analog Read] | |
| // | | |
| // [Steering Wheel Buttons] | |
| // | | |
| // GND |
Replace 0F B6 51 05 83 F2 01 with C6 41 05 01 B2 00 90
py -c "open('C:\\Program Files\\Sublime Text\\sublime_text.exe', 'rb+').write(open('C:\\Program Files\\Sublime Text\\sublime_text.exe', 'rb').read().replace(b'\x0F\xB6\x51\x05\x83\xF2\x01', b'\xC6\x41\x05\x01\xB2\x00\x90'))"| // Download totals.db from https://data-analysis.fedoraproject.org/csv-reports/countme/ | |
| // | |
| // curl -fsSL https://bun.sh/install | bash | |
| // bun run dnf-count.ts | |
| import { Database } from "bun:sqlite"; | |
| const db = new Database("totals.db"); | |
| const query = db.query(` |