Java Collection Edge Cases and Best Practices

🚀 Beats 100% of all Java solutions on LeetCode! Just solved LeetCode #290 — Word Pattern in Java with 0ms runtime, outperforming every submission. Here's how I approached it 👇 🧩 Problem: Given a pattern (like "abba") and a string of words, check if the words follow the exact same pattern — a full bijection. e.g. pattern = "abba", s = "dog cat cat dog" → true ✅ 💡 My approach: Used a single HashMap<Character, String> to map each pattern character to its corresponding word. The key insight: also check containsValue() to prevent two different characters from mapping to the same word — ensuring true one-to-one bijection. 📊 Results: Runtime: 0 ms — Beats 100.00% 🌿 Memory: 42.65 MB — Beats 80.14% 🔑 Key takeaway: Always verify bijection in both directions — a one-way map is not enough for pattern matching problems. One extra containsValue() check is all it takes! All 44 test cases passed ✅ — Clean, simple, and blazing fast. #LeetCode #Java #DSA #CodingChallenge #ProblemSolving #100Percent #Programming #SoftwareEngineering #CompetitiveProgramming #HashMap

Day 33/100 — Threads & Multithreading ⚡ Java can do multiple things at the same time using threads. Thread lifecycle: NEW → RUNNABLE → RUNNING → WAITING → TERMINATED 2 ways to create threads: // Method 1: extend Thread class MyThread extends Thread {   public void run() { println("Running!"); } } new MyThread().start(); // NOT run()! // Method 2: Runnable lambda (preferred!) Thread t = new Thread(() -> println("Lambda thread!")); t.start(); Most important rule: ALWAYS call start() — NOT run()! → run() = normal method call (same thread) → start() = creates new thread and calls run() 3 things to remember: → Prefer Runnable over extending Thread → start() not run() → Multiple threads = race conditions possible! 🎯 Challenge: Create 3 threads that each print their name 5 times. Observe the interleaved output! #Java #Threads #Multithreading #CoreJava #100DaysOfJava #100DaysOfCode

Day 7 of #100DaysOfCode — Java is getting interesting ☕ Today I explored the Java Collections Framework. Before this, I was using arrays for everything. But arrays have one limitation — fixed size. 👉 What if we need to add more data later? That’s where Collections come in. 🔹 Key Learnings: ArrayList grows dynamically — no size worries Easy operations: add(), remove(), get(), size() More flexible than arrays 🔹 Iterator (Game changer) A clean way to loop through collections: hasNext() → checks next element next() → returns next element remove() → safely removes element 🔹 Concept that clicked today: Iterable → Collection → List → ArrayList This small hierarchy made everything much clearer. ⚡ Array vs ArrayList Array → fixed size ArrayList → dynamic size Array → stores primitives ArrayList → stores objects Still exploring: Set, Map, Queue next 🔥 Consistency is the only plan. Showing up every day 💪 If you’re also learning Java or working with Collections — let’s connect 🤝 #Java #Collections #ArrayList #100DaysOfCode #JavaDeveloper #LearningInPublic

🚀 Understanding Class Loading Process in Java If you're diving into Java, one important concept you must understand is the Class Loading Process. Here's a simple breakdown 👇 🔹 1. Class Loader Java uses different class loaders to load classes into memory: - Bootstrap ClassLoader (loads core Java classes) - Platform ClassLoader - Application ClassLoader 🔹 2. Loading The ".class" file is loaded into memory by the class loader. 🔹 3. Linking This step ensures everything is ready for execution: ✔️ Verification – checks bytecode correctness ✔️ Preparation – allocates memory for static variables ✔️ Resolution – replaces symbolic references with actual references 🔹 4. Initialization Static variables and blocks are executed (e.g., "x = 42;"). 💡 Why it matters? Understanding this helps in debugging, performance optimization, and mastering how Java actually runs behind the scenes. #Java #Programming #Coding #OOP #Developers #JavaBasics #Learning

🚀 Arrays in Java (Quick Guide) An Array is one of the most important data structures in Java. It stores multiple values of the same data type in a fixed-size container. ✅ Key Features of Arrays Stores elements in contiguous memory Size is fixed once declared Supports index-based access Faster retrieval using index (O(1)) 📌 Example int[] arr = {10, 20, 30, 40}; System.out.println(arr[0]); // Output: 10 🔥 Advantages ✔ Fast access using index ✔ Easy to iterate ✔ Memory efficient for fixed data ⚠ Limitations ❌ Size cannot grow dynamically ❌ Insertion/deletion in middle is costly (O(n)) 💡 When to Use Arrays? 👉 When the size is known in advance 👉 When you need fast indexing 👉 For performance-critical applications Arrays are the foundation for many advanced structures like ArrayList, Heap, Stack, and more. hashtag #Java #Arrays #DSA #Programming #InterviewPreparation

🚀 Are you already using Parallel Streams in Java? Parallel Streams can be a great tool for improving performance in collection operations by taking advantage of multiple CPU cores to process data in parallel. With a simple change: list.stream() to: list.parallelStream() or: list.stream().parallel() it’s possible to execute operations like filter, map, and reduce simultaneously. But be careful: parallelizing doesn’t always mean speeding things up. ⚠️ Some important points before using it: ✅ It’s worth it when: * There is a large amount of data; * Operations are CPU-intensive; * Tasks are independent and side-effect free. ❌ It may make things worse when: * The collection is small; * There are I/O operations (database, API calls, files); * There is synchronization or shared state; * Processing order matters. Also, Parallel Streams use ForkJoinPool.commonPool() by default, which may cause contention with other tasks in the application. 💡 Rule of thumb: measure before you optimize. Benchmarking with tools like JMH can help avoid decisions based on guesswork. When used correctly, Parallel Streams can be a powerful way to gain performance with minimal code changes. #Java #Performance #Backend #SoftwareDevelopment #Programming

Topic of the day String? Why String is Immutable? 👉 In Java, a String is immutable, which means once it is created, its value cannot be changed. Example: String s = "Hello"; s.concat(" World"); 👉 You might expect: "Hello World" 👉 But actual output: "Hello" Because concat() creates a new object, instead of modifying the existing one. 🔍 Why did Java designers make String immutable? ✔️ Security – Strings are used in sensitive areas (like DB connections, file paths, network URLs) ✔️ Thread Safety – No need for synchronization (safe in multithreading) ✔️ Performance – Enables String Pool (memory optimization) ✔️ Caching – Hashcode can be cached (used in HashMap) If you are doing multiple string modifications, prefer: 👉 StringBuilder (faster, not thread-safe) 👉 StringBuffer (thread-safe) #Java #JavaConcepts #InterviewPreparation #Programming #Developers #Programming #Development #Coding

♻️ Ever wondered how Java manages memory automatically? Java uses Garbage Collection (GC) to clean up unused objects — so developers don’t have to manually manage memory. Here’s the core idea in simple terms 👇 🧠 Java works on reachability It starts from GC Roots: • Variables in use • Static data • Running threads Then checks: ✅ Reachable → stays in memory ❌ Not reachable → gets removed 💡 Even objects referencing each other can be cleaned if nothing is using them. 🔍 Different types of Garbage Collectors in Java: 1️⃣ Serial GC • Single-threaded • Best for small applications 2️⃣ Parallel GC • Uses multiple threads • Focuses on high throughput 3️⃣ CMS (Concurrent Mark Sweep) • Runs alongside application • Reduces pause time (now deprecated) 4️⃣ G1 (Garbage First) • Splits heap into regions • Balanced performance + low pause time 5️⃣ ZGC • Ultra-low latency GC • Designed for large-scale applications ⚠️ One important thing: If an object is still referenced (even accidentally), it won’t be cleaned → which can lead to memory issues. 📌 In short: Java automatically removes unused objects by checking whether they are still reachable — using different GC strategies optimized for performance and latency. #Java #Programming #JVM #GarbageCollection #SoftwareDevelopment #TechConcepts

Day 36/100 – Working with ArrayList in Java 📚 Today I practiced using ArrayList in Java, a dynamic array that allows flexible storage and manipulation of data. Unlike normal arrays, ArrayList can grow and shrink dynamically, making it very useful in real-world applications. Key learnings: • Adding elements using add() • Storing multiple values dynamically • Finding size using size() • Easier and more flexible than traditional arrays Understanding collections like ArrayList is important for handling data efficiently in Java. Building strong fundamentals step by step. 🚀 #100DaysOfCode #Java #ArrayList #DataStructures #CodingJourney #LearningInPublic

Every Java object starts with a Constructor — and today in class I learned exactly how it works! 🔧 A Constructor is a special method that is automatically called when an object is created. It has the same name as the class and has no return type — not even void. Its main job is to initialize the object's values at the time of creation. #JavaProgramming #Constructor #OOP #ObjectOrientedProgramming #CodeNewbie #LearnToCode #SoftwareDevelopment #JavaBeginners