Use enums instead.

With any blanket statements like this, there are always exceptions.
Though in general, I believe the use of enums is often a better choice compared to boolean, unless you really need to squeeze your data into one single physical bit.

Let’s talk about some of the fundamental software design principles, which are typically applied behind the scenes by designers.

Software architecture represents the result of a sequence of design decisions which take place over time as long as software system complexity increases.

For the sake of clarity, let’s define an architecture as a collection of components combined together via connectors, which represent constraints on how components interact.

These are my personal principles for building software. I hope to frequently update them as my views change. There can be
valid reasons for breaking them (they are principles, not laws), but in general I believe following
them works out well.

Rich Hickey emphasizes simplicity’s virtues over easiness’, showing that while many choose easiness they may end up with complexity, and the better way is to choose easiness along the simplicity path.

This is a collection of things I believe about computer programming as of today.
It’s based on my own experience.