Class Methods and the final Keyword

Every instance method runs on behalf of some object — when you call acct.deposit(50), Java hands deposit a hidden reference to acct, which is what this means inside the method. A static method has no such object. You call it on the class itself, like Math.√16, and nothing gets passed in as this. That's why a static method cannot read or write an instance variable sitting in its own class: instance variables live inside objects, one copy per object, and a static method isn't running inside any particular one. There is no object to reach through.

This is not a minor inconvenience you work around — it is a structural rule. A static method could be made to call an instance method only by first building an object and calling the method on that object, the same way any outside code would. Inside a static main, you cannot call an instance method bare; you write new BankAccount() and go from there. The keyword static genuinely changes what a method is allowed to do, not just how conveniently you can call it.

final works on variables the way static works on methods: it changes a capability. A final variable can be assigned once, and the compiler enforces that strictly — not once per run casually, but exactly one assignment, ever, whether at declaration or in a constructor. Try to assign it again and the code won't compile. Together, static and final describe two different kinds of locking: one locks a method away from objects, the other locks a variable's value in place once set.