I can see authors point when it comes to smaller website or app. I work on enterprise products that are rather complex with large surface area. Despite being a pretty good coder (or at least used to be), I wouldn't attempt to iterate on changes directly in the code and link all the flows etc. It would take much longer and I'd lose ability to make rapid changes.
Kindle Scribe. I'm reading a lot more books on it because I find experience much better compared to the small ones. Don't really use handwriting notes functionality because I rely on pen and paper for notes.
Armytek Wizard flashlight. Joy to use on the runs and for walking around neighborhood in the evening.
Pacsafe Metrosafe X Urban Sling. Kind of expensive but has a very thoughtful design. Now I have my wallet, notepad and bunch of other small things in one place instead of being spread out across various pockets.
This design system played a crucial role in turnaround of CX at AWS over the last 5 years.
People like to bash it but few realize the challenge of creating brand new purpose-built design system from scratch that can work at scale and complexity of AWS.
Is it perfect? No (what is perfect though?) Not a lot of people have been around long enough to understand how bad the situation was prior to Polaris (internal name for Cloudscape). On top of it, the team that owns it is highly competent and opinionated (hey Boris) and they are committed to support and evolution of it.
When I’ll have fitting use case, I will use it in a heartbeat in my own projects.
If I may make a suggestion (not sure if English is your second language or not). Consider using 'typical' instead of 'normal'. It took me awhile to get used to that but my daughter is better off this way.
