Werner Vogels predicts the future (Interview)

4 Dec 2025 · 1 h 31 min

Ask about this episode

Ask anything about it. ChatGPT or Claude reads this page and answers with the times it was said.

Connect VO and ask about every podcast you hear, including the moments you saved. Add to ChatGPT · Add to Claude

In short

Podcast Summary: Werner Vogels Predicts the Future (Interview)

Podcast Overview Podcast Title: The Changelog: Software Development, Open Source Episode Title: Werner Vogels Predicts the Future Guest: Werner Vogels, CTO of Amazon Episode Description: In this episode, Werner Vogels shares his insights and predictions for technology by 2026, discussing the potential of consumer robots, the importance of quantum-safe technologies, and the emergence of the "renaissance developer."

---

Key Themes and Predictions

Introduction

  • The episode begins with a welcome from host Jared, introducing the guests Adam and Sam.
  • Acknowledgment of the episode's focus on the future of technology and Werner's predictions.

Main Topics Discussed

  1. Consumer Robots and Companionship
  2. Prediction: Technology will redefine companionship, particularly through the use of consumer robots.
  3. Discussion:
  4. Increasing loneliness across demographics, especially among the elderly.
  5. Potential of robots to serve as companions, similar to pets.
  6. Examples from Japan show advancements in robotic companions that can assist and provide emotional support.
  1. Quantum-Safe Technologies
  2. Prediction: Quantum-safe encryption will become essential.
  3. Discussion:
  4. Quantum computing advancements are coming closer, making it vital to prepare encryption methods.
  5. Importance of implementing post-quantum cryptography to protect sensitive data from future decryption threats.
  1. The Renaissance Developer
  2. Prediction: The emergence of developers who are multi-disciplinary and possess a broad range of skills.
  3. Discussion:
  4. Traditional developers may become obsolete if they only focus on coding without understanding broader technology implications.
  5. The need for developers to communicate effectively with business stakeholders and understand system-wide impacts of their work.
  6. Emphasis on continuous learning and curiosity in the tech landscape.

Insights from Werner Vogels

  • Reflecting on his 21 years at Amazon, he discusses the evolution of his role from internal-focused CTO to external-facing technologist.
  • Highlights the responsibility of tech companies in addressing significant human problems, such as healthcare and food security, through innovation.
  • Encourages a shift in mindset towards a balance of specialization and a broad understanding of technology and its implications.

The Role of Technology in Society

  • Discussion on the societal impacts of technology, such as the shift from human interaction to reliance on devices and AI.
  • Concerns about potential addiction to technology and the importance of addressing this in future generations.

Conclusion

  • The episode wraps up with a call to action for developers to remain curious, embrace continuous learning, and adapt to the evolving technological landscape.
  • Jared thanks Werner for sharing his insights and discusses upcoming topics for future episodes.

---

Key Takeaways

  • Companionship Redefined: Robots may help mitigate loneliness, especially among the elderly.
  • Quantum Preparedness: Organizations must start adopting quantum-safe encryption methods to protect against future decryption risks.
  • Renaissance Developer: The future developer must possess a wide array of skills, including communication, curiosity, and system thinking.

Action Items for Developers

  • Embrace continuous education and be proactive in learning about new technologies.
  • Engage with business aspects of technology to better understand the implications of engineering decisions.
  • Investigate and implement quantum-safe technologies in current projects to ensure future security.

---

This summary captures the essence of the podcast episode by highlighting the key discussions, predictions by Werner Vogels, and implications for the future of technology and software development.

Written by AI. May contain mistakes. Listen to the episode to check what was said.

Hear the part that matters, and keep it.Open this episode in VO. Double tap your headphones to save a moment as you listen.
Get VO free

Transcript

Automatic transcript. May contain errors.

0:08Welcome everyone, I'm Jared and you are listening to the change log where each week Adam Sam and I interview the hackers, the leaders, and the innovators of the software world. We pick their brains, we learn from their failures, we get inspired by their accomplishments, and we have a lot of fun along the way. On this episode, Amazon CTO, Warner Vogels, stops by to help us explore his tech predictions for 2026 and beyond. Will companionship be redefined by consumer robots? Will QuantumSafe become the only safe worth talking about? Is this the dawn of the renaissance developer? We're infinitely curious why Warner came to this particular set of conclusions.

0:51Are you? But first, a big thank you to our partners at Fly.io, the public cloud built for developers who ship. We love Fly. You might too. Learn all about it at Fly.io. Okay, Warner Vogels predicts the future on the changelog. Let's do it.

1:13Well, friends, Agentic Postgres is here. And it's from our friends over at Tiger Data. This is the very first database built for agents and it's built to let you build faster. You know, a fun side note is 80 % of Cloud was built with AI. Over a year ago, 25 % of Google's code was AI generated. It's safe to say that now it's probably close to 100%. Most people I talk to, most developers I talk to right now, almost all their code is being generated. That's a different world. Here's the deal. agents are the new developers. They don't click. They don't scroll. They call. They retrieve. They parallelize.

1:49They plug in your infrastructure to places you need to perform. But your database is probably still thinking about humans only because that's kind of where Postgres is at. Tiger Data's philosophy is that when your agents need to spin up sandboxes, run migrations, query huge volumes of vector and text data, well, normal Postgres, it might choke. And so they fix that. Here's where we're at right now. Agentic Postgres delivers these three big leaps. Native search and retrieval, instant zero copy forks, and MCP server, plus your CLI, plus a cool free tier. Now, if this is intriguing at all, head over to tigerdata.com, install the CLI, just three commands, spin up an Agente Postgres service, and let your agents work at the speed they expect, not the speed of the old way.

2:35The new way, Agente Postgres, it's built for agents, is designed to elevate your developer experience and build the next big thing. Again, go to tigerdata.com to learn more.

3:06well everyone we have a treat we're here with the cto of amazon my gosh talking about predictions every year you have five they mostly come somewhat true in a couple years so you're pretty accurate warner welcome to the show again the last time you're here was for the no sequel smackdown back about 12 years ago jared 10 years ago was it forever ago episode 18 so back when no sequel was cool fresh and burgeoning now it's ubiquitous and everywhere and I guess still cool-ish. Yeah, engineering has come a long way since. I think the first NoSQL tools were really the first tools. Now, if you look at DynamoDB, if you look at Mongo, these are super robust, highly scalable tools where everybody can build a business on.

4:00Come a long way. I think, you know, it was Burjian. It was DynamoDB was coming out then. it was fresh and brand new i guess the cto you probably architect a lot of that stuff right what what do you do as part of your role like what is your role maybe then 15 years ago and then how is it now so first of all it's 21 years now right so that that's a bit and there is a predecessor to dynamo to be that's dynamo and one of the things when i joined amazon i joined us what was called a director of systems research. The idea was to bring... Now, let me go a little bit back. Think about 1994, when Jeff Bezos starts thinking about sort of the internet.

4:48And he starts a bookshop. He doesn't really want to start a bookshop. He's just fascinated by the internet. what are the things that you can do online that you will never be able to do in real life and he just picks a bookshop a good bookshop has 40 ,000 titles in stock yet there's millions of books out there so he thinks you could do that online but there is no book there is no software that you can buy there is no book that says and here is an e-commerce operation, the word e-commerce doesn't exist yet so everything that the Amazon engineers had to do to build Amazon was to invent everything themselves because the kind of technology that they could buy couldn't operate at their scale we've had a number of blurry noses because of that so when I joined Amazon engineers at Amazon were brilliant at scaling but from a let's say practical lots of scars kind of approach and Jeff hoped that by bringing a former academic in you get some more robustness you get some more better fundamental approach to scale and reliability and things like that And we did lots of large projects around removing all single points of failures or how to best measure.

6:32How do you measure? What does it mean to measure? If 50 % latency on your webpage means nothing. Well, it means that 50 % of your customers are getting a worse experience. You need to know how much works. now so now i think if i think about cto's there's there's sort of four or five different types and there's no real well developed well described one i think now first of all there's the data center manager yeah he reports up to the cio um then you have the cto that is the the second person in the startup and often the co-founder the first coder and then you have the big thinker sort of the role that I got when I came into Amazon, sort of like look at the whole picture, what other kind of things we need to do.

7:26But then when we started doing AWS, your world changes. You go from an internal-focused CTO to an external-focused CTO. And I think Scott Dietzen, who was at BA, I think it was at that time, He called it really an external technologist. The ability to talk to your customers, look at that, how are they using my products, and what are the problems that I see with 10, 20, 100 of my customers that they may not see as a single problem themselves, but you can find, if I can build a tool for that, I can really help my customers. and so your role changes from being purely internal to being external and and sort of bringing back things into and then then then over time i've i've become more and more interested in in those organizations both profit and non-profit that try to solve hard problems And with hard problems, I mean hard human problems.

8:48The United Nations expects that by 2050 we have 2 billion more people. I mean, how are we going to feed them? How are we going to make sure they have an economic future? How are we going to make sure they have healthcare? Those kind of problems are the ones that I'm mostly focused on today. on one hand, you know, by the way that we build technology at Amazon, but also by looking for those often young businesses and how can we support them. Take, for example, the Ocean Cleanup Project. It's a massive problem. The Grand Ocean garbage patch is full of fish nets and plastics, and there's about 30 rivers that sort of contribute mostly to that.

9:44So these guys have built plastic with GPS in them, threw them in the river and see them where they end up. Or they have these AI cameras on boats to sort of first, where do these boats go? But secondly, also, what are the things that they're seeing? And so working with those kind of customers is extremely satisfying because we're solving actually real human problems. We're not building spam filters. Well, 21 years is a long time. And there's that old quote, the best way to predict the future is to create it. you've spent 21 years with your teams creating in many ways the future that we're currently living in but you're also out there predicting it this is the fifth year perhaps you're writing these predictions you have five of them and they're fascinating i agree with most of them the companionship one i'm skeptical of but i would love to hear your your full case uh for us here but why why write these why predict the future in these ways and uh continue to do so there's a long history by large technology companies and if you think about IBM's and the Oracle's and whatever to sort of, or McKinsey or whatever, the consulting companies by kind of predicting the future.

11:07And always when I read them I always felt that they were a bit self-serving. And the things that I saw in the real world were different. I see significant human problems, you know, and some of them are our own nature, but quite a few are caused by technology or the way that we use technology. There's a leadership principle at Amazon. With success and scale comes broad responsibility. That means you don't only have a responsibility towards your shareholders to make money. you also need to serve your customers but at AWS of course that is builders how can we help builders best and then I write these predictions about things I see around me I have the fortune to travel the world so I was just in or just in spring I was in sub-Saharan Africa so Nigeria, Rwanda Kenya now in Kenya we were in Nairobi and of course you stay in the center of Nairobi beautiful buildings, whatever you drive 15 minutes and you see how the real Kenyans live and if you think how they work most of them are day laborers that means that they go to the bank they get two dollars they buy something, they try to sell it they bring the$2 back and hope to have 40 cents left to buy food they probably have that but then they don't have money left to cook it why?

12:58because these big canisters these butane canisters cost$10 and they don't have$10 and so there's a young company called Coco Networks that build a sort of ATM where you can go with a canister, you plop the canister in, and you say, give me 15 cents of gas. And then you can take that home, you can cook your food. Now, this is not a world-shocking problem, but it is solving really hard problems that people have. And those kind of companies are really the ones that, and those kind of problems, are often kind of the things that I'd like to service through the predictions. This year, you know, I do think there are things every year.

13:51I mean, I could have done 10 predictions. You could have, yeah. But that doesn't work that fairly well. Five is the magic number. Three is the magic number, five is better. Yeah, yeah. But, you know, was it two years ago? An example, a topic that has become more and more openly discussable is menopause for women. It's a major problem for them. But even mothers don't talk to their daughters about it. However, that is slowly changing. What kind of things do we see in the startup community that are trying to build, whether it's technology products or whether it is medicine or whatever, to solve those kind of problems.

14:44And so I also try to talk a little bit about things that people normally find a bit harder to talk about. Well, let's talk about one. Companionship, loneliness, robots. I do not have any disagreement whatsoever with your casting of the problem, which is that loneliness is on the rise, especially amongst elderly. But even across all demographics, we see an increase in loneliness, which has all kinds of health and mental wellness problems, just overall bad, right? But you seem optimistic because we have a new swath of robotic companions that are coming out. More like it's one of these problems. Well, you see the problem.

15:28Actually, sorry, I did this documentary series called Now Go Build. TV series. Probably two, three years ago, I was in Japan for that. Actually, for that, and that's where I first really dove deep in this particular topic. So Japan really was a society where kids take care of the elderly. Yeah, the grandparents live with the grandkids and the kids. Yeah, and that was normal. But the younger kids want to start making career. And there is a clear shift in Japanese society happening where the elderly are no longer taken care of by the younger people. And as such, you know, that's a shocker, not for the young kids, it's a shocker for the old people.

16:21They're really on their own and I think, and indeed I think that there are a lot of technology solutions possible to help these people. One of the things, and loneliness is something we'll get to but anything we can do as technologists to keep people longer out of hospitals or whatever care homes or whatever, the better it is. And if that means that a company in Japan that I met called Z-Works, they try to do all these innovations around these elderly people to help them. Make in your mattress a little bit of a sensitivity pad. And maybe in the middle of the night, you go to the toilet and you don't come back within 15 minutes, the alarm goes off.

17:23Yeah. And this doesn't seem like world-shocking kind of revolutions, but it does mean that people can stay independent longer. They can stay, yeah, and they don't feel that old. Let's put it like that. I think more and more people, I mean, becoming 100 years old is actually not that strange anymore, is it? And getting to that particular age, many of these people may have lost their partner if they had a partner. Or live far away from their mother family. I mean, especially in the US, I mean, after high school, you probably move away from where you lived, where you grew up. You go to a college somewhere in upstate New York, you go to work in California, and people are not close anymore.

18:25That truly is a loneliness epidemic. So what can we do? And I think, and I love the work that is happening around sort of companion robots. Sort of. Why? Because I always thought that people would treat a robot like a piece of metal mechanics. You know? Right. Turns out, it's not at all the games. They treat them like pets. Really. Kate Darling, MIT, she's done all the research around here, is, I can tell you absolutely amazing stories about how people get attached to their devices. The story, I think, is also in the predictions, 80 % of the people that have a Roomba, you know, the cleaner in the house, have given it a name.

19:27and one of the stories that Roomba tells like well one sent an old Roomba back because it needed to be repaired and they look at it and they tell the customer you know what we'll just give you a new one and they say no no no no no we want mineral food back really yeah they want the old one because they're attached to it now or Kate tells this story where at some moment she divides two groups of people and each get a dinosaur, a sort of baby dinosaur. And now they really fall in love with it. They give it a name. They play with it, blah, blah, blah. And then she gives them a hammer and she tells them, kill the dinosaur.

20:15Yeah. Nobody in the group will take the hammer and kill the dinosaur. They have no problem, though, going to the other group and kill their dinosaur. You know? So, no, this is sort of, why do I tell these stories? It's that while these things are technology, we treat them as living beings. And especially, I've always, of course, because before I was in computer science, I was in healthcare, you know, the application of these kind of tools, toys in hospitals are incredible. You know, if you're a young kid, a doctor is someone that is tall and, I don't know, dangerous or whatever you want to think.

21:11But, for example, there's this, the huggable robot is a small green thing with a nice snout and talks to the kid and whatever. Kids with a huggable have no problem talking to a doctor. Yeah, because they have their mate with them. And so those kind of things, I think, are crucial for us as technologists to think about. we see a problem not necessarily a problem that is going to make us a ton of money but we see a problem that is really important for people's psyche for people's feelings for loneliness who wants to be lonely? Nobody and if we can't do this through pure social interaction what's the next best thing?

22:10We have, or we, Amazon has Astro, but there's more robots like Astro. And they'll just run, they'll go search for you through the house and ask you if you've taken your medicine. Families or people that have these kind of robots, their medicine taking goes up 80%. Why? Because they're being continuously remembered. and it's and actually that way predates this is early on when we launched Alexa I got a story from a man who was suffering from early dementia and he knew what was coming speaking of Alexa that's her there she is You can't help me with that. I know that. So the only thing he had to do was put a post-it note on the device that says it's called Alexa.

23:20Right. Because one of the things that he noticed was that during the day his caregivers were getting more and more irritated with him. Why? Because he was asking the same thing. over and over and over again. What day is it today? What day is it today? And I was here, completely forgotten. And the thing with that, let's say, voice assistant was that you could ask it the same thing over and over and over again. And it would never get angry. It would always be happy. And it would always give the same answer. So there are technologies that we can develop. to help people have a good life. And I think if you can do that, spam filters, fine.

24:13Sure. Yeah, right. What I find interesting with this thought experiment is, and something I don't think I heard you say here or in your post, is we're actually to some degree programmed. I mean, I know I had a lovey of sorts when I grew up as a child. I know that I've got two boys that are growing up and they both have a thing that they were given at a very young age that is not technology, but it's about the best abstraction you can get. And a lot of people have had it in the last 50 years, even 200 years, even more is this idea of a companion that you you draw an affinity to. Now, this thing does not tell them about medicine, obviously.

24:58It does not remind them about things, but it's this object that they attach to and cling to. I mean, how many kids don't you see walk around with a little rabbit after 10 years? Yeah. Yeah. And you mentioned the dinosaur. I mean, my kids would no way ever destroy the thing. Like it's their lovey. It's their, it's their prize, you know, friend companion that has, you know, no humanity whatsoever, no ability to speak, no true reciprocal affection even. But it's theirs and it has been theirs and it's their affection point that is uniquely theirs and only theirs. So even from a young age, they've had this companion.

25:40So it doesn't surprise me that your prediction is maybe that as an antidote to loneliness. Well, I don't think it's an antithesis to loneliness. It is an assistant. I said antidote. People are still lonely. Yeah. But I have seen elderly ladies with a fake cat next to them, stroking the cat and the cat meows. And the elderly lady is extremely happy about that. Yeah. And so why not? yeah and the fact that we have had some or a phase in our in our existence where we think like oh no all relationships need to be human to human well maybe not yeah maybe there is there is more to that especially because I know we are getting older I mean look at all the baby boomers everybody over 65 or over 70.

26:42There's a very large group of people that is growing older and older and older and come with a new set of problems. Can we solve those as technologies? Can we make a contribution to that? That would be great. Because I think, you know, building technology is cool, but you know helping people is much better than than that

27:16well friends i don't know about you but something bothers me about github actions i love the fact that it's there i love the fact that it's so ubiquitous i love the fact that agents that do my coding for me believe that my cii cd workflow begins with drafting toml files for github actions that's great it's all great until yes until your builds start moving like molasses github actions is slow it's just the way it is that's how it works i'm sorry but i'm not sorry because our friends at namespace they fix that yes we use namespace.so to do all of our builds so much faster namespace is like github actions but faster i mean like way faster It caches everything smartly.

28:02It caches your dependencies, your Docker layers, your build artifacts. So your CI can run super fast. You get shorter feedback loops, happy developers because we love our time. And you get fewer, I'll be back after this coffee and my build finishes. So that's not cool. The best part is it's drop-in. It works right alongside your existing GitHub actions with almost zero config. It's a one-line change. so you can speed up your builds you can delight your team and you can finally stop pretending that build time is focus time it's not learn more go to namespace.so that's namespace.so just like it sounds like it said go there check them out we use them we love them and you should too namespace.so i think we leave it right there and turn to adam's favorite topic quantum quantum quantum i'll say it three times the headline for this particular prediction is quantum safe becomes the only safe now we've covered quantum computing here in the past and it's always been right around the corner it seems like it's always around the corner but your contention with some data to back it up is that that corner is getting closer and closer and it's maybe not five years away like it always has been or 18 months away it's actually there's things happening and it's like we're getting there we're getting there can you tell us more well i i do think more the most important thing is that i don't necessarily want to put a timeline on it i'm thinking two years ago or three years ago i think i said five to ten I think 5 is now more realistic.

29:49But I've seen a number of problems arising that I think we need to be aware of and take action on before that. I mean, it's not about... I mean, we run brackets, which is together with... Caltech is an institute about quantum. And I see different institutions making massive progress in terms of error correction, networks and things like that that actually believe make me believe that it's no longer how shall I say a vision it's an execution now it now it becomes an iterative process in improving the technology that we have created step by step by step until it becomes workable Now, there is a ton of other problems to solve.

30:45How do you program these beasts? I mean, how do you do that? How do you do with something that is not necessarily 100 % reliable? So how do you do that? So there's a ton of things that still has to be solved before we have production quantum machinery. but one of the things that these things to end they won't solve necessarily new problems they won't so they'll solve existing problems much faster there are things that would now take a thousand years in compute will then take a year or six months or two months yeah that's the premise of quantum well the one thing that then we'll able to do really really really really fast is decrypt and so anything that is uh has let's say is just elliptic or the usual rsa encrypted kind of things that are perfectly fine now because it will take way too long to decrypt then will be decrypted with a snap of your fingers.

32:04So the reason for the prediction actually is to put in people's minds that we need to start taking action now. If we want to be protected five years from now, from, let's say, the ability to decrypt anything that we have now. Now, all the hyperscalers, Google, Microsoft, Amazon, whatever, We all have been building post-quantum cryptography. We've been inserting that into our front end. And we're doing all of that. Unfortunately, we're not the only players in this world. There are lots of people with their own data centers still, with their colos, with their whatever, that will have a hard time protecting themselves.

32:57That's one thing. So really getting it into people's minds that they have to start taking action now if you want to be safe a number of years from now when these things become reality. The other thing is that you can't just lean back right now because a lot of the breakings or data stealing or whatever you call it is basically data harvesting. Nobody is interested. Basically, encrypted data is being retrieved. And people don't try to decrypt it. they'll wait till the machinery is there to be able to decrypt. Now, well, your medical data now will be decryptable in a few years from now. If we are not kept.

33:57And so, in fact, I don't necessarily mean script kiddies or whatever. It's really state actors. It might be, you know, commercial actors. who are interested in that kind of data, even if it's five years old, and I have all the relevant data for them to take action on. That's the scary part, really. The famous TV show you may have heard of this, Werner, is called Silicon Valley. And in season six, I'm going to spoil it for some folks, just a little tiny bit, let's just say. And you may know this because you may be a fan, or maybe you're not because it's too close to home. who knows, is that the AI they build or accidentally build to some degree, they give it a task and it essentially goes out of their bounds that they plan for and breaks encryption.

34:53So this is predicted in a TV show that's now ended, but very much prophetic in a lot of its satire. And that's been my major concern with Quantum is that in the future, we have a machine that is, as you said, it's non-deterministic or unpredictable in a lot of ways. It's also unpredictably predictable in the fact that it's unpredictable. But it has so much possibility that that's when encryption will essentially go away and the world we live in that is safe because of encryption is no longer safe. That's been my major thought around that, really, for quantum. Well, there's, of course, different types of encryption.

35:36and you have letters-based encryption and you have that. So there are types of encryption that you will be safe from sort of these type of decryption. But you need to start installing that now. You know, LibSSS was 500 ,000, 600 ,000 lines of code or something like that. I mean, you can imagine that because it had to have all sorts of different types of encryption in it. At some moment, we started realizing at Amazon that running all of our frontends with LibSSS was a major vulnerability. And so we implemented TLS with a limited set of encryption technologies and just put that in front of S3, for example.

36:32First of all, much cheaper, but we made it open source and we made sure that it is fast and inspectable. And more important, written in a way that we can use automatic reasoning to see whether or not we're protecting ourselves. So the most important part, I mean, now you hear more and more about automatic reasoning, with people like Byron Cook who have been working at Amazon for the past 15 years on these kind of problems, proving to ourselves that we are protecting our customers. That's not a press release that is going out or something like that. But there are technologies that you can use to sort of prove to yourself.

37:20Now, SNN, Signal to Noise, was the original name of the open source project, was purely also intended to get post-quantum encryption in the hands of everyone. Now, I told you, now you got scared about the data harvesting. Let me scare you a little bit more. probably every of your home devices hasn't been updated for a number of years yeah they were in linux whatever version uh no automatic updates or anything like that your automatic garage door yeah it might have a little bit of encryption in it between the key and you or think about hotel rooms your key is an encryption encoder and so there are so many small parts I mean first of all by coming back to these house devices I recently looked at one of the house that we have how many devices were on the network and that was something like 56 six.

Read the full transcript

38:42There's your Sonos, and there's your garage, and there's your light opener, and there's the thing that keeps track of this, and all these kind of things. Are all these things up to date? Are all these things protected? Are all these things up to new standards? We have a number of years to get this done, but we do need to start now. So the task today is what? What is the task we could do today as developers, as maybe potentially inventors? What should we do today to plan for quantum? That really is the question in there. First of all, and there's a number of areas. I mean, there's just using newer encryption technologies, but you can't imagine that, you know, something, some piece of data that you encrypted 15 years ago you're not going to go through all of your data and re-encrypt it again but you know are there gateway possibilities that protect you from that are there are there other problems other ways let's let's use our inventive brains and and find solutions to this because i believe we can but only if we make it a focus and the focus is not that quantum is five years away the most important part there is that we need to keep ourselves and our businesses safe and if that happened to be quantum or if it happened to be an alien spaceship that lands from whoever and suddenly turns out to be able to encrypt all our data decrypt all our data that doesn't really matter we need to start protecting ourselves how sure can we be that quantum safe technologies as we define them today actually will be quantum safe yeah well do we know do the work do the work i was hoping you already did it werner yeah yeah no it's just do the work you know then no no no that that is it the same goes for everything now.

41:00Let me take a whole different example. When at Amazon S3, we went from eventual consistency to strong consistency. That was a major change that impacted every piece of technology. How can you make sure that you touched every edge of this particular problem because it is either 100 % or not. So automatic reasoning plays a role in that. Annotating annotations, TLA +, other technologies that you have to prove to yourself that what you've built actually does exactly what you want it to do. so definitely I think automatic reasoning is continue to play a more role in giving us a secure feeling that we are on the right path the same is for example we recently launched Cairo that is the spec driven IDE for an AI system we use automatic reasoning there to limit the number of hallucinations that can happen.

42:31Yeah? Yeah. Not that automatic reasoning knows that terribly much more, but it knows A square plus B square C square is probably a triangle. And as such, it knows all the triangles in the world. if then this llm says this is a triangle i would make the reasoning you will say no that is not a triangle yeah and that is my that's just a simple example but we start building more and more technologies to prove to ourselves that we are doing the right thing well let me just take a quick moment to say we talked what wikipedia last week orner and i called it perhaps the eighth wonder of the world and if it is the eighth i would say amazon s3 is probably the ninth wonder of the world so just a quick moment of props to you and thank you for what is an amazing amazing piece of technology that's unlocked so much for so many businesses and people over the years s3 is is wild yeah yeah i am uh you know what my first programming languages were at school No.

43:43COBOL, 68 ,000 assembler, and Pascal. Okay. None of these programming languages, anybody writes anything anymore. Maybe I could make money as a COBOL programmer. I'm not too sure I'm doing well in 68 ,000 anymore, but things change over time. And we as humans adapt. But we're often ahead of the game. You know, we went from things like Pascal, which probably was sort of the first version of a little bit of structured programming, to C++ and Java and Python, and just the whole world. None of us panicked there. We just learned a new programming language. it's not like it's not like that we're suddenly frozen in our chair and now we have AI AI tools to help us building the systems that we do why should we start to be scared suddenly why should we suddenly become we just learn to use new tools because remember it's you that build not the tools it's also you that own it not the tools yeah if the tools is built something that and you're in a financial company that suddenly no longer makes you compliant it's pretty hard to say to the regulator oh that was the AI that was the tool yeah no no no no it's still your responsibility and as such i think that sort of we no matter how good tools we build we still need to educate ourselves we need to continue to keep ourselves on on a path of education learning continuing to learn and looking at you too you're not the youngest.

46:02So I'm pretty sure that before you wrote something in Python, you wrote something in C++ or in ABC. Yeah? I wasn't learning Python or going to the next programming language. My favorite being Rust at the moment. But there will be something else after Rust. Sure. We won't panic suddenly and thinking that the world will collapse and all our jobs are going to go away. No. No, we make sure that we educate ourselves. And crucial in all of that is curiosity. Yeah? If you just want to lean back, so if you just want to lean back and just, you know, write some code and things like that and don't want to learn the next language or whatever, then probably you've always been told.

47:00That has nothing to do with AI. You have to, because curiosity leads to learning. And these two things are, remain curious.

47:19What was it? Have you guys seen Ted Lasso? Yeah. Oh, yeah. The TV series. There is this brilliant darts scene where he froze 170. And he tells this story that... I saw this quote by Walt Whitman. It was painted on the wall there. It said, be curious, not judgmental. I like that. And he said, I suddenly realized that nobody had been curious in who I was. They were just bullying me just because they could. And curiosity is such an important part. Being curious about AI, being curious about quantum, be curious about how defense technology actually transforms into civil technology. If you're curious, you'll find out.

48:16and I think if you look at young kids they're all massively curious until we send them to school and then we make them conform to one standard they all need to become the same and regardless what their mentality is, regardless what their level of interest is I think everybody has the ability, how shall I say, to become special.

49:00I think one of the talents, and given that what we have, we have the Renaissance developer as one of the points in there, In the Renaissance, the core of Renaissance humanism was that the belief that humans are limitless in the capability of invention. As long as you keep their curiosity alive, the moment they're no longer curious, they'll lean back and it's over. and so I believe that that's really we are limited in the capabilities of inventing of do new things if we're just being allowed to I don't disagree you hit on a couple of your points the renaissance developer and the personalized learning which I think is hugely opportunistic or a huge opportunity for so many because, like you said, we sometimes by necessity, we push all of our children into a square hole, you know, regardless of their educational shape, and they must come out conformed to whatever standard.

50:21And I do think that technology is allowing us to break out of that conformity to a certain extent and provide personalized, customized education, you know, leaning into what the kid's interested in and playing to their strengths. Yeah, but also even also just learning maths. I remember I have two daughters. They're now in their close to their 40s. Don't tell them that. They got to know that, right? One of the things, so I'm not American. I'm not the U.S. I come from the Netherlands where high school has 10 different forms, depending on sort of what you're, you go to a school to become a welder, or you go to a school where you go to university, and there's a whole range in between.

51:19And then I come to the rest, and the kids have to go to high school, and all kids have to go to the same high school. They have to take the same classes. They have to score good in the same classes. And when one of my daughters, in the first time that she got into math class, there were four guys in the back of the room that were four years older than that she was, still had failed maths every time, but had to still sit in that class. Disruptive and, well, you know the stories. and as such I've always been a real fan of Ken Robinson professor from from the from the UK that moved to Los Angeles at some moment and I've been a real fan of him because he really looked at that instead of that we let our kids bloom and explore and become really what they can become, we turn them into factory workers, all doing the same thing.

52:37And that kills all the possibility in what these kids have in them. What do you see coming out or happening in the education space right now that leads you towards this prediction? Because you're predicting, you know, infinite personalization and these things. Are there solutions out there today? Are there companies working on it? Well, I think there's enough companies working on them. But what I see more and more is that these kids are doing it themselves. Yeah. Gen Alpha, the current kids that are in high school or going to high school, they really know how to use AI. or AI assistants. And they know how to make a curriculum for themselves.

53:28And they know how to make something from which they can learn. That is really a tool for them to build something that they just want to do. It helps them build things without having to have to go through a complete textbook first. Now, I still believe that you need to be able to do maths before you should be allowed to use a calculator. Yeah, that's like a reasonable kind of thing. But providing, if you're really interested in, let's say, how in the 1600s in Italy, from small states, this became one country. For some reason, I don't know. Kids have immense curiosity in anything. You can build yourself a curriculum that you become, not that you become an expert, but that you know everything about it.

54:32And this is something you have. Certainly you have control over that. Now, there's always two sides to this. The other side to this is that, and this is actually something from Ken Robinson again, And he says, there are no good schools. There are only good teachers. And he says, and what do most teachers spend their time on? Grading homework, doing administration, all these kind of things that actually have nothing to do with education. so yeah that that seems to me like a standard technology solution problem yeah and whether you solve that with ai or whether you solve that with some just some simple sequel fine yeah that doesn't really matter i believe that there should be a lot more support for teachers such that they can focus on things that is important.

55:38Well, individual interaction between a teacher and a student has so much more impact than the teacher just standing in front of the class. Yeah, by the way, Ted tells this wonderful story that he's a teacher and he tells his story that he's giving drawing lessons. and there's always this one girl in the back of the class that is never interested in anything but now they're drawing lessons and she's fanatic so she goes he goes to the back of the class and looks at what she's doing and he says what's she doing and she says i'm drawing god and he says but nobody knows how god looks like and she looks at him and she says but in a minute they will.

56:36That's funny. Yeah. Yeah. I mean, would we think, here's a blank paper, why don't you draw God? Yeah. Yeah? No. Yeah? But this is a kid. There are no boundaries to your curiosity and to what you can. all these things that these kids feel as constraints are put upon them yeah that's a double-edged sword with this curiosity point with with children i think especially with ai unfettered curiosity at a young age with such a powerful thing is not that smart but i've personally experienced my ability to be curious and to explore at my older age and i like to translate some of that to the younger generation because I agree.

57:27I think there's this idea of just in time learning when you learn about a new thing and there's curiosity there to accomplish a goal, but you can't really accomplish that goal until you've gone a little deeper here, here, and here for context. I think that's kind of the new term or the new word of maybe potentially 2025 is context. Sure, AI and maybe even agentic, but I think a subversion of that is context. Yeah. You know, this just-in-time learning is really, really fascinating. And you must have been to conference or whatever, to some tech conference at some moment where there is someone describes something about a new cache algorithm.

58:10Yeah. And they look at that and they think, that shouldn't work. Yeah. Or actually, Amazon, we have something called the Builder's Library that's available for everyone to look at. These are articles written by Amazon's most senior engineers. And there is this one article by Colin that I couldn't get my head around because I've grown up in a time that you minimize the number of bytes on the wire. One more byte means more time, more delay, whatever. That's no longer the case. You know, he describes this system in which if the receiver always has to do exactly the same number of things, because there are 10 things in this packet, but eight of them may be empty.

59:05But everything is just standardized. You don't need to think about it. And the resilience grows up. Yeah. and so it took me a long time to get my head around that but the first time I read the intro to the story it immediately picked my curiosity and it took me a long time to learn what he really tried to achieve there and so I think you know even no matter how old we are there are moments every time when you get sort of, oh, how would that be? I live here in a place where there are a lot of electric scooters. The ones that, what's it, Lime, that Uber bought and some others and whatever. And I've always seen them, but I always was interested in curious how would it be to wear one?

1:00:09Well, now it's just a click on your phone and you jump on it. Then you go to the supermarket to buy your groceries and then you come back. You know, and it's just fun. And so, but, you know, curiosity is really one of the most amazing things that is uplifting in our life. So there's only one of you and there's only so many hours in the day and really only so much focus to go around. So my question to you is, what if you had a teammate who could work just like you with all the context you have, but a little faster? That's what Notion's new AI agent feels like. Notion already brings all your notes, all your docs, all your projects into one single connected space that just works.

1:00:52Seamless, flexible, powerful, and actually kind of fun to use. But with Notion agent, your AI doesn't just help you work. It finishes it. Here's what makes Notion agent different. It can do anything you could do in Notion. It taps into your workspace, the web, and the connected tools like Slack and Google Drive to complete assigned actions end to end. With a single prompt, it forms a plan, executes it, and will even reassess and try again if it hits the snag. Now, creating new pages, building databases from scratch, summarizing entire projects, it does it too easy. And since it's all inside Notion, you're always in control.

1:01:28You tell your agent how to behave. It remembers and updates automatically. Now, over 50 % of Fortune 500 companies use Notion, and fast-moving teams like OpenAI, Ramp, and Vercel, they're using Notion too. And we use Notion. Send less emails, cancel more meetings, stay ahead. It's too easy. So if you're ready to try your new AI teammate, Notion agent, head to notion.com slash changelog. Get started there. That's all lowercase, notion.com slash changelog. And of course, when you use our link, you're supporting our show. And we love that. And by our friends over at NordLayer, toggle ready network security for modern teams.

1:02:05Yes, if you're running a team, whether it's a five person company or a 500 person company, network security should not require a dedicated IT department and months of configuration. NordLayer is a toggle ready network security platform that combines VPN, access control and threat protection into one easy use platform. No hardware, no complex setup, just secure connection and full control. in less than 10 minutes. The cool part is it's built on the standards of NordVPN and it's powered by their NordLynx protocol based on WireGuard. NordLayer is designed for businesses, not consumers. It's based on zero trust architecture.

1:02:42Only the right people have access to the right resources under the right conditions. You get granular control over who accesses what, from where, and on which device. And the chef's kiss, the cherry on top, so to speak. It works on all platforms. Windows, Mac OS, iOS, Android, And of course, my favorite, Linux. So the next step is to go to nordlayer.com slash the changelog. Yes, nordlayer.com slash the changelog. Use our code changelog hyphen 28. Yes, the hyphen is important. Changelog hyphen 28. Guess what? 20 % off NordLayer yearly plans using the code changelog hyphen 28. It's valid until December 10th, 2025.

1:03:24Once again, NordLayer.com slash the changelog.

1:03:31It makes me think about this next notion, which I'm not sure I agree with, but it's been potentially the phrase or at least the sentiment of the last year or so, mainly around fear, uncertainty and doubt, which is developers are dead. That we're a dying breed. AI is taking our jobs. It's going to replace us. And you seem to push back on that idea through being a Renaissance developer. I do think if your job was only being, and that sounds a bit negative, being a code monkey. Yeah. Just tap in. All you do is code. That's all you do. You don't think. You don't plan it. Yeah. If that would be. But I think most of us have had to think about some of the stuff that we built.

1:04:24You had to think about algorithms. You had to think about trade-offs. You had to think about sort of, you went over to your colleague on the other side and you said like, you know, this is what I need to solve here. But I think there's a cash over run if that happens and that will brown out. And do you think that too? Shall we set up a test environment and see whether that works or not? Or, you know, there are so many parts to developers, development that will require our brains. And that's why I picked the word Renaissance. It's because before the Renaissance, there were the Dark Ages. Thousand years, basically.

1:05:14The Black Death, the plague, all these kind of things. and everything was ordered by basically religious institutions. And that changed at some moment where people became interesting again in all the amazing things that had been done a thousand years before by the Arabs, by the Romans, by the Greek. And so where they suddenly completely started to change. and there is this word that is sort of associated with the renaissance that is polymouth and many people think that that's people that is someone who can do mathematics in many different forms no no no no poly means mouth and matininia means learning much to learn yeah and if you look at the people in those days, definitely they suddenly started to become interested in many more things than just only the one thing that they were specialized in.

1:06:26Da Vinci was not just a sculptor. I mean, he built airplanes while they didn't fly. But he did build them. And just trying. I mean, think about all the people in those days that suddenly allowed their curiosity to come out now and i think as um as developers there are a number of things that we will need to we encounter first of all i do think we've been learning for 50 years now or whatever how long we've been doing computer science probably 1960s so yeah 60 years yeah so So we've been learning programming languages for 60 years. We've been going from mainframes to minis to PCs to cloud to whatever.

1:07:26Everything required a new approach to building or enabled us to do new things. You know, before cloud, you may have only had one colo and never would be able to build a replicated database. But then cloud came and suddenly you could replicate your database. You need to learn that, how to do that. But still, it is. and definitely I believe that it's not just sufficient to and now I need to be careful because I don't want to give away too much of my keynote go ahead spill the beans I'm just kidding I believe to be successful not only in the future but also now is to not only have a deep specialism but start to become interested in the broadness as well.

1:08:32It's called a T developer. It is someone that is not just a database expert. Not just a database expert, but he knows about the other types of application. He knows about other programming languages. He may even be able to help his colleagues on the other side or at least can have a conversation about it. Understands the business principles. of the business that he's actually running to. Another area that I think the newer type of developers, the Renaissance developer, needs to be an excellent communicator. And with that, for example, I mean, if you look at the Amazon website, just imagine that for you.

1:09:21there are three there are some parts of the amazon website that always need to work because otherwise we can't sell anything browse search shopping cart uh checkout and reviews because if there are no reviews people don't buy things yeah five things that absolutely need to work and then we have all the other things that actually are really important as well then we have 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 nines do you want behind that?

1:10:13Or 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?

1:11:09Now, 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 yeah or you know i'm i'm happy going away my database is running my code is running everything's happening transactions are playing through and suddenly the number of transactions doubles. But there isn't a doubling of the number of the customer on the website. Who the hell is doing this to me?

1:12:08And as such, you know, being a specialist in one particular area and just staying there is safe. Yeah, it's fine. But you live in a bigger system. You know, if we think about, and that really comes out of 60s, 70s, Medellin Meadows began what's something called system thinking. It is this, in nature, you know, if you remove one piece out of that equation, of the complete nature equation, you know, you ruin the overall thing. At some moment, how was it? Yellowstone Park. There were too many wolves. They removed the wolves from the park. Oh, they were killing all the elks. So they removed all the wolves.

1:13:07And then the number of elves grows like mad. Right, backfire. Which starts eating all sorts of parts of Yellowstone. And so not until we introduce the wolves, the balance gets back. So on her thinking, on systems thinking, is something that we as the future Renaissance engineers need to be part of as well. We need to understand that the one thing that we're working on at this moment has impact on all the other pieces around it. We need to be able to communicate with the others. We need to be able to see how we are part of this bigger problem. And you know what? And it will be fun. It will be fun.

1:14:01I absolutely think. And so one of the things I think that I, I won't say hate. let's say one of the most less interesting parts I always in the beginning as my life as developer thought were code reviews yeah it's a bit like standing in front of the class the whole class gets a chance to say like you're an idiot right but code reviews are fun sometimes you think There's mistakes there. Or sometimes you go like, wow. That's an elegant solution. I wish it for the water. And code reviews are super important for junior engineers. Because the senior engineers are in the room and discussing the code on the screen there.

1:14:55And you're learning on the spot from the senior engineer. From all their years of experience. where someone will say, yeah, I tried that when we were building product X, Y, or Z. Yeah. And it didn't work then. Or the problem at that time was that. Now, whether 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. Yeah. 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. And so those things don't go away.

1:15:50And so, and as such, if your system has been created by one of the AI tools, and as I said earlier 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 a search generation of code may go faster reviews will probably go slower because this is not code that i've written now 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 unhuman entity created this code for you it takes longer to get used to it yeah and and so i mean and not that's not bad i mean none of this don't take this as that i'm sort of cracking on a ai as being no there's this parts that will never leave us we need to learn the next steps we need we continue to keep uh ownership of what we do We continue to need to learn the next language, the next tool, the next system that we built.

1:17:26And, you know, we need to know more than just that one piece. We need to be more than that. And my favorite, and he comes back in almost every presentation that I give, was Jim Gray. He won the Turing Award. This is the guy that actually built System R at IBM, the inventor of transactions. Jim was brilliant. Absolutely brilliant. There's an article, if you want to look it up, it's called 20 Questions to Jim Gray. Jim said, give me 20 business questions or questions that you as a user of a database would want to answer the database, that have the database answer. I will build a database for you yeah and by the way one of the most interesting questions is he walks he walks into the room where the big machinery is and he hears the disks rattling and he looks sideways and he listens to disk he says your database layout is wrong yeah that was something he could hear yeah he was not just a database expert he had a lot of other skills in other areas and so he was what we would call a T developer an I developer is someone that knows only one thing a T developer has you know number of knowledges in other areas whether it's computer science, whether it's from the world or whatever.

1:19:12It's a broader person than just only the database developer. And I think in the future, this is something that we will continue to harness. You need to know more. You need to be able, because how can you communicate with your colleagues that build other parts of the system if you actually don't know anything about what and how they're doing it? This idea of code review, one thing you're making me think about is at least the sentiment it seems today is getting through code review. It seems like you're suggesting, even though it's painful, not so much pausing, but not getting through it just to deliver the code to production and correctness, but to understand why the code is what it is.

1:20:03And especially if it's AI generated and the human in the loop is less informed specifically about the code itself, that it's more of an artifact of a plan, not an artifact of actual implementation themselves. Yeah. And I'm getting old. I just had a great answer to what you wanted. And I completely lost it. I do think that we've changed over time as developers. I mean, I've written VB. I don't think there's anybody that writes Visual Basic anymore, is there? Not on purpose. Yeah. Fix a bug maybe in legacy code if it's still there. Yeah, something like that. But it was fun when we were doing it.

1:20:52And, you know, I wasn't thinking about five databases replicated over five different data centers throughout the world at that particular moment. I was trying to fix my Excel code. And so we've all grown as developers over the past 10, 15, 20 years with all sorts of new tools. We have a new tool. there is one there is a particular point that a particular small problem I have with it is that if you look at all the other tools that we've developed we took some time to introduce them we learned we had learned people we told people why we were building the tools how we were building the tools how they could best use them yeah the typical early adopters and you had to cross the chasm and then you had the early majority and things like that.

1:21:54And it would take time. But you would learn, you would teach your users why and how that tool was there. With some of the current, the new generative AI tools, they were just dumped in people's lap without telling them what it could do or what it couldn't do. yeah and you know there isn't almost a cio that i meet today when i'm traveling that asked me he says what should i be doing with ai and i go like well my excuses it's very inappropriate to answer a question with a question but why are you asking me this and just yeah but those guys next door you know they will be ahead of us or and i say are you really certain of that and then maybe because you're a little bit older you know you start to drive down into what is actually the problem they're trying to solve with this technology?

1:23:08And is this the right technology for this? Every week we see five new models or 10 new models. Suddenly we went from regular LLMs to reasoning LLMs. I think as a business, there is no shame in hitting the pause button for a moment and say, why don't we get ourselves educated about all of this? Yeah, and not just us as technologists, but also the business. Yeah, because at this moment, quite a few of our architectures are being determined by the media, not by us. Yeah, that shouldn't be the case. Yeah, we, together with our business, business should determine how our architectures should look like, not because the newest thing.

1:24:10And of course, and that's the task of the media. And the task of the media is also to write negative headlines. Even things are looking up. That company is massively behind that company. Yeah, you know what? AWS was never a consumer company. So we don't build consumer products. We build tools such that you can build your chatbots. Right. If Amazon, if AWS doesn't have a chatbot, means that we're out of business in AI, it just means it's not our business. And I think sort of that's really crucial in all of this, that we take time to learn the technologies, the capabilities of the technology, and where it can help us in our businesses.

1:25:03And, you know, if we also give it to a whole bunch of Gen Alpha kids that can go do wild with it and build their own educational curriculum with them, great, let them have it. Yeah? It's a bit like us 50 years ago with hammer and nails and building your own thing up in the tree, you know, and now kids do different things. But, you know, we need to give them the tools for it. And, but definitely in business, I think there is no shame in hitting the pause button and spend some time on education and making sure that you and your engineers are making the right decisions with the right tools. There is no hurry.

1:25:57There is no company will go out business in the company two months because they weren't using AI. Well, you heard it here first because very few people are saying that out loud. And while I agree with you and I think that it is a problem, I wonder if we have an appetite as an industry to address said problem. I think we're just barreling forward and we'll see what happens. But I also agree when you say give the kids the tools. Give the kids the tools. Oh, it's a big one. one of the other things I didn't make it this time into the predictions did I do it last year? one of the things that I think last year is one of the things I talked about one of the things that worries me is that parents driving in their car the kids are in the back seat they're getting when are you getting home and that was how we used to drive home now the kids get an ipad and become youtube experts and they're quiet in the back and the parents love it yeah but you set kids up from four or five years old to to get dopamine reactions they know how to manipulate youtube continuously and it's not only that they are said they're in this dopamine high, there's something else called dopamine too that actually removes your willpower in these kind of cases.

1:27:33Whenever you stand at the bus stop next time, look at how many people pull their cell phone out even if they know that the bus is three minutes away. Nobody wants to be bored anymore. Nobody wants to just stare out in the distance and use their brains. And we can't help ourselves because we've ruined ourselves. And if we do this with our young kids, we will have an epidemic on our hands 10, 15 years from now in terms of addiction. Invasive. Sorry, guys. I keep yapping. No, we appreciate it. We know you got to go. Didn't quite make it to your fifth, but great, great predictions. Thank you for sharing your extended thoughts on them and giving us some time today.

1:28:29Okay. Well, I really enjoyed it, guys. Come and watch my keynote, the last keynote at reInvent. I'm doing the C30 on Friday and Thursday. Nice. So after me, everybody can do whatever they want. You're the closer. You're the closer. I am the closer. Awesome, Werner. Well, you're welcome back anytime. Coming close. Yes. Okay. Bye-bye. Thank you, Werner.

1:28:59There you have it. Werner Vogel's predictions for 2026 and beyond. He had another one about defense technology that we didn't quite get to. Find the link to his article in the show notes. So do you agree with him? Do you disagree? What do you think will happen next? Let us know in the comments by joining our free community and chatting with us in Zulip. that link is also in your show notes thanks again to our partners at fly.io and to our beat freaking residents breakmaster cylinder who's hard at work remixing your state of the log voicemails we have a couple trickling in but we need more send us one why don't you at changelog.fm slash sotl that link is also you guessed it in your show notes all right that's it goodbye for now but we'll be back on Friday with Nick Neesey talking Anthropix, Acquisition of Bun, Sourcegraph and Amp splitting into Nick's latest Claude Code shenanigans, and what do we make of the new browser war?

1:29:56It's a good one. We'll talk to you then.

1:30:28Game on.

From the publisher

Amazon CTO, Werner Vogels, stops by to help us explore his tech predictions for 2026 and beyond. Will companionship be redefined by consumer robots? Will quantum-safe become the only safe worth talking about? Is this the dawn of the renaissance developer? We're infinitely curious why Werner came to this particular set of conclusions. Are you?

More from The Changelog: Software Development, Open Source

All 232 episodes
Werner Vogels predicts the future (Interview)The Changelog: Software Development, Open Source · 1 h 31 min
Listen in VO