# Why the author questions SOLID and proposes CLARITY principles

DevFeed: [Why the author questions SOLID and proposes CLARITY principles](<https://devfeed.tech/articles/when-solid-breaks-choose-clarity-38657.md>)

Original publisher: [Read original article](<https://krossovochkin.com/posts/2025_05_05_when_solid_breaks_choose_clarity/>)

Published: 2025-05-05T00:00:00Z

Content type: opinion

Language: en

Sources: [Vasya Drobushkov](<https://devfeed.tech/sources/vasya-drobushkov.md>)

Topics: [Development](<https://devfeed.tech/topics/development.md>), [Programming](<https://devfeed.tech/topics/programming.md>), [clean-code](<https://devfeed.tech/topics/clean-code.md>)

Tags: [best-practices](<https://devfeed.tech/tags/best-practices.md>), [development](<https://devfeed.tech/tags/development.md>), [opinions](<https://devfeed.tech/tags/opinions.md>), [programming](<https://devfeed.tech/tags/programming.md>)

## AI overview

The author argues that SOLID principles are interpreted inconsistently and that rigid application can produce difficult-to-maintain code. The article proposes using a set of principles called CLARITY instead, beginning with consistent abstraction levels.

## Source excerpt

A long time ago, when I had just started my journey into programming, development, and engineering, it wasn't easy to find information, and bikeshedding could happen quite often because of that. We read books to gain insights into best practices and learn how to do things correctly. The concepts from the past were usually crucial and provided a great ramp-up to avoid obvious mistakes. Over time, we became flooded with information and opinions. In such an environment, old-time thoughts may even seem better, as they've been tested by time and by many engineers in the field.