Choose a convention and stick with it. Your chosen conventions could be the worst fit for your domain, but the code following "a" convention ensures that people jumping in later can actually follow along and it makes refactoring at least bearable.

I personally don't like when people stick to SOLID like it's the holy hammer, but nearly every serious programming language has a convention on how to write SOLID code, and it will be followed, which makes my job easier if I'm new to the codebase.

I tend to agree with this take. If you do something wrong at least doing it consistently will be more valuable than not. Unfortunately dogma is not easy to avoid. Even it wasn't for Bob's Clean Code, some other guy would distill some patterns, market another book with a catchy title that'd be inevitably somewhat misunderstood and misused.