Python for Loop with Else Block for Cleaner Code

⁉️ Have you ever actually thought about what __name__ == "__main__" means? Most of us wrote it the first time because a tutorial said so. Today I was structuring a small backend service in Python. Nothing flashy yet, just defining the application entry point. And that familiar line showed up again: ✳️ if __name__ == "__main__": It’s simple, but it solves an important architectural problem. In Python, every file is a module. When you execute a file directly: ✳️ python app.py Python assigns: ✳️ __name__ = "__main__" But when the same file is imported somewhere else: ✳️ import app Now: ✳️ __name__ = "__app__" That difference determines whether certain blocks of code run or stay dormant. Why is that useful? Because it lets you: • Keep runtime logic separate from reusable logic • Prevent accidental execution when modules are imported • Define a clear entry point for your application • Expose objects (like a Flask/FastAPI app instance) without auto-starting the server Without this guard, importing a module could trigger execution unintentionally — which becomes messy in larger systems. It’s one of those small Python conventions that quietly enforces better structure. Not flashy. But foundational. #Python #BackendDevelopment #SoftwareEngineering #Architecture

What can’t we do with Python? 🤔 Every time I think I’ve explored enough… Python casually unlocks another door. This week, I stumbled upon a library called FreeSimpleGUI — a lightweight way to build desktop applications without diving into heavy frameworks. Curiosity did what it always does. I couldn’t ignore it. So instead of just reading the docs, I built something simple: 👉 A To-Do List desktop application. Nothing fancy. Just: Add tasks Edit tasks Mark complete Clean, minimal UI And honestly? The result was way better than I expected. No complex boilerplate. No overwhelming setup. Just pure Python doing what it does best — making developers feel powerful. Sometimes we think: Python is for data science. Python is for automation. Python is for ML. Python is for backend. But then it quietly whispers: "Hey, I can build desktop apps too." 😄 The best part? You can prototype a working desktop app in hours, not days. 🎥 I’ve attached a short demo video below. 💻 GitHub link is in the comments if you'd like to explore the code: https://lnkd.in/g4nUBw2m If you’re a Python developer and haven’t explored GUI development yet — this might be your sign. What’s the most unexpected thing you’ve built with Python? #Python #OpenSource #DesktopApp #100DaysOfCode #Learning #Developers #FreeSimpleGUI

Ever wondered how Python knows what to do when you use + between two objects? Or how len() works on your custom class? The answer lies in magic methods (also called dunder methods). These are special methods wrapped in double underscores, and they're what make Python feel like magic. Here are a few that changed how I write code: __init__ — The constructor everyone knows. But it's just the beginning. __repr__ & __str__ — Control how your object looks when printed or logged. Debugging becomes 10x easier when your objects speak for themselves. __len__, __getitem__, __iter__ — Make your custom class behave like a built-in list or dictionary. Your teammates won't even know the difference. __enter__ & __exit__ — Power behind the with statement. Perfect for managing resources like files, DB connections, and locks. __eq__, __lt__, __gt__ — Define what "equal" or "greater than" means for your objects. Sorting a list of custom objects? No problem. __call__ — Make an instance callable like a function. This one unlocks some seriously clean design patterns. The real power of magic methods isn't just the syntax — it's that they let you write intuitive, Pythonic APIs that feel native to the language. When your custom class supports len(), iteration, and comparison naturally, your code becomes easier to read, test, and maintain. What's your favorite magic method? Drop it in the comments #Python #SoftwareEngineering #Programming #PythonTips #CleanCode #BackendDevelopment

Day 2 of my Python journey🐍 Today I moved from basic syntax to handling user interaction and manipulating data. I applied these new concepts by writing a basic terminal-based calculator script. 🖥️ Here is a straightforward breakdown of the Day 2 concepts from the CodeWithHarry playlist: ⌨️ User Input: Learned to use the built-in input() function to capture data directly from the terminal console. 🔄 Typecasting: Coming from a JavaScript background where types are often coerced automatically, Python is stricter. I learned that inputs are received as strings by default and must be explicitly converted using functions like int() or float() before performing calculations. ✂️ String Slicing & Methods: Explored how Python handles text data, specifically using bracket syntax [start:end] for slicing, which is a clean and efficient way to extract substrings. Progress is steady. 📈 For those working across different languages, do you prefer stricter typing (like Python) or looser typing (like standard JavaScript) for daily tasks? 👇 #Python #LearningInPublic #SoftwareEngineering #FrontendDev #CodeWithHarry

🐍 A simple Python trick to combine related lists into a dictionary 👇 🔹 What this code does: 👉 Combines two related lists (names and scores) into a single dictionary using Python’s zip() function 🧩 👉 Each name becomes a key and each score becomes its value. 🔹 Why we use this ✨ Avoids writing manual loops ✨ Keeps the code short, clean, and readable ✨ Converts raw list data into structured key-value pairs 🔹 Where this is useful: 📊 Data handling and transformation 🤖 Automation scripts 🌐 Backend logic and API response processing 👩🎓 Use cases like student marks, user records, product prices, and configuration data 🔹 What we can build using this: 🧾 Structured datasets for reports and validation 🗄️ Database-ready or JSON-ready data 📈 Inputs for analytics and dashboards Python says: “Give me two lists, I’ll neatly pack them into a dictionary.” 🐍📦 📤 Result (Output): {'Alice': 80, 'Bob': 90, 'Charlie': 85} ❓ Your turn: How do you usually combine related lists in Python? #Python #CodingTips #DataHandling #Automation #DeveloperLife

One-Line Sorting with Custom Lambda Key (Sort Integers by The Number of 1 Bits) 💯 || O(N log N) || Just tackled a fun bit-manipulation and sorting problem on LeetCode (Problem 1356), and I wanted to share a super clean, Pythonic way to solve it! 🐍 🎯 The Problem: Sort an array of integers based on the number of 1s in their binary representation. If two numbers have the same number of 1s, sort them by their decimal value. 💡 The Approach: Instead of writing a complex custom comparator, Python’s built-in sorting handles multi-level conditions beautifully. By passing a list [primary_condition, secondary_condition] to the key argument, Python sorts by the first element and automatically falls back to the second if there's a tie. Here is the one-liner: Python class Solution: def sortByBits(self, arr: List[int]) -> List[int]: return sorted(arr, key=lambda x: [bin(x).count('1'), x]) 📊 Complexity: Time: O(N log N) — Python's Timsort algorithm does the heavy lifting, and counting bits for 32-bit integers takes O(1) time. Space: O(N) — Using sorted() creates a new list. Pro-Tip: If you want to optimize for space, you can swap sorted(arr, ...) for arr.sort(...) to sort the array in-place! What is your favorite Python built-in function or one-liner tip? Let me know in the comments! 👇 #Python #LeetCode #Algorithms #CodingInterviews #SoftwareEngineering #DataStructures

The Python "Gotcha" That Every Developer Hits Once Ever had a function return data from a previous call that you never asked for? You might be falling for the Mutable Default Argument trap. It’s a classic behavior that still catches experienced devs off guard. Take a look at the comparison below 👇 The Issue: Code 1 ❌ When you use a mutable object like a list or dict as a default argument, Python evaluates that expression only once — at the moment the function is defined. It doesn't create a new list for every call. Instead, it reuses the same object in memory. The result? Your data "leaks" from one function call to the next, creating a persistent state you probably didn't want. The Fix: Code 2 ✅ To ensure a clean slate every time, use the Late Binding pattern: Set the default value to None Initialize the mutable object inside the function body This ensures that a brand-new list or dictionary is created only when the function actually runs. ⚡ Key Takeaway Avoid using [], {}, or set() as default arguments. Stick to None or immutable types (strings, ints, tuples) to keep your code predictable and side-effect-free. It’s a small implementation detail, but mastering it saves hours of debugging "ghost data" in your backend. #Python #PythonDeveloper #Programming #SoftwareEngineering #BackendDevelopment #CodingTips #CleanCode #Debugging #ProgrammingTips #DevCommunity #SoftwareDevelopment

Day 2 of 10: Mastering Python's Data Structures 🐍⚙️ Day 2 of my 10-day Python sprint is in the books! Today, I moved past the basic syntax and dove straight into how Python organizes and handles data. Coming heavily from a JavaScript background, it is fascinating to see how Python maps these concepts. Here are my biggest takeaways from today's session: 📌 Dictionaries: These are collections of key-value pairs. They feel right at home—basically native JSON objects—but they come packed with powerful built-in methods out of the box.📌 Tuples: This is a completely immutable data type. Having a built-in structure that cannot be changed after creation is a massive win for writing secure, predictable backend logic.📌 Sets: These are collections of non-repetitive elements. They make handling unique values and mathematical operations (like unions and intersections) incredibly fast and elegant compared to writing manual filter loops.📌 Lists: Highly versatile containers to store a set of values of any data type. As I continue building AI-integrated SaaS products, having a rock-solid grasp on these exact structures is non-negotiable for efficiently handling API payloads and formatting data for LLM context windows.   Python engineers: In your production code, do you find yourself defaulting to Lists, or do you strictly use Tuples when you know the data shouldn't change? Let’s debate below! 👇 #Python #SoftwareEngineering #BuildInPublic #CodeWithHarry #10DayChallenge

200 seconds to process a 20-page PDF. Users complained. I blamed the embedding model. The model wasn't the problem. My code was. Three small fixes cut processing time to 6 seconds. 10x faster. No new hardware. No model changes. Just better async Python. 𝗧𝗵𝗲 𝗽𝗮𝘁𝘁𝗲𝗿𝗻: Most slow RAG systems have the same handful of problems. Sequential loops pretending to be async. Synchronous code blocking the event loop. Python doing work the database should handle. Fix #1: Parallel embedding with asyncio.gather(). 100 sequential API calls became 100 parallel calls. 20 seconds → 200ms. Fix #2: Non-blocking SQS with asyncio.to_thread(). My boto3 calls looked async but weren't. They froze the entire process while waiting for AWS. Wrapping them in threads freed the event loop. Fix #3: Database-level filtering. I was fetching 100 results from Qdrant and filtering in Python. Embarrassing. The fix was uncommenting old code and fixing one bug. The takeaways: → Use asyncio.gather() for independent async operations → Wrap sync code with asyncio.to_thread() to avoid blocking → Push filtering to the database, not Python loops → Check for sequential waits in async functions I turned this into a full article with code examples, before/after diagrams, and when to apply each pattern. Link in comments 👇

𝐍𝐮𝐦𝐏𝐲 𝐁𝐨𝐨𝐥𝐞𝐚𝐧 𝐓𝐫𝐚𝐩 I’m still at the very beginning of my Python journey. But even with my tiny amount of experience, I already hit a subtle NumPy trap that can easily sneak into real code. Python is full of surprises — even at the very beginning It happens when you create an untyped NumPy array and fill it with a function that should return booleans… …but sometimes returns 𝙉𝙤𝙣𝙚 when processing fails. At first, you expect a clean boolean array — because the function normally returns 𝙏𝙧𝙪𝙚 or 𝙁𝙖𝙡𝙨𝙚. But NumPy has other plans. Here’s the trap 👇 🟥 𝟏) 𝐔𝐧𝐭𝐲𝐩𝐞𝐝 𝐚𝐫𝐫𝐚𝐲 + 𝐚 𝐟𝐮𝐧𝐜𝐭𝐢𝐨𝐧 𝐭𝐡𝐚𝐭 “𝐬𝐡𝐨𝐮𝐥𝐝” 𝐫𝐞𝐭𝐮𝐫𝐧 𝐛𝐨𝐨𝐥𝐞𝐚𝐧𝐬 𝒂𝒓𝒓 = 𝒏𝒑.𝒆𝒎𝒑𝒕𝒚(10) # 𝒏𝒐 𝒅𝒕𝒚𝒑𝒆  𝒂𝒓𝒓[𝒊] = 𝒎𝒚_𝒇𝒖𝒏𝒄() # 𝑻𝒓𝒖𝒆 / 𝑭𝒂𝒍𝒔𝒆 ... 𝒐𝒓 𝑵𝒐𝒏𝒆 You expect a clean boolean array because the function usually returns 𝙏𝙧𝙪𝙚/𝙁𝙖𝙡𝙨𝙚. But if even one value is 𝙉𝙤𝙣𝙚, NumPy must pick a type that can hold all values. 🟦 𝟐) 𝐍𝐮𝐦𝐏𝐲 𝐬𝐢𝐥𝐞𝐧𝐭𝐥𝐲 𝐬𝐰𝐢𝐭𝐜𝐡𝐞𝐬 𝐭𝐨 𝐝𝐭𝐲𝐩𝐞=𝐨𝐛𝐣𝐞𝐜𝐭 𝒂𝒓𝒓𝒂𝒚([𝑻𝒓𝒖𝒆, 𝑭𝒂𝒍𝒔𝒆, 𝑵𝒐𝒏𝒆, ...], 𝒅𝒕𝒚𝒑𝒆=𝒐𝒃𝒋𝒆𝒄𝒕) Impact: no vectorization logical operations break masks behave unpredictably performance collapses You think you have a NumPy boolean array. You actually have a Python object array. 🟩 𝟑) 𝐓𝐡𝐞 𝐬𝐢𝐥𝐞𝐧𝐭 𝐜𝐨𝐧𝐯𝐞𝐫𝐬𝐢𝐨𝐧 𝐭𝐫𝐚𝐩 Trying to fix it: 𝒂𝒓𝒓 = 𝒏𝒑.𝒆𝒎𝒑𝒕𝒚(10, 𝒅𝒕𝒚𝒑𝒆=𝒃𝒐𝒐𝒍)  𝒂𝒓𝒓[𝒊] = 𝒎𝒚_𝒇𝒖𝒏𝒄() NumPy converts: 𝑵𝒐𝒏𝒆 → 𝑭𝒂𝒍𝒔𝒆 (silently) Impact: 👉you lose the meaning of “no result” 👉your data becomes wrong 👉the bug becomes invisible ⭐ 𝐓𝐚𝐤𝐞𝐚𝐰𝐚𝐲 Same code. Same function. Two completely different arrays. NumPy’s dtype inference can hide subtle bugs — and I found this one with almost no Python experience. 𝐂𝐮𝐫𝐢𝐨𝐮𝐬 𝐭𝐨 𝐤𝐧𝐨𝐰: 👉 Have you ever run into this behavior? 👉 Or another NumPy dtype surprise? #python #numpy #datascience #cleanCode #devTips #programming