🚀 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

💎 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

🚨 Exception Handling in Java: A Complete Guide I used to think exception handling in Java was just about 👉 try-catch blocks and printing stack traces. But that understanding broke the moment I started writing real code. I faced: - unexpected crashes - NullPointerExceptions I didn’t understand - programs failing without clear reasons And the worst part? 👉 I didn’t know how to debug properly. --- 📌 What changed my approach Instead of memorizing syntax, I started asking: - What exactly is an exception in Java? - Why does the JVM throw it? - What’s the difference between checked and unchecked exceptions? - When should I handle vs propagate an exception? --- 🧠 My Learning Strategy Here’s what actually worked for me: ✔️ Step 1: Break the concept - Types of exceptions (checked vs unchecked) - Throwable hierarchy - Common runtime exceptions ✔️ Step 2: Write failing code intentionally I created small programs just to: - trigger exceptions - observe behavior - understand error messages ✔️ Step 3: Learn handling vs designing - try-catch-finally blocks - throw vs throws - creating custom exceptions ✔️ Step 4: Connect to real-world development - Why exception handling is critical in backend APIs - How improper handling affects user experience - Importance of meaningful error messages --- 💡 Key Realization Exception handling is not about “avoiding crashes” 👉 It’s about writing predictable and reliable applications --- ✍️ I turned this learning into a complete blog: 👉 Exception Handling in Java: A Complete Guide 🔗 : https://lnkd.in/gBCmHmiz --- 🎯 Why I’m sharing this I’m documenting my journey of: - understanding core Java deeply - applying concepts through practice - and converting learning into structured knowledge If you’re learning Java or preparing for backend roles, this might save you some confusion I had earlier. --- 💬 What was the most confusing exception you faced in Java? #Java #CoreJava #ExceptionHandling #BackendDevelopment #SpringBoot #LearningInPublic #SoftwareDevelopment #CodingJourney

🚀 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

🔹 Version 1: Traditional Switch Case Started with the basics of switch-case in Java using the traditional approach. ✔ Uses ":" (colon) syntax ✔ Requires "break" to prevent fall-through ✔ Simple and widely used in older Java versions 🔹 Version 2: Multiple Case Labels Explored handling multiple inputs in a single case block. ✔ Multiple case labels share the same logic ✔ Reduces code duplication ✔ Makes code more readable This version showed me how to simplify conditions when different inputs produce the same result. 🔹 Version 3: Arrow Syntax (->) Learned the modern switch syntax introduced in newer Java versions. ✔ Uses "->" instead of ":" ✔ No need for "break" ✔ More concise and readable 🔹 Version 4: Switch as Expression (No Breaks) Tried using switch as an expression instead of a statement. ✔ No "break" needed ✔ Directly returns a value ✔ More structured and efficient This approach made my code shorter and more expressive. 🔹 Version 5: Single Result Variable Focused on improving code structure by using a single result variable. ✔ All cases return a value ✔ Output handled outside the switch ✔ Better separation of logic and display This makes the code more maintainable and reusable. 🔹 Version 6: Using yield Explored advanced switch expressions using "yield". ✔ Used inside block cases ✔ Allows multiple statements before returning value ✔ More flexibility in logic This helped me understand how to handle complex scenarios inside switch expressions. #java #Codegnan #CodingJourney #SwitchCase My gratitude towards my mentor #AnandKumarBuddarapu #SakethKallepu #UppugundlaSairam

🔍 Understanding Arrays in Java (Memory & Indexing) Today I learned an important concept about arrays in Java: Given an array: int[] arr = {10, 20, 30, 40, 50}; We often think about how elements are stored in memory. In Java: ✔ Arrays are stored in memory (heap) ✔ Each element is accessed using an index ✔ JVM handles all memory internally So when we write: arr[0] → 10 arr[1] → 20 arr[2] → 30 arr[3] → 40 arr[4] → 50 👉 We are NOT accessing memory directly 👉 We are using index-based access Very-Important Point:  👉 Concept (Behind the scenes) we access elements using something like base + (bytes × index) in Java 💡 Let’s take an example: int[] arr = {10, 20, 30, 40, 50}; When we write: arr[2] 👉 We directly get 30 But what actually happens internally? 🤔 Behind the scenes (Conceptual): Address of arr[i] = base + (i × size) let's suppose base is 100 and we know about int takes 4 bytes in memory for every element :100,104,108,112,116 So internally: arr[2] → base + (2 × 4) Now base is : 100+8=108 now in 108 we get the our value : 30 Remember guys this is all happening behind the scenes 👉 You DON’T calculate it 👉 JVM DOES it for you 👉 But You Still need to know ✔ Instead, it provides safety and abstraction 🔥 Key Takeaway: “In Java, arrays are accessed using indexes, and memory management is handled by the JVM.” This concept is very useful for: ✅ Beginners in Java ✅ Understanding how arrays work internally ✅ Building strong programming fundamentals #Java #Programming #DSA #Coding #Learning #BackendDevelopment

📅🚀 Date Formats in Java Handling date and time is a crucial part of building real-world applications — from logging events to scheduling systems. While learning Java, I explored how powerful the java.time package is for managing dates efficiently and cleanly. 📌 Key Classes You Should Know: • LocalDate → Handles only date (year, month, day) • LocalTime → Handles time (hours, minutes, seconds) • LocalDateTime → Combines both date & time 📌 Formatting & Parsing Dates: Using DateTimeFormatter, we can easily convert dates into readable formats and vice versa. 🔹 Example: LocalDate date = LocalDate.now(); DateTimeFormatter formatter = DateTimeFormatter.ofPattern("dd-MM-yyyy"); String formattedDate = date.format(formatter); 📌 Popular Date Patterns: • dd-MM-yyyy → 31-03-2026 • yyyy-MM-dd → 2026-03-31 • dd/MM/yyyy → 31/03/2026 • MMM dd, yyyy → Mar 31, 2026 📌 Why It Matters: ✔ Ensures consistency across applications ✔ Improves readability for users ✔ Helps in internationalization (different regions use different formats) ✔ Essential for backend systems, APIs, and databases 💡 Small improvements like proper date formatting can make your applications look more professional and user-friendly. What date format do you usually use in your projects? 👇 Grateful to my mentor Anand Kumar Buddarapu for guiding me and helping me understand real-world concepts in Java. #Java #Programming #Coding #JavaDeveloper #TechLearning #SoftwareDevelopment #DeveloperJourney

🚀 Deep Dive into the static Keyword in Java Today I explored one of the most important core concepts in Java — the static keyword. Understanding static is essential because it explains how memory is managed and how class-level behavior works in Java. A Java class contains two major types of members: 🔹 Static Members (Class Level) • Static Variables • Static Methods • Static Blocks 🔹 Non-Static / Instance Members (Object Level) • Instance Variables • Instance Methods • Instance Blocks • Constructors 👉 Key Idea: Static members belong to the class (imaginary) Instance members belong to the object (real) 📌 Rules of Static (Very Important) ✔ Static members can directly access only static data ✔ Instance members can access both static and non-static data ❌ Static members cannot directly access instance variables ✔ Static keyword can be applied to variables, methods, blocks, and nested classes 🔹 Static Variables Static variables are class-level variables. ✨ Key points: • Belong to the class, not objects • Created once when the class loads into memory • A single copy is shared by all objects • Initialized before instance variables 💡 Perfect use cases: • Counters • Constants • Shared configuration values 🔹 Static Methods Static methods belong to the class, not objects. ✔ Can access only static data directly ✔ Cannot call non-static members directly ✔ Called using ClassName.methodName() Example: ClassName.methodName(); Static methods are commonly used for utility functions. 🔹 Static Block (Execution Flow) A static block is a special block that runs only once when the class loads. 📌 Purpose: • Initialize static variables • Perform one-time setup tasks Execution Order in Java When a class is loaded: 1️⃣ Static variables 2️⃣ Static block 3️⃣ Main method starts 4️⃣ Object creation → Instance block 5️⃣ Constructor 6️⃣ Instance methods This flow explains how Java manages memory segments (Stack, Heap, Static Area) during execution. Understanding static helps us write memory-efficient, optimized, and well-structured programs 💻✨ Next in my Java journey → Exploring more advanced OOP concepts 🔥 TAP Academy #Java #OOP #Programming #Developers #CodingJourney #LearnInPublic #ComputerScience

Day 11/100 – Java Practice Challenge 🚀 Continuing my #100DaysOfCode journey with another important Java concept. 🔹 Topic Covered: Compile-time vs Runtime Polymorphism 💻 Practice Code: 🔸 Compile-time Polymorphism (Method Overloading) class Calculator { int add(int a, int b) { return a + b; } int add(int a, int b, int c) { return a + b + c; } } 🔸 Runtime Polymorphism (Method Overriding) class Animal { void sound() { System.out.println("Animal sound"); } } class Cat extends Animal { @Override void sound() { System.out.println("Cat meows"); } } public class Main { public static void main(String[] args) { // Compile-time Calculator c = new Calculator(); System.out.println(c.add(10, 20)); System.out.println(c.add(10, 20, 30)); // Runtime Animal a = new Cat(); a.sound(); } } 📌 Key Learnings: ✔️ Compile-time → method decided at compile time ✔️ Runtime → method decided at runtime ✔️ Overloading vs Overriding difference 🎯 Focus: Understanding how Java resolves method calls 🔥 Interview Insight: Difference between compile-time and runtime polymorphism is one of the most frequently asked Java interview questions. #Java #100DaysOfCode #MethodOverloading #MethodOverriding #Polymorphism #JavaDeveloper #Programming #LearningInPublic

I used == for Strings when I first started learning Java… and got the wrong result 😅 That small mistake led me to understand one of the most important Java concepts: Heap Memory + String Constant Pool (SCP) Example 1 👇 String str1 = "Zayyni"; String str2 = "zayyni"; System.out.println(str1 == str2); // false System.out.println(str1.equals(str2)); // false System.out.println(str1.equalsIgnoreCase(str2)); // true Here: == → compares memory reference (same object or not) .equals() → compares actual content .equalsIgnoreCase() → compares content while ignoring case sensitivity Now the interesting part 👇 String str1 = new String("Zayyni"); String str2 = new String("Zayyni"; System.out.println(str1 == str2); // false System.out.println(str1.equals(str2)); // true Why? Because new String() creates a new object in Heap Memory every single time. Even if the value is the same, Java creates separate objects. But when we write: String str1 = "Zayyni"; String str2 = "Zayyni"; Java uses the String Constant Pool (SCP) where duplicate string literals are not created again. This saves memory and improves performance. That’s also one of the major reasons why String is immutable in Java — it makes pooling safe, efficient, and reliable. Sometimes the smallest Java concepts teach the biggest lessons. This topic is simple… but it appears in interviews more than people expect 👀 What Java concept confused you the most when you started? 👇 #Java #JavaDeveloper #SpringBoot #BackendDevelopment #Programming #SoftwareEngineering #Coding #Developers #JavaProgramming #JVM #StringPool #HeapMemory #InterviewPreparation #DeveloperLife #TechLearning #CleanCode #CodingJourney #LinkedInLearning #SoftwareDeveloper