Constraint are good

Most people think about constraint in a bad way

I think constraint is good for many reasons

Constraints gives you a limited set of options to perform or use.

GraphQL is better than REST because it has more constraints, you can’t do everything you want in GraphQL.

You can’t ask any data, and you can’t return any data. You need to think first in the structure of the data that you want to expose to end users.

Declarative provides a limit set of operations that you can perform.

When you move to imperative you can do anything, but I argue that you should avoid this to reduce complexity.

K8s declarative yaml are better than CDK before you can’t do everything you want in your infra.

So it is easier to maintain in the long run.

Avoid trying to fix all edge cases in the low level building blocks.

Constraints limits complexity as you need to work with a limited set of options.

Constraints limit the number of Abstractions that you can use.

Design System are constraints for your product UI, it does not let you do everything, as you want to keep consistency

Constraints are about consistency.

Habits are constraints to your daily life to make your more productive

Constraints are about less choices

Letting tools make decisions for you (Defer Understand )

• https://www.jackfranklin.co.uk/blog/letting-tools-make-choices/

Building Block gives you a limited set of basic blocks to work on, if you need something that is not available in any block you have 2 options:

1. create a new block increasing complexity
2. try to rethink your current needs