Java Method Overriding Explained

#Day45 – Map in Java: Key-Value Pairs & Problem Solving -#Programming ⚠️ Today, I explored one of the most powerful data structures in Java — Map, which helps in storing data in key-value pairs and solving real-world problems efficiently. 💡 Key Learnings: ✔ Map → collection of key-value pairs ✔ Key → unique (no duplicates allowed) and Value → can have duplicates ✔ One key maps to exactly one value ✔ Methods: put(), get(), remove(), containsKey(), containsValue() ✔ keySet() → get all keys , values() → get all values ✔ entrySet() → get key-value pairs , size() and isEmpty() ✔ Types of Map → HashMap, LinkedHashMap, TreeMap ✔ HashMap → no order , LinkedHashMap → maintains insertion order ✔ TreeMap → sorts keys 🧠 Example Solved: Solved a problem to count the frequency of each character in a string (e.g., Mississippi → M1i4s4p2) using Map. Learned how to efficiently track occurrences using containsKey(), get(), and put() methods. A big thank you to TAP Academy, Harshit T Sir, and Somanna M G Sir for explaining complex concepts in such a simple and practical way. Your teaching style, real-world examples, and constant support have made a huge difference in my understanding of Java and problem-solving. 🙏 #Java #CollectionsFramework #Map #HashMap #LinkedHashMap #DataStructures #CodingJourney #Consistency

🚀 Exploring Method Overloading in Java As part of my journey in mastering Object-Oriented Programming in Java, I recently explored one of the most powerful concepts of Polymorphism — Method Overloading. 💡 What is Method Overloading? Method overloading is the process of creating multiple methods with the same name in a class, but with different parameter lists. It allows the same action to behave differently based on the input — making programs more flexible and readable. 🔹 Three Ways to Achieve Method Overloading A method can be overloaded by changing: 1️⃣ Number of parameters 2️⃣ Data types of parameters 3️⃣ Order/sequence of parameters ❌ Invalid Case If two methods have the same name + same parameters but different return types, it is NOT valid overloading and results in a compile-time error. Example: int area(int, int) float area(int, int) → Compilation Error 🚫 🧠 Why is it called False (Virtual) Polymorphism? To the user, it looks like one method performing multiple tasks (one-to-many). But internally, each call maps to a separate method (one-to-one) — hence the term False Polymorphism. ⚡ Type Promotion in Overloading If an exact match is not found, Java automatically promotes smaller data types to larger ones: byte → short → int → long → float → double This makes method overloading even more powerful and flexible! 👩💻 Simple Example class AreaCalculator { int area(int l, int b) { return l * b; } double area(double r) { return 3.14 * r * r; } int area(int side) { return side * side; } } TAP Academy ✨ Learning these core OOP concepts is helping me build stronger foundations in Java and improve my problem-solving skills step by step. #Java #OOP #Programming #CodingJourney #ComputerScience #LearningInPublic 

🚀 Learning Core Java – Understanding the final Keyword Today I explored an important concept in Java — the final keyword. The final keyword is used to restrict modification and helps make code more secure, predictable, and stable. It can be used with: ✔ Variables ✔ Methods ✔ Classes 🔹 1. Final Variable If a variable is declared as final: 👉 Its value cannot be changed once assigned It becomes a constant. Example conceptually: final int MAX = 100; This improves safety and prevents accidental modification. 🔹 2. Final Method If a method is declared as final: 👉 It cannot be overridden by the child class This is useful when we want to preserve the original behavior of a method. 🔹 3. Final Class If a class is declared as final: 👉 It cannot be inherited This is used when we want to stop extension of a class for security or design reasons. Example: String class is a famous final class in Java. 🔎 Why abstract and final Cannot Be Used Together These two keywords contradict each other: ✔ abstract → Must be overridden ✔ final → Cannot be overridden Because of this: ❌ abstract final is not allowed in Java 🔹 Difference Between final, finally, and finalize() final ✔ A keyword ✔ Used with variables, methods, and classes finally ✔ A block used with try or try-catch 👉 It executes whether exception occurs or not Mainly used for cleanup operations like closing files or database connections. finalize() ✔ A method of the Object class 👉 Called internally by the Garbage Collector before object destruction ⚠ Deprecated since JDK 9 due to unpredictable behavior and performance issues. 💡 Key Insight 👉 final = Restriction 👉 finally = Cleanup block 👉 finalize() = Garbage collection method Understanding these small differences avoids big confusion during interviews and real projects. Excited to keep strengthening my Core Java fundamentals! 🚀 #CoreJava #FinalKeyword #JavaDeveloper #ObjectOrientedProgramming #ProgrammingFundamentals #LearningJourney #SoftwareEngineering

Day 41 of Learning Java: Method Overriding If method overloading was about flexibility,method overriding is about customization. What is Method Overriding? It’s when a subclass provides its own implementation of a method that is already defined in the parent class. Same method name. Same parameters. But different behavior. 🔹 Simple example- class Parent { void watchTV() { System.out.println("Watching News/Serial"); } } class Child extends Parent { @Override void watchTV() { System.out.println("Watching Music/Sports"); } } Same method → different output depending on the object. • Parent defines a general behavior • Child modifies it based on its own need • This helps in writing more flexible and reusable code 🔹 Key points to remember • Method signature must be the same • Happens during runtime (runtime polymorphism) • Inheritance is required 👉 You cannot override: static methods private methods final methods 🔹 One important concept Parent ref = new Child(); ref.watchTV(); Even though the reference is of Parent, the method of Child gets executed. 👉 This is called dynamic method dispatch 🔹 About @Override It’s not mandatory, but it helps: ✔ Avoid mistakes ✔ Makes code more readable ✔ Ensures you’re actually overriding #Java #OOP #MethodOverriding #LearningInPublic #Programming#sql #branding

🚀 Learning Core Java – Achieving Runtime Polymorphism using Loose Coupling Today I explored an important concept in Java — Runtime Polymorphism through Loose Coupling. Runtime polymorphism is one of the most powerful features of Object-Oriented Programming because it helps us write flexible, scalable, and maintainable code. 🔹 What is Tight Coupling? Tight Coupling means: 👉 A child class reference is used to create and access a child class object Example conceptually: Child child = new Child(); Here, the code is directly dependent on the child class. This creates: ❌ Less flexibility ❌ Harder maintenance ❌ Difficult scalability Because if the implementation changes, the code also needs changes. 🔹 What is Loose Coupling? Loose Coupling means: 👉 A parent class reference is used to refer to a child class object Example conceptually: Parent ref = new Child(); This is also called: ✔ Upcasting ✔ Runtime Polymorphism ✔ Dynamic Method Dispatch Here, the parent reference can call overridden methods of the child class at runtime. This gives: ✔ Better flexibility ✔ Easy maintenance ✔ Scalable design ✔ Cleaner architecture 🔹 Limitation of Loose Coupling Using a parent reference: 👉 We can only access methods available in the parent class Even though the object is a child object, we cannot directly access specialized methods of the child class. 🔹 How to Access Child-Specific Methods? We use Downcasting 👉 Convert parent reference back to child reference Conceptually: Child child = (Child) ref; Now the parent reference behaves like a child reference, and we can access: ✔ Specialized methods ✔ Child-specific properties 💡 Key Insight 👉 Tight Coupling = Less flexibility 👉 Loose Coupling = More flexibility + Runtime Polymorphism 👉 Downcasting helps access specialized child methods This concept is heavily used in Spring Framework, Dependency Injection, Interfaces, and Enterprise Applications. Understanding this helps build professional-level Java applications. Excited to keep strengthening my OOP fundamentals! 🚀 #CoreJava #RuntimePolymorphism #LooseCoupling #TightCoupling #ObjectOrientedProgramming #JavaDeveloper #ProgrammingFundamentals #LearningJourney

🚀 Learning Core Java – Understanding Aggregation and Composition Today I explored an important OOP concept in Java — Aggregation and Composition. Both Aggregation and Composition are called Associative Relationships because they represent the “Has-A” relationship between classes. This means one class contains or uses objects of another class instead of inheriting from it. 🔹 What is Has-A Relationship? In this relationship: ✔ There is one Primary Class ✔ There can be one or more Secondary Classes The way secondary class objects participate inside the primary class defines the type of relationship. 🔹 Aggregation Aggregation means: 👉 The secondary class can exist independently, even without the primary class. This represents a weak association. Example: 📱 Mobile has a Charger Even if the mobile phone is removed, the charger can still exist independently. So this is Aggregation. 🔹 Composition Composition means: 👉 The secondary class cannot exist independently without the primary class. This represents a strong association. Example: 📱 Mobile has an Operating System Without the mobile phone, the operating system has no separate meaningful existence in that context. So this is Composition. 🔎 Simple Difference ✔ Aggregation → Independent existence possible ✔ Composition → Dependent existence only 💡 Key Insight Aggregation and Composition help us model real-world relationships more accurately and build better object-oriented designs. 👉 Both are Has-A relationships 👉 Aggregation = Weak association 👉 Composition = Strong association Understanding these concepts is essential for writing clean, scalable, and maintainable Java applications. Excited to keep strengthening my OOP fundamentals! 🚀 #CoreJava #Aggregation #Composition #ObjectOrientedProgramming #HasARelationship #JavaDeveloper #ProgrammingFundamentals #LearningJourney

Java Pass by Value — Finally Made Simple One concept that confused me for a while was: 👉 Is Java pass by value or pass by reference? Here’s the simplest way to understand it 👇 🔹 Example class Main { static void add(int a, int b) { a = a + 10; b = b + 20; } public static void main(String[] args) { int a = 5, b = 10; add(a, b); int res = a + b; System.out.println(res); // Output: 15 } } 👉 Even after calling the function, a and b don’t change ✔ Because Java passes copies of values ❌ Trying Pass by Reference in Java // Not valid in Java static void add(int &a, int &b) { a = a + 10; b = b + 20; } 👉 This gives a compile error ✔ Java doesn’t support reference parameters like C++ So What’s the Truth? ✔ Java is always pass by value ✔ Variables are copied, not shared 🤔 Why? 🛡️ Safer memory handling 🔒 No unexpected changes in variables 🧠 Simple and predictable behavior Grateful to my Java mentor Syed Zabi Ulla sir for clearing this misconception so clearly, and to my DSA mentor satya sai Sir who first introduced us to this concept while teaching functions in C++. Also thankful to my college PW Institute of Innovation for providing the right learning environment 🚀 💡 One line to remember: Java copies values, never shares variables. #Java #Programming #DSA #LearningJourney #Developers

🚀 Learning Core Java – Understanding toString() Method and Its Significance Today I explored one of the most commonly used methods from the Object class in Java — the toString() method. Since every class in Java implicitly extends the Object class, every object gets access to the toString() method by default. 🔹 What is toString()? The toString() method is used to return the string representation of an object. Whenever we print an object directly using: System.out.println(object); Java internally calls: object.toString(); 🔹 Default Behavior of toString() By default, the toString() method returns: 👉 ClassName@HexadecimalHashCode 🔹 Why Do We Override toString()? To make object output more readable and meaningful, we override the toString() method. Instead of memory-like output, we can display useful information such as: ✔ Name ✔ ID ✔ Age ✔ Product Details ✔ Employee Information This improves: ✔ Debugging ✔ Logging ✔ Readability ✔ User-friendly output 💡 Key Insight 👉 toString() converts an object into a meaningful string representation 👉 Default output is technical and less useful 👉 Overriding it improves clarity and maintainability A well-written toString() method makes Java code cleaner and easier to understand. Excited to keep strengthening my Core Java fundamentals! 🚀 #CoreJava #ToStringMethod #ObjectClass #JavaProgramming #OOP #JavaDeveloper #ProgrammingFundamentals #LearningJourney

💎 Understanding the Diamond Problem in Java (and how Java solves it!) Ever heard of the Diamond Problem in Object-Oriented Programming? 🤔 It happens in multiple inheritance when a class inherits from two classes that both have the same method. The Problem Structure: Class A → has a method show() Class B extends A Class C extends A Class D extends B and C Now the confusion is: Which show() method should Class D inherit? This creates ambiguity — famously called the Diamond Problem Why Java avoids it? Java does NOT support multiple inheritance with classes. So this problem is avoided at the root itself. But what about Interfaces? Java allows multiple inheritance using interfaces, but resolves ambiguity smartly. If two interfaces have the same default method, the implementing class must override it. Example: interface A { default void show() { System.out.println("A"); } } interface B { default void show() { System.out.println("B"); } } class C implements A, B { public void show() { A.super.show(); // or B.super.show(); } } Key Takeaways: No multiple inheritance with classes in Java Multiple inheritance allowed via interfaces Ambiguity is resolved using method overriding Real Insight: Java doesn’t just avoid problems — it enforces clarity. #Java #OOP #Programming #SoftwareDevelopment #CodingInterview #TechConcepts

📘✨ Collections and Framework Introduction to ArrayList in Java – Conceptual Overview 🚀 Continuing my learning, I focused on the theory behind ArrayList, a fundamental part of Java’s data handling 📋 🔹 ArrayList is a class that implements a dynamic array, meaning its size can change automatically during runtime 🔄 🔹 It belongs to the Java Collections Framework and is widely used for storing and managing data efficiently 💡 Core Properties: ✔ Preserves insertion order 📑 ✔ Allows duplicate elements 🔁 ✔ Provides random (index-based) access ⚡ ✔ Dynamically resizes as data grows 📈 💡 Performance Insight ⚙️ - Fast for accessing elements (O(1)) - Slower for inserting/removing elements in between (due to shifting) - Better suited for read-heavy operations 💡 Behind the Scenes 🔍 - Internally uses an array structure - When capacity is full, it creates a larger array and copies elements - Default capacity grows automatically 💡 Use Cases 🌍 📌 Managing lists of students, products, or records 📌 Applications where order matters 📌 Situations where frequent searching/access is required 💡 Drawbacks ⚠️ ❌ Not efficient for frequent insertions/deletions ❌ Not thread-safe without synchronization 🎯 Final Thought 💡 ArrayList offers a perfect balance between simplicity and performance, making it one of the most commonly used data structures in Java 💻✨ #Java #ArrayList #Collections #Programming #CodingLife #Developer #LearningJourney #HarshitT #TapAcademy