Python Basics Cheat Sheet

Mastering strings in Python is one of those “small” skills that quietly powers almost everything we build—APIs, data pipelines, web apps, you name it. This week I revisited the fundamentals of Python strings: - Creating and slicing strings to access and update specific parts - Formatting with `format()` to build clean, readable outputs - Leveraging powerful built-in methods like `strip()`, `split()`, `join()`, `find()`, `replace()`, and case conversions (`lower()`, `upper()`, `title()`) to clean and transform text efficiently What struck me again is how much you can do *just* with string methods before reaching for heavier tools. If you’re starting with Python (or even revisiting basics), investing time in string operations is one of the highest-ROI steps you can take as a developer or data professional.

I used to throw everything into a Python list. 🐍 Need to store data? List. Track config values? List. Remove duplicates? List + awkward manual looping. It worked — but it was the programming equivalent of using a Swiss Army knife to cut a steak. So I wrote about it. My latest blog breaks down all 4 core Python data structures — List, Tuple, Set, and Dictionary — and more importantly, teaches you *when* to reach for each one. 📌 Key takeaways: → Lists are your ordered, flexible workhorse — but mutability can bite you → Tuples signal immutability and are faster + hashable (great for dict keys) → Sets handle deduplication and membership checks in O(1) time — huge at scale → Dictionaries are the backbone of almost every real-world Python application The moment you stop defaulting to lists for everything, your code gets faster, cleaner, and easier to reason about. If you're learning Python — or brushing up before interviews — this one's for you. 👇 🔗 [https://lnkd.in/gm2NBypi] #Python #DataScience #MachineLearning #PythonProgramming #100DaysOfCode #DataStructures #Innomatics #InnomaticsResearchLabs #InnomaticsResearchLabs

🧠 Python Concept: map() Apply a function to all items effortlessly 😎 ❌ Traditional Way numbers = [1, 2, 3, 4] squared = [] for num in numbers: squared.append(num * num) print(squared) ✅ Pythonic Way numbers = [1, 2, 3, 4] squared = list(map(lambda x: x * x, numbers)) print(squared) 🧒 Simple Explanation Think of map() like a machine 🏭 ➡️ It takes each item ➡️ Applies a function ➡️ Gives back results automatically 💡 Why This Matters ✔ Cleaner functional style ✔ No manual loops ✔ Useful in data processing ✔ Works great with lambda functions ⚡ Bonus Example names = ["alice", "bob", "charlie"] upper_names = list(map(str.upper, names)) print(upper_names) 🐍 Transform data like a pro 🐍 Let Python do repetitive work #Python #PythonTips #CleanCode #LearnPython #Programming #DeveloperLife #100DaysOfCode

Logic in Python – Understanding and, or, and not! 🔗🐍 Programs aren’t just about calculations—they need to make decisions. That’s where logical operators come in. They let us combine multiple conditions and control the flow of our code. This session was all about mastering the three core logical operators in Python: and, or, and not. Here’s what I learned: --- 🔹 The and Operator · Returns True only if both operands are True. · Otherwise, it returns False. A and B True + True = True True + False = False False + True = False False + False = False ```python print((2 < 3) and (1 < 2)) # True and True → True print((5 > 3) and (2 > 5)) # True and False → False ``` --- 🔹 The or Operator · Returns True if at least one operand is True. · Only False if both are False. A B A or B True + True = True True + False = True False + True = True False + False = False ```python print(True or False) # True print(False or False) # False ``` --- 🔹 The not Operator · Reverses the boolean value. · not True → False · not False → True ```python print(not True) # False print(not False) # True ``` --- ✅ Key Takeaways: · Logical operators work with boolean values and return booleans. · and → all must be true · or → at least one true · not → flips the truth value · You can combine them with relational operators to build complex conditions. --- 💬 Let’s Discuss: Have you ever used and/or in a real project? What’s the most creative condition you’ve built with them? Drop your examples below! 👇 --- 🔖 #Python #LogicalOperators #CodingBasics #LearnToCode #ProgrammingLogic #NXTWave #TechJourney

🚀 Built a simple Python script to clean up my messy Downloads folder! We all download files daily, and things get cluttered fast. So I wrote a quick automation script using Python to organize files into folders like Images, Documents, Archives, etc. 💡 Here’s the code: ```python from pathlib import Path import shutil # Folder to organize source = Path("C:/Users/YourName/Downloads") # File type mapping folders = { ".jpg": "Images", ".png": "Images", ".pdf": "Documents", ".zip": "Archives", ".exe": "Installers" } for file in source.iterdir(): if file.is_file(): folder_name = folders.get(file.suffix.lower()) if folder_name: destination = source / folder_name destination.mkdir(exist_ok=True) shutil.move(str(file), destination / file.name) ``` ⚡ What it does: * Scans your Downloads folder * Detects file types * Creates folders automatically * Moves files to the right place Sometimes, small automations like this can save a lot of time and keep your system organized. #Python #Automation #Coding #Developers #Productivity #Backend

🧠 Python Concept: walrus operator (:=) Assign and use in one line 😎 ❌ Traditional Way data = input("Enter something: ") if len(data) > 5: print(f"You entered {data}") ❌ Problem 👉 Repeating variable 👉 Extra lines ✅ Pythonic Way (:=) if (data := input("Enter something: ")) and len(data) > 5: print(f"You entered {data}") 🧒 Simple Explanation ⚡ Think of := like “assign + use together” ➡️ Store value ➡️ Use it immediately ➡️ No extra lines 💡 Why This Matters ✔ Shorter code ✔ Avoid repetition ✔ Useful in loops & conditions ✔ Advanced Python skill ⚡ Bonus Example while (line := input("Type: ")) != "exit": print(line) 🐍 Write less, do more 🐍 Python gives powerful shortcuts #Python #PythonTips #AdvancedPython #CleanCode #LearnPython #Programming #DeveloperLife #100DaysOfCode

🐍 The most misunderstood line in Python is this: for item in [1, 2, 3]: Most developers think the for loop just "goes through the list". What it actually does: calls iter([1,2,3]) to get an iterator, then calls next() on it repeatedly until StopIteration is raised. That's the entire protocol. Once you understand that, generators click immediately. A generator function with yield IS an iterator — Python implements iter and next automatically. And the magic of yield is that the function pauses at each yield and resumes from there on the next call. Full guide: iterator protocol from scratch, generator functions vs expressions, yield from for delegation, lazy 5-stage file processing pipeline, context managers (enter/exit), @contextmanager, suppress, ExitStack, and send()/throw() for two-way generator communication. A generator expression uses 200 bytes. An equivalent list uses 8MB. For the same data. 📎 Free PDF. Zero pip installs — pure Python standard library. #Python #Generators #Iterators #ContextManagers #PythonProgramming #SoftwareEngineering #CleanCode #BackendDev #Programming

🧠 Python Concept: Mutable vs Immutable Why your data changes… or doesn’t 😳 ❌ Confusing Behavior x = [1, 2, 3] y = x y.append(4) print(x) 👉 Output: [1, 2, 3, 4] 😵💫 🧒 Why? 👉 Lists are mutable (can change) 👉 Both x and y point to same object ✅ Immutable Example x = (1, 2, 3) y = x y = y + (4,) print(x) 👉 Output: (1, 2, 3) ✅ 🧒 Simple Explanation 👉 Mutable = can change 🧱 👉 Immutable = cannot change 🔒 💡 Why This Matters ✔ Avoid unexpected bugs ✔ Important for memory understanding ✔ Used in real-world debugging ✔ Frequently asked in interviews ⚡ Bonus Tip x = [1, 2, 3] y = x.copy() 👉 Now changes in y won’t affect x 🐍 Know your data types 🐍 Small concept, big impact #Python #PythonTips #CleanCode #LearnPython #Programming #DeveloperLife #100DaysOfCode

I did not expect a Python topic about “unique items” to feel this useful… but sets changed that fast. 🐍 Day 7 of my #30DaysOfPython journey was all about sets, and this one felt different because it was less about storing data and more about controlling it. A set is an unordered collection of distinct items. It cannot hold duplicates, which makes it super handy in real-world coding. Today I explored: 1. Creating sets with set() built-in function and {} 2. Checking length with len() 3. Using in to check if an item exists 4. Adding items with add() to add a single item and update() for multiple items 5. Removing items with remove() (raise error if item not present), discard() (does not raise error), and pop() (removes a random item) 6. Clearing a set with clear() 7. Deleting a set with del 8. Converting a list to a set to remove duplicates 9. Set operations like union(), intersection(), difference(), and symmetric_difference() 10. Checking issubset(), issuperset(), and isdisjoint() What made sets interesting to me today was how practical they are when you want uniqueness, comparison, or clean data without duplicates. They may look simple on the surface, but they solve a very specific kind of problem really well. Which Python data type has surprised you the most so far: lists, tuples, or sets? Github Link - https://lnkd.in/eJfTX-HQ #Python #LearnPython #CodingJourney #30DaysOfPython #Programming #DeveloperJourney