Hafeez Pizofreude pizofreude

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.

Git Gist: Advanced Workflows & Best Practices

For Fellow-Level BI & Analytics Engineers & Fullstack Software Engineers

1. Core Git Concepts (Refresher)

🖥️ Bash Terminal Cheatsheet

Fellow-level reference · Quick lookup, no fluff.

📁 File & Directory Navigation

Command	What it does
`pwd`	Print current working directory

Always Free AWS Services

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

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

🚀 START HERE: System Instructions

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.

Phase 1: Reverse Engineer the BRD (The "Why")

PR Best Practices

Best Practice: Single PR for Related Changes

For all categories of changes that are closely related, they should be in one PR because:

1. Atomic Change Principle

The main code change, tests, and documentation all serve the same purpose: e.g. Ref: Issue #619 making ItemSample publicly available
They form a complete, logical unit of work
Splitting them would create incomplete states in the codebase

How to Clean Up Fork Commits and Sync with Upstream

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.

The Problem

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.).

Solution: 3 Options to Clean Up

📚 R & RStudio: Working Directory Cheatsheet

This cheatsheet covers how to control and troubleshoot the working directory in R, RStudio Desktop, and RStudio Cloud. A correct working directory makes data import, script sourcing, and project management much smoother.

1️⃣ RStudio Desktop: Setting the Working Directory

A. Launch from Terminal with Correct Directory

Windows check whether your system supports UEFI by following these steps:

Press Win + R, type msinfo32, and hit Enter.
In the System Information window, look for BIOS Mode.
If it says UEFI, your laptop supports it! If it says Legacy, it does not.

Rufus

For UEFI supported system, we can opt to GPT for partition scheme. Otherwise, choose MBR.