惯性聚合 高效追踪和阅读你感兴趣的博客、新闻、科技资讯
阅读原文 在惯性聚合中打开

推荐订阅源

爱范儿
爱范儿
P
Palo Alto Networks Blog
月光博客
月光博客
H
Hackread – Cybersecurity News, Data Breaches, AI and More
I
InfoQ
aimingoo的专栏
aimingoo的专栏
腾讯CDC
T
Threatpost
D
DataBreaches.Net
Vercel News
Vercel News
F
Fortinet All Blogs
Engineering at Meta
Engineering at Meta
C
Cybersecurity and Infrastructure Security Agency CISA
Forbes - Security
Forbes - Security
U
Unit 42
C
Check Point Blog
Blog — PlanetScale
Blog — PlanetScale
O
OpenAI News
量子位
TaoSecurity Blog
TaoSecurity Blog
Microsoft Azure Blog
Microsoft Azure Blog
cs.AI updates on arXiv.org
cs.AI updates on arXiv.org
V
Visual Studio Blog
Recorded Future
Recorded Future
云风的 BLOG
云风的 BLOG
Security Archives - TechRepublic
Security Archives - TechRepublic
The Last Watchdog
The Last Watchdog
S
Security Affairs
Attack and Defense Labs
Attack and Defense Labs
罗磊的独立博客
Stack Overflow Blog
Stack Overflow Blog
Microsoft Security Blog
Microsoft Security Blog
让小产品的独立变现更简单 - ezindie.com
让小产品的独立变现更简单 - ezindie.com
V
V2EX
小众软件
小众软件
S
SegmentFault 最新的问题
www.infosecurity-magazine.com
www.infosecurity-magazine.com
W
WeLiveSecurity
AI
AI
Threat Intelligence Blog | Flashpoint
Threat Intelligence Blog | Flashpoint
博客园 - 聂微东
I
Intezer
Know Your Adversary
Know Your Adversary
Exploit-DB.com RSS Feed
Exploit-DB.com RSS Feed
P
Proofpoint News Feed
freeCodeCamp Programming Tutorials: Python, JavaScript, Git & More
The Cloudflare Blog
博客园_首页
NISL@THU
NISL@THU
K
KPMG report finds enterprise disconnect between AI and its ROI | CIO

DEV Community

Authentication Security Deep Dive: From Brute Force to Salted Hashing (With Java Examples) Why AI Systems Don’t Fail — They Drift Spilling beans for how i learn for exam😁"Reinforcement Learning Cheat Sheet" I Replaced Chrome with Safari for AI Browser Automation. Here's What Broke (and What Finally Worked) How Python Borrows Other People's Work The $40 Architecture: Processing 1 Billion API Requests with 99.99% Uptime Vibe Coding: A Workflow Guide (From Zero to SaaS) Most webhook security guides protect the wrong side. The scary part is delivery. Headless CMS for TanStack Start: Build a Blog with Cosmic EU Age Verification App "Hacked in 2 Minutes" — What Actually Happened Comfy Cloud’s delete function does not actually remove files Running AI Models on GPU Cloud Servers: A Beginner Guide Event-driven media intelligence with AWS Step Functions and Bedrock I scored 500 AI prompts across 8 quality dimensions — here's what broke How to Call Google Gemini API from Next.js (Free Tier, No Backend Needed) The Portal Protocol: Reclaiming Human Connection in the Age of AI How to Fix Your Team's Scattered Knowledge Problem With a Self-Hosted Forum Intro to tc Cloud Functors: A Graph-First Mental Model for the Modern Cloud Designing Multi-Tenant Backends With Both Ownership and Team Access I Built a Neumorphic CSS Library with 77+ Components — Here's What I Learned PostgreSQL Performance Optimization: Why Connection Pooling Is Critical at Scale Cómo construí un SaaS multi-rubro para gestionar expensas en Argentina con FastAPI + Vue 3 🚀 I Built an Ethical Hacking Scanner Tool – Open Source Project I Replaced /usage and /context in Claude Code With a Single Statusline A Pythonic Way to Handle Emails (IMAP/SMTP) with Auto-Discovery and AI-Ready Design I Collected 8.9 Million Polymarket Price Points — Here's What I Found About How Markets Really Move EcoTrack AI — Carbon Footprint Tracker & Dashboard Everyone's Using AI. No One Agrees How. 5 self-hosted ebook managers worth trying in 2026 Building Your First AI Agent with LangChain: From Chatbot to Autonomous Assistant Common SOC 2 Failures (Real World) Stop Vibe-Checking Your AI App: A Practical Guide to Evals How to Use SonarQube and SonarScanner Locally to Level Up Your Code Quality Your Next To-Do App Is Dead — I Replaced Mine with an OpenClaw AI Sign a Nostr event in 60 lines of Python using coincurve — no nostr-sdk, no nbxplorer, no rust toolchain ITGC Audit Explained Like You’re in Big 4 Patch Tuesday abril 2026: Microsoft parcha 163 vulnerabilidades y un zero-day en SharePoint Stop scraping everything: a better way to track competitor price changes Listing on MCPize + the Official MCP Registry while routing payments OUTSIDE the marketplace — how I kept 100% of my x402 revenue Building an AI-Powered Risk Intelligence System Using Serverless Architecture Why We Ripped Function Overloading Out of Our AI Toolchain Testing AI-Generated Code: How to Actually Know If It Works SaaS Churn Is Killing Your Business. Here Is What to Do About It (Without a Support Team) The Speed of AI Is No Longer Linear - And Self-Improving Models Are Why How to Implement RBAC for MCP Tools: A Practical Guide for Engineering Teams From Standard Quote to Persuasive Proposal: AI Automation for Arborists I built a CLI that scaffolds complete multi-tenant SaaS apps Axios CVE-2025–62718: The Silent SSRF Bug That Could Be Hiding in Your Node.js App Right Now The dashboard that ended our friendship Data Pipelines Explained Simply (and How to Build Them with Python) The Hidden Cost of AI Systems Nobody Talks About. undefined vs undeclared, and how typeof behaves Switching from file-based jobs to NATS/Kafka in Rust without changing code io_uring Adventures: Rust Servers That Love Syscalls Why Agentic AI is Killing the Traditional Database The POUR principles of web accessibility for developers and designers Quantum Neural Network 3D — A Deep Dive into Interactive WebGL Visualization How To Install Caveman In Codex On macOS And Windows Automation Pipeline Reliability: Why Your Workflow Breaks When Nobody Is Watching I Built an 'Open World' AI Coding Agent — It Works From ANY Folder From Freelancing to Product: A Tech Service Company's SaaS Transformation China's AI Giants: Adding Tencent Hunyuan & ByteDance Doubao to AI University (74 Providers) On the Vibe Coders and Their Lies clerk: Auto-Summarize Your Claude Code Sessions AI Weekly — 2026/04/10–04/17 | The Model Lockdown Is Here, but the Toolchain Is the Real Battleground AI 週報 — 2026/04/10–2026/04/17 模型封鎖潮來了,但工具鏈才是真戰場 Maybe this is how Open-Source apps are born... 🚀 Fine-Tune LLMs with LoRA and QLoRA: 2026 Guide tRPC v11 + Next.js App Router: End-to-End Type Safety Without the Boilerplate ShadCN UI in 2026: Why I Stopped Installing Component Libraries and Started Owning My Components SaaS Billing in React Server Components: Stripe + Supabase Without a Single `useEffect` Join our DEV Weekend Challenge — $1,000 in Prizes Across TEN winners! Submissions Due April 20 at 6:59 AM UTC. Implementing FSRS Spaced Repetition in Flutter + Supabase — Adding Memory Science to an AI Learning App "I Texted My Localhost From the Train — Claude Code Fixed the Bug Before I Got Home" I Built a Sales Prep AI and It Went Deeper Than Expected Design to Code #2: One JSON, Eleven Outputs Solving the 100M-Row Problem: A Summary Table Pattern for High-Volume Push Notification Logs Flutter Web With Wasm: What Actually Changes For Developers I Built 50 Royalty-Free Soundtracks for My Side Project in a Weekend Using AI Music Generation The Vibe Coding Security Checklist: 7 Things to Check Before You Ship Stop Letting Googlebot Guess Fix Your React App's SEO Right Desconstruindo o Streaming do LinkedIn: Como Criar um Engine de Extração de Vídeo de Alta Performance com HLS e FFmpeg (EDA Part-1) EDA (Exploratory Data Analysis) Explained With Real Life — Why Looking at Your Data Is the Most Important Step in Machine Learning Brand Relationship Management at Scale: Our 4-Touch Outreach System for 200+ Brands Why String.fromEnvironment() Might Return an Empty String in Dart JGuardrails 1.0.0 — Hardening Java LLM Apps Against Jailbreaks, Toxicity, and Prompt Injection Plan and Schedule a Full Week of Threads Content From One Claude Conversation Coding Cat Oran Ep3, Five Tables Changed Everything Updated: BFF Pattern I'm done watching freelancers get buried by 200 proposals. So I'm building the alternative. This is my first post BFS Algorithm in Java Step by Step Tutorial with Examples Tracking LLM Pricing Monthly: An Open Dataset for 22 AI Models How We Measure Content ROI on a Comparison Site: Revenue Attribution Without Perfect Data Introducing Nova AI Ops: The AI-Native Operating System for SRE Teams I built a free desktop video downloader for Windows — Grabbit How Talkie OCR Helps Vision-Impaired & Dyslexic Users Read the World Around Them VRCFaceTracking安装和iPhone面捕配置教程,有bug Even CrowdStrike Can't See Your Agents The Automation Gold Rush: What n8n Workflows and Claude Are Opening Up for Developers Right Now
Understanding Java Constructors and Inheritance Through Simple Real-World Analogies
Ebenezer · 2026-06-04 · via DEV Community

Hey Folks! 👋

Good Day...

This blog is a summary of the concepts covered during the last two classes at my institute.

One of the reasons I enjoy writing these blogs is that they serve as my personal knowledge journal. Whenever I need a quick refresher on a concept, I can simply revisit my blog instead of searching through notes or recordings. It helps me reinforce what I've learned while also documenting my learning journey.

Over the past two days, we explored several important Java concepts, including constructors, the this keyword, inheritance, constructor chaining.

In this blog, I'll share what I learned in the simplest way possible, using real-world analogies, practical examples, and the thought process that helped me understand these concepts more clearly. If you're a beginner learning Java, I hope this walkthrough makes these topics a little easier to grasp and a lot more memorable.

What Is a Constructor?

According to Oracle Java Documentation:

A constructor is a special method that is used to initialize objects. The constructor is called when an object of a class is created.

In simple terms:

Imagine you order a new smartphone.

Before the phone reaches your hands, the factory installs the operating system, configures the hardware, and prepares everything for use.

A constructor does exactly the same thing for an object.

Before you use an object, Java uses the constructor to prepare it.


My First Confusing Example

I wrote the following code:

public class SuperMarket {

    String name = "python";
    int price;

    public SuperMarket(String name, int price) {

        System.out.println("Are you constructor?");

        name = name;
        price = price;
    }

    public static void main(String[] args) {

        SuperMarket product1 = new SuperMarket("abc", 20);

        System.out.println(product1.name);
    }
}

Enter fullscreen mode Exit fullscreen mode

I expected the output to be:

abc

Enter fullscreen mode Exit fullscreen mode

But Java printed:

python

Enter fullscreen mode Exit fullscreen mode

And honestly...

I was completely confused.

After all, I passed "abc" into the constructor.

Why was Java ignoring it?


The Hotel Room Analogy

Imagine a hotel room already contains a welcome card:

Guest Name : python

Enter fullscreen mode Exit fullscreen mode

This is equivalent to:

String name = "python";

Enter fullscreen mode Exit fullscreen mode

Now a new guest arrives and says:

new SuperMarket("abc", 20);

Enter fullscreen mode Exit fullscreen mode

Inside the constructor, Java receives:

name = "abc"
price = 20

Enter fullscreen mode Exit fullscreen mode

But then I wrote:

name = name;

Enter fullscreen mode Exit fullscreen mode

Java sees two variables named name.

Variable 1

Belongs to the object:

String name = "python";

Enter fullscreen mode Exit fullscreen mode

Variable 2

Belongs to the constructor parameter:

public SuperMarket(String name, int price)

Enter fullscreen mode Exit fullscreen mode

Java always looks at the nearest variable first.

Therefore:

name = name;

Enter fullscreen mode Exit fullscreen mode

actually means:

parameterName = parameterName;

Enter fullscreen mode Exit fullscreen mode

Nothing changes.

The object's value remains:

name = "python";

Enter fullscreen mode Exit fullscreen mode

That's why Java printed:

python

Enter fullscreen mode Exit fullscreen mode


The Solution: this

The correct code is:

public SuperMarket(String name, int price) {

    this.name = name;
    this.price = price;
}

Enter fullscreen mode Exit fullscreen mode

Here:

this.name

Enter fullscreen mode Exit fullscreen mode

means:

The name variable belonging to the current object.

Now Java understands:

this.name = name;

Enter fullscreen mode Exit fullscreen mode

as:

objectName = parameterName;

Enter fullscreen mode Exit fullscreen mode

or:

"python" = "abc"

Enter fullscreen mode Exit fullscreen mode

After execution:

product1.name

Enter fullscreen mode Exit fullscreen mode

contains:

abc

Enter fullscreen mode Exit fullscreen mode


Can We Avoid Using this?

Yes.

We can rename the parameters.

public SuperMarket(String productName, int productPrice) {

    name = productName;
    price = productPrice;
}

Enter fullscreen mode Exit fullscreen mode

Now there is no confusion.

However, in professional Java projects, most developers prefer:

this.name = name;

Enter fullscreen mode Exit fullscreen mode

because it is cleaner and follows standard coding conventions.


Enter Inheritance

After understanding constructors, we moved to inheritance.

I created two classes.

Parent Class

public class Mobile {

    public Mobile() {
        System.out.println("Mobile Parent");
    }

    public void call() {
        System.out.println("Calling");
    }

    public void msg() {
        System.out.println("Msg");
    }
}

Enter fullscreen mode Exit fullscreen mode

Child Class

public class Samsung extends Mobile {

    public Samsung() {
        System.out.println("Hey");
    }

    public void touch() {
        System.out.println("Touch");
    }
}

Enter fullscreen mode Exit fullscreen mode

Then I created an object:

Samsung samsung = new Samsung();

Enter fullscreen mode Exit fullscreen mode

Output:

Mobile Parent
Hey

Enter fullscreen mode Exit fullscreen mode

Now another question appeared.

Why is the Mobile constructor running when I only created a Samsung object?


Understanding super()

According to Java documentation:

The super keyword refers to the immediate parent class object.

When used as:

super();

Enter fullscreen mode Exit fullscreen mode

it calls the constructor of the parent class.

Think of it like this:

A child cannot exist before the parent exists.

Similarly, Java cannot fully create a child object until the parent portion of the object is initialized.


The House Construction Analogy

Imagine building a two-floor house.

Before constructing the first floor, you must build the ground floor.

Ground Floor
      ↓
First Floor

Enter fullscreen mode Exit fullscreen mode

Inheritance works exactly the same way.

Mobile
    ↓
Samsung

Enter fullscreen mode Exit fullscreen mode

Before Java builds the Samsung portion, it first builds the Mobile portion.

That's why Java automatically executes:

super();

Enter fullscreen mode Exit fullscreen mode

before running the Samsung constructor.


The Hidden super()

The interesting part is:

Even if we don't write:

super();

Enter fullscreen mode Exit fullscreen mode

Java automatically inserts it.

This constructor:

public Samsung() {
    System.out.println("Hey");
}

Enter fullscreen mode Exit fullscreen mode

is internally treated as:

public Samsung() {

    super();

    System.out.println("Hey");
}

Enter fullscreen mode Exit fullscreen mode

Execution Flow:

Mobile Constructor
        ↓
Samsung Constructor

Enter fullscreen mode Exit fullscreen mode

Output:

Mobile Parent
Hey

Enter fullscreen mode Exit fullscreen mode


Why Did "Mobile Parent" Print Twice?

My code later looked like this:

public static void main(String[] args) {

    Mobile mobile = new Mobile();

    Samsung samsung = new Samsung();

    samsung.touch();
    samsung.msg();
}

Enter fullscreen mode Exit fullscreen mode

Output:

Mobile Parent
Mobile Parent
Hey
Touch
Msg

Enter fullscreen mode Exit fullscreen mode

Initially I thought Java was calling the parent constructor twice for Samsung.

But that wasn't true.

Let's analyze it.


Object 1

Mobile mobile = new Mobile();

Enter fullscreen mode Exit fullscreen mode

Output:

Mobile Parent

Enter fullscreen mode Exit fullscreen mode


Object 2

Samsung samsung = new Samsung();

Enter fullscreen mode Exit fullscreen mode

Output:

Mobile Parent
Hey

Enter fullscreen mode Exit fullscreen mode


Total Output

Mobile Parent
Mobile Parent
Hey
Touch
Msg

Enter fullscreen mode Exit fullscreen mode

Two objects were created.

Therefore the Mobile constructor executed twice.


Why Wasn't "Hey" Printed Twice?

This question bothered me for a while.

The answer is simple.

I created:

new Mobile();

Enter fullscreen mode Exit fullscreen mode

once

and

new Samsung();

Enter fullscreen mode Exit fullscreen mode

once

Only Samsung objects can execute:

Samsung()

Enter fullscreen mode Exit fullscreen mode

constructor.

Since only one Samsung object was created:

Hey

Enter fullscreen mode Exit fullscreen mode

appeared only once.


My Biggest Takeaway

Before this exercise, I used to think constructors were just syntax.

Now I see them differently.

Constructors are responsible for:

  • Initializing objects
  • Assigning values
  • Preparing inherited classes
  • Executing parent-child constructor chains
  • Ensuring objects are ready before use

References

While exploring constructors, inheritance, and super(), I referred to the following resources for deeper understanding:

  1. Oracle Java Tutorials – Classes and Objects
    https://docs.oracle.com/javase/tutorial/java/javaOO/

  2. Oracle Java Tutorials – Constructors
    https://docs.oracle.com/javase/tutorial/java/javaOO/constructors.html

  3. Oracle Java Tutorials – Inheritance
    https://docs.oracle.com/javase/tutorial/java/IandI/subclasses.html

  4. Oracle Java Tutorials – Using the super Keyword
    https://docs.oracle.com/javase/tutorial/java/IandI/super.html

  5. Java Language Specification (JLS)
    https://docs.oracle.com/javase/specs/