The article critiques object-oriented programming (OOP), arguing that it has led to problematic practices in software development. The author defines key terms like data structures, functions, classes, and methods to establish a clear framework for discussion. They point out that OOP relies heavily on classes and methods, which can create rigid dependencies and hinder code reusability. For instance, instance methods in OOP are tightly coupled to their classes, limiting their applicability to other data types and making it difficult to handle cases like null values. The author shares a personal anecdote from an early C# interview, highlighting confusion over OOP constructs like static constructors and the Singleton pattern. This experience sparked a deeper examination of OOP’s validity, leading to a belief that it complicates programming unnecessarily. The comparison between OOP and functional programming (FP) reveals significant differences, especially regarding how methods and functions are structured and reused. The author argues that FP, with its emphasis on pure functions and immutability, offers a more flexible and predictable approach to programming. Through examples, the article illustrates how OOP’s reliance on class methods creates challenges in reusability and adaptability. A method in a class can only operate on instances of that class, which limits its utility across different types of data. In contrast, a functional approach allows for more straightforward manipulation of data without the same dependencies. This perspective raises questions about the efficacy of OOP, suggesting that its widespread adoption may not reflect the best practices in programming today.