Skip to main content

Coding Standards In Java

 Coding Standards for Components: It is recommended to write components name by its purpose. This approach improves the readability and maintainability of code.

Coding Standards for Classes: Usually class name should be noun starting with uppercase letter. If it contains multiple word than every inner word should start with uppercase.

Eg: String, StringBuffer, Dog

Coding Standards for Interface: Usually interface name should be adjective starting with uppercase letter. If it contains multiple word than every inner word should start with uppercase.

Eg: Runnable, Serializable, Comparable

Coding Standards for Methods: Usually method name should either be verb or verb noun combination starting with lower letter. If it contains multiple word than every inner word should start with uppercase.

Eg: print(), sleep(), setSalary()

Coding Standards for Variables: Usually variable name should be noun starting with lowercase letter. If it contains multiple word than every inner word should start with uppercase.

Eg: name, age. mobileNumber

Coding Standards for Constants: Usually constant name should be noun. It should contain only uppercase If it contains multiple word than words are separated with ( _ ) underscore symbol. Usually we declare constants with public static and final modifiers.

Java Bean Coding Standards: A Java Bean is a simple java class with private properties and public getter and setter methods

Getter Methods:

It should be public method

Method name should be prefixed with “get”

It should not take any argument

Setter Methods:

It should be public method

Return Type should be void

Method name should be prefixed with “set”

It should take some argument

public class StudentBean{

private String name;

public void setName(String name){

this.name=name;

}

public String getName(){

return name;

}

}

Note: For boolean properties getter method can be prefixed with “get” or “is”

Comments

Popular posts from this blog

JDK 25: The new features in Java 25

 Java Development Kit (JDK) 25, scheduled for release in September 2025, is set to introduce several significant enhancements. Here's an overview of the notable features: 1. Stable Values API (Preview): This feature introduces stable values—objects holding immutable data treated as constants by the Java Virtual Machine (JVM). By allowing greater flexibility in initialization timing compared to final fields, stable values aim to improve application startup times. They enable performance optimizations akin to constant-folding, previously exclusive to JDK code, and ensure thread-safe, single-time initialization. This decouples the creation of stable values from their initialization without significant performance penalties.  2. Removal of 32-bit x86 Port: JDK 25 plans to eliminate both the source code and build support for the 32-bit x86 port, which was deprecated in JDK 24. Maintaining this port has become less beneficial, especially with the challenges in keeping it updated wit...

Interview Preparation Guide for IT Graduates: What to Expect in 2024

Introduction: The evolving nature of IT interviews Importance of holistic preparation Section 1: Technical Interviews Common formats: whiteboard coding, take-home assignments, online coding platforms Key areas to focus: algorithms, data structures, system design Section 2: Behavioral Interviews STAR method (Situation, Task, Action, Result) for structuring responses Common questions: teamwork, problem-solving, handling failure Section 3: Coding Challenges Recommended platforms: LeetCode, HackerRank, Code Signal Strategies for practicing effectively Section 4: Soft Skills Communication: articulating thoughts clearly  Teamwork: working collaboratively in a diverse environment Adaptability: learning new technologies quickly Conclusion:Importance of mock interviews and feedback Resources and tools to aid in preparation

Clean Architecture with Spring Boot: A Good Idea?

Clean Architecture with Spring Boot: In the world of software development, architecture plays a crucial role in determining the maintainability, scalability, and testability of an application. One architecture style that has gained popularity is Clean Architecture . But what exactly is Clean Architecture, and is it a good idea to use it with Spring Boot? Let’s dive in! What is Clean Architecture? Clean Architecture is a software design philosophy introduced by Robert C. Martin, also known as "Uncle Bob." The main idea behind Clean Architecture is to separate the concerns of your application into distinct layers, making your codebase more modular, easier to maintain, and less dependent on external frameworks. The Layers of Clean Architecture Clean Architecture is typically divided into the following layers: 1. Entities : The core business logic of your application. This layer is independent of any external system or framework. It contains the business rules that are critical t...