text stringlengths 0 2.68k |
|---|
**Jerod Santo:** It's the why. |
**Amanda Silver:** Well, it's the conversation. Like, if you think about, you were having a conversation with your designer, or another engineer on the team, in terms of how something should work... Maybe over time the history of that conversation should actually be something that's persisted into the codebase, in some... |
**Jerod Santo:** Yeah. And hopefully in a summarized fashion, so it's actually grokkable... |
**Amanda Silver:** Yeah, exactly. |
**Jerod Santo:** I know there's some people that keep actual -- I can't remember if it's called a why document... But it's basically around their decisions. Not the decision we made, but why we made the decision. And so you can go back to that and be like "No, here's why there's this fence here." |
**Amanda Silver:** Exactly. |
**Jerod Santo:** You see a fence, you're like "Why is the fence there? It doesn't need to be there." It's like, "Well, there was a reason... And none of us know why. It's lost to history." But now you can go back to that chat or that context, and at least link it somehow, whether it's summarized, or linkable, or whatev... |
**Amanda Silver:** Yeah. Maybe in that world developers don't have to write documentation. |
**Jerod Santo:** Now you're selling me. |
**Adam Stacoviak:** Oh, my gosh... \[laughter\] Or they write one. They write one, the initial spec. |
**Jerod Santo:** That's right. |
**Adam Stacoviak:** Yeah, I was thinking about that, too. |
**Jerod Santo:** Alright, awesome. This has been a blast. |
**Amanda Silver:** Yeah, thanks for having me, guys. |
**Jerod Santo:** Thanks so much for sitting down with us, Amanda. |
**Adam Stacoviak:** Very fun. Thank you. |
• Discussion of Werner Vogels' background and experience as CTO of Amazon |
• Evolution of NoSQL tools, including DynamoDB and MongoDB |
• Description of Werner Vogels' role at Amazon, from director of systems research to external-focused CTO |
• Discussion of hard human problems, such as feeding and providing economic futures for 2 billion more people by 2050 |
• Overview of Amazon's focus on solving real human problems, including the ocean cleanup project |
• Explanation of Werner Vogels' predictions, including the fifth annual set, and why he writes them |
• Discussion of Werner Vogels' philosophy on technology's impact on society and the importance of responsibility with scale |
• Loneliness and its impact on mental and physical health |
• Technological solutions to address loneliness, including companion robots |
• Japan's changing society and its impact on elderly care |
• The potential for technology to help people stay independent and connected |
• The concept of attachment and affection towards robots and other non-human entities |
• The importance of considering the emotional and psychological impact of technology on users |
• Children forming strong attachments to non-human companions |
• Loneliness and the potential of technology to alleviate it |
• Quantum computing and its implications for security |
• The importance of preparing for the potential decryption of encrypted data |
• The need for post-quantum cryptography and the implementation of new encryption methods |
• Discussion of post-quantum encryption and the need for its adoption |
• Concerns about data harvesting and the security of connected devices |
• The importance of keeping technology and businesses safe, regardless of the threat (quantum or otherwise) |
• The role of automatic reasoning and proof in ensuring the security of systems |
• The use of AI and machine learning in building secure systems |
• The need for education and self-learning in the face of technological change, particularly with regard to AI and quantum computing |
• The importance of curiosity in driving learning and staying ahead of technological advancements |
• The importance of curiosity in children and its suppression in traditional education systems |
• The potential of technology to provide personalized and customized learning experiences |
• The limitations of traditional education systems and the need for more support for teachers |
• The role of AI in facilitating curiosity and just-in-time learning |
• The need for teachers to focus on individual interaction and not just grading and administration |
• The potential for children to take control of their own learning and create customized curricula |
• The importance of context and understanding in learning and problem-solving |
• Electric scooters and the convenience of technology |
• The concept of "Developers are dead" due to AI and automation |
• The Renaissance developer: being a polymath with broad interests and skills |
• The importance of deep specialism and broadness in development |
• Communication and system thinking as essential skills for Renaissance developers |
• The need for developers to consider the impact of their work on the entire system, not just their own code |
• Importance of code reviews for junior engineers and AI-generated code |
• Responsibility for AI-generated code and the need for human oversight |
• Value of human skills and knowledge in addition to technical expertise |
• Dangers of rushing into AI adoption without proper education and understanding |
• Need for businesses to take ownership of their architectures and make informed decisions about technology adoption |
• Importance of education and learning before adopting new technologies |
• Benefits of taking time to understand AI capabilities and limitations before implementing them |
• The industry's potential to address a problem related to kids and technology |
• The impact of technology on children, specifically the addiction to screens and social media |
• The manipulation of children through dopamine reactions from a young age |
• The potential long-term consequences of this trend, including addiction and a loss of willpower |
• The need to be aware of and address this issue to prevent an epidemic in the next 10-15 years |
**Adam Stacoviak:** Well, 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 of years, so you're pretty accurate, Werner... Welcome to the show again. The last time you were here was for the NoSQL Smack... |
**Jerod Santo:** Forever ago. Episode 18. |
**Adam Stacoviak:** Back when NoSQL was cool, fresh and burgeoning... Now it's ubiquitous and everywhere, and I guess still cool... Coolish. Coolish. |
**Werner Vogels:** 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. |
**Adam Stacoviak:** Come a long way. I think it was burgeoning. DynamoDB was coming out then, it was fresh and brand new... I guess as CTO, you probably architected a lot of that stuff. What do you do as part of your role? What is your role maybe then, 15 years ago, and then how is it now? |
**Werner Vogels:** So first of all, it's 21 years now, so that's a bit... And there is a predecessor to DynamoDB. That's Dynamo. And one of the things - when I joined Amazon, I joined as what was called a director of systems research. The idea was to bring... Let me go a little bit back. Think about 1994, when Jeff Bez... |
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, you get some more robustness. You get a better fundamental approach to scale, and reliability, and things like that. And we did lot... |
If I think about CTOs, there's sort of four or five different types. And there's no real well-developed, well-described one. First of all, there's the data center manager. He reports up to the CIO. Then you have the CTO, that is the second person in the startup, often the co-founder, the first coder... And then you hav... |
\[08:15\] So your world changes from being purely internal to being external, and sort of bringing back things into -- and then over time, I've become more and more interested in those organizations, both profit and non-profit, that try to solve hard problems. And with hard problems, I mean hard human problems. |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.