What are your opinions on https://en.wikipedia.org/wiki/SOLID ?

as long as it makes sense in your head it's valid

people overthink external organization systems too much

Asked LLM if it's a good idea to use it yes or no and to be critical and it said yes :P

Cherry pick from SOLID whatever makes sense for the particular project and team.

First reaction was 'Snake'? ... but then I saw the actual Wikipedia page.

By letters.

[S, O and I]: There is merit to having a base/generic implementation of some struct or functionality, then writing each specialization of it separately. This gives you granularity, in that you only have to include the bits you're actually going to use. In some cases this can speed up build times a lot as simply put you'll usually wind up with less symbols per file.

[L]: If the first field of struct B is an instance of struct A, then yes, ((A ptr) B) is a valid cast. The type theory word salad is very much redundant in this case, the property in question is mere common sense.

[D]: Making it so one module isn't dependent on the implementation _details_ of another is sound advice.

In conclusion, these ideas have validity and practical application, yet there is a special place in hell for Uncle Bob nonetheless.

I don't like capitals in URIs.