Upgrade to Python f-strings for cleaner code

𝐍𝐮𝐦𝐏𝐲 𝐁𝐨𝐨𝐥𝐞𝐚𝐧 𝐓𝐫𝐚𝐩 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

🐍 I didn’t understand Python performance… until I learned THIS. I always heard: “Python is slow.” But no one explained *why*. Then I hit a real backend issue. Same logic. Same data. Different performance. That’s when it clicked 👇 🧠 Python is not slow. ❌ WRONG. The way we USE Python can be slow. Here’s what’s happening behind the scenes 👀 • Python runs on an interpreter • Code executes line by line • Each operation has overhead • Loops + heavy computation = pain 🐢 Example: Doing millions of calculations in a Python loop ❌ Letting optimized C libraries (like NumPy) do it ✅ 💡 The real lesson: ✨ Python shines in I/O (APIs, DB, files, network) ✨ Python struggles with raw CPU-heavy work ✨ Knowing this changes how you design systems Now I ask before writing code: ❓ Is this CPU-bound or I/O-bound? ❓ Should this be async? ❓ Should this move to another service? Python didn’t fail me. My understanding did. Once you know this, Python becomes a powerful backend weapon 🚀 #Python #BackendDevelopment #SoftwareEngineering #Performance #DeveloperLearning #TechExplained #ProgrammingConcepts

🧠 Python Concept That Runs When Class Is Called: __call__ on Classes Objects can be callable… but classes can customize calls too 👀 🤔 The Surprise When you do: obj = MyClass() Python actually does: obj = MyClass.__call__() 🧪 Example class Logger: def __call__(self, msg): print("LOG:", msg) log = Logger() log("Hello") 🎯 Class instances become functions 🧠 But Classes Themselves Use __call__ class Meta(type): def __call__(cls, *args, **kwargs): print("Creating instance") return super().__call__(*args, **kwargs) class User(metaclass=Meta): pass u = User() ✅ Output Creating instance Metaclass intercepted construction. 🧒 Simple Explanation 🥤 Imagine a vending machine 🥤 Press button → machine runs → gives item 🥤 That press = __call__. 💡 Why This Is Powerful ✔ Factories ✔ Dependency injection ✔ Framework hooks ✔ Callable objects ✔ Advanced APIs ⚡ Real Uses 💻 PyTorch modules 💻 FastAPI dependencies 💻 Decorator classes 💻 DSL builders 🐍 In Python, calling isn’t just for functions 🐍 Classes and objects can redefine what “()” means. 🐍 __call__ is the hook behind that power. #Python #PythonTips #PythonTricks #AdvancedPython #CleanCode #LearnPython #Programming #DeveloperLife #DailyCoding #100DaysOfCode

I spent two weeks implementing every major sorting algorithm from scratch in Python only to prove that Python’s built-in sorted() crushes them all 😅 We all learned the same story: Bubble Sort → Quick Sort → Merge Sort Big-O charts tell us which one is “fastest.” But in real CPython, the story flips. Interpreter overhead changes everything: Expensive object comparisons Function call & recursion costs Memory allocations GC pauses The results surprised even me: • Bubble Sort dies at ~1,000 elements • Insertion Sort quietly wins on small or nearly-sorted data • My best Quick/Merge implementations? 5–150× slower than sorted() (Timsort) And that’s the key. Timsort isn’t just an algorithm. It’s a hybrid, written in optimized C, designed around how real data actually behaves. 📌 The lesson every Python developer should internalize: Understand algorithms deeply — but trust the standard library in production. Reimplementing fundamentals rarely pays off. Solving real problems does. Full deep dive (benchmarks, code, raw data, and why Python changes the rules): 👉 https://lnkd.in/ge2wVaEP Run the benchmarks yourself: 👉 https://lnkd.in/gbyJpCqt What’s the most surprising Python performance quirk you’ve discovered? 👇 #Python #Algorithms #SoftwareEngineering #Performance #CPython #Coding

Day 9: Mastering Type Casting in Python 🐍 Today I explored how Python handles type conversions, and it's more powerful than I initially thought! Type casting lets us convert data from one type to another, which is essential when working with user inputs, APIs, or databases. Key takeaways: Implicit vs Explicit Casting: Python automatically converts some types (like int to float), but we often need to explicitly cast data using functions like int(), str(), float(), and bool(). Real-world scenario: Converting user input (always a string) into integers for calculations, or formatting numbers as strings for display. Common pitfalls I learned to avoid: Not every string can be cast to an integer, and float to int conversion truncates decimals rather than rounding. Code snippet from today: python # User age input age = int(input("Enter your age: ")) # Converting for display price = 49.99 print(f"Price: ${str(price)}") # List to string items = ['apple', 'banana', 'cherry'] print(', '.join(items)) The journey continues! Each day brings new understanding of how Python handles data behind the scenes. #Python #FullStackDevelopment #CodingJourney #100DaysOfCode #LearningToCode #WebDevelopment

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

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 12 of my Python Full-Stack Journey — Mastering Lists! Today I went deep into one of Python's most powerful built-in data structures: Lists. Here's what I covered: ✅ Creating and indexing lists ✅ Slicing (list[1:4], negative indexing) ✅ List methods — append(), extend(), insert(), remove(), pop(), sort(), reverse() ✅ List comprehensions (honestly a game-changer 🤯) ✅ Nested lists and iterating with loops The "aha moment" today? List comprehensions. Instead of writing 4 lines to filter a list, you can do it in ONE: squares = [x**2 for x in range(10) if x % 2 == 0] Clean. Pythonic. Beautiful. 🧠 Lists feel simple at first — but understanding how they work under the hood (mutability, references, shallow vs. deep copy) is where real Python thinking begins. 12 days in. The foundation is getting solid. Drop a 💬 if you're also learning Python — would love to connect and grow together! #Python #100DaysOfCode #FullStackDeveloper #LearningInPublic #PythonJourney #CodeNewbie #SoftwareDevelopment