iiinova — where your digital self keeps evolving

Sumit Saurabh @sumit.bsky.social · 10/09/2026

Let’s have listening devices all around us. OR NOT!

020

Sumit Saurabh @sumit.bsky.social · 08/09/2026

So good to see that you’re here too! Welcome welcome!

020

Sumit Saurabh @sumit.bsky.social · 08/09/2026

I yearn to be this skilled 🙏

020

Sumit Saurabh @sumit.bsky.social · 17/08/2026

Is this strictly limited to folks from the USA or would you be open to the right candidate from elsewhere?

100

Sumit Saurabh @sumit.bsky.social · 15/08/2026

Hi Alan, is this still open?

100

Reposted by Sumit Saurabh

Ash Parrish, Kotaku's LeBron James @adashtra.bsky.social · 08/07/2026

Every day this post becomes ever more correct

@PPathole Tech enthusiasts: My entire house is smart. Tech workers: The only piece of technology in my house is a printer and I keep a gun next to it so I can shoot it if it makes a noise I don't recognize.

203431747

Sumit Saurabh @sumit.bsky.social · 08/07/2026

Hey Darcy, is this remote (overlapping hours)?

010

Sumit Saurabh @sumit.bsky.social · 04/03/2025

🔟 Final Takeaway: Use Git Stash Wisely ✔️ Great for quick, temporary saves ❌ Not a replacement for commits 💡 When in doubt, create a branch instead

000

Sumit Saurabh @sumit.bsky.social · 04/03/2025

9️⃣ Bonus: Recovering a Dropped Stash 😱 Accidentally dropped a stash? You might still recover it: Try: git fsck --lost-found and look for stash-like commits.

100

Sumit Saurabh @sumit.bsky.social · 04/03/2025

8️⃣ Managing & Cleaning Up Stashes 🗑 Clear all stashes: git stash clear 🗑 Delete a specific stash: git stash drop stash@{1} Pro tip: If you use stashes often, clean them up regularly!

100

Sumit Saurabh @sumit.bsky.social · 04/03/2025

7️⃣ Better Alternatives to git stash 🚀 Use WIP commits: git commit -m "WIP" 🚀 Create a temporary branch 🚀 Use git worktree for parallel work

100

Sumit Saurabh @sumit.bsky.social · 04/03/2025

6️⃣ When You Shouldn’t Use git stash ❌ 🚨 If your work is important (stashes aren’t safe long-term) 🚨 If you switch tasks often (easy to forget stashes) 🚨 If you need team visibility (stashes are local, not shared)

100

Sumit Saurabh @sumit.bsky.social · 04/03/2025

5️⃣ When You Should Use git stash ✅ ✔️ Switching branches temporarily ✔️ Need a clean working directory for testing ✔️ Quickly save work without committing

100

Sumit Saurabh @sumit.bsky.social · 04/03/2025

4️⃣ Applying a Specific Stash If you have multiple stashes, apply a specific one using: git stash apply stash@{2} This applies the 3rd stash in your history (zero-based index).

100

Sumit Saurabh @sumit.bsky.social · 04/03/2025

3️⃣ Keep Track of Stashes with Messages By default, stashes are unnamed, which can get messy. Instead, use: 📝 git stash push -m "WIP: Fixing login bug" 📜 View stash history: git stash list

110

Sumit Saurabh @sumit.bsky.social · 04/03/2025

2️⃣ The Basics: Stashing and Applying 🗄 Stash changes: git stash ♻️ Apply latest stash: git stash pop (removes it from stash history) 🔄 Apply without removing: git stash apply

110

Sumit Saurabh @sumit.bsky.social · 04/03/2025

1️⃣ What Is git stash? 🔹 Temporarily saves uncommitted changes 🔹 Cleans your working directory 🔹 Lets you switch branches without committing 🔹 Think of it as a clipboard for your code

110

Sumit Saurabh @sumit.bsky.social · 03/03/2025

7️⃣ Bonus: Stacked PRs Work Best With Feature Flags 🚩 🔹 Ship incomplete features behind flags 🔹 Merge incrementally without affecting users 🔹 Reduce risk of breaking production

020

Sumit Saurabh @sumit.bsky.social · 03/03/2025

6️⃣ Merge Strategy: Bottom-Up vs. Top-Down 🔹 Bottom-up: Merge base PR first, then the next 🔹 Top-down: Rebase from the base PR as you go Tools like gh stack & av make this effortless!

100

Sumit Saurabh @sumit.bsky.social · 03/03/2025

5️⃣ Example: Adding a Dark Mode Feature 🌙 ❌ One Big PR – Backend, API, UI, styles, settings all in one = 🔥 ✅ Stacked PRs: 1️⃣ Backend: Store dark mode preference 2️⃣ API: Expose preference 3️⃣ UI: Toggle switch + styles Much easier to review!

110

Sumit Saurabh @sumit.bsky.social · 03/03/2025

4️⃣ Developers Benefit Too 🚀 🔹 Less waiting for approvals 🔹 Merge work incrementally instead of all at once 🔹 Avoid rewriting code due to delayed feedback 🔹 Keep main branch stable while shipping fast

100

Sumit Saurabh @sumit.bsky.social · 03/03/2025

3️⃣ Reviewers Love Stacked PRs ❤️ ✅ Faster reviews (small changes = quick feedback) ✅ Focused discussions (each PR solves one problem) ✅ Fewer merge conflicts (less code churn) ✅ Easier debugging (pinpoint issues in smaller PRs)

100

Sumit Saurabh @sumit.bsky.social · 03/03/2025

2️⃣ What Are Stacked PRs? 🔹 A sequence of smaller, dependent PRs 🔹 Each PR builds on the previous one 🔹 Easier to review since each PR focuses on a single step Example: ✅ PR 1: Refactor DB schema ✅ PR 2: API changes ✅ PR 3: Update UI

100

Sumit Saurabh @sumit.bsky.social · 03/03/2025

1️⃣ Big PRs = Big Problems ❌ Hard to review ❌ Reviewers get lost in too many changes ❌ Endless back & forth slows progress ❌ Rubber-stamping leads to hidden bugs Stacked PRs fix this 👇

110

Sumit Saurabh @sumit.bsky.social · 27/02/2025

I hope you've found this thread helpful and learnt something new. If you did: ✅ Follow me @sumitsaurabh927 for more. ✅ Like and comment down below ✅ Repost the quote below:

000

Sumit Saurabh @sumit.bsky.social · 27/02/2025

🔟 TL;DR: Rebase Like a Pro 🚀 ✅ Use rebase for clean history ✅ Never rebase shared branches ✅ Always backup before rebasing ✅ If things go wrong, use git reflog

100

Sumit Saurabh @sumit.bsky.social · 27/02/2025

9️⃣ The Safe Way to Rebase 🛡️ Before rebasing, always: ✅ Backup your branch (git branch backup-feature) ✅ Fetch the latest changes (git fetch origin) ✅ Use interactive mode (git rebase -i)

100

Sumit Saurabh @sumit.bsky.social · 27/02/2025

8️⃣ Interactive Rebase: The Power Move ⚡ Want to edit, squash, or reorder commits? Use interactive rebase: - git rebase -i HEAD~3 You can pick, squash, or edit commits for a polished commit history!

100

Sumit Saurabh @sumit.bsky.social · 27/02/2025

7️⃣ When to Use Merge Instead of Rebase? 🔄 🔹 Merge preserves history & is safer for shared branches 🔹 Rebase creates a cleaner history but rewrites commits Use merge when collaborating on the same branch!

100

Sumit Saurabh @sumit.bsky.social · 27/02/2025

6️⃣ Fixing a Broken Rebase 😵 Rebased & lost commits? Use the reflog! - git reflog - git reset --hard HEAD@{1} This restores your branch before the rebase—lifesaver! 🔥

100

Sumit Saurabh @sumit.bsky.social · 27/02/2025

5️⃣ Never Rebase a Shared Branch 🚨 If a branch is already pushed & used by others, avoid rebasing! ✅ Safe: Rebasing local feature branches ❌ Unsafe: Rebasing main or shared branches Golden rule: If you’ve pushed it, don’t rebase it!

100

Sumit Saurabh @sumit.bsky.social · 27/02/2025

4️⃣ The Danger of Rewriting History ⚠️ Rebase modifies commit history, which is fine locally but dangerous after pushing. If others pull your rebased branch, Git gets confused & may create duplicate commits or break history.

100

Sumit Saurabh @sumit.bsky.social · 27/02/2025

3️⃣ How to Use Rebase? 👨‍💻 To update your branch with main: - git checkout feature-branch - git fetch origin - git rebase origin/main Your commits now sit on top of the latest main—no merge commit needed!

100

Sumit Saurabh @sumit.bsky.social · 27/02/2025

2️⃣ Why is Rebase Useful? 🎯 🔹 Keeps history clean & linear 🔹 Makes reviewing PRs easier 🔹 Avoids unnecessary merge commits 🔹 Helps resolve conflicts before merging Great for keeping feature branches up to date with main!

100

Sumit Saurabh @sumit.bsky.social · 27/02/2025

1️⃣ What is Git Rebase? 🤔 Rebase rewrites history by moving commits from one branch onto another. Instead of a messy merge commit, it applies your changes linearly on top of the latest branch. ✅ Cleaner history ✅ No unnecessary merge commits

100

Sumit Saurabh @sumit.bsky.social · 27/02/2025

Why Git Rebase is Powerful (But Dangerous if Used Wrong) Git rebase can clean up your commit history & make merges smoother—but misuse it, and you’ll break everything! Here’s why rebase is powerful, when to use it, and how to avoid disasters 👇

121

Sumit Saurabh @sumit.bsky.social · 24/02/2025

I hope you've found this thread helpful and learnt something new. If you did: ✅ Follow me @sumitsaurabh927 for more. ✅ Like and comment down below ✅ Repost the quote below:

000

Sumit Saurabh @sumit.bsky.social · 24/02/2025

🔟 Always Use CI/CD for IaC 🚀 Manually applying infra = risky & inconsistent 😬 ✅ Automate deployments with GitHub Actions, Jenkins, Terraform Cloud ✅ Review PRs before applying changes ✅ Enables safe & predictable infra changes

100

Sumit Saurabh @sumit.bsky.social · 24/02/2025

9️⃣ Document Everything 📝 Future-you will thank you for good docs 😅 ✅ Write README files for infra setups ✅ Document architecture decisions (ADR) ✅ Use diagrams to show infra relationships 🏗️

100

Sumit Saurabh @sumit.bsky.social · 24/02/2025

8️⃣ Automate Testing & Validation ✅ IaC mistakes = costly outages 🛑 ✅ Use terraform validate or cfn-lint ✅ Run policy checks (OPA, AWS Config) ✅ Automate tests in CI/CD pipelines

100

Sumit Saurabh @sumit.bsky.social · 24/02/2025

7️⃣ Write Descriptive Commit Messages 📜 "Updated main.tf" tells nothing 🤦‍♂️ ✅ Be specific in commit messages ✅ Explain why the change was made ✅ Makes debugging & auditing easier

100

Sumit Saurabh @sumit.bsky.social · 24/02/2025

6️⃣ Follow the Principle of Least Privilege 🔐 Over-permissioned resources = security nightmare 🚨 ✅ Limit IAM roles & permissions ✅ Use read-only access where possible ✅ Rotate secrets & API keys frequently

100

Sumit Saurabh @sumit.bsky.social · 24/02/2025

5️⃣ Implement State Management Properly 💾 Infra tools track state—don’t mess it up! ✅ Use remote state storage (S3, Terraform Cloud) ✅ Lock state files to avoid conflicts (terraform state lock) ✅ Backup your state regularly 🚀

110

Sumit Saurabh @sumit.bsky.social · 24/02/2025

4️⃣ Use Modules for Reusability 🔄 Don't copy-paste IaC—modularize it! ✅ Create reusable Terraform modules or CloudFormation stacks ✅ Keep networking, storage & compute separate ✅ Makes infra scalable & easy to update

100

Sumit Saurabh @sumit.bsky.social · 24/02/2025

3️⃣ Keep Config & Code Separate 🏗️ Hardcoding values = painful updates 😬 ✅ Use variables & parameterized configs ✅ Store sensitive data in secret managers (Vault, AWS Secrets) ✅ Define environment-specific configs properly

100

Sumit Saurabh @sumit.bsky.social · 24/02/2025

2️⃣ Stick to One IaC Tool 📌 Mixing Terraform, CloudFormation & Pulumi = chaos 😵‍💫 ✅ Pick one tool & standardize it across teams ✅ Avoid writing infra manually—everything should be in code ✅ Reduce complexity by keeping it consistent

100

Sumit Saurabh @sumit.bsky.social · 24/02/2025

1️⃣ Use Version Control for Everything 🛠️ Treat IaC like application code. ✅ Store all infra code in Git ✅ Use branches & PRs for changes ✅ Tag releases for rollback safety Infra should be repeatable & reversible 🚀

100