Werner Vogels

Then we have, what is it, recommendations, personalization, whatever.

And then there is stuff that is just nice to have.

Now, take, for example, bestseller lists.

Now, as a technologist, you need to be able to have a conversation with the business and say, how many lines do you want behind that?

Or you want four nines behind your bestseller list.

Well, that's going to cost you so much.

And then it becomes a business decision how I am going to implement this.

But I need to be able to explain to the business what the risks are, what the costs are, how resilient can I make this?

But without that kind of communication, you're not building the things that you want for your customers.

So a very important part of the Renaissance developer is to be able to communicate in exactly the right way, not only to the business,

But also with your customers.

What are you building?

How does this interact with this?

If I show you a picture of the thousands of microservices that builds out Amazon.com.

If I do something here, what's happening there?

Is there a relationship between the two?

So system thinking becomes crucial as well.

Not just about your little piece that you're building, but what impact does that have on other things?

Or, you know, I'm happy going away.

My database is running.