HAMZA ROMDHANI’s Post

Moving from Manual to Automated: My Python File Organizer I’ve been spending my time lately diving deep into Python fundamentals, and I just finished a project that perfectly bridges the gap between basic syntax and functional automation: a File Organizer script. The goal was simple: take a cluttered directory and instantly sort files into category-specific folders (Images, Docs, Media, etc.) based on their extensions. What I focused on in this build: Scalable Data Structures: Instead of a simple key-value pair, I implemented the 'extension_map' as a dictionary of lists. This makes the script incredibly easy to maintain and scale as I add more file types. Modern Path Handling: I used 'pathlib' for object-oriented path manipulation. It’s cleaner, more readable, and ensures the script works across Windows, macOS, and Linux. The DevOps Mindset: Beyond just writing the code, I focused on "idempotency" using .mkdir(exist_ok=True) so the script can run repeatedly without errors, and implementing error handling to manage files that are currently in use. This project was a great exercise in nested iteration and dictionary manipulation. It’s a small step, but these are the building blocks for the larger automation and orchestration tasks I’m working toward in Cloud DevOps. Next up: Adding logging to track file movements and perhaps setting this up as a scheduled task! #Python #DevOps #Automation #CloudEngineering #CodingJourney #PythonCrashCourse #SoftwareDevelopment

🚀 Automated Jenkins Upgrade with Python – No Manual Effort! Keeping Jenkins up-to-date is critical for security and stability… but let’s be honest — doing it manually is boring and error-prone 😅 So I built a Python script that: ✅ Fetches the latest LTS version directly from Jenkins ✅ Detects the currently running version using Java ✅ Compares versions intelligently ✅ Downloads the latest WAR file automatically ✅ Safely stops Jenkins, updates the WAR, and restarts it 💡 Bonus: Added detailed validation logs at every step for better debugging and reliability. This is a simple yet powerful automation that can save time for DevOps teams managing multiple Jenkins instances. 🔧 Tech Stack: Python 🐍 Linux (systemctl) Jenkins WAR deployment 📌 Why this matters: Automating routine maintenance tasks = Less downtime + More productivity Would love your thoughts 👇 How are you managing Jenkins upgrades in your environment? #DevOps #Jenkins #Automation #Python #SRE #Cloud #CI_CD #InfrastructureAsCode

🚀 Bash vs PowerShell vs Python vs Go — Simple Thinking for SREs (with when to switch) Most engineers ask: Which language should I use? Better question: When should I STOP using one and switch to another? 🔹 Bash = Glue Best for: Quick scripts, CI/CD, chaining commands ⚠️ Limitations: Hard to manage complex logic Weak error handling Debugging becomes painful 🔁 Switch when: Script grows beyond ~100–150 lines You need conditions, retries, or structured data 👉 Move to: Python 🔹 PowerShell = Windows Automation Best for: Windows / Azure infra ⚠️ Limitations: Verbose Not ideal for Linux-heavy or distributed systems Slower for large-scale automation 🔁 Switch when: You need cross-platform support You’re building scalable backend tools 👉 Move to: Python or Go 🔹 Python = Brain (Logic + Automation) Best for: APIs, automation, integrations ⚠️ Limitations: Slower execution GIL limits parallelism Dependency/version issues 🔁 Switch when: Performance becomes a bottleneck You need high concurrency or low latency 👉 Move to: Go 🔹 Go = Engine (Performance + Scale) Best for: High-performance systems, agents, services Used in: Docker Kubernetes Terraform ⚠️ Limitations: More code to write Less flexible than Python Slower for rapid prototyping 🔁 Switch when: You need quick iteration or scripting 👉 Move to: Python 💡 Real-world SRE stack evolution: Bash → Python → Go (Use PowerShell only if your ecosystem requires it) 🧠 Final insight: Don’t think “Which language is best?” Think: 👉 “At what point does this tool become a liability?” That’s where senior engineering starts. What’s something you’ve outgrown recently? 👇 #DevOps #SRE #Cloud #Engineering #Happyengineering

Dockerfile helps in building the image, and docker-compose helps in running multiple containers together. Small concepts, but very useful in real projects 🚀 #DevOps #Learning #Kubernetes #Docker #CloudComputing #Azure #AWS #Terraform #CI_CD #CloudEngineering #SoftwareEngineering #Linux #Python #DevOpsEngineer #CloudEngineer #OpenToWork #Hiring #JobSearch   #TechJobs #ITJobs #CareerGrowth #Learning #Tech #Programming

Deploying QR Generator to Azure App Service Steps: • Created App Service • Selected Python runtime • Configured pipeline deployment • Connected service connection • Enabled auto deployment Now every push deploys automatically. This is production-like setup. #AzureAppService #Azure #DevOps #CloudProject

[Azure Updates] [Launched] Generally Available: Microsoft Agent Framework 1.0. Microsoft Agent Framework is now version 1.0 for both .NET and Python, with stable APIs and a long-term support commitment. Agent Framework 1.0 supports multi-agent orchestration, multi-provider model support, and cross-runtime interoperability via A2A an #azure #azureupdates https://lnkd.in/esqS8KXe

Kubernetes made simple (finally understood it this way) ☸️ When I started learning Kubernetes, everything felt confusing — pods, nodes, clusters, YAML... too many terms. But then I looked at it as a lifecycle, and everything started making sense. Here’s the easiest way to understand it: 🔹 Step 1: Write Code You build your application (Java, Python, Node.js, etc.) 🔹 Step 2: Build Image Package your app into a Docker image 🔹 Step 3: Push Image Store it in a container registry (Docker Hub / ECR) 🔹 Step 4: Deploy to Kubernetes Use YAML or Helm to deploy your app 🔹 Step 5: Run Application Kubernetes creates Pods and runs your app 🔹 Step 6: Scale & Heal Auto scaling + self-healing (if a pod fails, it restarts automatically) 🔹 Step 7: Update Rolling updates with zero downtime 🔹 Step 8: Monitor Track performance using Prometheus & Grafana 💡 The real power of Kubernetes: ✅ No manual deployments ✅ Automatic scaling ✅ Self-healing systems ✅ High availability In simple terms, Kubernetes is like a smart manager that runs your application without you constantly watching it. Once you see it as a flow instead of complex concepts, everything becomes easier. #kubernetes #aws #k8s #devops

DevOps looks easy… until production says “hello” 😅 From the outside, it’s all: ☁️ AWS dashboards 🤖 Python automation 🌐 fancy web UIs ⚙️ clean CI/CD pipelines Everything looks smooth… Like you just click buttons and things deploy themselves 🚀 But then… 🔥 Production goes down. And suddenly you’re: ➡️ SSH’ing into servers like a hacker ➡️ reading logs like a detective ➡️ googling errors like your life depends on it ➡️ typing random Linux commands hoping one works 😭 At this point… No dashboards. No UI. No automation saving you. Just you… and the terminal. That’s when you understand: 🐧 Linux is not optional 💻 Bash is not optional ⚙️ CLI is not optional They’ve been there all along… running everything… silently. Real DevOps lesson: You can avoid the terminal in the beginning… But don’t worry— 👉 it will find you eventually. ⸻ #DevOps #Linux #Bash #CloudComputing #AWS #TechHumor #CloudEngineer #SRE #Automation

Day 7 of My DevOps Learning Journey! Today, I built my first real DevOps-style automation script using Python — a Server Health Monitoring Tool. This was a big step from learning basics to actually creating something practical and useful. 💡 What I implemented: 1. Read multiple servers from a file 2. Automated ping checks using Python (subprocess) 3. Determined server status (UP / DOWN) 4. Extracted response time (latency) using regex 5. Added colored terminal output (green = UP, red = DOWN) 6. Logged results into files for tracking 7. Built a basic alert system when a server is DOWN 📊 Features of my script: Real-time server status monitoring Response time measurement Clean and readable terminal output Logging + alert mechanism (like real monitoring systems) 🧠 This exercise helped me understand how real-world tools like monitoring systems work behind the scenes from executing system commands to parsing outputs and triggering alerts. Step by step, I’m moving from learning concepts to building practical DevOps tools #DevOps #Python #Automation #Monitoring #LearningInPublic #DevOpsJourney #Day6 #Linux

Modern distributed systems don’t just run services… They orchestrate communication between them intelligently. And Service Registry + Discovery is the backbone of that intelligence What tools have you used for service discovery? (Eureka / Consul / Kubernetes?)hashtags #Microservices #SystemDesign #SoftwareEngineering #CloudComputing #DistributedSystems #BackendDevelopment #DevOps #Kubernetes #APIs #SoftwareArchitecture #TechLearning #Programming #Java #SpringBoot