When designing beautiful web pages we have the tendency to fallback to the well know options. This most of the time reduces to Bootstrap and Material Design. If you want to offer flexibility in your design proposal is important to know what other frameworks in the market can offer to you.
I’ll be listing the different design frameworks I’m finding in the wild with notes on the pros and cons I find in them. If you want to keep updated with the list just subscribe.

There is the XP guide “Do the simplest thing that could possible work”, but how to tell apart simple from easy? Sometimes simple is easy, actually as a guide for me I say “Simple is easy to understand”, but sometime easy leads to complex, and most of the time getting something simple requires hard work. So, are there rules that help us get to simple design?

The principle defines that objects of a superclass shall be replaceable with objects of its subclasses without breaking the application.

Software entities (classes, modules, functions, etc.) should be open for extension but closed for modification.

Easy Understanding
Easy of Change
Easy of Debugging
Flexibility

• policy
• location

High-level modules, which provide complex logic, should be easily reusable and unaffected by changes in low-level modules, which provide utility features.

A better design makes it easier to make changes.

An alternative to SOLID when the problem is not clear enough to get to a sound design.

Technical debt are decisions we make during development that we know are not optimal because they require more work to get optimal but we decide to deal with the consequences because we see more value in delivering at that time.

There are two ways of constructing a software design

Really excellent video on how to replace inheritance with composition in javascript.