> For the complete documentation index, see [llms.txt](https://www.pranaypourkar.co.in/the-programmers-guide/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://www.pranaypourkar.co.in/the-programmers-guide/interview-guide/technical/java-interview-companion/java-key-concepts/set-3.md).

# Set 3

## What are Public Static Methods ?

These are methods that belong to the class itself rather than to any particular instance of the class. They can be called without creating an instance of the class. Common uses for `public static` methods include utility methods, helper functions, or methods that operate on class-level data. For example:

```java
public class MathUtils {
    public static int add(int a, int b) {
        return a + b;
    }
}
```

Here, `add` is a `public static` method of the `MathUtils` class, allowing us to call it like `MathUtils.add(2, 3)` without needing to create an instance of `MathUtils`.

## What are Public Static Final Variables ?

These are constants that are associated with the class and cannot be changed once they are assigned a value. They are often used for values that are meant to be constant throughout the execution of the program. For example:

```java
public class Constants {
    public static final double PI = 3.14159;
}
```

Here, `PI` is a `public static final` variable of the `Constants` class, and its value cannot be modified once it's set. We can access it using `Constants.PI`.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://www.pranaypourkar.co.in/the-programmers-guide/interview-guide/technical/java-interview-companion/java-key-concepts/set-3.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.