Overcoming the Pendrive Problem with Git

Day 16: Goodbye GUI, Hello Terminal! Today I learned how to create and push a repository using only the Command Line Interface (CLI). Here is the 5-step workflow I mastered today: 1️⃣ git init → Initialize a new empty repository. 2️⃣ git add . → Stage all my files (Get them ready). 3️⃣ git commit -m "message" → Save the changes history. 4️⃣ git branch -M main → Rename the branch to standard "main". 5️⃣ git push -u origin main → Send everything to GitHub. It looks intimidating at first, but once you get the flow, it is so much faster than clicking around a website. #Coding #GitCommands #CLI #DevOps #WebDevelopment #StudentLife

Ever wonder how developers collaborated before Git? 📁 Back then, we used pendrives, zip files, and folders named as 🥴"final_v2." It was a mess of overwritten code and lost work🙄. I just published a new blog on Why Version Control Exists❓. I break down: The "Pendrive Analogy" of old-school coding. Why sharing code manually is a recipe for disaster. How Git acts as an independent "code tracker" to save our projects. 🚀 Read the full story: https://lnkd.in/gAxW4aUd #Git #Programming #TechCommunity #versioncontrol

I built a tool to solve my own frustration with messy Git commits. Stop cluttering your source code with temporary notes like me. I’ve always found it counter-intuitive to add temporary TODOs or logic explanations directly into the source file, especially when working on large, unfamiliar codebases. It risks accidental commits and creates noise in Git diffs. To solve this, I built Shadow Comments, a VS Code extension that allows you to add a private annotation layer over your code. Key Features: 1. Zero-Footprint: Your notes are stored locally and do not modify the actual .py, .cpp, or .js files. 2. Workflow-Focused: Use shortcuts to toggle visibility or add notes instantly without breaking your flow. 3. Persistence: Annotations stay linked to the specific lines, even after restarting the editor. This started as a personal utility to help me navigate complex repositories at NUST, but I’ve now released it on the Marketplace for anyone who wants a cleaner workspace. Check it out here: https://lnkd.in/dc_k_7xC Feedback is welcome. #SoftwareEngineering #VSCode #DeveloperTools #OpenSource #Productivity #Programming #VSCodeExtensions #SystemDesign

Every developer needs this ☕!! Git commands cheat sheet, a version control to boost developer productivity. If you code daily, this mug hits too close to home 😄 This isn’t just a coffee mug, it’s a Git survival guide staring back at you while you debug, commit, push, pull… and pray nothing breaks. From git init to git rebase, it’s basically saying: “Relax. You’ve got this. One commit at a time.” Perfect for: Developers who live in the terminal Engineers who forget commands under pressure Techies who believe coffee + Git = productivity Which Git command do you use the MOST git pull, git commit, or git status? #Git #Developers #Programming #SoftwareEngineering #DevLife #Coding #TechCommunity #VersionControl #LinkedInTech #CoffeeAndCode #CLI

🚀 Git Scaring You? Let's Fix That. We've all been there: staring at a "detached HEAD" state, wondering if we should just delete the repo and re-clone it. 😅 But Git doesn't have to be a black box. Whether you are pushing your first commit or bisecting a regression, having the right commands at your fingertips changes everything. I put together this Cheatsheet covering the full lifecycle: 1️⃣ Setup: The foundations. 2️⃣ The Daily Cycle: Commit, add, stash, repeat. 3️⃣ Branching: Keeping work isolated. 4️⃣ Workflows: Trunk-based vs. Feature branches. 5️⃣ Debugging: Finding the needle in the haystack. 6️⃣ Repair: The "Undo" buttons you didn't know you had. 💡 Pro Tip: git reflog is your safety net. It remembers everything you've done, even if you deleted the branch. Swipe through to upgrade your version control game! 👉 #Git #DevOps #SoftwareEngineering #Coding #Cheatsheet #WebDevelopment #TechTips #Programming

📚 Pro Git (Second Edition, open-access)   🔹 Free Resource — Follow us for more learning material   🔗 Link: https://lnkd.in/dC7YWbtf Pro Git by Scott Chacon and Ben Straub is the definitive guide to Git — the distributed version control system that underpins modern software workflows. It covers everything from basic repository setup and branching strategies to advanced topics like rebasing, collaboration workflows, submodules, and Git internals, making it a valuable reference for both learners and professionals. At Krabo Systems, we believe in sharing knowledge that empowers professionals and teams to grow without barriers. Follow us for more free resources and insights. #git #versioncontrol #softwareengineering #developers #opensource #programming #collaboration #workflow #codeManagement #branches #rebasing #gitInternals #ci #devops #learning #education #training #free #javascript #rust #go #typescript #python #systems #linux #dev #code #ai #docker #kubernetes #web #react #html #css #machinelearning #ml

🚨 Git Commands That Look the Same — But Aren’t! Ever typed a Git command thinking “This should be safe…” …and suddenly your branch is broken? 😅 Some Git commands look almost identical, but their impact is very different. This quick visual explains the most confusing ones — in a simple way 👇 🔹 git fetch vs git pull 🔹 git reset --soft vs git reset --hard 🔹 git checkout vs git switch 🔹 git revert vs git reset 🔹 git stash apply vs git stash pop 💡 Pro Tip: If you’re working on a shared repo, avoid commands that rewrite history unless you really know what you’re doing. If this saved you from a Git disaster: 👍 Like | 🔁 Share | 💬 Comment your favorite Git tip #git #developers #programming #coding #softwareengineering #devtips #careerdevelopment

Git Merge vs Git Rebase Here’s the simplest way to think about merge vs rebase 🔹 Git Merge 1. Combines branches by creating a merge commit 2. Keeps the full history of both branches 3. Safe and straightforward 4. Best for shared branches like main It's somewhat looks like, “Let’s keep everything exactly as it happened.” 🔹 Git Rebase 1. Moves your commits on top of another branch 2. Creates a clean, linear history 3. Great for feature branches before a PR 4.Not safe on shared branches (rewrites history!) Simply, --Use merge when history matters --Use rebase when clarity matters #git #versioncontrol #developers #learning #programming #softwareengineering #frontend #fullstack

just spent 3 hours debugging code that worked perfectly yesterday. The culprit? A single semicolon I deleted while "cleaning up" my code. Here's what I learned (the hard way): "If it ain't broke, don't fix it" exists for a reason Git commits are your best friend - commit early, commit often Never trust "just a quick cleanup" before a deadline • Sometimes the smallest changes break everything The funny part? My error message was completely unhelpful. Stack Overflow had 47 different solutions. None of them worked. Then I did what every programmer eventually does... I stared at my screen for 20 minutes, questioned my life choices, and finally ran a diff check. One. Missing. Semicolon. Pro tip: Before you spend hours debugging, check if you accidentally deleted something during your last "improvement." Fellow developers - what's the smallest bug that's cost you the most time? #Programming #SoftwareDevelopment #CodingLife #DeveloperHumor #TechLife #LearnToCode