Python Logging Module for Professional Error Tracking

Week 2/52: I fired myself from organising my computer. We all have that one folder. The "Downloads" folder. It’s a digital graveyard of random PDFs, installers from 2021, and zip files named image(4).zip. I used to spend hours manually cleaning it up, only for it to get messy again a week later. So for Week 2 of my coding challenge, I decided to automate the chore away. 🚀 Project: Downloads Janitor Pro The Problem: Digital clutter is an "invisible problem." It doesn't break your computer, but it breaks your focus. The Solution: A Python Desktop App that watches my Downloads folder in real-time. - Auto-Sort: If I download an image, it instantly moves to /Images. If I download a PDF, it goes to /Docs. - Auto-Unzip: It detects .zip files, extracts them to a folder, and archives the original. (This is a life saver). - Strict Mode: I added a toggle that forces any unrecognized file into a /Misc folder. My Downloads folder is now permanently empty. The Tech Stack: - Python 🐍 - watchdog library (for file system events) - Tkinter (for the GUI) - Threading (to keep the app responsive while processing files) The Lesson: Week 1 was a 20-line script. Week 2 is a multi-threaded GUI app. The goal of this challenge isn't just to build projects, but to compound complexity. 🔗 Code is live on GitHub: https://lnkd.in/g8_jvYQe 👇 Be honest: How many files are currently sitting in your Downloads folder? #Python #Automation #CodingChallenge #Week2 #52Weeks52Projects #Productivity #OpenSource

🚀 What I Learned Fixing a Broken Python Environment (Windows Case Study). 💡 Sharing this in case it helps someone else avoid the same pain. Over the past few days, while working on a data automation project, I ran into serious issues with: ❌ Virtual environments are conflicting ❌ Packages refusing to install ❌ Jupyter kernels not showing ❌ “Works on my machine” syndrome At first, it was frustrating. Then I realised: this is real engineering work. Here are the key lessons I’m taking forward: 1️⃣ One Project = One Virtual Environment Never reuse environments. Every project gets its own: python -m venv .venv Isolation prevents 80% of dependency problems. 2️⃣ Always Verify Your Interpreter Before installing anything, check: python -c "import sys; print(sys.executable)" If it’s wrong, everything else will be wrong. 3️⃣ Windows Builds Need Special Handling Some libraries (like psutil) try to compile from source and fail without C++ tools. Solution: pip install --only-binary=:all: psutil==5.9.8 Use pre-built wheels whenever possible. 4️⃣ Jupyter Needs Explicit Registration Installing ipykernel is not enough. You must register it: python -m ipykernel install --user --name project Otherwise, notebooks won’t see your environment. 5️⃣ Terminal Context Matters PowerShell ≠ Python. If you’re not inside Python, Python commands won’t work. Use: python -c "..." or a notebook. 💡 The Bigger Lesson Environment management is not “basic stuff”. It’s a core engineering skill. Most production failures start with: ➡️ “It worked on my machine.” Now I always verify my interpreter, venv, and kernel before writing a single line of code. #Python #DataEngineering #LearningInPublic #WindowsDev #VirtualEnvironment #Jupyter #TechCareers #CareerSwitch #BuildInPublic #DevLife

🌟 New Blog Just Published! 🌟 📌 Secure Python Projects: Manage Secrets with .env File 🚀 📖 Keeping secrets is a critical part of building secure software. When you work on Python projects, you often need to use API keys, database passwords, or other sensitive information. If you store...... 🔗 Read more: https://lnkd.in/dQnQ4xdu 🚀✨ #pythonsecurity #environmentvariabl #secretmanagement

Day 96 of Backend/Cloud/DevOps Journey - Debugging bcrypt Compatibility Issues Today was all about real-world debugging. Spent the session troubleshooting a passlib/bcrypt compatibility issue that persisted even after switching Python versions. What I accomplished: • Installed Python 3.12 via Homebrew to replace Python 3.14 (learned that compilation from source takes time due to C extension building) • Discovered the issue wasn't Python version but bcrypt library version incompatibility with passlib • Pinned bcrypt to version 4.0.1 to resolve passlib's internal self-test failures • Successfully tested all auth utilities: hash_password, verify_password, create_access_token, verify_token • Learned why pinning dependency versions in requirements.txt prevents environment inconsistencies across deployments • Updated verify_token() to include algorithms parameter for security best practices Technical insights: • Homebrew's "make" step compiles C source code to machine code which is CPU-intensive and time-consuming • Virtual environments are tied to the Python version that created them—you cannot switch versions without recreating the venv • The bcrypt 72-byte password limit caused passlib's detect_wrap_bug() self-test to fail on newer bcrypt versions (4.1+) • Pinning dependencies (bcrypt==4.0.1) ensures consistent behavior across development, staging, and production environments • The algorithms parameter in jwt.decode() prevents algorithm confusion attacks—always specify explicitly • Real-world debugging often means the obvious fix (switching Python versions) doesn't work and requires deeper investigation • Library compatibility issues are common in production—this is why teams use stable Python versions not bleeding edge Key lesson: When an error persists after the "obvious" fix, dig deeper into the dependency chain. The root cause was bcrypt library version, not Python version. Auth system now fully functional: password hashing with bcrypt salting, password verification, JWT creation with expiration, and token decoding with validation. Next steps: Complete User model in SQLAlchemy, create users table, build registration and login endpoints. #100DaysOfCode #Python #FastAPI #Debugging #bcrypt #DependencyManagement #BackendDevelopment #CloudEngineering #DevOps #LearningInPublic #TechCareer #BuildInPublic

Here’s a demo of my Python command engine in action!🔥🔥🔥 This project is designed to bridge the gap between technical commands and everyday language. Whether it’s scanning your PC, opening apps, checking you IP address or viewing reports, you can simply say it in plain English and the engine executes it for you. The voice recognition feature makes it even more intuitive, giving non‑IT users the power to manage tasks without needing to memorize commands. This is just the demo version — more features and less bugs on the way! #Automation #IT #TlotloMasisi

🚀 Day 11/100: From Logic Puzzles to Network Sockets Today’s Focus: LeetCode 125 (Valid Palindrome): I revisited string manipulation. Instead of clunky loops, I used a Pythonic generator expression: "".join(c.lower() for c in s if c.isalnum()). It’s efficient, readable, and handles "dirty data" exactly like a data processing script should. The "Why" of Networking: I’m officially starting to bridge the gap between Python and DevOps. I wrote a small script using the socket library to check if specific ports are open. The Big Realization: Understanding if a port is "listening" or if a DNS is resolving is just as important as writing an O(n) algorithm. Lesson of the day: When you're too tired to solve a "Hard" problem, solve an "Easy" one. Just don't stop moving. #LeetCode #Python #DevOps #Networking #MCA #ContinuousLearning #100DaysOfCode #CareerTransition

🎙️ Introducing the Python SDK for Pinch API This SDK makes it easy to start using the API, whether you’re prototyping or building a real voice translation system. It supports production-ready pipelines, along with examples and documentation that focus on setup, troubleshooting, and common workflows. The SDK repository is now open source and available on GitHub (link in the comments). The API itself is built to support real-time systems. We’re exposing the underlying primitives so developers can build their own real-time SDKs or integrations on top of it, rather than being locked into a single abstraction. 🫶 Note to the community: we’re happy to review PRs and work with the community. The goal is to make Pinch easier to build on and, over time, surface high-quality integrations directly in our docs. We can’t wait to see what you ship!

🚀 Why writing tests changed how I develop software While working on my latest Python project, I reached a point where adding new features started to feel risky. Not because the logic was complex — but because I could no longer be 100% sure that new changes wouldn’t break existing behavior. That’s where testing stopped being “optional” and became a necessity. By writing unit tests and integration tests: • I fixed a clear target for how my system should behave • I gained confidence to refactor and improve the code • I caught database, schema, and edge-case issues before they became real problems Without tests, development feels like moving forward without knowing whether you’re still on the same page as yesterday. With tests, every change is anchored to a shared and verifiable truth. This part of the project reminded me that tests are not just about finding bugs — they are about maintaining direction, consistency, and trust in your own system. 🐍 Python · SQLAlchemy · Pydantic · Pytest #SoftwareEngineering #Python #Testing #BackendDevelopment #LearningByBuilding