Java Inheritance: Reusing Code for Scalable Applications

In college, I "learned" many programming languages. Python, Java, JavaScript, C. I touched them all. But touch is the right word. I never went deep. Flow control (loops, if-else), basic CRUD APIs; nothing beyond the surface. One such language was Go. I've been at Groww since my 3rd year of college, and somewhere around 85% of my work has been Java or JVM-based. And honestly? Java is a fantastic language for what it's designed for. Enterprise scale, batteries included, battle-tested for decades. I have deep respect for it. But Go has been quietly taking over. Its simplicity, built-in concurrency primitives, fast compile times, and lean runtime make it increasingly attractive for high-throughput backend services and infrastructure tooling. More teams are picking it up every year. We have a few Go services at Groww, and I recently had to work on one of them. Coming from a Java mental model (where I've spent nearly 4 years), the syntax and idioms felt foreign. Goroutines vs threads. No classes, no exceptions. Interfaces that are implicitly satisfied. Error handling via return values. I kept reaching for patterns that just don't exist the same way in Go. I asked Claude for help in understanding the differences. What came out of that conversation was something I thought was worth turning into a proper resource: a side-by-side reference for Java developers learning Go, mapping familiar Java concepts to their Go equivalents. So I built it. 21 guided sections, Java vs Go code comparisons, covering everything from the mental model shift to project layout. Claude helped me build the site itself. I'm genuinely interested in learning in public and building tools that help others learn. If you're a Java developer navigating Go (or vice versa), I hope this saves you a few hours of confusion. 🔗 Links in comments — deployed site + GitHub repo. The repo is open. If you spot something wrong or want to add a section, PRs and issues are very welcome. Would love the community's help in making it more complete and accurate. 🙏

🚀 AI Powered Java Full Stack Journey with Frontlines EduTech (FLM) — Day 5 📌 Naming Conventions & Data Types in Java — The First Strong Step into Coding Day 5 marked the beginning of actual coding fundamentals. This session focused on writing clean, structured, and meaningful Java code. The key topics covered were: 👉 Naming Conventions 👉 Variables & Data Types 👉 Why Java is a Strictly Typed Language 🔥 1. Naming Conventions in Java — Code’s First Impression Coding is not just about logic. Proper naming makes code readable, professional, and maintainable. ✔ Class Names → PascalCase Every word starts with a capital letter. Examples: • StudentProfile • CollegeAttendance Rules: • Can use alphabets and numbers • Cannot start with a number • _ and $ are allowed but not recommended ✔ Variable Names → camelCase First word lowercase, next words capitalized. Examples: • studentId • assignmentScore Rules: • Cannot start with a number • Use meaningful names • Avoid unnecessary special characters ✔ Method Names → camelCase Examples: • calculateCgpa() • submitAssignment() ✔ Package Names → lowercase only Examples: • com.student.portal • com.flm.media ✔ Project Names → PascalCase Examples: • JavaBasicsProject • CollegeAttendanceTracker Understanding naming standards made me realize how important clean structure is in real-time development. 🔥 2. Data Types in Java (Strongly Typed Nature) Java requires us to declare the type of data before storing a value. It ensures type safety and prevents unexpected errors. 🧊 Primitive Data Types (8 Total) ✔ Integer Types: • byte (1 byte) → -128 to 127 • short (2 bytes) • int (4 bytes) → commonly used • long (8 bytes) → large values ✔ Decimal Types: • float (4 bytes) → ~7 digits precision • double (8 bytes) → ~16 digits precision ✔ Character Type: • char (2 bytes) → stores single character like 'A' ✔ Boolean Type: • true / false 🧠 Why Multiple Number Types? Because of memory optimization and range control. • byte → small values • int → default numeric type • long → very large numbers This session gave me clarity on memory allocation and type safety in Java. 🎯 Day 5 Takeaways: ✨ Importance of proper naming conventions ✨ Structure and readability in coding ✨ Clear difference between byte, short, int, and long ✨ Understanding float vs double precision ✨ Strongly typed nature of Java ✨ Basics of memory usage With each day, my understanding of Java fundamentals is becoming stronger and more structured. Grateful for the continuous learning journey 🚀 Special thanks to Krishna Mantravadi, Upendra Gulipilli, and Fayaz S for making every concept simple and practical. #Java #FullStackDeveloper #LearningInPublic #DataTypes #NamingConventions #JavaBasics #FrontlinesEduTech #CodingLife #Day5

🔥 Java Deep Dive – Understanding How Java Really Works (Post #2) In my previous post, I explored Java Access Modifiers (public, private, protected, default) — how we control visibility 🔐 Today, I took the next step… 👉 Non-Access Modifiers in Java — controlling behavior ⚙️ I’m still learning and exploring, and sharing my understanding along the way to grow with the community 🙌 💡 My Understanding (with real-world + code) 🔹 static – Shared Across All Objects 🏢 ➡️ Like a company name — same for every employee class Company {    static String companyName = "ABC Pvt Ltd"; } 👉 No need to create objects — shared everywhere 🔹 final – Cannot Be Changed 🔒 ➡️ Like your NIC / Date of Birth class Person {    final String nic = "200012345678"; } 👉 Once assigned → ❌ cannot modify 🔹 abstract – Blueprint 🧩 ➡️ Like a Vehicle concept (rules, not implementation) abstract class Vehicle {    abstract void start(); } class Car extends Vehicle {    void start() {        System.out.println("Start with key");    } } 👉 Defines what to do, not how 🔹 synchronized – One at a Time 🏧 ➡️ Like an ATM machine synchronized void withdraw() {    // only one thread at a time } 🔹 transient – Do Not Store 🚫💾 ➡️ Like passwords / PINs transient String password; 🔹 volatile – Always Latest Value 📡 ➡️ Like a live cricket score volatile int score; 🔹 native – External Power ⚡ ➡️ Calls C/C++ code for system-level operations native void print(); 🧠 Big Picture ✔️ Access Modifiers → Who can access 🔐 ✔️ Non-Access Modifiers → How things behave ⚙️ 🚀 My Learning Approach I’m currently focusing on: ✔️ Understanding concepts with real-world thinking ✔️ Writing simple code examples ✔️ Building a strong Core Java foundation 📌 I’m still learning, and I know there’s a lot more to improve — So I’m sharing my journey to learn better and connect with others in the same path 🤝 🔜 What’s Next? 👉 Understanding how Access Modifiers and Non-Access Modifiers are stored in memory (Stack vs Heap) 💬 If you have suggestions, corrections, or tips — I’d truly appreciate it! #Java #SoftwareEngineering #BackendDevelopment #LearningJourney #100DaysOfCode

🚀 Learning Update: Deep Dive into Java Inheritance Today’s session gave me a much clearer understanding of one of the core pillars of Object-Oriented Programming in Java — Inheritance. I learned that inheritance is the process by which one class acquires the properties and behaviors of another class. It plays a major role in code reusability, reduced development effort, and better program structure. Key concepts I learned: 🔹 Static in Java Before moving fully into inheritance, I revised the concept of static in Java: Static variables help in memory efficiency because only one copy is created for the entire class. Static blocks are used to initialize static variables and execute code before the main() method. Static methods can be called without creating objects, making them useful for class-level functionality. I also learned that static can be used with an inner class, but not with an outer class. 🔹 Inheritance in Java Inheritance allows a child class to access the fields and methods of a parent class using the extends keyword. This makes programs more structured and avoids rewriting the same logic again and again. Types of inheritance I understood: ✅ Single Inheritance – One parent and one child ✅ Multilevel Inheritance – Grandparent → Parent → Child ✅ Hierarchical Inheritance – One parent with multiple children ✅ Hybrid Inheritance – Combination of inheritance types ❌ Multiple Inheritance – Not allowed in Java because of the Diamond Problem / Ambiguity ❌ Cyclic Inheritance – Not allowed because it creates inconsistency in type hierarchy Every class in Java indirectly extends the Object class Private members do not participate in inheritance Constructors are not inherited Constructor execution between parent and child happens using constructor chaining with super() Difference between multilevel and multiple inheritance is very important 🔹 UML & Class Diagrams Another interesting takeaway was understanding how inheritance is represented using UML diagrams and how these diagrams help in the design phase of software development. This also connected with the idea of Software Development Life Cycle (SDLC), where requirement analysis and planning happen before coding begins. My takeaway: This session helped me realize that Java is not just about syntax — it is about understanding how real-world relationships are modeled in software. Strong basics in OOP concepts like inheritance are essential before moving on to polymorphism, abstraction, interfaces, exception handling, multithreading, collections, and advanced Java. Grateful for another step forward in my Java learning journey. Looking forward to learning more about constructor chaining, super keyword, and access modifiers in the next sessions. #Java #CoreJava #OOP #Inheritance #JavaProgramming #LearningJourney #SoftwareDevelopment #UML #SDLC #Programming #StudentDeveloper #CodingJourney TAP Academy

🚀 Mastering Stack in Java: A Common Mistake & Learning Moment! While working on a classic problem—Balanced Brackets using Stack—I came across a subtle but important mistake that many learners (and even developers!) tend to make. 🔍 The Problem Check whether a given string of brackets like {[()]} is balanced or not. 💡 The Mistake Using: 👉 remove() instead of pop() At first glance, it seems fine… but here’s the catch: ❌ remove() → removes element from anywhere in the stack ✅ pop() → removes the top element (LIFO principle) And Stack is all about Last In First Out! ⚠️ Why this matters? Without proper matching and order, your logic may incorrectly validate unbalanced expressions. 🧠 Key Learnings ✔ Always follow LIFO in stack problems ✔ Match opening & closing brackets correctly ✔ Check for empty stack before popping ✔ Validate final stack is empty 💻 Correct Java Program import java.util.*; public class StackBasedProgram { public static void main(String[] args) { Scanner sc = new Scanner(System.in); int n = 4; while (n-- > 0) { String token = sc.next(); Stack<Character> st = new Stack<>(); boolean isBalanced = true; for (char c : token.toCharArray()) { if (c == '{' || c == '(' || c == '[') { st.push(c); } else if (c == '}' || c == ')' || c == ']') { if (st.isEmpty()) { isBalanced = false; break; } char top = st.pop(); if ((c == '}' && top != '{') || (c == ')' && top != '(') || (c == ']' && top != '[')) { isBalanced = false; break; } } } if (!st.isEmpty()) { isBalanced = false; } System.out.println(isBalanced); } } } ✨ Takeaway Small mistakes in method selection can completely change program behavior. Understanding the core concept is more important than just making the code run! 📌 This is a great exercise for students learning: Data Structures (Stack) Problem Solving Debugging skills 💬 Have you ever made a small mistake that taught you a big concept? Share your experience! #Java #DataStructures #Stack #Coding #Programming #Debugging #Learning #InterviewPreparation #Developers #ProblemSolving

In the last 20 years, I’ve coded with Java, C++, Rust, Go, and Python. Today, my programming language is slowly moving to English, and I’m not scared of that. A lot of engineers are. They think that if code starts coming from prompts, plans, and agents, then somehow the craft is dying. I don’t see it that way. I see it as the next abstraction layer. There was a time when people wrote much closer to the machine. Then we moved higher. Then higher again. Assembly to C to C++ C++ to Java, Python, Go. Every jump made some people uncomfortable. Now we are going through one more jump. A few months back, I was still using AI mostly inside VS Code. I would prompt, guide it, correct it, ask it to retry, and keep steering line by line. But in the last week or so, something changed for me. I moved more of my workflow to a CLI agent model, using ClaudeClaw. Now I define what I want in English. I ask for a plan first. I review the plan. Then the agent executes. It writes code, changes files, shows me diffs, and I review those diffs before I publish. What makes this even more interesting is how the workflow itself is evolving. You can now assign roles. A TL bot can break down the work and assign parts to 3 software developer bots. Once they execute the code, the TL bot reviews it. - Then the build can go to 2 QA bots for verification. - Any bugs found can go back to the developer bots for fixes. - Then it goes through reverification again. That cycle can keep running until the code reaches an acceptable quality level. The strange part is this: I am not staring at code the whole time anymore. I am spending more time thinking about: – what I want built – what the right approach is – whether the plan makes sense – whether the diff matches the intent That is still engineering. The interface has changed. The responsibility has not. People keep asking, "So are you not coding anymore?" No. I still am. When I wrote Java, that was already an abstraction over lower-level instructions. The computer still did not "understand Java", It understood something much lower after many layers translated my intent. This is the same thing again, just one level higher. English is becoming a valid way to express programming intent. That does not mean everybody suddenly becomes a great engineer. It just means the barrier to entry is getting lower. The hard part is moving up the stack. The syntax burden is reducing. The thinking burden is not. That is why I am not afraid of this shift. Only now, the language I start with is increasingly English. And honestly, I think more engineers should get comfortable with that reality.

This!! Every time a new high-level programming language comes out, the barrier to entry drops a little more. First it was machine code. Then assembly. Then C. Then Python, JavaScript, Go Now English At this rate, I wouldn’t be surprised if the next step is: “Build me a food delivery app with real-time tracking, AI recommendations, and dark mode.” …thinks really hard for 5 seconds… App: Deployed to production. Future job description: “Required skills: Strong problem solving, basic internet connection, and the ability to think clearly.” Software engineers in 2040: “Sorry, the app crashed… I had a distracting thought in the middle of deployment.” 😅

This is a very neat take on the future of programming. It might be my confirmation bias but I found this post very interesting.

🚀 AI Powered Java Full Stack Journey with Frontlines EduTech (FLM) – Day 6 📌 Strings & Operators in Java — Understanding Data and Actions Day 6 helped me understand how Java handles text using Strings and how operators perform calculations and updates. This session made coding feel more practical and structured. 🔷 String (Non-Primitive Data Type) String is not a primitive type — it is a class. It stores a sequence of characters including letters, numbers, spaces, and symbols. String name = "Charan"; String course = "Java Full Stack"; Key Points: • Default value of a class reference = null • Size ≈ characters × 2 bytes (excluding object overhead) • Strings belong to java.lang (no import needed) • Spaces are counted as characters ⭐ Why String Matters Used in forms, login systems, messages, and user input. It plays a major role in real-time applications. 🔹 Immutability Once created, a String cannot be changed. If modified, a new object is created. String s = "Java"; s = "FullStack"; // new object 🔹 Common Methods name.length(); name.toUpperCase(); name.charAt(0); name.contains("Java"); 🔹 Empty vs Null String a = ""; // length = 0 String b = null; // no reference Calling methods on null causes NullPointerException. 🔥 Operators in Java Operators perform operations on values and variables. 1️⃣ Arithmetic Operators int a = 10, b = 5; a + b; // Addition a - b; // Subtraction a * b; // Multiplication a / b; // Division a % b; // Remainder Note: 10 / 0 → Error 10.0 / 0 → Infinity 2️⃣ Assignment Operators int a = 10; a += 5; a -= 2; a *= 3; a /= 4; a %= 5; They make value updates shorter and more efficient. 🎯 Day 6 Takeaways ✨ String is a class and immutable ✨ Understanding null vs empty ✨ Practical use of String methods ✨ Strong clarity on arithmetic operators ✨ Efficient use of assignment operators Each day is strengthening my Java fundamentals and coding confidence. Grateful for the continuous learning journey 🚀 Thanks to Krishna Mantravadi, Upendra Gulipilli, and Fayaz S for the clear and practical teaching. #Java #JavaBasics #JavaOperators #StringsInJava #FullStackDeveloper #LearningInPublic #Day6 #FrontlinesEduTech

Multithreading: the skill that separates 'it works' from 'it scales under load'. This intro covers the basics of why threads matter, how to create them, and the first pitfalls to avoid. If you've ever wondered why your app slows down with more users, start here. Full read: https://lnkd.in/eh2ai9GC Author: Ayush Shrivastava Our April Java Backend bootcamp builds on this foundation all the way to production grade concurrency (thread pools, synchronization, avoiding deadlocks). #Java #Multithreading #BackendEngineering #MasteringBackend