Python Cheat Sheet: Essential Functions for Beginners

🐍 Python List Operations – The Only Cheat Sheet You'll Need Master lists with these 25+ essential operations: 🔍 Accessing & Finding • list[i] → Get single item by index • list[start:end] → Get multiple items (slicing) • a, b, c = list → Unpack all items into variables • list.index(x) → Find position of first item with value x • x in list → Check if value x exists (True/False) 📊 Analyzing & Counting • len(list) → Total number of items • list.count(x) → Count how many times value x appears • max(list) / min(list) → Find highest/lowest values ✏️ Modifying Lists • list.append(x) → Add item x to the end • list.insert(i, x) → Insert item x at index i • list.extend(other_list) → Add items from another list • list[index] = new_value → Change item at specific index 🗑️ Removing Items • list.pop(i) → Remove and return item at index i (default last) • list.remove(x) → Remove first occurrence of value x • list.clear() → Remove all items 🔄 Sorting & Copying • list.sort() → Sort list in place (ascending) • list.reverse() → Flip order in place • new_list = sorted(list) → Get sorted copy • copy_list = list.copy() → Create a shallow copy ⚙️ Iteration & Processing • enumerate(list) → Iterate with index and value • [fn(x) for x in list if condition] → List comprehension (filter + transform in one line) • zip(list_a, list_b) → Pair items from two lists 💡 Pro tip: List comprehension is the most elegant Python feature. Master it and you'll write cleaner, faster code. #Python #PythonLists #CodingCheatSheet #DataStructures #LearnPython

Same condition. Same variables. Different result… depending on how you write it. 🤯 This is where Python stops being “easy” and starts being precise. 🧠 Today’s concept: Truthiness, Short-Circuiting & Operator Precedence Three small ideas. Massive impact. # 1. Truthiness (Not just True/False) data = [] if data: print("Has data") else: print("Empty ❌") 👉 Empty values ([], {}, "", 0, None) are False 👉 Everything else is True # 2. Short-Circuiting (Python stops early) def check(): print("Checking...") return True result = False and check() print(result) 👉 Output: False 👉 check() NEVER runs Because: False and anything → already False Python doesn’t evaluate further # 3. OR short-circuit behavior def fallback(): print("Fallback executed") return "Default" value = "Data" or fallback() print(value) 👉 Output: "Data" 👉 fallback() NEVER runs Because: True or anything → already True # 4. Operator Precedence (Silent bugs ⚠️) a = True b = False c = False result = a or b and c print(result) 👉 Output: True Because Python reads it as: a or (b and c) NOT: (a or b) and c ⚠️ Real-world bug pattern # Looks correct, but isn't if user == "admin" or "manager": print("Access granted") 👉 ALWAYS True ❌ Correct way: if user == "admin" or user == "manager": 💡 Advanced takeaway: and → returns first False or last True value or → returns first True value Conditions don’t always return True/False—they return actual values #Python #AdvancedPython #CodingJourney #LearnInPublic #100DaysOfCode #SoftwareEngineering #Debugging #TechSkills

You might want to take a look at this, Everybody says NumPy is faster than Python List. But, How fast ?? Well I looked into it !! So, here is the overhead of every value you use in Python. Let's say you use a value 42. Here is the detailed overhead. ob_refcnt - 8 bytes (For garbage collection, if reference count is zero, then python just deletes it from RAM) ob_type - 8 bytes (For storing what datatype that value belongs to, here that's integer) ob_digit - 8 bytes (For the actual value - 42). Therefore, 24 bytes for each value. Let's take it a step further. Say you have a 4 values to store just [1, 2, 3, 4] and Let's compare Python list vs NumPy array. Python List : Stores Pointers not the actual values and Hence, you need a list of pointers first, each pointer in the "pointer list" points to the actual value that is scattered across different locations of RAM. So, in-order to store 4 elements. 4 x 8 = 32 (pointer list) 4 x 24 = 96 (actual values) Therefore, 32 + 96 = 128 Bytes. NumPy arrays : It's contiguous and also homogeneous. Also, we don't have pointers model. Here we store actual values next to each other. Thus, giving us a easy traversal using strides. 4 x 8 = 32 Bytes. NumPy can store raw values directly because it enforces a single dtype. Since every element is the same size, it can locate any element using simple math (base + index × itemsize) instead of pointers. Python lists allow mixed types and that's exactly what forces the pointer model. Note: I am only comparing the storage models here. Both Python lists and NumPy arrays have their own object overhead which I've intentionally left out to keep the comparison clean. Apart from storage models. There is another reason why NumPy is so powerful in numerical computations and that is vectorization Vectorization in NumPy : When you do np.sum(a), NumPy runs optimized C code across the entire array in one shot no Python interpreter involved. A Python loop hits interpreter overhead on every single element. That's the real reason NumPy can be 10-100x faster for numerical operations. There is reason why this guy is named as "Numerical Python" !!

🚀Today I explored another important concept in Python — Strings 💻 🔹 What is a String? A string is a sequence of characters used to store text data. Anything written inside quotes (' ' or " ") is considered a string in Python. 🔹 How Strings Work: 1️⃣ Each character has a position (index) 2️⃣ We can access characters using indexing 3️⃣ We can extract parts of a string using slicing 4️⃣ We can modify output using built-in methods 👉 Flow: Text → Access/Manipulate → Output 🔹 Operations I explored: ✔️ Indexing Accessing individual characters using position ✔️ Slicing Extracting a part of the string ✔️ String Methods Using built-in functions like upper(), lower(), replace() 🔹 Example 1: Indexing & Slicing text = "Python" print(text[0]) # P print(text[-1]) # n print(text[0:4]) # Pyth 🔹 Example 2: String Methods msg = "hello world" print(msg.upper()) print(msg.replace("world", "Python")) 🔹 Key Concepts I Learned: ✔️ Indexing (positive & negative) ✔️ Slicing ✔️ Built-in string methods ✔️ Immutability (strings cannot be changed directly) 🔹 Why Strings are Important: 💡 Used in user input 💡 Data processing 💡 Text manipulation in real-world applications 🔹 Real-life understanding: Strings are everywhere — from usernames and passwords to messages and data handling in applications Learning step by step and gaining deeper understanding every day 🚀 #Python #CodingJourney #Strings #Programming

🧠 Python Concept: strip(), lstrip(), rstrip() Clean your strings like a pro 😎 ❌ Problem text = " Hello Python " print(text) 👉 Output: " Hello Python " 😵💫 (extra spaces) ❌ Traditional Way text = " Hello Python " text = text.replace(" ", "") print(text) 👉 Removes ALL spaces ❌ (not correct) ✅ Pythonic Way text = " Hello Python " print(text.strip()) # both sides print(text.lstrip()) # left only print(text.rstrip()) # right only 🧒 Simple Explanation Think of it like cleaning dust 🧹 ➡️ strip() → clean both sides ➡️ lstrip() → clean left ➡️ rstrip() → clean right 💡 Why This Matters ✔ Clean user input ✔ Avoid bugs in comparisons ✔ Very useful in real-world apps ✔ Cleaner string handling ⚡ Bonus Example text = "---Python---" print(text.strip("-")) 👉 Output: "Python" 🐍 Clean data, clean code 🐍 Small functions, big impact #Python #PythonTips #CleanCode #LearnPython #Programming #DeveloperLife #100DaysOfCode

I used to think strings were the “easy” part of Python… today proved me wrong. 🐍 Day 04 of my #30DaysOfPython journey was all about strings, and honestly, this topic felt way more powerful than I expected. A string is basically any data written as text — and it can be written using single quotes, double quotes, or triple quotes. Triple quotes also make multiline strings super easy. Today I explored: 1. len() to check length 2. Concatenation to join strings together 3. Escape sequences like \\n, \\t, \\\\, \\', \\" 4. Old style formatting with %s, %d, %f 5. New style formatting with {} 6. Indexing and unpacking characters 7. Reversing a string with str[::-1] And then came the string methods… that part felt like unlocking a toolbox: capitalize(), count(), startswith(), endswith(), find(), rfind(), format(), index(), rindex(), isalnum(), isalpha(), isdigit(), isnumeric(), isidentifier(), islower(), isupper(), join(), strip(), replace(), split(), title(), swapcase() What hit me today was this: strings are everywhere. Names, messages, input from users, file data, logs, even the little things we ignore at first. So yeah — not “just text.” More like one of the most important building blocks in programming. Github Link - https://lnkd.in/gUkeREkz What was the first Python topic that looked simple but turned out to have way more depth than expected? #Python #LearnPython #CodingJourney #30DaysOfPython #Programming #DeveloperJourney

I wrote just one line of Python code, and it worked. That’s when I realized something. Python is not just code, it’s instructions that bring ideas to life. Let me explain it like I’m explaining to a baby. Imagine you have a robot 🤖 You tell the robot: “Bring water” The robot follows your instruction step by step and that’s exactly what Python implementation is. What is Python Implementation? It simply means, writing instructions (code) And Python understands it Then executes it step by step For example, If I write, print("Hello, Precious") Python doesn’t argue. It doesn’t guess. It simply says, “Okay, let me display this.” And it shows, "Hello, Precious" But here’s what really blew my mind, Python doesn’t just run code. It reads it Interprets it Executes it immediately That’s why Python is called an interpreted language. Why this matters for Data Analysis As someone who have learn, Excel, SQL, Tableau and now Python I’m realizing that python is where everything comes together. Data cleaning, Data analysis, Automation, Visualization. All in one place. I used to think, “Learning tools is enough” Now I know that understanding how they work is the real power. If you’re learning Python or planning to, what was your first “aha” moment? Let’s talk 👇 #Python #DataAnalytics #LearningInPublic #SQL #Excel #Tableau #Programming #TechJourney #BeginnerInTech #DataScience #CareerGrowth

Python codebases that break under pressure all share one thing in common. The developer skipped the fundamentals. Not the syntax. Not the frameworks. Not the libraries. The fundamentals. Arrays. Sets. Hash Maps. Trees. Queues. The building blocks that every great Python developer has locked in. Here's the pattern I keep seeing 👇 --- Developers who skipped DSA fundamentals: ❌ Use a list when a set would be 100x faster ❌ Write nested loops when one pass is enough ❌ Reach for a new library when the right structure solves it ❌ Hit performance walls they can't explain — let alone fix ❌ Spend days debugging what should take minutes to trace Developers who know their DSA fundamentals: ✅ Look at a problem and immediately know the right tool ✅ Write code that scales from 100 to 10,000,000 records ✅ Debug faster because they understand what's happening underneath ✅ Ship cleaner, leaner solutions — less code, more impact ✅ Never fear a technical interview because they think in structures --- The irony? Everyone wants to learn the latest Python framework. FastAPI. LangChain. PyTorch. But the developers who master those tools fastest — are the ones who understood the fundamentals first. Because frameworks change every year. Fundamentals don't. A list in Python is still a dynamic array. A dict is still a hash map. A set still gives you O(1) lookup. These truths were built into the language in 1991. They'll still be true in 2035. --- If you're learning Python right now: Don't rush to the shiny stuff. Spend one week deeply understanding Arrays and Lists. Spend one week on Hash Maps and Sets. Spend one week on Trees and Graphs. That one month will compound into years of better code. Fundamentals aren't the starting point. They're the competitive advantage. --- 💬 What's the one DSA concept that changed how you write Python? I read every comment — drop it below. 👇 ♻️ Repost this for every developer in your network still chasing frameworks. They need to see this first. 👉 Follow for practical Python + DSA content — built for developers who want to go deep. #Python #DSA #DataStructures #PythonProgramming #SoftwareEngineering #CodingTips #LearnToCode #TechCareer #BuildInPublic #100DaysOfCode

OrJSON looks like a small optimization. Until you realize how much time your API spends just serializing JSON. In many Python APIs, the bottleneck isn’t only the database or the LLM. Sometimes it’s the most invisible step: turning Python objects into JSON. What is OrJSON? A high-performance JSON library for Python, written in Rust. It replaces the default json module and focuses on one thing: speed. It: → serializes faster → deserializes faster → supports dataclass, datetime, numpy, UUID out of the box → returns bytes instead of str So what’s happening under the hood? The idea is simple: optimize the hottest path in your API. → less overhead per operation → less work per payload → faster UTF-8 writing And it shows. In its own benchmarks: → dumps() can be ~10x faster than json → loads() can be ~2x faster Where this actually matters: → large payloads → APIs returning a lot of JSON → RAG metadata, events, telemetry → long lists Now the part most people ignore: Trade-offs. → orjson.dumps() returns bytes, not str → no built-in file read/write helpers → not always a perfect drop-in replacement → holds the GIL during serialization So when should you use it? → large responses → heavy metadata → serialization shows up in profiling And when won’t it help? → DB is your bottleneck → LLM latency dominates → responses are small → network / I/O dominates OrJSON won’t magically make your API fast. But if serialization is on your hot path, it’s one of the highest ROI optimizations you can make.

I used to write extra code for things Python could do in one line. Loops for indexing. Manual swaps for reversing. Temporary variables for pairing data. It worked… but it wasn’t elegant. Then I started really understanding Python lists and its built-in functions — and it honestly felt like upgrading the way I think. The first time I used sort(), I realized I didn’t need to reinvent sorting logic every time. But more importantly, I learned that how you sort matters — like using a custom key instead of forcing the data to fit your logic. reverse() taught me something subtle. There’s a difference between changing the original list and creating a new one. That distinction sounds small, but it matters a lot when you're debugging or working with shared data. Then came zip() — and this one completely changed how I handle multiple lists. Instead of juggling indexes, I could iterate cleanly over related data. It made my code feel more readable, almost like telling a story instead of solving a puzzle. And enumerate()… this replaced so many messy loops. No more manual counters. Just clean, intentional iteration with both index and value. What really stood out to me wasn’t just shorter code — it was clearer thinking. I stopped asking, “How do I write this logic?” And started asking, “What’s the cleanest way Python already supports this?” That shift matters a lot in interviews and real projects. Because good code isn’t just about working — it’s about being readable, maintainable, and efficient. Now when I solve problems, I try to use built-ins wherever it makes sense. Not as shortcuts, but as tools that reflect a deeper understanding of the language. Still learning, still improving — but definitely writing better code than I was yesterday.