Werner Vogels
๐ค SpeakerAppearances Over Time
Podcast Appearances
because the senior engineers are in the room and discussing the code on the screen there, and you're learning on the spot from these senior engineers, from all their years of experience, where someone will say, yeah, I tried that when we were building product X, Y, or Z, and it didn't work then, or the problem at that time was that.
Now, where did the code on the screen
is generated by you or by some AI agent, doesn't really matter.
We still need to do code reviews.
Because we have ownership.
And whether we used a tool to create the code that we're looking at, or whether we actually wrote it ourselves, we're still responsible for it.
We still own it.
Yeah, and so those things don't go away.
And so, and as such, if your system has been created by one of the AI tools, and as I said earlier, you know, you are responsible for it, especially if you're in life sciences, if you're in healthcare, if you're in financial services, in whatever, you cannot only rely on the fact that, oh, but AI built it.
you are still responsible for what you deliver.
And that means you need to be able to look at it.
And as such, generation of code may go faster.
Reviews will probably go slower.
Because this is not code that I've written.
If it's my code, I can go stand up in front of the class and say, oh, and this is why I did this, and this is why I did that.
But if a complete unknown, inhuman entity created this code for you, it takes longer to get used to it.
And so that's not bad.
I mean, none of this, don't take this as that I'm sort of cracking on AI as being.
No, there's parts that will never leave us.
We need to learn the next steps.