vi = POSIX baseline (available everywhere).
vim-only = requires Vim 8+.
nvim-only = Neovim-specific.
<leader>defaults to\— most configs remap it to,or<Space>.
Hafeez Pizofreude pizofreude
🏠
pizofreude
/ vim_cheatsheet.md
Last active
April 22, 2026 18:17
Covers 14 sections: modal model, survival kit, navigation, insert modes, operators + text objects, search/replace, visual/block mode, registers + macros, marks, buffers/windows/tabs, ex commands, full `.vimrc`, full Neovim `init.lua` + `lazy.nvim` + LSP setup, analytics recipes, and the quick reference card. A few things worth calling out: - The…
pizofreude
/ nano_cheatsheet.md
Last active
April 22, 2026 18:19
Nano Cheatsheet for Fellow Analytics Engineer: Covers 8 sections: opening, navigation, search/replace, editing, selection, buffers, saving, and a ready-to-paste `.nanorc` config tuned for Python/dbt/YAML/SQL workflows. The quick reference card at the bottom is designed to be readable even after you've internalized most shortcuts. One thing to ac…
Windows Terminal, Command Prompt, PowerShell, Git Bash, Warp, iTerm2, Alacritty, Kitty, WezTerm, Ghostty, Tabby, Cmder, ConEmu, PuTTY, MobaXterm, ZOC, Hyper, Babun, Fish, Zsh, and Tilix. Modern favorites include Warp for AI, Ghostty for native speed, WezTerm for scripting, and iTerm2/Alacritty for power users.
Here’s a comprehensive Git Gist tailored for both Fellow-level BI & Analytics Engineers and Fellow-level Fullstack Software Engineers. This Gist covers advanced workflows, best practices, and tips for collaboration, scalability, and maintainability—key for senior engineers in both domains.
For Fellow-Level BI & Analytics Engineers & Fullstack Software Engineers
pizofreude
/ bash_cheatsheet.md
Last active
April 12, 2026 16:47
Bash Terminal Cheatsheet for Analytics Engineering
After your 12-month Free Tier period expires, you can continue using AWS services that have "Always Free" offers. These services remain free up to specified limits as long as you have a valid AWS account. Some examples of Always Free services include:
- AWS Lambda - 1 million free requests per month
- Amazon DynamoDB - 25 GB of storage
- Amazon SNS - 1 million publishes per month
- Amazon CloudWatch - 10 custom metrics and alarms
- AWS CodeCommit - 5 active users per month
- AWS CodePipeline - 1 active pipeline per month
pizofreude
/ reframe-framework.md
Created
March 3, 2026 23:53
A structured, Fellow-Level methodology to reverse engineer a Business Requirements Document (BRD) and Product Requirements Document (PRD) from a live website URL or provided screenshots.
| framework_name | REFRAME |
|---|---|
| version | 1.1 |
| trigger_keyword | REFRAME |
| description | A structured, Fellow-Level methodology to reverse engineer a Business Requirements Document (BRD) and Product Requirements Document (PRD) from a live website URL or provided screenshots. |
| usage | Apply the REFRAME framework to[URL/Screenshots] |
| author_persona | Fellow-Level Product Manager and Business Analyst |
pizofreude
/ reverse_engineering_BRD_PRD.md
Created
March 3, 2026 23:29
Framework to reverse engineer BRD & PRD from a live website URL
Reverse engineering a Business Requirements Document (BRD) and a Product Requirements Document (PRD) from a live website is a classic exercise for Product Managers and Business Analysts. Because you are working backward from the final output, you have to separate the "Why" (BRD) from the "What and How" (PRD).
Here is the best, most structured methodology to reverse engineer these documents from a URL.
For all categories of changes that are closely related, they should be in one PR because:
- The main code change, tests, and documentation all serve the same purpose: e.g. Ref: Issue #619 making
ItemSamplepublicly available - They form a complete, logical unit of work
- Splitting them would create incomplete states in the codebase
pizofreude
/ git-cleanup-fork-sync-upstream.md
Created
July 11, 2025 03:55
This gist captures the key learning and provides a reusable reference for future fork cleanup scenarios.
TIL: When you accidentally add commits to your fork that shouldn't be there (like personal notes), here's how to clean them up and get back in sync with the upstream repository.
Your fork shows: "This branch is X commits ahead of upstream:main" but those commits contain changes you don't want to contribute back (like personal notes, experiments, etc.).
NewerOlder