Solved "Remove Duplicates from Sorted Array" on LeetCode in C++

🎯 Day 10 of my 120 Days of Coding Challenge — LeetCode Problem 10: Regular Expression Matching (Hard) Today’s challenge was one of the classic Dynamic Programming problems that really tests your logical thinking and pattern-handling skills! 💡 🧩 Problem Statement: Given a string s and a pattern p, we need to determine if the entire string matches the pattern. The pattern may contain: . → Matches any single character * → Matches zero or more of the preceding element For example: s = "aa", p = "a" → ❌ (no match) s = "aa", p = "a*" → ✅ (matches) s = "ab", p = ".*" → ✅ (matches any string) 💭 Approach Used: I used a Dynamic Programming (DP) approach to efficiently check matches between prefixes of s and p. Here’s how I broke it down: Define dp[i][j] as whether the first i characters of s match the first j characters of p. Handle base cases like empty strings and patterns with *. Build up the DP table based on matching rules: Direct match or . → inherit from dp[i-1][j-1]. * → can represent zero or multiple occurrences of the previous character. ⏱ Time Complexity: O(m × n) 📦 Space Complexity: O(m × n) ✨ Key Takeaway: This problem taught me how powerful DP can be in handling complex pattern-based problems, especially when multiple possibilities (like zero or multiple occurrences) are involved. It’s a perfect mix of logic and structure — and very satisfying once it clicks! 🔥 #Day10 #100DaysOfCode #120DaysOfCode #LeetCode #DynamicProgramming #ProblemSolving #CodingChallenge #CPlusPlus #LearningEveryday #KeepCoding

🚀 Day 57 of My LeetCode Journey 🚀 🔹 Today I solved Longest Common Prefix. Key Idea: To find the longest common prefix in a list of strings, we assume the first string as the prefix and gradually shrink it while checking with every other string. The moment a string doesn't start with the prefix, we trim the prefix until it matches — or becomes empty. 💡 What I learned: String operations like startsWith() can simplify logic. Sometimes, a simple greedy shrinking approach performs better than overthinking the solution. Clean code > complex code. 🧠 Takeaway: Break the problem into smaller checks. Don’t force complexity when simplicity solves it efficiently. Here’s the mindset: ➡️ Small progress every day still counts as progress. ➡️ Consistency beats intensity. #100DaysOfCode #leetcode #codingjourney #java #programming #learning

Continued from my previous post on Programming Setup 👇 💠 All-in-One IDEs (For Multiple Languages) If you want one software for all your coding — here are the top picks ( see the attachment below👇) 💡 Best Choice :- VS Code — supports all major languages via extensions , open-source , perfect for beginners 🌍 🎯 Final Tips :- ➢ Keep your projects organized in folders ➢ Practice coding daily ➢ Learn one language deeply before switching ➢ Use YouTube or Docs for extra tutorials 💬 Conclusion :- Starting your setup is your first step toward becoming a developer. Once your tools are ready, learning becomes smooth & fun 🚀 Share this post to help other beginners too 👩💻👨💻 #CodingSetup #BeginnersGuide #CProgramming #SQL #WebDevelopment #Python #VSCode #LearningJourney #ProgrammingLife #LinkedInLearning

🚀 Today's Problem Solved: Minimum Characters to Form "abc" Pattern While solving coding problems, sometimes the most interesting challenges are the ones that look simple but need logical pattern thinking. Today I solved a problem where the goal was to convert any given string into a perfect sequence of repeated "abc" by adding the minimum number of characters. 🔍 Example: Input: b We want: "abc" pattern So we add 'a' before and 'c' after → Result = 2 additions 🧠 Key Idea: I compared the input string with a cyclic pattern "abc", advancing when matched, and inserting characters when mismatched. This ensures minimum insertions and gives an efficient solution. 💡 What I learned: 1. Pattern simulation technique 2. String pointer traversal 3. How to maintain minimal edits 4. Optimizing logic instead of brute forcing all possibilities Problem Link:https://lnkd.in/eY36EPNK #coding #leetcode #cplusplus #programming #softwareengineer #developer #dsa #problemsolving #competitiveprogramming #codeforces #interviewpreparation #career #learning #growthmindset #students #techcommunity #100daysofcode #softwaredevelopment #devjourney

💡 𝐃𝐚𝐲 𝟔 𝐨𝐟 #𝟏𝟎𝟎𝐃𝐚𝐲𝐬𝟏𝟎𝟎𝐓𝐨𝐨𝐥𝐬 𝐓𝐨𝐝𝐚𝐲’𝐬 𝐭𝐨𝐨𝐥: Exercism → https://exercism.org/ 𝐖𝐡𝐚𝐭 𝐢𝐬 𝐢𝐭? Exercism is a free, community-driven learning platform offering hundreds of practical coding exercises across 70+ programming languages — with the added bonus of human mentors reviewing your work. 𝐖𝐡𝐲 𝐈 𝐥𝐢𝐤𝐞 𝐢𝐭? It complements cheat-sheet sites (like QuickRef.ME from yesterday) by going from “look up syntax fast” to “practice what you just learned and get feedback”. Covers a broad spectrum of languages and has beginner-friendly tracks plus more advanced ones. The mentorship element helps you go beyond rote answers — you learn the idiomatic way to write code in that language. 𝐐𝐮𝐢𝐜𝐤 𝐭𝐢𝐩: If you used QuickRef.ME to refresh a command or syntax yesterday, jump into Exercism today: pick that same language (for example: Python or JavaScript), start one exercise from the track, submit it and review the feedback. It closes the loop between “look up” → “apply” → “improve”. Have you used Exercism (or similar platforms) before? Drop your experience below 👇 Stay tuned for Tool #7 tomorrow! #100Days100Tools #ToolOfTheDay #LearningTools #CodePractice #DevTools #Programming

🚀 Day 5 – LeetCode Problem Solving Journey 💻 Today’s problem was “Remove Element”, an easy-level array problem that focuses on in-place modification — a key concept for memory-efficient programming. Problem Statement: Given an array nums and a value val, remove all occurrences of val in-place and return the number of elements that are not equal to val. The relative order of elements may be changed. Example 1: Input: nums = [3,2,2,3], val = 3 Output: 2, nums = [2,2,_,_] Example 2: Input: nums = [0,1,2,2,3,0,4,2], val = 2 Output: 5, nums = [0,1,4,0,3,_,_,_] 🧠 Concept Used: Two-pointer technique In-place replacement of valid elements Time Complexity: O(n) Space Complexity: O(1) Every problem builds consistency, clarity, and confidence — one step closer to mastering DSA. 💪 #LeetCode #Day5 #ProblemSolving #CodingJourney #100DaysOfCode #Python #DSA #Programming #DevelopersCommunity #SoftwareEngineering #TechLearning #CareerGrowth #ipec #ipec30

The Power of Small, Daily Progress in Coding When I first started learning to code, I believed that in order to get better, I would need to work for hours every day. To be honest, though, that strategy never succeeded. On some days, I felt exhausted, disoriented, or just angry. Then I decided to do something easy: Just code a little bit every day. 20 to 30 minutes, or even an hour is fine. And it changed everything. Some days I corrected a lot of mistakes. Some days I just watched tutorials. Some days I just practiced, built a lot of programs, and failed at many of them. But by learning to code daily, things started getting easier. I began to understand logic better, remember syntax naturally, and actually started enjoying the process. The truth is, small steps every day may not seem exciting, but over time they can become something exciting. Don't worry about being flawless if you're learning to code. Simply keep going, one line of code at a time. You'll be shocked at how far you can go with this consistency. #CodingJourney #Consistency #DeveloperLife #Python #WebDevelopment #KeepLearning

𝐓𝐡𝐞 𝐅𝐢𝐫𝐬𝐭 𝐑𝐮𝐥𝐞 𝐨𝐟 𝐂𝐨𝐝𝐢𝐧𝐠: “𝐃𝐨𝐞𝐬 𝐢𝐭 𝐰𝐨𝐫𝐤? 𝐘𝐞𝐬? 𝐓𝐡𝐞𝐧 𝐃𝐎𝐍’𝐓. 𝐓𝐎𝐔𝐂𝐇. 𝐈𝐓.” 😬💻⁣⁣⁣⁣⁣ ⁣⁣⁣⁣⁣ This image humorously captures one of the unwritten rules of software development — if your code works, resist the urge to “improve” it just for the sake of it.⁣⁣⁣⁣⁣ ⁣⁣⁣⁣⁣ Because let’s be honest…⁣⁣⁣⁣⁣ 🧑💻 One “tiny tweak” can turn into a full-day debugging session.⁣⁣⁣⁣⁣ 💥 Sometimes, practicality beats perfection.⁣⁣⁣⁣⁣ ⁣⁣⁣⁣⁣ If it ain’t broke — don’t fix it. 😉⁣⁣⁣⁣⁣ ⁣⁣⁣⁣⁣ Follow Varun Sharma For More #codingmeme #programming #coding #developerlife #softwaredeveloper #programmerhumor #webdevelopment #python #java #techlife #programmingmemes #devlife #computerscience #debugging #funny #softwareengineering

🚀 Day 3 Topic: Sealed, Static & Partial Classes in C# C# gives us three special keywords that change how a class behaves. Let’s understand them in the simplest possible way 👇 🔒 1️⃣ Sealed Class — “No Inheritance Allowed” A sealed class can create objects, but cannot be inherited. ✔️ Meaning You can create an object of a sealed class But you cannot create a child class from it ✔️ When to use? When you want to stop other classes from extending/modifying your class 💡 Think of it like a locked box — you can use it, but can’t add anything to it. 🧰 2️⃣ Static Class — “Only One Copy, No Objects” A static class cannot create objects. Everything inside it must be static. ✔️ Meaning ❌ No object creation ❌ Cannot inherit or be inherited ✔️ Use directly by class name (like Math) ✔️ When to use? Utility/helper classes Global functions (e.g., “Convert”, “Math”) 💡 Think of it like a toolbox on a wall — everyone can use the tools, but nobody can make a copy. 📂 3️⃣ Partial Class — “One Class, Many Files” A partial class can create objects, because it’s just a normal class split into pieces. ✔️ Meaning ✔️ Object creation allowed ✔️ Inheritance allowed ✔️ All parts combine into one class at compile time ✔️ When to use? Large classes Auto-generated + manual code separation + Cleaner organization ❓ Tricky Interview Question 👉 If a static class cannot be instantiated, how does its static constructor run? 💬 One-Line Summary “Sealed stops inheritance, Static stops objects, Partial splits the class.” #DotNet #CSharp #DotNetDeveloper #DotNetCommunity #Programming #CodingChallenge #CodeDesign #TechLearning #SoftwareEngineering #CleanCode #OOP #Developers #100DaysOfCode #LearnToCode #Day3 #CSharpBasics #MicrosoftDotNet #BackendDeveloper #DevCommunity

DAY 7 - Project 4 (A Login System With Attempts) 🚀 For day 7, I worked on a project by applying what I've learnt on the While statement. My goal on this project is to allow a user to use three tries to enter the correct password. At first, I wanted only a final message if all attempts failed, but then I thought, why not give feedback after each wrong entry, rather than making it plain? Adding that small "elif" statement made the program more interactive and user-friendly. Running the final version successfully felt like ....... Reflecting on this first week, I realized something important: Python isn’t just about writing code. It’s about thinking logically, experimenting, and learning from mistakes. Every error message is not a failure; it’s a guide pointing to where you can improve, like isn't that the reason why the terminal shows us where the errors come from? Every small success builds confidence. This week reminded me that learning to code is much like learning a new language. You stumble, correct yourself, experiment, and eventually, it starts to make sense. And while Python may look intimidating at first, its readability and simplicity make it an incredible language for anyone willing to dive in. Here’s to many more weeks of learning, debugging, one line of code at a time. #Python #CodingJourney #LearnToCode #Programming #SoftwareDevelopment #TechLearning #BeginnerDeveloper #CodeNewbie #ProblemSolving #ContinuousLearning