Shell Scripting Cheat Sheet for DevOps Automation

spent some time learning bash scripting today started with basics what is shebang and why it’s used. understood what shell actually is and bash, zsh, ksh are just different shells. then tried basic things like - taking input, printing output variables if else, loops also learned how to run scripts directly with ‘./‘ and using interpreters like ‘sh’. tested some scripts by passing arguments into them. looked at some built-in variables like $HOME, $USER, $SHELL executed the scripts in debugging mode and checked what happens when a script fails. pipes failing was something new for me cause the scripts checks the output of a last piped command, in between any failure happens then the script does not stop executing. #devops #linux

RAM hogs are hiding in plain sight. Find them in one command. 🔥 The Command `ps aux --sort=-%mem | head -n 6` What it does: `ps aux` lists every running process. `--sort=-%mem` orders by memory usage, biggest first. `head -n 6` shows the top six lines (top hogs). #linux #terminal #bash #commandline #devops #sysadmin #programming #softwareengineering #developer #productivity #opensource #automation #buildinpublic #learntocode

If you include the programming done by Agents In their response to your prayers What is the most popular language? Not Python Not Typescript Not Java or C# lol Not M6800 Assembler Although that would be a good answer, I grant you that And Not the Others What then pray tell! It is Windows Powershell Yes, Windows Powershell Why? Because in every project Regardless of your role Regardless of what you have installed Regardless of the setup It's there Never gonna give you up Never gonna let you down Never gonna run around and desert you Never gonna make you cry Never gonna say goodbye Never gonna tell a lie and hurt you

No more chasing 'Exception' in aging logs. The terminal just handed you instant context. 🔥 `time grep -R 'Exception' /var/log 2>/dev/null` Time = duration, grep -R = recursive search, 'Exception' = literal, /var/log = log root, 2>/dev/null = hide errors. You're debugging a flaky service at 2AM. Run this on the prod box to surface every exception with timestamps, in one go. One oneliner, instant context, faster triage. 🔥 What command would you pair this with? Drop it below. #linux #terminal #bash #commandline #devops #sysadmin #programming #softwareengineering #productivity #loganalysis #opensource #troubleshooting #buildinpublic #learntocode

Today lets know about "what is SHEBANG" in Linux scripting 😊 Shebang is the first line in the script. "#!/bin/bash" it tells the system which interpreter to run the script Without shebang, the system may not know how to run the script properly, it is very important for scripting and automation. now let us write shebang with different interpreters #!/bin/bash - runs with Bash #!/usr/bin/python3 - runs with Python #!/usr/bin/php - runs with PHP #DevOps #Linux #AWS #ShellScripting #CloudComputing #Automation

One important realization while working with multithreading in C++: std::thread vs pthread is not about which creates threads — both ultimately rely on the OS. It’s about how you interact with them. At a glance: C++ → std::thread → pthread → OS threads So what actually changes? With pthread: • Low-level C API • Manual handling (void*, return codes) • More control, more room for mistakes With std::thread: • Modern C++ abstraction • RAII-based safety • Strong typing • Exception handling • Cleaner, more readable code The key shift: You’re not switching away from system threads you’re switching to a safer and more expressive interface to use them. That’s why modern C++ feels powerful: It doesn’t remove control it wraps it intelligently. Rule of thumb: Use pthread when you need fine-grained system-level control Use std::thread for almost everything else Curious: Did you start your journey with low-level pthread, or jump straight into modern C++ threading? #cpp #cplusplus #multithreading #concurrency #linux #softwareengineering #programming

Master the Linux Command Line: The Power of Grep, Sed, and Awk. 🚀 If you work with Linux, you know that data manipulation is where the real magic happens. Understanding the "Big Three" can turn hours of manual work into seconds of automation: Grep: Your search engine for the terminal. Perfect for finding patterns and filtering through mountains of logs. Sed (Stream Editor): The master of find-and-replace. Ideal for transforming text on the fly without even opening the file. Awk: A full-blown programming language for data processing. If you need to extract columns or perform calculations, Awk is your best friend. Stop clicking and start scripting. Which one do you use the most in your workflow? 💻 #Linux #DevOps #SystemAdministration #CodingTips #Grep #Sed #Awk

Tired of setting up your dev machine every time? 🐧 BDH Linux is a custom Linux environment built for Backend Developers on Arch/Manjaro. One command. Everything ready. pipx install bdh-linux bdh-linux install all ✅ Python 3.12+ ✅ FastAPI + PostgreSQL ✅ ZSH + Oh My Zsh ✅ Cyberpunk terminal theme ✅ BDH aliases pre-configured No more wasting hours on setup. Just code. ⚡ Works on: Arch / Manjaro Linux 🔗 https://lnkd.in/gZJS29vZ #Linux #Manjaro #ArchLinux #BackendDevelopment #OpenSource #FastAPI #Python #DeveloperTools

NEED to share this.. with everybody. There is a really easy way to become root in linux. To mitigate it now do this: echo "install algif_aead /bin/false" > /etc/modprobe.d/disable-algif.conf rmmod algif_aead 2>/dev/null || true Most Linux LPEs need a race window or a kernel-specific offset. Copy Fail is a straight-line logic flaw — it needs neither. The same 732-byte Python script roots every Linux distribution shipped since 2017. Read site https://copy.fail/

Me before today: "Yeah, I know what ThreadPool is... theoretically." Me after today: Actually implements background workers, fixes race conditions with locks, and makes code run 3x faster. The "Aha!" moment: running multiple tasks simultaneously vs. one by one and watching the execution time drop from 6 seconds to 2 seconds.  Level 3 task with Codveda done! #CodvedaAchievements! Finally put those OS theory concepts (Linux daemons, who? 😂) into real C# code. Biggest wins: Async/await = non-blocking magic ThreadPool = reusing workers like a boss lock = stopping threads from fighting over data Simulated daemons in Windows (feeling powerful) Theory → Practice = Growth 📈 Anyone else remember their first "aha" moment with async programming? #Codveda #CodvedaProjects #CSharp #NeverStopLearning #threading