Ansh Kapoor’s Post

Day 10/60 Continuing Chapter 2: Flow Control Continuing Topic l - Making Decisions 2. Code blocks i⁠f⁠ statements don't decide on skipping or running the entire code. They only make decisions about a code block. We use an indentation of two spaces to highlight code blocks, like indenting this display statement. Indentation refers to the space between the code and the code editor's margin. A code block can be more than a one-liner. All lines with the same indentation belong to the same code block. We can see it here when we use  p⁠r⁠i⁠n⁠t⁠(⁠)⁠ to add one more line at the beginning. 🧩Code if True: print ("Look at me!") print("I'm a code block") 🖥️Output Look at me! I'm a code block If the indentation is incorrect, the computer can't understand your code. This leads to an  I⁠n⁠d⁠e⁠n⁠t⁠a⁠t⁠i⁠o⁠n⁠E⁠r⁠r⁠o⁠r⁠ showing up in the console. Instead of using the boolean  T⁠r⁠u⁠e⁠ , we can save it in a variable like  g⁠r⁠e⁠e⁠t⁠ and use it as the condition. 🧩Code greet = True if greet: print("Hello!") 🖥️Output Hello! Using a variable like  g⁠r⁠e⁠e⁠t⁠ set to  F⁠a⁠l⁠s⁠e⁠ allows us to skip code like the display statement. 🧩Code greet = False if greet: print("Hello!") 🖥️Output is empty 🧠Challenge of the day What is the output of this code? 🧩Code if True: print ("Look at me!") print("I'm a code block") #python #ai #programming #bigtech

Hello dudes and dudettes!! 🚀 Day 21/150 — Solved LeetCode 151: Reverse Words in a String Today’s problem was a great reminder that even something as simple as a sentence can hide a few tricky details 😄 At first glance, reversing words sounds easy… But once spaces start behaving weirdly, things get interesting. 🧠 What’s the Problem About? You’re given a string that contains words separated by spaces. Your task is to: 👉 Reverse the order of words 👉 Not the characters inside them 💡 Example Input: "the sky is blue" Output: 👉 "blue is sky the" 🔥 The Twist It’s not just about reversing words… The string might contain: Extra spaces at the beginning Extra spaces at the end Multiple spaces between words Example: " hello world " Expected Output: 👉 "world hello" So we also need to clean up the spaces while solving it. 🧠 The Thought Process Instead of overcomplicating things, I broke it down: Extract the words (ignore spaces) Reverse their order Join them back with a single space That’s it. Simple steps → clean solution. ⚙️ Why This Approach Works Splitting automatically removes extra spaces Reversing handles the order Joining ensures proper formatting No unnecessary checks. No messy conditions. 😎 Why This Problem Is Interesting It looks easy but tests your handling of edge cases Shows how built-in operations can simplify problems Reinforces the idea that clarity beats complexity 💡 What I Learned Clean input → clean output Breaking a problem into steps makes it easier Sometimes the best solution is the simplest one 🎯 Key Takeaway “Don’t fight the problem — break it down and let simple steps solve it.” 🔥 Another step forward in the journey — writing cleaner, smarter solutions. #LeetCode #Algorithms #Strings #ProblemSolving #CodingJourney #100DaysOfCode #Python #LearningInPublic

Hello dudes and dudettes!! 🚀 Day 19/150 — Solved LeetCode 58: Length of Last Word Today’s problem looked super simple at first… but taught me a great lesson about handling edge cases carefully 😄 🧠 What’s the Problem About? You’re given a string that contains words separated by spaces. Your task is to find the length of the last word. Sounds easy, right? Well… not always 👇 💡 The Catch The string might contain: Extra spaces at the beginning Extra spaces at the end Multiple spaces between words So it’s not just about “finding the last word” — it’s about finding the last valid word. 🔥 Example Input: " hello world " At first glance, it looks messy 😵 But the actual last word is: 👉 "world" 👉 Length = 5 🧠 The Thought Process Instead of trying to split everything immediately, I started thinking: Why not scan from the end? Because: The last word is always near the end We can skip spaces quickly Then just count characters until we hit a space ⚙️ Approach That Worked Ignore trailing spaces Start from the end of the string Count characters until a space appears That count is your answer Simple, efficient, and clean. 😎 Why This Problem Is Interesting It’s not about complexity — it’s about precision It shows how small edge cases can break simple logic It encourages thinking in reverse (which is surprisingly powerful) 💡 What I Learned Always consider edge cases like extra spaces Sometimes scanning backward is smarter than forward Even easy problems can sharpen your attention to detail 🎯 Key Takeaway “Simple problems aren’t always trivial — they test how carefully you think.” 🔥 Another step forward — improving not just coding skills, but problem-solving mindset. #LeetCode #Algorithms #ProblemSolving #CodingJourney #100DaysOfCode #Python #LearningInPublic

DEBUGGING WAS BREAKING Last two week, I was stuck for 1+ hours and 1 time a day on 2 simple bugs and 1 major. The chart wasn’t rendering. Flask wasn’t running. HTML not work fine. Right now working everything. Frustration - Anxiety - Anger. I kept trying random fixes. Changing code blindly(that time frustrated) It got worse. Then I realized something: How to debugging? And I need a checklist. Then use AI and make this checklist. Now every time I face a bug, I follow this: Define the exact problem Read the actual error (not assumptions) Identify where the issue is (backend/frontend/data) Check what I changed last Search smart (not randomly) Take a break if stuck > 40 min(Take short break and walk and deep breathing) Write the solution MOST IMPORTANT: Write the lesson learned Now I am trying to change my perspective. I stopped panicking. I stopped guessing. And try to shift Bugs are no longer my enemy. They are feedback. If you're learning Python / Data Science / Web Dev… You don’t need more tutorials. You need a system like this. Final reminder I read every time I feel stuck: “I am not stuck. I am in the process of understanding.” #Python #Debugging #Flask #DataScience #LearningInPublic #DeveloperMindset

Google NotebookLM is powerful. But the web UI is holding you back. Here's what most people don't know you can automate the entire thing with Python → I spent my Sunday digging into NotebookLM-Py, an unofficial open-source Python library that unlocks capabilities Google hasn't exposed in the browser yet. What you get with this: → Full API + CLI control — create notebooks, add sources, and query programmatically → Export to PPTX, JSON, and batch-download artifacts (not possible in the web UI) → Connect directly to AI agents like Claude Code, Codex, and other LLMs → Bulk-import YouTube videos, PDFs, and Google Drive files as sources → Auto-generate podcasts, study guides, flashcards, quizzes, videos, and mind maps Why this matters if you're building with AI: → You can feed your entire knowledge base into NotebookLM via script → Generate audio overviews and research reports at scale → Pipe outputs directly into your existing AI workflows → No more copy-pasting — everything is programmatic I've packaged up the full setup scripts, docs, and walkthrough. Comment "SCRIPTS" below and I'll DM you the zip. #NotebookLM #AIAutomation #PythonScripts #AITools #BuildInPublic

Hey, stumbled on this new Agent Zero framework on GitHub trending today. It's a Python AI agent setup that feels way beyond my junior level—handles tasks autonomously, like a mini dev team in code. Trying to tweak it for some data pipelines, but man, getting the agents to not go rogue is tricky, even with the docs. Super handy for automating ML experiments though, if you can wrangle it. Wonder how long before these things write our resumes? 😅

Two claps → my entire workflow is ready 👏👏 I built a small automation using Python and Claude that listens for two consecutive snaps/claps and instantly sets up my working environment. Once triggered, it automatically: • Opens Claude • Launches Chrome with my main tabs (Outlook, tracking Claude usage, and Lovable for web development) The idea was simple: reduce the friction of getting started and make my workflow faster and smoother. Instead of manually opening everything every time, it’s now done in seconds with a single trigger. Projects like this are helping me explore how AI and automation can be integrated into everyday tasks to improve efficiency and productivity. Looking forward to building more systems like this. 🚀 #AI #Python #Automation #Productivity #DeepLearning

I had a funny moment while coding today. 😁 Everything was going great. Data was ready. Then I typed the usual code: X = df.drop("price", axis=1) y = df["price"] And my brain just stopped: "Wait... why do we always use X and y? Who made this a rule?" 🤨😭 I looked it up, and it is actually just simple math 📐: Capital X = A big group of data (many columns). Small y = Just one thing (one column). Big data gets a big letter. Small data gets a small letter. 🤯 Do I have to use them? No. I could use normal names like features and price. But am I going to do that? Nope! Tomorrow I will use X and y again. It is just a habit now! 🌚 It is funny how in ML, the biggest questions come from the smallest things. 😅 Be honest: Do you use normal names, or do you also just use X and y? 👇 #MachineLearning #Python #DataScience #CodingLife #SimpleCode

update from previous post[https://lnkd.in/dVx_NrDQ] From "Arrow Code" to Clean Architecture. 🏹 ➡️ 🧱 I’ve hit a major turning point in my Python journey. I realized my code was starting to look like an arrow—layers upon layers of if statements and while loops pushing my logic further and further to the right. In professional dev circles, they call this Arrow Code, and it's a nightmare to maintain. Here’s how I "flattened" my latest project: ✅ Decomposition: I broke down massive, nested blocks into small, dedicated functions. Each function now does one thing well, making the main logic readable at a single glance. ✅ The "Gatekeeper" Pattern: Instead of scattered validation, I built a centralized handler to act as a security guard for all user inputs. ✅ State Management: I’m now mastering the "Baton Pass"—using return values and arguments to move data (like budgets) safely through the app instead of relying on global variables. ✅ Professional Workflow: I’m officially using Git branches and Pull Requests on GitHub to review my own work and track my architectural improvements. The goal isn't just to write code that the computer understands; it’s to write code that other humans can read. 🚀 #CleanCode #Python #SoftwareEngineering #Refactoring #CodingJourney #BuildInPublic

Hello dudes and dudettes!! 🚀 Day 13/150 — Solved LeetCode 238: Product of Array Except Self Today’s problem was a perfect mix of simplicity and smart thinking 🤯 At first glance, it feels straightforward: 👉 For each element, multiply all the other elements But the catch? ⚡ You can’t use division ⚡ And you need to do it in O(n) time That’s where things get interesting. 🧠 Initial Thought My first instinct was: “Okay, just loop through the array and multiply everything except the current element.” But that leads to O(n²) time complexity ❌ Too slow for large inputs. 💡 The Breakthrough Moment Instead of recalculating everything again and again, I realized: 👉 Why not reuse previous computations? This leads to a powerful idea: Compute products from the left side Compute products from the right side Combine both 🔥 The Core Idea For every index: 👉 Answer = (product of elements on the left) × (product of elements on the right) No division. No repeated work. Just smart reuse. 📊 Example Input: [1, 2, 3, 4] We mentally break it like this: Left products → builds progressively from the start Right products → builds from the end Then combine both to get: 🎯 Output: [24, 12, 8, 6] 😎 What Made This Problem Interesting? It looks simple, but forces you to think efficiently Teaches how to avoid redundant computation Shows how powerful prefix & suffix patterns are 💡 What I Learned Don’t recompute — reuse Think in terms of patterns, not brute force Sometimes the best solution comes from splitting the problem into two passes 🎯 Key Takeaway “Efficiency isn’t about doing more work faster… it’s about doing less work smarter.” 🔥 Another step forward in the journey — learning to think, not just code. #LeetCode #Algorithms #DataStructures #ProblemSolving #CodingJourney #100DaysOfCode #Python #LearningInPublic