# Avoid static imports

DevFeed: [Avoid static imports](<https://devfeed.tech/articles/avoid-static-imports-37681.md>)

Original publisher: [Read original article](<https://carlosbecker.com/posts/avoid-static-imports/>)

Author: Carlos Alexandro Becker

Published: 2015-07-05T00:00:00Z

Content type: opinion

Language: en

Sources: [Carlos Becker](<https://devfeed.tech/sources/carlos-becker.md>)

Topics: [Java](<https://devfeed.tech/topics/java.md>), [Object-oriented programming (OOP)](<https://devfeed.tech/topics/oop.md>)

Tags: [antipattern](<https://devfeed.tech/tags/antipattern.md>), [avoid](<https://devfeed.tech/tags/avoid.md>), [code](<https://devfeed.tech/tags/code.md>), [java](<https://devfeed.tech/tags/java.md>), [oop](<https://devfeed.tech/tags/oop.md>), [readability](<https://devfeed.tech/tags/readability.md>)

## AI overview

The article argues that Java static imports should be used sparingly because overuse can obscure where methods and members originate, pollute the namespace, and reduce code readability and maintainability. It recommends importing only a small number of frequently used static members when appropriate.

## Source excerpt

There are a lot of Java API's and Frameworks which rely on static methods and the sort. Arguably, this is a bad OOP practice, but let's not enter this particular subject just yet.