Building a CLI Quiz App with Bash and JSON

Most bash scripts I've seen in the wild are missing three flags that could prevent serious production damage. When I started learning bash scripting as part of my Linux fundamentals work, I came across this: #!/bin/bash set -euo pipefail Two lines. Every professional script should start with them. Here's why each flag matters: -e — Exit immediately if any command fails Without this, bash happily continues running after an error. Your script fails silently on step 3 and keeps executing through step 10. In production that means partial changes, broken state, and damage that's hard to trace. -u — Treat undefined variables as errors Without this, a typo in a variable name becomes an empty string. That empty string gets passed to commands, used in file paths, or fed into conditionals — and your script keeps running with garbage data. -o pipefail — Catch failures inside pipes Without this, a command like: failing_command | grep foo ...returns success because grep succeeded, even though the first command failed. Pipe failures are completely invisible without this flag. Three flags. One line. The difference between a script that fails safely and one that causes silent damage. I wrote six scripts this week working through bash fundamentals — from hello world to argument validation, loops, functions, and error handling. Every single one starts with this header now. Small habits. Production mindset from day one. All notes are documented and versioned in my homelab GitHub repo. #Linux #Bash #DevOps #Scripting #Homelab #BuildInPublic #SRE

Big milestone for my open-source project, selinux-explain! 🚀 After a lot of great feedback from the Linux community, the tool is officially available via COPR for Fedora and EPEL (RHEL, Rocky, AlmaLinux). Deciphering SELinux AVC denials no longer requires downloading static binaries or running heavy Python daemons. You can now get instant, offline, plain-English translations and fix commands directly through your package manager: sudo dnf copr enable matband/selinux-explain sudo dnf install selinux-explain The rule engine now covers PostgreSQL, Docker/Podman, BIND, and Postfix edge cases. Check out the repo and let me know your thoughts! https://lnkd.in/dQjC-Y8z #Linux #DevOps #SELinux #RustLang #Fedora #RedHat #OpenSource

The Ultimate SQL Cheat Sheet From Beginner → Intermediate → Advanced 🔹 Beginner: SELECT, WHERE, ORDER BY 🔹 Intermediate: JOIN, GROUP BY, HAVING 🔹 Advanced: CTEs, Window Functions, Optimization SQL can literally change your salary. #Git #Command #Github #Linux #Programming #Developer #Beginner #Advanced #JavaScript #Coding #DevOps #Workflow w3schools.com JavaScript Mastery GitHub

Nobody told me Bash scripts could fail silently. You run the script. No errors. Looks fine. But half the logic just... didn't execute. I hit this on Day 2 and spent an hour debugging nothing. The fix was 3 words: set -euo pipefail Put it at the top of every script. It forces the script to die the moment something goes wrong instead of quietly skipping it and moving on. This is apparently standard in production. Nobody mentions it in tutorials. Built a Service Health Monitor today using loops, conditionals and traps. Checks services, retries on failure, logs everything with timestamps. Pushed to GitHub. Day 3 tomorrow awk and sed. hashtag#Linux hashtag#Bash hashtag#DevOps hashtag#LearningInPublic

Do you know your file metrics vs. your file changes? 🔍📂 In the Linux terminal, two commands are essential for inspecting files, but they serve completely different purposes. Understanding when to use wc vs. diff is a hallmark of an efficient developer. 📊 wc (Word Count): The Quantifier Think of wc as your file's "Vital Signs" monitor. It doesn't care what is inside the file; it only cares about how much is there. • Use it to count lines (-l), words (-w), or characters (-m). • Pro Tip: Pipe your output into wc -l to quickly count how many processes are running or how many files are in a directory. 🔄 diff (Difference): The Comparator Think of diff as a manual "Git Diff." It analyzes two files line-by-line to tell you exactly what changed. • It tells you which lines were added, changed, or deleted. • Pro Tip: Use diff -u (Unified format) for a much more readable output that looks like a GitHub Pull Request! The Bottom Line: Use wc when you need statistics. Use diff when you need history or comparison. I’ve designed a side-by-side comparison chart to help you keep these straight. Save 📌 it for your next debugging session! #Linux #Bash #DevOps #ProgrammingTips #BackendDeveloper #CodingLife #TerminalShortcuts #SoftwareEngineering

🚀 BDH Linux just hit 3,600+ downloads in its first week on PyPI! Honestly didn't expect this. I built BDH Linux to solve my own problem — wasting 3+ hours setting up a fresh Linux machine every time. Turns out, other developers had the same pain. 📦 What is BDH Linux? An automated setup script that transforms a fresh Manjaro/Arch system into a full backend workspace in under 10 minutes. ✨ Pre-configured with: 🐍 Python 3.12+ & FastAPI 🐘 PostgreSQL & Docker 🎨 Cyberpunk ZSH terminal theme ⚙️ bdh-fastapi-new CLI — instant FastAPI scaffolding ⚡ Philosophy: "Install once — start coding immediately." 3,600 downloads in week 1 is just the beginning. Phase 2 — standalone Arch ISO — is coming. 🔥 🔗 GitHub: https://lnkd.in/gtJMSRbQ Drop a ⭐ if this sounds useful! #OpenSource #Linux #Python #FastAPI #BackendDevelopment #ArchLinux #DeveloperTools

Rust 1.95 dropped yesterday and honestly I'm still procesing it. Three things stood out to me immediately. First — cfg_select! If you've ever written platform-specific code in Rust, you know the pain. Different behavior for Linux vs Windows vs embedded targets meant ugly workarounds or pulling in the cfg-if crate just to stay sane. cfg_select! fixes this cleanly. It's basically a compile-time match on your build configuration. Native to the language now. No extra dependency. No weird syntax. Small addition. Massive quality of life improvement. Second — if-let guards inside match expressions. This one is genuinely exciting for anyone writing complex pattern matching logic. You can now write conditions inside a match arm that themselves do pattern matching. So instead of nesting or restructuring your entire match block just to handle a computed value, you express it right there in the arm where it belongs. Code that used to feel awkward now reads exactly how your brain thinks. Third — the atomic update APIs. AtomicBool, AtomicPtr, and the integer atomics all got update() and try_update() methods. This makes lock-free programming significantly less error-prone. You no longer have to manually write the compare-exchange loop every single time. For anyone doing systems work or concurrency — this one saves real hours. What I love most about this release is what it says about the direction Rust is heading. Every version, the rough edges get smoother. Every release, the things that used to require a crate or a workaround become part of the language itself. Rust isn't just getting more powerful. It's getting more humane. If you haven't already — rustup update stable and go explore. 🦀 What feature from 1.95 are you most excited about? Drop it below. ♻️ Repost to reach every Rustacean who hasn't seen the release notes yet.

I built **PomoWatch** — a minimal Pomodoro timer for the desktop. **Features:** - Work, short break, and long break timers - Configurable session durations and cycle count - Start, pause, and reset controls - Completed session counter - Multiple themes **Install on Ubuntu:** ``` wget https://lnkd.in/gGgUp-WY sudo apt install ./pomowatch_0.1.0-1_all.deb pomowatch ``` Or run from source with uv: ``` uv run main.py ``` Beyond the app itself, the repo is also a practical reference for two things that often feel abstract until you work through them hands-on: **Debian packaging** — the project includes a full `debian/` directory with a working `dpkg-buildpackage` setup. It covers control files, install rules, changelogs, and how to produce a distributable `.deb` that installs cleanly via `apt`. **Docker containerisation of a desktop GUI** — the included `Dockerfile` demonstrates how to run a Tkinter app inside a container by forwarding X11 from the host, including display and audio device passthrough. A useful pattern if you have ever wondered how to containerise GUI apps on Linux. Both are documented in the README and `BUILD_DEB.md` if you want to follow along or adapt them to your own projects. **Source code:** 👉 https://lnkd.in/gNbtVpDQ Open source. Contributions and feedback are welcome. #productivity #opensource #pomodoro #linux #debian #docker #packaging #developers

A moment I'll never forget. Two emails from Greg Kroah-Hartman (Linux Kernel maintainer): "This is a note to let you know that I've just added the patch titled 'staging: greybus: audio: Use sysfs_emit in show functions' to my staging git tree..." "This is a note to let you know that I've just added the patch titled 'staging: greybus: arche-platform: Use sysfs_emit instead of sprintf' to my staging git tree..." My patches are now in the Linux Kernel ! For context: I have a B.Sc. in Agriculture. I'm self-taught in C and systems programming. Six months ago, the idea of contributing to the kernel felt impossible. What changed? I stopped waiting to feel "ready enough" and just started: → Read kernel documentation → Found small issues I could fix → Submitted patches following LKML guidelines → Learned from code review feedback The patches themselves? Converting sprintf to sysfs_emit in the Greybus subsystem—small changes, but they improve kernel safety and follow best practices. Here's what I learned: - Start small (these were ~10 line changes) - Documentation matters (I also contributed watchdog driver docs) - Code review is a gift (Guenter Roeck's feedback taught me more than any tutorial) - Agriculture background ≠ barrier to kernel development To anyone thinking "I'm not experienced enough for open source": You are. Pick a project. Read the contribution guide. Submit something small. The kernel doesn't care about your degree. It cares about your code. #Linux #OpenSource #KernelDevelopment #SelfTaught #TechCareer #FromAgricultureToCode P.S. - If you're interested in contributing to the Linux Kernel, the staging tree (where Greybus lives) has excellent beginner-friendly issues. Start there.

Running Kiro IDE on immutable Linux distros was painful. Not anymore. Kiro is AWS's agentic AI IDE — spec-driven development, agent hooks, and natural language coding assistance. But the official package only ships as .deb and .tar.gz. On immutable distros like Fedora Silverblue, openSUSE MicroOS, or SteamOS? Installing those formats is either impossible or breaks system integrity. So I built kiro-desktop-flatpak. ✨ One-command install — works on any Linux distro 🔄 Auto-updates — GitHub Actions checks for new releases daily 🔒 Sandboxed — no system dependency pollution 🐳 Docker/Podman support — setup guides included for immutable distros Add the remote, install, run. Kiro's built-in updater is disabled; version management happens through Flatpak instead. If you're on an immutable distro or just prefer a clean system, this is for you. Links in the first comment 👇 #Linux #Flatpak #KiroIDE #OpenSource #DevTools #ImmutableLinux #FedoraSilverblue