Java this vs super: Understanding the difference

🚀 Learning Core Java – Method Hiding & Variable Hiding Today I explored an interesting concept in Java — Method Hiding and Variable Hiding. When a class inherits properties and behavior from another class, we usually talk about method overriding. But things behave differently when static methods and variables are involved. 🔹 Method Hiding (Static Methods) In Java: ✔ Instance methods → can be overridden ✔ Static methods → cannot be overridden If a child class defines a static method with the same signature as the parent: 👉 It does NOT override the method 👉 Instead, it hides the parent method This is called Method Hiding. 🔎 Important: • The method that gets executed depends on the reference type, not the object type • This is resolved at compile-time (not runtime) 🔹 Variable Hiding When a child class declares a variable with the same name as in the parent class: 👉 The child variable hides the parent variable This applies to: ✔ Static variables ✔ Instance variables 🔎 How to Access Parent Members? We use the super keyword to access hidden members of the parent class: ✔ super.variable → Access parent variable ✔ super.method() → Access parent method (if needed) 💡 Key Insight 👉 Instance methods → Overriding (Runtime Polymorphism) 👉 Static methods → Method Hiding (Compile-time behavior) 👉 Variables → Always Hiding (No overriding concept) Understanding this difference helps in avoiding confusion and writing predictable and clean Java code. Excited to keep strengthening my Core Java fundamentals! 🚀 #CoreJava #MethodHiding #VariableHiding #JavaProgramming #ObjectOrientedProgramming #JavaDeveloper #ProgrammingFundamentals #LearningJourney

While learning Java, I realized something important: 👉 Writing code is easy 👉 Handling failures correctly is what makes you a good developer So here’s my structured understanding of Exception Handling in Java 👇Java Exception Handling — the part most tutorials rush through. If you're writing Java and your only strategy is wrapping everything in a try-catch(Exception e) and hoping for the best, this is for you. A few things worth understanding properly: 1. Checked vs Unchecked isn't just trivia Checked exceptions (IOException, SQLException) are compile-time enforced — the language is telling you these failure modes are expected and you must plan for them. Unchecked exceptions (RuntimeException and its subclasses) signal programming bugs — they shouldn't be caught and hidden, they should be fixed. 2. finally is a contract, not a suggestion That block runs regardless of what happens. Use it for resource cleanup. Better yet, use try-with-resources in modern Java — it handles it automatically. 3. Rethrowing vs Ducking "Ducking" means declaring throws on a method and letting the caller deal with it. Rethrowing means catching it, maybe wrapping it with more context, and throwing again. Know when each makes sense. 4. Custom exceptions add clarity A PaymentDeclinedException tells the next developer (and your logs) far more than a generic RuntimeException with a message string. The image attached gives a clean visual overview — bookmarking it might save you a Google search or two. TAP Academy kshitij kenganavar What's your go-to rule for exception handling in production systems? #Java #SoftwareDevelopment #CleanCode #JavaDeveloper #BackendEngineering #TechEducation #100DaysOfCode

☕ A Fun Java Fact Every Developer Should Know Did you know that every Java program secretly uses a class you never write? That class is "java.lang.Object". In Java, every class automatically extends the "Object" class, even if you don't write it explicitly. Example: class Student { } Even though we didn't write it, Java actually treats it like this: class Student extends Object { } This means every Java class automatically gets powerful methods from "Object", such as: • "toString()" converts object to string • "equals()" compares objects • "hashCode()" used in collections like HashMap • "getClass()" returns runtime class information 📌 Example: Student s = new Student(); System.out.println(s.toString()); Even though we didn't define "toString()", the program still works because it comes from the Object class. 💡 Why this is interesting Because it means Java has a single root class hierarchy — everything in Java is an object. Understanding small internal concepts like this helps developers write cleaner and smarter code. Learning Java feels like uncovering small hidden design decisions that make the language so powerful. #Java #Programming #SoftwareDevelopment #LearnJava #Coding #DeveloperJourney

🚀 Understanding Key Java Differences: throw vs throws & final, finally, finalize Java has several keywords that sound similar but serve completely different purposes. Understanding these differences is essential for writing clean and efficient code. Let’s break them down 👇 🔹 throw vs throws 👉 throw Used to explicitly throw an exception Used inside a method or block Throws a single exception at a time throw new ArithmeticException("Error occurred"); 👉 throws Used in method signature Declares exceptions that a method might throw Can declare multiple exceptions void readFile() throws IOException, SQLException { // code } 💡 Key Difference: throw is used to actually throw an exception, while throws is used to declare exceptions. 🔹 final vs finally vs finalize 👉 final Keyword used with variables, methods, and classes Variable → value cannot be changed Method → cannot be overridden Class → cannot be inherited final int x = 10; 👉 finally Block used with try-catch Always executes (whether exception occurs or not) Used for cleanup activities try { int a = 10 / 0; } finally { System.out.println("Cleanup done"); } 👉 finalize Method called by Garbage Collector before object destruction Used for cleanup (rarely used in modern Java) protected void finalize() throws Throwable { System.out.println("Object is destroyed"); } 💡 Key Difference: final → restriction keyword finally → execution block finalize → method for cleanup before garbage collection ✨ Takeaway: Small keywords can make a big difference in Java. Mastering these improves your code quality and helps you handle exceptions and memory more effectively. Keep learning, keep coding, and keep growing 💻🚀 #Java #ExceptionHandling #ProgrammingConcepts #Developers #CodingJourney #KeepLearning #OOP TAP Academy

💡 Different Ways to Handle Exceptions in Java Exception handling is a crucial part of writing robust and reliable applications. Understanding how and when to handle exceptions can make your code cleaner, safer, and easier to debug. Here are three important ways to handle exceptions in Java: 🔹 1. Handling Exception (try-catch) This is the most common approach where we handle the exception immediately. try { int a = 10 / 0; } catch (ArithmeticException e) { System.out.println("Exception handled: Division by zero"); } 👉 Used when you can resolve the issue at the same place. 🔹 2. Rethrowing the Exception (try-catch, throw, throws, finally) Here, we catch the exception but pass it to the caller after performing some actions. void divide() throws ArithmeticException { try { int a = 10 / 0; } catch (ArithmeticException e) { System.out.println("Logging the exception..."); throw e; // rethrowing } finally { System.out.println("Cleanup done"); } } 👉 Useful when the current method cannot fully handle the exception. 🔹 3. Ducking the Exception In this approach, we don’t handle the exception in the method. Instead, we declare it using throws and let the caller handle it. void readFile() throws Exception { FileReader file = new FileReader("test.txt"); } 👉 Ideal when you want to delegate exception handling responsibility to the calling method. 💡 Key Takeaway: Choosing the right way to handle exceptions depends on the situation. Sometimes you handle it immediately, sometimes you pass it on — and sometimes you let someone else take care of it! Keep practicing and exploring — that’s how we write better and more resilient code 💻✨ #Java #ExceptionHandling #CodingConcepts #ProblemSolving #LearningJourney #Developers #KeepGrowing TAP Academy

💡 Java Exception Handling — Are You Losing Important Errors? 🚨 While learning Java, I came across something very important: 👉 Chained Exceptions 🔹 What is a Chained Exception? A chained exception means linking one exception with another, so we don’t lose the original error. 🔴 Without Chaining (Bad Practice) try { int a = 10 / 0; } catch (Exception e) { throw new RuntimeException("Something went wrong"); } ❌ Output: RuntimeException: Something went wrong 👉 Problem: Original error (/ by zero) is LOST ❌ 🟢 With Chaining (Best Practice) try { int a = 10 / 0; } catch (Exception e) { throw new RuntimeException("Something went wrong", e); } ✅ Output: RuntimeException: Something went wrong Caused by: ArithmeticException: / by zero 👉 Now we get the complete error story ✅ 🔍 Why is this important? ✔ Helps in debugging ✔ Keeps original error intact ✔ Used in real-world backend systems ✔ Makes logs more meaningful 🧠 Golden Rule: 👉 Always pass the original exception: throw new Exception("Message", e); 💬 Simple Analogy: Without chaining → "Something broke" ❌ With chaining → "Something broke because X happened" ✅ 🔥 Small concept, but BIG impact in real projects! #Java #ExceptionHandling #Programming #Coding #Developers #Backend #SoftwareEngineering #LearningJourney

As I continue exploring Java, one concept that stood out to me is the Optional class. While learning, I realized how frequently null values can cause issues in programs, especially leading to NullPointerException. Optional, introduced in Java 8, provides a cleaner and more structured way to handle such scenarios. What I understood about Optional: Optional is a container object that may or may not contain a value. Instead of returning null, we can return an Optional to clearly indicate that a value might be absent. Why I find it useful: It reduces the need for multiple null checks and makes the code more readable and expressive. It also encourages better coding practices by forcing us to think about handling missing values. Key methods I explored: Creation: - Optional.empty() - Optional.of(value) - Optional.ofNullable(value) Checking: - isPresent() - isEmpty() Retrieving: - get() (should be used carefully) - orElse(defaultValue) - orElseGet(Supplier) - orElseThrow() Transformation: - map() - flatMap() - filter() Actions: - ifPresent() - ifPresentOrElse() Example I tried: Optional<String> name = Optional.ofNullable("Java"); String result = name .map(String::toUpperCase) .orElse("DEFAULT"); My takeaway: Optional is not just a class, it is a better way of thinking about handling null values. I am still exploring it, but it already feels like a powerful tool for writing safer and cleaner Java code. Looking forward to learning more and applying it in real-world projects. #Java #OptinalClass

Many beginners write classes in Java… …but forget how objects actually get initialized. That’s where Constructors come in. A constructor is a special method used to initialize objects. Constructors in Java are not just for initialization. They can also call each other. This is called Constructor Chaining. Example: class Student { String name; int age; ``` Student() { this("Unknown", 0); // calls parameterized constructor } Student(String name, int age) { this.name = name; this.age = age; } void display() { System.out.println(name + " - " + age); } ``` } Now: Student s1 = new Student(); s1.display(); Output: Unknown - 0 What’s happening here? The default constructor is calling another constructor using "this()". Key points: * this() is used for constructor chaining within the same class * It must be the first statement inside the constructor Why this matters: It avoids code duplication and makes initialization cleaner. Real takeaway: Write less code, but smarter code. #Java #OOP #Constructors #JavaProgramming #LearningInPublic #Coding

🚀 Optimizing Java Switch Statements – From Basic to Modern Approach Today I explored different ways to implement an Alarm Program in Java using switch statements and gradually optimized the code through multiple versions. This exercise helped me understand how Java has evolved and how we can write cleaner, more readable, and optimized code. 🔹 Version 1 – Traditional Switch Statement The basic implementation uses multiple case statements with repeated logic for weekdays and weekends. While it works, it results in code duplication and reduced readability. 🔹 Version 2 – Multiple Labels in a Case Java allows grouping multiple values in a single case (e.g., "sunday","saturday"). This reduces repetition and makes the code shorter and easier to maintain. 🔹 Version 3 – Switch Expression with Arrow (->) Java introduced switch expressions with arrow syntax. This removes the need for break statements and makes the code cleaner and less error-prone. 🔹 Version 4 – Compact Arrow Syntax Further simplification using single-line arrow expressions improves code readability and conciseness. 🔹 Version 5 – Returning Values Directly from Switch Instead of declaring a variable and assigning values inside cases, the switch expression directly returns a value, making the code more functional and elegant. 🔹 Version 6 – Using yield in Switch Expressions The yield keyword allows returning values from traditional block-style switch expressions, providing more flexibility when writing complex logic. 📌 Key Learning: As we move from Version 1 to Version 6, the code becomes: More readable Less repetitive More modern with Java features Easier to maintain and scale These small improvements show how understanding language features can significantly improve the quality of code we write. 🙏 A big thank you to my mentor Anand Kumar Buddarapu for guiding me through these concepts and encouraging me to write cleaner and optimized Java code. #Java #JavaProgramming #CodingJourney #SoftwareDevelopment #LearnJava #SwitchStatement #Programming #DeveloperGrowth

🚀 Learning Core Java – Understanding the Diamond Problem Today I explored an important concept in Java — the Diamond Problem. In Java, every class implicitly extends the Object class (since JDK 1). This means all classes share a common parent. ⸻ 🔷 What is the Diamond Problem? The Diamond Problem occurs when multiple inheritance creates ambiguity in method resolution. Let’s understand conceptually: • Class A is the parent (implicitly extends Object) • Class B and Class C both extend A • Both override a method (for example: toString()) • Now, Class D tries to inherit from both B and C 👉 The question is: Which method should Class D use? • From Class B? • From Class C? This confusion creates ambiguity. Because of this structure, it visually looks like a diamond shape: A / \ B C \ / D 🚫 Why Java Does Not Allow This To avoid this ambiguity: ❌ Java does not support multiple inheritance using classes ❌ This prevents method conflicts and keeps behavior predictable ⸻ ✅ How Java Solves It Java allows multiple inheritance using interfaces, where: ✔ There is no ambiguity in basic method declarations ✔ If conflicts occur (default methods), Java forces explicit resolution ⸻ 💡 Key Insight 👉 Diamond Problem = Ambiguity in multiple inheritance 👉 Java avoids it by restricting multiple inheritance in classes 👉 Uses interfaces as a safe alternative ⸻ Understanding this concept is important for writing clean, predictable, and scalable Java applications. Excited to keep strengthening my OOP fundamentals! 🚀 ⸻ #CoreJava #DiamondProblem #ObjectOrientedProgramming #JavaDeveloper #ProgrammingConcepts #LearningJourney #SoftwareEngineering #TechLearning