This is a great start into the week. Creates some fast smiles and than some more serious afterthoughts.

This is a great start into the week. Creates some fast smiles and than some more serious afterthoughts.

I absolutely agree that working backwards from real customer needs must be guiding product design. Not featuritis or Buzzword Compliance. No smart for the smart product label.

I also love technology which ease my life. I don’t mind a smart environment. The thing is - and I’m addressing my fellow technologists here - we need to make sure that we design those systems in reliable fashion.

Established frameworks like the AWS Well-Architected Framework [1] can provide guidance. While I’m still just add a blanket if it get’s cold, I would recommend implementation of graceful degradation[2] — keep the core function alive with reduced service when a dependency fails — to not get toasted …

[1] https://aws.amazon.com/architecture/well-architected/ [2] https://docs.aws.amazon.com/wellarchitected/latest/reliability-pillar/rel_mitigate_interaction_failure_graceful_degradation.html