POPULARITY
2 episodes with mindmup
2 episodes with mindmup
2 episodes with mindmup
2 episodes with mindmup
2 episodes with mindmup
BONUS: Gojko Adzic on Optimizing Products for Long-Tail Users (Agile Online Summit 2024 Replay) In this BONUS episode, we revisit Gojko Adzic's insightful interview at the Agile Online Summit 2024. Gojko, an award-winning author and software expert, unpacks the principles behind his latest book, Lizard Optimization, offering a fresh perspective on improving product usability by addressing the needs of long-tail users. From learning from unexpected user behaviors to refining products with a systematic approach, this episode is filled with practical tips for product teams and Agile practitioners. What is Lizard Optimization? Drawing from his experiences as a product developer, Gojko introduces the idea of Lizard Optimization. He discusses how observing unexpected user behaviors led him to refine his SaaS tools like Narakeet and MindMup. By focusing on usability challenges and unusual patterns, he has turned serendipity into actionable insights. “Users aren't stupid—they're just finding creative ways to get value from your product. Listen to them.” Gojko explains the inspiration behind the metaphor of the “Lizardman constant,” a concept from a Scott Alexander blog post. He describes how this principle applies to product optimization: understanding and addressing the 4% of surprising, unexplainable behaviors can uncover opportunities for innovation. “The job isn't to judge users—it's to explore why they're doing what they're doing and how we can help them succeed.” The High-Level Process of Lizard Optimization Gojko outlines the systematic process described in his book to leverage unexpected user behavior: Observe Misuse: Identify how users deviate from expected patterns. Extract Insights: Focus on one unexpected behavior as a signal. Remove Obstacles: Help users achieve their goals more easily. Monitor Impacts: Detect and adjust for unintended consequences. “Start monitoring for the predictable but unexpected—those hidden gems can unlock your next big feature.” Practical Advice for Product Teams For teams ready to apply these concepts, Gojko emphasizes the importance of expanding observability tools to include product metrics and not just technical ones. He shares how tracking unpredictable user actions can inspire impactful changes. “About a third of what we do delivers value—focus on finding where unexpected value lies.” Recommended Resources To dive deeper into these ideas, Gojko recommends: Trustworthy Online Controlled Experiments by Ron Kohavi Evidence Guided by Tim Herbig LizardOptimization.org “Experimentation and evidence-based decision-making are the keys to building better products.” Closing Thoughts: “Look for the Unexpected” Gojko's parting advice for Agile practitioners is simple yet powerful: Look for the unexpected. By embracing surprises in user behavior, teams can transform minor inconveniences into major opportunities for growth. “The unexpected is where innovation begins.” About Gojko Adzic Gojko Adzic is an award-winning author, speaker, and product creator. His books, including Lizard Optimization, Impact Mapping, and Specification by Example, have become essential reads for Agile practitioners and product teams worldwide. Gojko is a 2019 AWS Serverless Hero, the winner of the 2016 European Software Testing Outstanding Achievement Award, and the 2011 Most Influential Agile Testing Professional Award. He has also co-founded several successful SaaS tools, including Narakeet, MindMup, and Votito. You can link with Gojko Adzic on LinkedIn.
Gojko Adzic - Lizard OptimizationLook who's back! Gojko Adzic will present us his new book Lizard Optimization: Unlock product growth by engaging long-tail users.As we read on the back cover: "Lizard Optimization is a technique for designing product development experiments by engaging long-tail users that seem to follow some unexplainable "lizard" logic. It can help you understand your audience better and improve your products. The method is based on the author's experience managing an online software product that grew explosively from November 2021 to November 2022. The key user metric, tracking when people are getting value from the product, increased by more than 500 times in those 12 months (times, not percent). This happened after a period of unremarkable growth and a slow decline. Looking back, the key factor in reversing the decline and unlocking exponential growth was a counter-intuitive approach to engaging users. This book is a summary of the key lessons from that crazy growth phase, synthesized into a simple process that you can apply to improve your products, and help you unlock growth, reduce churn and increase revenue."And as usual - plenty of space for your questions!
Gojko Adzic - Lizard OptimizationLook who's back! Gojko Adzic will present us his new book Lizard Optimization: Unlock product growth by engaging long-tail users.As we read on the back cover: "Lizard Optimization is a technique for designing product development experiments by engaging long-tail users that seem to follow some unexplainable "lizard" logic. It can help you understand your audience better and improve your products. The method is based on the author's experience managing an online software product that grew explosively from November 2021 to November 2022. The key user metric, tracking when people are getting value from the product, increased by more than 500 times in those 12 months (times, not percent). This happened after a period of unremarkable growth and a slow decline. Looking back, the key factor in reversing the decline and unlocking exponential growth was a counter-intuitive approach to engaging users. This book is a summary of the key lessons from that crazy growth phase, synthesized into a simple process that you can apply to improve your products, and help you unlock growth, reduce churn and increase revenue."And as usual - plenty of space for your questions!
This interview was recorded for the GOTO Book Club.http://gotopia.tech/bookclubRead the full transcription of the interview hereGojko Adzic - Software Delivery Consultant & Author of "Lizard Optimization" and many more BooksDave Farley - Continuous Delivery & DevOps Pioneer, Award-winning Author, Founder & Director of Continuous Delivery Ltd.RESOURCESGojkohttps://twitter.com/gojkoadzichttps://www.linkedin.com/in/gojkohttps://github.com/gojkohttps://gojko.netDavehttps://twitter.com/davefarley77https://linkedin.com/in/dave-farley-a67927http://www.continuous-delivery.co.ukhttp://www.davefarley.netDESCRIPTIONDave Farley and Gojko Adzic discuss Gojko's latest book “Llizard Optimization”, which involves identifying and leveraging unconventional uses and misuses of products to improve them for all users. Gojko shares insights and examples from his experiences with Narakeet and MindMup, highlighting how addressing the needs of outlier users led to significant product enhancements and growth.They also touch on broader themes of user retention, the joy of building and solving problems, and the balance between solo work and collaborative efforts in software development and writing.RECOMMENDED BOOKSGojko Adzic • Lizard OptimizationGojko Adzic • Impact MappingAdzic, Evans & Roden • Fifty Quick Ideas To Improve Your TestsAdzic, Evans & Korac • Fifty Quick Ideas to Improve Your User StoriesAdzic & Korac • Humans vs ComputersGojko Adzic • Specification by ExampleAdzic, Marcetic & Bisset • Bridging the Communication GapAdzic & Korac • Running ServerlessKat Holmes • MismatchDavid Farley • Modern Software EngineeringDave Farley • Continuous Delivery PipelinesDave Farley & Jez Humble • Continuous DeliveryTwitterInstagramLinkedInFacebookLooking for a unique learning experience?Attend the next GOTO conference near you! Get your ticket: gotopia.techSUBSCRIBE TO OUR YOUTUBE CHANNEL - new videos posted daily!
What do lizards have to do with product growth? In this episode, Gojko Adzic reveals how unusual user behaviors can unlock massive opportunities for product innovation. Discover the four steps to mastering "Lizard Optimization" and learn how you can turn strange user actions into game-changing insights. Overview In this episode of the Agile Mentors Podcast, host Brian Milner chats with Gojko Adzic about his new book, Lizard Optimization. Gojko explains the concept of finding product growth signals in strange user behaviors, sharing examples where unexpected user actions led to product breakthroughs. He outlines a four-step process for optimizing products by learning, zeroing in, removing obstacles, and double-checking. Gojko also discusses helpful tools like session recorders and observability tools that can enhance product development by uncovering and addressing unique user behaviors. References and resources mentioned in the show: Gojko Adzic 50% OFF Lizard Optimization by Gojko Adzic Mismatch: How Inclusion Shapes Design by Kat Holmes Trustworthy Online Experiments by Ron Kohavi Advanced Certified Scrum Product Owner® Subscribe to the Agile Mentors Podcast Join the Agile Mentors Community Want to get involved? This show is designed for you, and we’d love your input. Enjoyed what you heard today? Please leave a rating and a review. It really helps, and we read every single one. Got an Agile subject you’d like us to discuss or a question that needs an answer? Share your thoughts with us at podcast@mountaingoatsoftware.com This episode’s presenters are: Brian Milner is SVP of coaching and training at Mountain Goat Software. He's passionate about making a difference in people's day-to-day work, influenced by his own experience of transitioning to Scrum and seeing improvements in work/life balance, honesty, respect, and the quality of work. Gojko Adzic is an award-winning software consultant and author, specializing in agile and lean quality improvement, with expertise in impact mapping, agile testing, and behavior-driven development. A frequent speaker at global software conferences, Gojko is also a co-creator of MindMup and Narakeet, and has helped companies worldwide enhance their software delivery, from large financial institutions to innovative startups. Auto-generated Transcript: Brian (00:00) Welcome in Agile Mentors. We're back for another episode of the Agile Mentors podcast. I'm with you as always, Brian Milner. And today, very special guest we have with us. have Mr. Goiko Atshich with us. I hope I said that correctly. Did I say it correctly? Close enough. Okay. Well, welcome in, Goiko. Glad to have you here. Gojko (00:15) Close enough, close enough. Brian (00:21) Very, very, very happy to have Goiko with us. If you're not familiar with Goiko's name, you probably are familiar with some of his work. One of the things I was telling him that we teach in our advanced product owner class every time is impact mapping, which is a tool that Goiko has written about and kind of come up with on his own as well. Gojko (00:21) Thank you very much for inviting me. Brian (00:47) But today we're having him on because he has a new book coming out called Lizard Optimization, Unlock Product Growth by Engaging Long Tail Users. And I really wanted to talk to him about that and help him explain, have him explain to us a little bit about this idea, this new concept that his new book is about. So, Goiko, let's talk about it. Lizard Optimization, in a nutshell, what do you mean by that? What is it? Gojko (01:14) We're going to jump into that, but I just need to correct one of the things you said. I think it's very, very important. You said I came up with impact mapping and I didn't. I just wrote a popular book about that. And it's very important to credit people who actually came up with that. It's kind of the in -use design agency in Sweden. And I think, you know, they should get the credit for it. I literally just wrote a popular book. Brian (01:19) Okay. Gotcha. Gotcha, gotcha. Apologies for that incorrect. Thank you for making that correction. So lizard optimization. Gojko (01:44) So, lizard optimization. Good. So, lizard optimization is an idea to find signals for product ideas and product development ideas in strange user behaviors. When you meet somebody who does something you completely do not understand, why on earth somebody would do something like that? Brian (02:03) Okay. Gojko (02:11) and it looks like it's not done by humans, it looks like it's done by somebody who follows their own lizard logic, using stuff like that as signals to improve our products. Not just for lizards, but for everybody. So the idea came from a very explosive growth phase for one of the products I'm working on, where it... had lots of people doing crazy things I could never figure out why they were doing it. For example, one of the things the tool does is it helps people create videos from PowerPoints. You put some kind of your voiceover in the speaker notes, the tool creates a video by using text to speech engines to create voiceover from the speaker notes, aligns everything and it's all kind of for you. People kept creating blank videos and paying me for this. I was thinking about why on earth would somebody be creating blank videos and it must be a bug and if it's a bug then they want their money back and they'll complain. So I chased up a few of these people and I tried to kind of understand what's going on because I originally thought we have a bug in the development pipeline for the videos. So... I started asking like, you know, I'm using some, I don't know, Google slides or, you know, keynote or whatever to produce PowerPoints. Maybe there's a bug how we read that. And the person, no, no, we, know, official Microsoft PowerPoint. They said, well, can you please open the PowerPoint you uploaded? Do you see anything on the slides when you open it? And the person, no, it's blank. Right? Okay, so it's blank for you as well. I said, yeah. So. Brian (03:48) Yeah. Gojko (03:54) What's going on? so what I've done is through UX interviews and iterating with users and research, we've made it very, very easy to do advanced configuration on text -to -speech. And it was so much easier than the alternative things that people were creating blank PowerPoints just to use the text -to -speech engines so they can then extract the audio track from it. Brian (03:54) Yeah, why? Gojko (04:23) and then use that and it was this whole mess of obstacles I was putting in front of people to get the good audio. It wasn't the original intention of the tool. It wasn't the original value, but people were getting unintended value from it. And then I ended up building just a very simple screen for people to upload the Word document instead of PowerPoints. And it was much faster for users to do that. A month later, there was many audio files being built as videos. Two months later, audio... production overtook video production. then at the moment, people are building many, many more audio files than video files on the platform. So it was an incredible growth because of this kind of crazy insight of what people were doing. kind of usually, at least kind of in the products I worked on before, when you have somebody abusing the product, product management fight against it. There's a wonderful story about this in... Founders at work a book by Jessica Livingston and she talks about this kind of group of super smart people in late 90s who Came up with a very very efficient Cryptography algorithm and a way to compute the cryptography so they can run it on low -power devices like Paul pilots Paul pilots were you know like mobile phones, but in late 90s and Then they had to figure out, how do we monetize this? Why would anybody want to do this? So they came up with the idea to do money transfer pumping, Palm pilots, you know, why not? And kind of the built a website. This was the late nineties as a way of just demoing this software to people who didn't have a Palm pilot device next to them. The idea was that you'd kind of see it on the website, learn about it, then maybe download the Palm pilot app and use it in anger. People kept just using the website, they're not downloading the Palm Pilot app. So the product management really wasn't happy. And they were trying to push people from the website to the Palm Pilot app. were trying to, they were fighting against people using this for money transfer on the web and even prohibiting them from using the logo and advertising it. They had this whole thing where nobody could explain why users were using the website because it was a demo thing. It was not finished. It was not sexy. It was just silly. And Jessica kind of talks to one of these people who insists that it was totally inexplicable. Nobody could understand it. But then a bit later, they realized that the website had one and half million users and that the Pongpilot app had 12 ,000 users. So they kind of decided, well, that's where the product is really. And that's like today, people know them as PayPal. They're one of the biggest payment processes in the world because kind of, you know, they realized this is where the product is going. And I think in many, many companies, people Brian (07:03) Ha ha. Gojko (07:18) stumble upon these things as happy accidents. And I think there's a lot more to it. We can deliberately optimize products by looking for unintended usage and not fighting it, just not fighting it. just understand this is what people are getting as value. And I think for me as a solo product founder and developer and product manager on it, One of the really interesting things is when you have somebody engaging with your product in an unexpected way, most of the difficult work for that user is already done. That person knows about you, they're on your website or they're using your product, the marketing and acquisition work is done. But something's preventing them from achieving their goals or they're achieving some value that you did not really know that they're going to achieve. you know, that's something the product can do to help them and remove these obstacles to success. So that's kind of what lizard optimization is making this process more systematic rather than relying on happy accidents. And by making it more systematic, then we can help product management not fight it and skip this whole phase of trying to fight against our users and claim that users are stupid or non -technical or... They don't understand the product, but they're trying to figure out, well, that's what the real goals are. And then following that. Brian (08:47) That's awesome. So the pivot, right? The pivot from here's what we thought our problem was we were solving to now here's what we're actually solving and we should organize around this actual problem, right? Gojko (09:02) or here's what we're going to solve additionally. This is the problem we've solved, but hey, there's this problem as well. And then the product can grow by solving multiple problems for people and solving related problems and solving it for different groups of people, for example. And that's the really interesting thing because I think if you have a product that's already doing something well for your users and a subset of them are misusing it in some way, then kind of... Brian (09:04) Yeah. Gojko (09:30) The product might already be optimized for the majority of users, but there might be a new market somewhere else. So there might be a different market where we can help kind of a different group of users and then the product can grow. Brian (09:43) Yeah, I like to focus on the user. There's an exercise that we'll do in one of our product owner classes where we have a fake product that is a smart refrigerator. And one of the exercises we try to get them to brainstorm the different kinds of users that they might have for it. And one of the things that always comes out in that class is as they're going through and trying to describe the types of users, they inevitably hit to this crossroads where they start to decide Well, yes, we're thinking of this as a home product, something for people to use in their homes. But then the idea crosses their mind, well, what about commercial kitchens? What about people who might use this in another setting? And it's always an interesting conversation to say, well, now you've got a strategic choice to make, because you can target both. You can target one. You can say, we're ignoring the other and we're only going in this direction. So to me, I think that's kind of one of the interesting crossroad points is to say, how do I know when it's time to not just say, great, we have this other customer segment that we didn't know about, but actually we should start to pivot towards that customer segment and start to really target them. Gojko (11:03) Yeah, think that's a fundamental question of product development, isn't it? Do you keep true to your vision even if it's not coming out or if something else is there that's kind more important than I think? For me, there's a couple of aspects to that. One is, laser focus is really important to launch a product. You can't launch a product by targeting... the whole market and targeting a niche type, figuring out, you know, user personas, figuring out like really, really, this is the product who we think the product, this is the group who we think the product is for and giving them a hundred percent of what they need is much better than giving 2 % to everybody because then the product is irrelevant. But then to grow the product, we need to kind of grow the user base as well. And I think one of the things that... is interesting to look at and this comes from a book called Lean Analytics. It's one of my kind of favorite product management books is to look at the frequency and urgency of usage. If you have a group that's kind of using your product, a subgroup that's using your product very frequently compared to everybody else, that might be kind of the place where you want to go. The more frequently, the more urgently people reach for your product when they have this problem. the more likely they are going to be a good market for it. with kind of another product that I've launched in 2013, we originally thought it's going to be a product for professional users. And we aimed at the professional users. And then we found that a subcategory that we didn't really expect, were kind of teachers and children in schools. we're using it a lot more frequently than professional users. And then we started simplifying the user interface significantly so that it can be used by children. And it's a very, very popular tool in schools now. We are not fighting against other professional tools. We were kind of really one of the first in the education market there. And it's still a very popular tool in the education market because we figured a subgroup that's using it very frequently. Brian (13:14) Hmm. Yeah, that's awesome. How do you know when, you know, what kind of threshold do you look for to determine that, this is, because, you know, in your book, you're talking about, you know, behaviors that are not normal, right? People using your product in a way that you didn't anticipate. And what kind of threshold do you look for to that says, hey, it's worth investigating this? You know, I've got this percentage or this number of people who are using it in this strange way. At what point do you chase that down? Gojko (13:49) I think it's wrong to look at the percentages there. I think it's wrong to look at the percentages because then you get into the game of trying to justify economically helping 0 .1 % of the users. And that's never going to happen because what I like about this is an idea from Microsoft's Inclusive Design and the work of Kat Holmes who wrote a book called Mismatch on Brian (13:52) Okay. Gojko (14:17) assistive technologies and inclusive design for disabled people. And she talks about how it's never ever ever going to be economically justified to optimize a product to help certain disabilities because there's just not enough of them. And there's a lovely example from Microsoft where, Microsoft Inclusive Design Handbook where they talk about three types of, Brian (14:34) Yeah. Gojko (14:44) disabilities, one are permanent. So you have like people without an arm or something like that. And I'm going to kind of throw some numbers out now, order of magnitude stuff. I have these details in the book and there's kind of the micro -inclusive design handbook. Let's say at the moment, the 16 ,000 people in the U .S. without one arm or with a disabled arm. And then you have these kind of situational disabilities where because of an occupation like you have a bartender who needs to carry something all the time or a worker who does it, one arm is not available and they only have one arm to work on and this temporary like a mother carrying a child or something like that. So the other two groups are order of magnitude 20 -30 million. We're not, by making the software work well with one hand, we're not helping 16 ,000 people, we are helping 50 million people. But you don't know that you're helping 50 million people if you're just thinking about like 16 ,000. I think they have this kind of, one of the key ideas of inclusive design is solve for one, kind of help, design for one, but solve for many. So we are actually helping many, many people there. So think when you figure out that somebody is doing something really strange with your product, you're not helping just that one person. Brian (15:45) Right, right. Hmm. Gojko (16:13) you're helping a whole class of your users by making the software better, removing the obstacles to success. this is where I, you know, going back to the PowerPoint thing I mentioned, once we started removing obstacles for people to build the audios quickly, lots of other people started using the product and people started using the product in a different way. And I think this is a lovely example of what Bruce Torazzini talks about is the complexity paradox because He's a famous UX designer and he talks about how once you give people a product, their behavior changes as a result of having the product. So the UX research we've done before there is a product or there is a feature is not completely relevant, but it's a changed context because he talks about people have a certain amount of time to do a task. And then when they have a tool to complete the task faster, they can take on a more complicated task or they can take on an additional task or do something else. I think removing obstacles to use a success is really important. Not because we're helping 0 .1 % of people who we don't understand, but because we can then improve the product for everybody. And I think that's kind of the magic of lizard optimization in a sense, where if we find these things where somebody's really getting stuck. but if we help them not get stuck, then other people will use the product in a much better way. And I think this is, know, the name lizard optimization comes from this article by Scott Alexander, who talks about the lizard man's constant in research. And the article talks about his experiences with a survey that combined some demographic and psychological data. So they were looking at where you live and what your nationality is and what gender you are and then how you respond to certain psychological questions. he said, like there's about 4 % of the answers they could not account for. And one person wrote American is gender. Several people listed Martian as nationality and things like that. some of these, he says some of these things will be people who didn't really understand the question. they were distracted, they were doing something else, or they understood the question but they filled in the wrong box because, know, the thick thumbs and small screens, or they were kind of malicious and just, you know, wanted to see what happens. when you kind of add these people together, they're not an insignificant group. kind of, he says 4%. And if... we can help these people, at least some of these people, and say reduce churn by 1%. That can compound growth. Reducing churn, keeping people around for longer is an incredible way to kind of unlock growth. going back to what we were talking about, some people might be getting stuck because they don't understand the instructions. Some people might be getting stuck because they're using the product in a way you didn't expect. And some people might just like not have the mental capacity to use it the way you expected them to be used. But if we can help these people along, then normal users can use it much, easier. And you mentioned a smart fridge. I still remember there was this one wonderful bug report we had for my other product, which is a collaboration tool. we had a bug report a while ago. that the software doesn't work when it's loaded on a fridge. And it's like, well, it was never intended to be loaded on a fridge. I have no idea how you loaded it on a fridge. It's a mind mapping diagramming tool. It's intended to be used on large screens. Where does a fridge come in? And then we started talking to this person. This was before the whole kind of COVID and work from home disaster. The user was a busy mother and she was kind of trying to collaborate with her colleagues while making breakfast. breakfast for kids and kind of running around the kitchen she wasn't able to kind of pay attention to the laptop or a phone but her fridge had a screen so she loaded the software on the fridge and was able to kind of pay attention to collaboration there and you know we of course didn't optimize the software to run on fridges that's ridiculous but we realized that some people will be using it without a keyboard and without a mouse and then we kind of restructured the toolbar, we made it so that you can use it on devices that don't have a keyboard and then the whole tablet thing exploded and now you get completely different users that don't have keyboards and things like that. I think that's where I think is looking at percentages is a losing game because then you start saying, but 0 .1 % of people use this. But yeah, I think lizard optimization is about using these signals to improve the products for everybody. Brian (21:30) That's a great example. I love that example because you're absolutely right. You're not trying to necessarily solve that one problem because you don't anticipate there's going to be a lot of people who are going to want to run that software on a fridge. However, the takeaway you had from that of, we can do this for people who don't have a keyboard or a mouse. There's another way that they might operate this that could apply to lots of different devices and lots of different scenarios. Now we're talking about a much bigger audience. Now we're talking about opening this up to larger segments of the population. I love that. I think that's a great example. I know you talk about that there's kind of a process for this. Help us understand. You don't have to give away the whole candy story here from the book, but help us kind of understand in broad, terms what kind of process people follow to try to chase these things down. Gojko (22:26) So there's like a four step process that's crystallized for me. And the book is kind of more as a, like a proposal or a process. It's something that works for me and I'm hoping that other people will try it out like that. So it might not necessarily stay like that in a few years if we talk again. And I've narrowed it down to four steps and kind of the four steps start with letters L, Z, R and D. Lizard. And it's kind of so learn how people are misusing your products, zero in on one area, on one behavior change you want to improve, then remove obstacles to use a success and then double check that what you've done actually created the impact you expected to make. I think kind of when we look at people who follow their own logic or people who follow some lizard logic you don't really understand, by definition they're doing something strange. your idea of helping them might not necessarily be effective or it might not go all the way or it might. So double checking at the end that people are actually now doing what you expect them to do or doing something better is really, really, really important. And then using signals from that to improve the kind of feedback loop is critical. I had this one case where people were getting stuck on a payment format entering tax details and The form was reasonably well explained. There was an example in the forum how to enter your tax ID and people were constantly getting stuck. A small percentage of people was getting stuck on it. However, I don't want to lose a small percentage of people that want to pay me on the payment form. So I thought, well, how about if I remove that field from there? I speed it up for everybody and then I can guide them later into entering the tax details to generate an invoice. I thought that was a brilliant idea. tested it with a few users. Everybody loved it, so I released it. And then a week later, I realized that, yes, I've sold it for the people that were getting confused, but I've ended up confusing a totally different group of people that expects the tax fields there. So the net effect was negative. then I went back to the original form. so there's lots of these things where people don't necessarily behave the way you think they will. Brian (24:38) Hahaha. Gojko (24:48) Ron Kohavi has a wonderful book about that called Trustworthy Online Experiments. And he has data from Slack, from Microsoft, from Booking .com and... The numbers are depressive. on one hand, the numbers range from 10 to 30, 40 % success rate for people's ideas. And if leading companies like that do things that don't pan out two thirds of the time, then we have to be honest building our products and say, well, maybe this idea is going to work out, maybe not. Brian (25:03) Hahaha. Wow. Gojko (25:30) the more experimental the population is, the more risky that is. think monitoring and capturing weird user behaviors, capturing errors helps you understand that people are getting stuck. as you said, you don't want to follow everybody. There's going to be a lot of noise there. We need to extract signals from the noise. That's what the second step is about, focusing on one specific thing we want to improve. Then, try to remove obstacles and then double -checking that we've actually removed them. That's the four steps. And there's like a shorter version of all the four steps. It's easier to remember. It's listen alert, zooming, rescue them, and then double check at the end. that's again, LZRD. Brian (26:13) That's awesome. Yeah, I love the process and I love the kind of steps there. Are there tools that you recommend for this that are easier to try to determine these things or chase them down or are there tools that you find are more helpful? Gojko (26:32) So there's lots of tools today for things like A -B testing and looking at experiments and things that are very helpful to do this scale. And it's kind of especially useful for the last step. In terms of kind of focusing and things like that, the five stages of growth from the linear analytics are a good tool. Impact mapping is a good tool. Kind of any focusing product management technique that says, well, these are the business goals we're working on now, or these are the kind of user goals we're working on now. out of, know, 50 lizards we found last week, these three lizards seem to be kind of in that area. And for the first step, spotting when people are getting stuck, there's a bunch of tools that are interesting, like session recorders for web products. There's one from Microsoft called Clarity that's free. There's another called Full Story that's quite expensive. There's a couple of open source one, one is packaged within Matomo analytics application. There's a bunch of these other things. Any kind of observability or monitoring tool is also very useful for this because we can spot when people are getting stuck. One of the things I found particularly helpful is logging all user errors. When a user does something to cause an error condition in a product, the product of course tells them like, know, an error happened. But then... logging it and analyzing that information in the back is really critical. for something like that, people sometimes use web analytics tools or any kind of product analytics. I think what's going to be interesting in the next couple of years, and I think if people start doing this more, is we'll see. more like these technical exception analytics tracking tools mixed with this because most of the product analytics are showing people what they expect to see, not what they don't expect to see. And I'll just give you an example of this way. was really helpful. So I've mentioned the screen where people can upload the Word documents. Occasionally people would select weird file types. So they'll select images, they'll select, I don't know, what else. Brian (28:31) Yeah. Gojko (28:49) Sometimes I guess that's a result of, know, a fat finger press or somebody not selecting the right thing. I have a not insignificant percentage of users every day that try to upload Android package files into a text -to -speech reader. Android package files and application files, I don't know what the right way is to read out an Android application. My best guess is people are doing that. as a, you know, these things where you drop a USB in front of an office and somebody kind of mistakenly plugs it in. So maybe they're hoping that I'll know the Android application on my phone just because they've uploaded it. I don't know, but a small percentage of users was trying to upload files that had SRT and VTT extensions, which are subtitle files. And they were not supported, but Brian (29:31) Yeah. Gojko (29:45) I kept getting information that people are uploading those types of files. And then I said, well, this is interesting because it's a text to speech system. People are uploading subtitle files, there's text in, so why don't I just ignore the timestamps and read the text? I can do that. And I started supporting that. And then some people started complaining that, well, the voice is reading it slower than the subtitles. I said, well, yes, because... Brian (30:11) Ha Gojko (30:12) You know, you're uploading subtitles that were read by an actor in a movie. This is a voice that's reading it at their speed. And then we started talking and it turns out that these people were doing it for corporate educational videos where they have a video in English, they need it in French, German, Spanish and all the else, but they don't want to kind of re -edit the video. They just want an alternate audio track. Okay, I mean, I have the timestamps, we can speed up or slow down the audio, it's not a big deal. And we've done that and this was one of the most profitable features ever. Like a very small percentage of the users need it, but those that need it produce hundreds of thousands of audio files because they translate the corporate training videos. And now, you know, we're getting into that numbers game. If I said, you know, there's like 0 .1 % of people are uploading subtitle files. Brian (30:58) Yeah. Gojko (31:07) then it doesn't matter. if we start thinking about, this is potentially interesting use case, it creates growth on its own because then people find you. And I think my product was the first that was actually doing synchronous subtitles. Competitors are doing it now as well. But it opened the massive, massive market for us. And people, you know, I got there by monitoring user errors, by, you know, the fact that somebody uploaded a file that had an unsupported extension. That was our insight. Brian (31:38) Wow, that's really cool. That's a great story. This is fascinating stuff. And it makes me want to dive deeper into the book and read through it again. But I really appreciate you coming on and sharing this with us, Goiko. This is good stuff. Again, the book is called, Lizard Optimization, Unlock Product Growth by Engaging Long Tail Users. And if I'm right, we talked about this a little bit before. We're going to offer a discount to to the listeners, Gojko (32:07) Yes, we will give you a listen as a 50 % discount on the ebook. the ebook is available from Lean Pub. If you get it from the discount URL that I'll give you, then you'll get a 50 % discount immediately. Brian (32:24) Awesome. So we'll put that in our show notes. If you're interested in that, you can find the show notes. That's a great deal, 50 % off the book and it's good stuff. well, I just, I can't thank you enough. Thanks for making time and coming on and talking this through your book. Gojko (32:40) Thank you, it was lovely to chat to you.
We are so glad you joined us to help you start your new year! This episode's guest is Matthew Rathbun. Matthew will be discussing business suggestions, strategies, and ideas to help you make your plans for success in 2024. This is the first part of a series on Business Planning with Matthew this month. The second part will launch later this month. [2:55] Matthew is the EVP of a Coldwell Banker company with 10 or 11 offices in the D.C.-Maryland-Virginia area. [3:40] Matthew started teaching and has been teaching ever since. He is currently the president-elect for the Real Estate Business Institute, a good partner for CRD, providing lots of education to agents. [4:20] There has been attrition in the industry. A lot of agents are not seeing a lot of production right now. When you plan for next year, you have to base it on reality. [5:33] We are knowledge workers more than salespeople. The buyer hires you as a buyer's agent for what you know. How do you provide clarity on your value as a buyer's agent? [7:00] A knowledge worker will say, “I know the market, what my capabilities are, and what my consumer base is and I'm going to build a strategic plan.” [7:37] You can be a knowledge worker to your consumers and demonstrate that value to them. You can use your knowledge and say, “I'm the CEO of me.” [9:21] What are we changing for 2024? Agents need to be much more precise with their goals to be able to look back and see what they've accomplished and why this is a good career for them. [11:12] Matthew goes over tips and tools on how to interject your goals. Substantial industry changes are coming but most of our chaos is controllable. [13:00] You're controlling whatever chaos you can. Putting systems in place is so important. “You do not rise to the level of your goals, you fall to the level of your systems.” — James Clear [15:48] With industry changes, Matthew says training will be a core part of any successful agent's business. [18:33]. Change is good. A bad change can be corrected to something better. Have a healthy mindset on addressing change. Lean into change and what it means. [23:06] It's time to add to your listing kit and improve the buyer consultation kit on your website. Market your value proposition for buyers. Matthew discusses what to do in the next 30 to 90 days. [25:45] Agents need a better consumer persona. Who do you want to work with? Just saying you want to work with sellers or with buyers is not focused enough to reach the core consumer that you want. [30:18] Matthew cites Atomic Habits, by James Clear as the most transformative book. He recommends other books. [32:50] Monica urges you to check the resources mentioned in this episode and Matthew Rathbun's website linked in the notes. What education do you need to add to your life and business? The Center for REALTOR® development highly recommends ABR®, The Accredited Buyer's Representative designation. Tweetables: “This is very much an industry where you get to eat what you kill. You hunt it. You kill it. Now you get to enjoy it, so to speak.” — Matthew Rathbun “Change is good. I've always said change is good. Even if it's bad change, it's generally going to be corrected and lead to something that's better.” — Matthew Rathbun “Every successful CEO is a reader. That's one of the common traits of all successful CEOs.” — Matthew Rathbun Guest Links:Matthew Rathbun on Facebook Canva Templates at Etsy.com NARRPR.com REALTOR® Property Resource Building a StoryBrand: Clarify Your Message So Customers Will Listen, by Donald Miller Atomic Habits: An Easy & Proven Way to Build Good Habits & Break Bad Ones, by James Clear Building a Second Brain: A Proven Method to Organize Your Digital Life and Unlock Your Creative Potential, by Tiago Forte Getting Things Done: The Art of Stress-Free Productivity, by David Allen Canva.com Alignment.io Trello.com MyStorybrand.com Freeform – app for iPads and iPhones only MindMup.com Coffitivity.com Matthewrathbun.com/resources/ NAR Resource LinksNAR.realtor/technologyABR® SRS Additional Links: Microcourses found at Learning.REALTOR. Use the coupon code PODCAST to obtain 15% off the price of any microcourse! CRD@NAR.REALTOR Crdpodcast.REALTOR Learning.REALTOR — for NAR Online Education Training4RE.com — List of Classroom Courses from NAR and its affiliates CRD.REALTOR — List of all courses offered REBI Host Information: Monica Neubauer Speaker/Podcaster/REALTOR® Monica@MonicaNeubauer.com MonicaNeubauer.com FranklinTNBlog.com Monica's Facebook Page: Facebook.com/Monica.Neubauer Instagram: Instagram.com/MonicaNeubauerSpeaks Guest Bio Matthew Rathbun I'm unapologetically me. I love learning and sharing what I've learned with anyone willing to listen. It's what I've done all of my life. I'm a restless and demanding learner myself, so I focus on people in the audience who want advanced information, a little humor, and actionable information when they leave. If a learner attends one of my sessions, I feel honored to have them there and feel that I have a duty to ensure that the time they have given me will be valuable to them. I believe that every moment with learners should count. I still work with clients and actually practice the skills and information that I deliver in each class. I'm also a licensed broker in Virginia, DC, and Maryland and a licensed instructor in many states in the U.S. I am the Executive Vice President of a large multi-office firm in Virginia and oversee operations, risk management, and agent development among other things. Before becoming a broker, I was a high-performing agent and received a number of awards and accolades throughout the year including the Virginia Association Instructor of the Year, and was recognized by RISMedia Newsmaker Thought Leader in 2020. My course offerings are pretty extensive and I'm always happy to create unique content if it's within my knowledge base. I'm a certified CRS instructor and have contributed to or written various national certification and designation courses for RRC, REBAC, and REBI (all three NAR education institutes). My emphasis is on leadership development, technology, risk management, and advanced practice of real estate. I have a wide range of experience with risk reduction, including serving on the local, state, and national professional standards workgroups, MLS compliance committees, and various other industry opportunities that have given me broad exposure to what should be the best practices in the industry. I am an alumnus of the VAR Leadership Academy. As an author, I have contributed to many real estate industry magazines and online industry news venues. A few accolades: ■ REBI National Distinguished Instructor of the Year 2021 ■ CRS National Instructor of the Year 2020 ■ Virginia Association of REALTORS® — Instructor of the Year 2007 ■ RISMedia Newsmaker — 2020 Influencer ■ Virginia REALTORS® Graduate — Leadership Academy — 2007 ■ Fredericksburg Assoc. of REALTORS® — Realtor of the Year 2020 ■ Fredericksburg Assoc. of REALTORS® — President's Award 2010 ■ Fredericksburg Assoc. of REALTORS® — Code of Ethics Award 2011 ■ Fredericksburg Assoc. of REALTORS® — Rookie of the Year 2003 ■ Fredericksburg Assoc. of REALTORS® — Honor “Role” ■ Fredericksburg Assoc. of REALTORS® — Production Awards ■ Coldwell Banker Recruiter Award — Virginia
PMとして大規模開発の苦労など MTG ドキュメント スケジュール管理 Mind Mup Kids Connect Kids Connect Kids Connectではエンジニアを募集しています
Cette semaine, nous avons croisé une antilope qui courait très vite dans notre jungle ! Nous avons invité Anne Ambrosini qui a eu la gentillesse de nous présenter l'intérêt du mind mapping (cartes mentales) en formation et plus particulièrement l'outil mindmup accessible à tous, 100% en ligne, gratuit et surtout collaboratif. Les usages pédagogiques de mindmup sont très nombreux: en amont d'une formation pour répondre à un cahier des charges et faire une analyse de la demande, pour préparer des scripts de vidéos pédagogiques; pendant la formation en réveil pédagogique, en synthèse ou fiche mémo; après la formation en évaluation ou en ancrage en laissant la main aux participants pour faire leur plan d'actions
About Gojko AdzicGojko Adzic is a partner at Neuri Consulting LLP. He one of the 2019 AWS Serverless Heroes, the winner of the 2016 European Software Testing Outstanding Achievement Award, and the 2011 Most Influential Agile Testing Professional Award. Gojko’s book Specification by Example won the Jolt Award for the best book of 2012, and his blog won the UK Agile Award for the best online publication in 2010.Gojko is a frequent speaker at software development conferences and one of the authors of MindMup and Narakeet.As a consultant, Gojko has helped companies around the world improve their software delivery, from some of the largest financial institutions to small innovative startups. Gojko specializes in agile and lean quality improvement, in particular impact mapping, agile testing, specification by example, and behavior driven development.Twitter: @gojkoadzicNarakeet: https://www.narakeet.comPersonal website: https://gojko.netWatch this video on YouTube: https://youtu.be/kCDDli7uzn8This episode is sponsored by CBT Nuggets: https://www.cbtnuggets.com/TranscriptJeremy: Hi everyone, I'm Jeremy Daly and this is Serverless Chats. Today my guest is Gojko Adzic. Hey Gojko, thanks for joining me.Gojko: Hey, thanks for inviting me.Jeremy: You are a partner at Neuri Consulting, you're an AWS Serverless Hero, you've written I think, what? I think 6,842 books or something like that about technology and serverless and all that kind of stuff. I'd love it if you could tell listeners a little bit about your background and what you've been working on lately.Gojko: I'm a developer. I started developing software when I was six and a half. My dad bought a Commodore 64 and I think my mom would have kicked him out of the house if he told her that he bought it for himself, so it was officially for me.Jeremy: Nice.Gojko: And I was the only kid in the neighborhood that had a computer, but didn't have any ways of loading games on it because he didn't buy it for games. I stayed up and copied and pasted PEEKs and POKEs in a book I couldn't even understand until I made the computer make weird sounds and print rubbish on the screen. And that's my background. Basically, ever since, I only wanted to build software really. I didn't have any other hobbies or anything like that. Currently, I'm building a product for helping tech people who are not video editing professionals create videos very easily. Previously, I've done a lot of work around consulting. I've built a lot of product that is used by millions of school children worldwide collaborate and brainstorm through mind-mapping. And since 2016, most of my development work has been on Lambda and on team stuff.Jeremy: That's awesome. I joke a little bit about the number of books that you wrote, but the ones that you have, one of them's called Running Serverless. I think that was maybe two years ago. That is an excellent book for people getting started with serverless. And then, one of my probably favorite books is Humans Vs Computers. I just love that collection of tales of all these things where humans just build really bad interfaces into software and just things go terribly.Gojko: Thank you very much. I enjoyed writing that book a lot. One of my passions is finding edge cases. I think people with a slight OCD like to find edge cases and in order to be a good developer, I think somebody really needs to have that kind of intent, and really look for edge cases everywhere. And I think collecting these things was my idea to help people first of all think about building better software, and to realize that stuff we might glance over like, nobody's ever going to do this, actually might cause hundreds of millions of dollars of damage ten years later. And thanks very much for liking the book.Jeremy: If people haven't read that book, I don't know, when did that come out? Maybe 2016? 2015?Gojko: Yeah, five or six years ago, I think.Jeremy: Yeah. It's still completely relevant now though and there's just so many great examples in there, and I don't want to spent the whole time talking about that book, but if you haven't read it, go check it out because it's these crazy things like police officers entering in no plates whenever they're giving parking tickets. And then, when somebody actually gets that, ends up with thousands of parking tickets, and it's just crazy stuff like that. Or, not using the middle initial or something like that for the name, or the birthdate or whatever it was, and people constantly getting just ... It's a fascinating book. Definitely check that out.But speaking of edge cases and just all this experience that you have just dealing with this idea of, I guess finding the problems with software. Or maybe even better, I guess a good way to put it is finding the limitations that we build into software mostly unknowingly. We do this unknowingly. And you and I were having a conversation the other day and we were talking about way, way back in the 1970s. I was born in the late '70s. I'm old but hopefully not that old. But way back then, time-sharing was a thing where we would basically have just a few large computers and we would have to borrow time against them. And there's a parallel there to what we were doing back then and I think what we're doing now with cloud computing. What are your thoughts on that?Gojko: Yeah, I think absolutely. We are I think going in a slightly cyclic way here. Maybe not cyclic, maybe spirals. We came to the same horizontal position but vertically, we're slightly better than we were. Again, I didn't start working then. I'm like you, I was born in late '70s. I wasn't there when people were doing punch cards and massive mainframes and time-sharing. My first experience came from home PC computers and later PCs. The whole serverless thing, people were disparaging about that when the marketing buzzword came around. I don't remember exactly when serverless became serverless because we were talking about microservices and Lambda was a way to run microservices and execute code on demand. And all of a sudden, I think the JAWS people realized that JAWS is a horrible marketing name, and decided to rename it to serverless. I think it most important, and it was probably 2017 or something like that. 2000 ...Jeremy: Something like that, yeah.Gojko: Something like that. And then, because it is a horrible marketing name, but it's catchy, it caught on and then people were complaining how it's not serverless, it's just somebody else's servers. And I think there's some truth to that, but actually, it's not even somebody else's servers. It really is somebody else's mainframe in a sense. You know in the '70s and early '80s, before the PC revolution, if you wanted to be a small software house or a small product operator, you probably were not running your own data center. What you would do is you would rent it based on paying for time to one of these massive, massive, massive operators. And in fact, we ended up with AWS being a massive data center. As far as you and I are concerned, it's just a blob. It's not a collection of computers, it's a data center we learn something from and Google is another one and then Microsoft is another one.And I remember reading a book about Andy Grove who was the CEO of Intel where they were thinking about the market for PC computers in the late '70s when somebody came to them with the idea that they could repurpose what became a 8080 processor. They were doing this I think for some Japanese calculator and then somebody said, "We can attach a screen to this and make this a universal computer and sell it." And they realized maybe there's a market for four or five computers in the world like that. And I think that that's ... You know, we ended up with four or five computers, it's just the definition of a computer changed.Jeremy: Right. I think that's a good point because you think about after the PC revolution, once the web started becoming really big, people started building data centers and collocation facilities like crazy. This is way before the cloud, and everybody was buying racks and Dell was getting really popular because people buying servers from Dell, and installing these in their data centers and doing this. And it just became this massive, whole industry built around doing that. And then you have these few companies that say, "Well, what if we just handled all that stuff for you? Rather than just racking stuff for you," but started just managing the software, and started managing the networking, and the backups, and all this stuff for you? And that's where the cloud was born.But I think you make a really good point where the cloud, whatever it is, Amazon or Google or whatever, you might as well just assume that that's just one big piece of processing that you're renting and you're renting some piece of that. And maybe we have. Maybe we've moved back to this idea where ... Even though everybody's got a massive computer in their pocket now, tons of compute power, in terms of the real business work that's being done, and the real global value, and the things that are powering global commerce and everything else like that, those are starting to move back to run in four, five, massive computers.Gojko: Again, there's a cyclic nature to all of this. I remember reading about the advent of power networks. Because before people had electric power, there were physical machines and movement through physical power, and there were water-powered plants and things like that. And these whole systems of shafts and belts and things like that powering factories. And you had this one kind of power load in a factory that was somewhere in the middle, and then from there, you actually have physical belts, rotating cogs in other buildings, and that was rotating some shafts that were rotating other cogs, and things like that.First of all, when people were able to package up electricity into something that's distributable, and they were running their own small electricity generators next to these big massive machines that were affecting early factories. And one of the first effects of that was they could reuse 30% of their factories better because it was up to 30% of the workspace in the factory that was taken up by all the belts and shafts. And all that movement was producing a lot of air movement and a lot of dust and people were getting sick. But now, you just plug a cable and you no longer have all this bad air and you don't have employees going sick and things like that. Things started changing quite a lot and then all of a sudden, you had this completely new revolution where you no longer had to operate your own electric generator. You could just plug in and get power from the network.And I think part of that is again, cyclic, what's happening in our industry now, where, as you said, we were getting machines. I used to make money as a Linux admin a long time ago and I could set up my own servers and things like that. I had a company in 2007 where we were operating our own gaming system, and we actually had physical servers in a physical server room with all the LEDs and lights, and bleeps, and things like that. Around that time, AWS really made it easy to get virtual machines on EC2 and I realized how stupid the whole, let's manage everything ourself is. But, we are getting to the point where people had to run their own generators, and now you can actually just plug into the electricity network. And of course, there is some standardization. Maybe U.S. still has 110 volts and Europe has 220, and we never really get global standardization there.But I assume before that, every factory could run their own voltage they wanted. It was difficult to manufacture for these things but now you have standardization, it's easier for everybody to plug into the ecosystem and then the whole ecosystem emerged. And I think that's partially what's happening now where things like S3 is an API or Lambda is an API. It's basically the electric socket in your wall.Jeremy: Right, and that's that whole Wardley maps idea, they become utilities. And that's the thing where if you look at that from an enterprise standpoint or from a small business standpoint if you're a startup right now and you are ordering servers to put into a data center somewhere unless you're doing something that's specifically for servers, that's just crazy. Use the cloud.Gojko: This product I mentioned that we built for mind mapping, there's only two of us in the whole company. We do everything from presales, to development testing supports, to everything. And we're competing with companies that have several orders of magnitude more employees, and we can actually compete and win because we can benefit from this ecosystem. And I think this is totally wonderful and amazing and for anybody thinking about starting a product, it's easier to start a product now than ever. And, another thing that's totally I think crazy about this whole serverless thing is how in effect we got a bookstore to offer that first.You mentioned the world utility. I remember I was the editor of a magazine in 2001 in Serbia, and we had licensing with IDG to translate some of their content. And I remember working on this kind of piece from I think PC World in the U.S. where they were interviewing Hewlett Packard people about utility computing. And people from Hewlett Packard back then were predicting that in a few years' time, companies would not operate their own stuff, they would use utility and things like that. And it's totally amazing that in order to reach us over there, that had to be something that was already evaluated and tested, and there was probably a prototype and things like that. And you had all these giants. Hewlett Packard in 2001 was an IT giant. Amazon was just up-and-coming then and they were a bookstore then. They were not even anything more than a bookstore. And you had, what? A decade later, the tables completely turned where HP's ... I don't know ...Jeremy: I think they bought Compaq at some point too.Gojko: You had all these giants, IBM completely missed it. IBM totally missed ...Jeremy: It really did.Gojko: ... the whole mobile and web and everything revolution. Oracle completely missed it. They're trying to catch up now but fat chance. Really, we are down to just a couple of massive clouds, or whatever that means, that we interact with as we're interacting with electricity sockets now.Jeremy: And going back to that utility comparison, or, not really a comparison. It is a utility now. Compute is offered as a utility. Yes, you can buy and generate compute yourself and you can still do that. And I know a lot of enterprises still will. I think cloud is like 4% of the total IT market or something. It's a fraction of it right now. But just from that utility aspect of it, from your experience, you mentioned you had two people and you built, is it MindMup.com?Gojko: MindMup, yeah.Jeremy: You built that with just two people and you've got tons of people using it. But just from your experience, especially coming from the world of being a Linux administrator, which again, I didn't administer ... Well, I guess I was. I did a lot of work in data centers in my younger days. But, coming from that idea and seeing how companies were building in the past and how companies are still building now, because not every company is still using the cloud, far from it. But not taking advantage of that utility, what are those major disadvantages? How badly do you think that's going to slow companies down that are trying to innovate?Gojko: I can give you a story about MindMup. You mentioned MindMup. When was it? 2018, there was the Intel processor vulnerabilities that were discovered.Jeremy: Right, yes.Gojko: I'm not entirely sure what the year was. A few years ago anyway. We got a email from a concerned university admin when the second one was discovered. The first one made all the news and a month later a second one was discovered. Now everybody knew that, they were in panic and things like that. After the second one was discovered, we got a email from a university admin. And universities are big users, they need to protect the data and things like that. And he was insisting that we tell him what our plan was for mitigating this thing because he knows we're on the cloud.I'm working on European time. The customer was in the U.S., probably somewhere U.S. Pacific because it arrived in the middle of the night. I woke up, I'm still trying to get my head around and drinking coffee and there's this whole sausage CV number that he sent me. I have no idea what it's about. I took that, pasted it into Google to figure out what's going on. The first result I got from Google was that AWS Lambda was already patched. Copy, paste, my day's done. And I assume lots and lots of other people were having a totally different conversation with their IT department that day. And that's why I said I think for products like the one I'm building with video and for the MindMup, being able to rent operations as a utility, but really totally rent ops as a utility, not have to worry about anything below my unique business level is really, really important.And yes, we can hire people to work on that it could even end up being slightly cheaper technically but in terms of my time and where my focus goes and my interruptions, I think deploying on a utility platform, whatever that utility platform is, as long as it's reliable, lets me focus on adding value where I can actually add value. That makes my product unique rather than the generic stuff.Jeremy: You mentioned the video product that you're working on too, and something that is really interesting I think too about taking advantage of the cloud is the scalability aspect of it. I remember, it was maybe 2002, maybe 2003, I was running my own little consulting company at the time, and my local high school always has a rivalry football game every Thanksgiving. And I thought it'd be really interesting if I was to stream the audio from the local AM radio station. I set up a server in my office with ReelCast Streaming or something running or whatever it was. And I remember thinking as long as we don't go over 140 subscribers, we'll be okay. Anything over that, it'll probably crash or the bandwidth won't be enough or whatever.Gojko: And that's just one of those things now, if you're doing any type of massive processing or you need bandwidth, bandwidth alone ... I remember T1 lines being great and then all of a sudden it was like, well, now you need a T3 line or something crazy in order to get the bandwidth that you need. Just from that aspect of it, the ability to scale quickly, that just seems like such a huge blocker for companies that need to order provision servers, maybe get a utility company to come in and install more bandwidth for them, and things like that. That's just stuff that's so far out of scope for building a business to me. At least building a software business or building any business. It's crazy.When I was doing consulting, I did a bit of work for what used to be one of the largest telecom companies in the world.Jeremy: Used to be.Gojko: I don't want to name names on a public chat. Somewhere around 2006, '07 let's say, we did a software project where they just needed to deploy it internally. And it took them seven months to provision a bunch of virtual machines to deploy it internally. Seven months.Jeremy: Wow.Gojko: Because of all the red tape and all the bureaucracy and all the wait for capacity and things like that. That's around the time where Amazon when EC2 became commercially available. I remember working with another client and they were waiting for some servers to arrive so they can install more capacity. And I remember just turning on the Amazon console. I didn't have anything useful to running it then but just being able to start up a virtual machine in about, I think it was less than half an hour, but that was totally fascinating back then. Here's a new Linux machine and in less than half an hour, you can use it. And it was totally crazy. Now we're getting to the point where Lambda will start up in less than 10 milliseconds or something like that. Waiting for that kind of capacity is just insane.With the video thing I'm building, because of Corona and all of this remote teaching stuff, for some reason, we ended up getting lots of teachers using the product. It was one of these half-baked experiments because I didn't have time to build the full user interface for everything, and I realized that lots of people are using PowerPoint to prepare that kind of video. I thought well, how about if I shorten that loop, so just take your PowerPoint and convert it into video. Just type up what you want in the speaker notes, and we'll use these neurometrics to generate audio and things like that. Teachers like it for one reason or the other.We had this influential blogger from Russia explain it on his video blog and then it got picked up, my best guess from what I could see from Google Translate, some virtual meeting of teachers of Russia where they recommended people to try it out. I woke up the next day, the metrics went totally crazy because a significant portion of teachers in Russia tried my tool overnight in a short space of time. Something like that, I couldn't predict it. It's lovely but as you said, as long as we don't go over a hundred subscribers, we're fine. If I was in a situation like that, the thing would completely crash because it's unexpected. We'd have a thing that's amazingly good for marketing that would be amazingly bad for business because it would crash all our capacity we had. Or we had to prepare for a lot more capacity than we needed, but because this is all running on Lambda, Fargate, and other auto-scaling things, it's just fine. No sweat at all. It was a lovely thing to see actually.Jeremy: You actually have two problems there. If you're not running in the cloud or not running on-demand compute, is the fact that one, you would've potentially failed, things would've fallen over and you would've lost all those potential customers, and you wouldn't have been able to grow.Gojko: Plus you've lost paying customers who are using your systems, who've paid you.Jeremy: Right, that's the other thing too. But, on the other side of that problem would be you can't necessarily anticipate some of those things. What do you do? Over-provision and just hope that maybe someday you'll get whatever? That's the crazy thing where the elasticity piece of the cloud to me, is such a no-brainer. Because I know people always talk about, well, if you have predictable workloads. Well yeah, I know we have predictable workloads for some things, but if you're a startup or you're a business that has like ... Maybe you'd pick up some press. I worked for a company that we picked up some press. We had 10,000 signups in a matter of like 30 seconds and it completely killed our backend, my SQL database. Those are hard to prepare for if you're hosting your own equipment.Gojko: Absolutely, not even if you're hosting your own.Jeremy: Also true, right.Gojko: Before moving to Lambda, the app was deployed to Heroku. That was basically, you need to predict how many virtual machines you need. Yes, it's in the cloud, but if you're running on EC2 and you have your 10, 50, 100 virtual machines, whatever running there, and all of a sudden you get a lot more traffic, will it scale or will it not scale? Have you designed it to scale like that? And one of the best things that I think Lambda brought as a constraint was forcing people to design this stuff in a way that scales.Jeremy: Yes.Gojko: I can deploy stuff in the cloud and make it all distributed monolith, so it doesn't really scale well, but with Lambda because it was so constrained when it launched, and this is one thing you mentioned, partially we're losing those constraints now, but it was so constrained when it launched, it was really forcing people to design things that were easy to scale. We had total isolation, there was no way of sharing things, there was no session stickiness and things like that. And then you have to come up with actually good ways of resolving that.I think one of the most challenging things about serverless is that even a Hello World is a distributed transaction processing system, and people don't get that. They think about, well, I had this DigitalOcean five-dollar-a-month server and it was running my, you know, Rails up correctly. I'm just going to use the same ideas to redesign it in Lambda. Yes, you can, but then you're not going to really get the benefits of all of this other stuff. And if you design it as a massively distributed transaction processing system from the start, then yes, it scales like crazy. And it scales up and down and it's lovely, but as Lambda's maturing, I have this slide deck that I've been using since 2016 to talk about Lambda at conferences. And every time I need to do another talk, I pull it out and adjust it a bit. And I have this whole Git history of it because I do markdown to slides and I keep the markdown in Git so I can go back. There's this slide about limitations where originally it's only ... I don't remember what was the time limitation, but something very short.Jeremy: Five minutes originally.Gojko: Yeah, something like that and then it was no PCI compliance and the retries are difficult, and all of this stuff basically became sold. And one of the last things that was there, there was don't even try to put it in a VPC, definitely, you can but it's going to take 10 minutes to start. Now that's reasonably okay as well. One thing that I remember as a really important design constraint was effectively it was a share nothing platform because you could not share data between two Lambdas running at the same time very easily in the same VM. Now that we can connect Lambdas to EFS, you effectively can do that as well. You can have two Lambdas, one writing into an EFS, the other reading the same EFS at the same time. No problem at all. You can pump it into a file and the other thing can just stay in a file and get the data out.As the platform is maturing, I think we're losing some of these design constraints, and sometimes constraints breed creativity. And yes, you still of course can design the system to be good, but it's going to be interesting to see. And this 15-minute limit that we have in Lamdba now is just an artificial number that somebody thought.Jeremy: Yeah, it's arbitrary.Gojko: And at some point when somebody who is important enough asks AWS to give them half-hour Lamdbas, they will get that. Or 24-hour Lambdas. It's going to be interesting to see if Lambda ends up as just another way of running EC2 and starting EC2 that's simpler because you don't have to manage the operating system. And I think the big difference we'll get between EC2 and Lambda is what percentage of ops your developers are responsible for, and what percentage of ops Amazon's developers are responsible for.Because if you look at all these different offerings that Amazon has like Lightsail and EC2 and Fargate and AWS Batch and CodeDeploy, and I don't know how many other things you can run code on in Lambda. The big difference with Lambda is really, at least until very recently was that apart from your application, Amazon is responsible for everything. But now, we're losing design constraints, you can put a Docker container in, you can be responsible for the OS image as well, which is a bit again, interesting to look at.Jeremy: Well, I also wonder too, if you took all those event sources that you can point at Lambda and you add those to Fargate, what's the difference? It seems like they're just merging into two very similar products.Gojko: For the video build platform, the last step runs in Fargate because people are uploading things that are massive, massive, massive for video processing, and just they don't finish in 15 minutes. I have to run to Fargate, and the big difference is the container I packaged up for Fargate takes about 40 seconds to actually deploy. A new event at the moment with the stuff I've packaged in Fargate takes about 40 seconds to deploy. I can optimize that, but I can't optimize it too much. Fargate is still order of magnitude of tens of seconds to process an event. I think as Fargate gets faster and as Lambda gets more of these capabilities, it's going to be very difficult to tell them apart I think.With Fargate, you're intended to manage the container image yourself. You're responsible for patching software, you're responsible for patching OS vulnerabilities and things like that. With Lambda, Amazon, unless you use a container image, Amazon is responsible for that. They come close. When looking at this video building for the first time, I was actually comparing code. I was considering using CodeBuild for that because CodeBuild is also a way to run things on demand and containers, and you actually can get quite decent machines with CodeBuild. And it's also event-driven, and Fargate is event-driven, AWS Batch is event-driven, and all of these things are converging to each other. And really, AWS is famous for having 10 products that do the same thing effectively and you can't tell them apart, and maybe that's where we'll end.Jeremy: And I'm wondering too, the thing that was great about Lambda, at least for me like you said, the shared nothing architecture where it was like, you almost didn't have to rely on anything other than the event that came in, and the processing of that Lambda function. And if you designed your systems well, you may have some bottleneck up front, but especially if you used distributed transactions and you used async invocations of downstream functions, where you could basically take some data that you needed to pass into it, and then you wouldn't necessarily need that to communicate with anything other than itself to process that data. The scale there was massive. You could just keep scaling and scaling and scaling. As you add things like EFS and that adds constraints in terms of the number of transactions and connections that, that can make and all those sort of things. Do these things, do they become less reliable? By allowing it to do more, are we building systems that are less reliable because we're not using some of those tried-and-true constraints that were there?Gojko: Possibly, but every time you add a new moving part, you create one more potential point of failure there. And I think for me, one of the big lessons when I was working on ... I spent a few years working on very high throughput transaction processing systems. That's why this whole thing rings a bell a lot. A lot of it really was how do you figure out what type of messages you send and where you send them. The craze of these messages and distributed transaction processing systems in early 2000s, created this whole craze of enterprise service buses later that came. We now have this... What is it called? It's not called enterprise service bus, it's called EventBridge, or something like that.Jeremy: EventBridge, yes.Gojko: That's effectively an enterprise service bus, it's just the enterprise is the Amazon cloud. The big challenge in designing things like that is decoupling. And it's realizing that when you have a complicated system like that, stuff is going to fail. And especially when we were operating around hardware, stuff is going to fail badly or occasionally, and you need to not bring the whole house down where some storage starts working a bit slower. You create circuit breakers, you create layers and layers of stuff that disconnect things. I remember when we were looking originally at Lambdas and trying to get the head around that and experimenting, should one Lambda call another? Or should one Lambda not call another? And things like that.I realized, let's say for now, until we realize we want to do something else, a Lambda should only ever talk to SNS and nothing else. Or SQS or something like that. When one Lambda completes, it's going to track a message somewhere and we need to design these messages to be good so that we can decouple different parts of the process. And so far, that helps too as a constraint. I think very, very few times we have one Lambda calling another. Mostly when we actually need a synchronized response back, and for security reasons, we wanted to isolate something to a single Lambda, but that's effectively just a black box security isolation. Since creating these isolation layers through messages, through queues, through topics, becomes a fundamental part of designing these systems.I remember speaking at the conference to somebody. I forgot the name of the person who was talking about airline. And he was presenting after me and he said, "Look, I can relate to a lot of what you said." And in the airline community basically they often talk about, apparently, I'm not an airline programmer, he told me that in the airline community, talk about designing the protocol being the biggest challenge. Once you design the protocol between your components, the message is who sends what where, you can recover from almost any other design flaw because it's decoupled so if you've made a mess in one Lambda, you can redesign that Lambda, throw it away, rewrite it, decouple things a different way. If the global protocol is good, you get all the flexibility. If you mess up the protocol for communication, then nothing's going to save you at the end.Now we have EFS and Lambda can talk to an EFS. Should this Lambda talk directly to an EFS or should this Lambda just send some messages to a topic, and then some other Lambdas that are maybe reserved, maybe more constrained talk to EFS? And again, the platform's evolved quite a lot over the last few years. One thing that is particularly useful in that regard is the SQS FIFO queues that came out last year I think. With Corona ...Jeremy: Yeah, whenever it was.Gojko: Yeah, I don't remember if it was last year or two years ago. But one of the things it allows us to do is really run lots and lots of Lambdas in parallel where you can guarantee that no two Lambdas access the same kind of business entity that you have in the same type. For example, for this mind mapping thing, we have lots and lots of people modifying lots and lots of files in parallel, but we need to aggregate a single map. If we have 50 people over here working with a single map and 60 people on a map working a different map, aggregation can run in parallel but I never ever, ever want two people modifying the same map their aggregation to run in parallel.And for Lambda, that was a massive challenge. You had to put Kinesis between Lambda and other Lambdas and things like that. Kinesis' provision capacity, it costs a lot, it doesn't auto-scale. But now with SQS FIFO queues, you can just send a message and you can say the kind of FIFO ID is this map ID that we have. Which means that SQS can run thousands of Lambdas in parallel but they'll never run more than one Lambda for the same map idea at the same time. Designing your protocols like that becomes how you decouple one end of your app that's massively scalable and massively parallel, and another end of your app that we have some reserved capacity or limits.Like for this kind of video thing, the original idea of that was letting me build marketing videos easier and I can't get rid of this accent. Unfortunately, everything I do sounds like I'm threatening someone to blackmail them. I'm like a cheap Bond villain, and that's not good, but I can't do anything else. I can pay other people to do it for me and we used to do that, but then that becomes a big problem when you want to modify tiny things. We paid this lady to professionally record audio for a marketing video that we needed and then six months later, we wanted to change one screen and now the narration is incorrect. And we paid the same woman again. Same equipment, same person, but the sound is totally different because two different equipment.Jeremy: Totally different, right.Gojko: You can't just stitch it up. Then you end up like, okay, do we go and pay for the whole thing again? And I realized the neurometric text-to-speech has learned so much that it can do English better than I can. You're a native English speaker so you can probably defeat those machines, but I can't.Jeremy: I don't know if I could. They're pretty good now. It's kind of scary.Gojko: I started looking at one like why don't they just put stuff in a Markdown and use Markdown to generate videos and things like that? All of these things, you get quota limits still. I thought we were limited on Google. Google gave us something like five requests per second in parallel, and it took me a really long time to even raise these quotas and things like that. I don't want to have lots of people requesting stuff and then in parallel trashing this other thing over there. We need to create these layers of running things in a decent limit, and I think that's where I think designing the protocol for this distributed system becomes an importance.Jeremy: I want to go back because I think you bring up a really good point just about a different type of architecture, or the architectural design of decoupling systems and these event-driven things. You mentioned a Lambda function processes something and sends it to SQS or sends it to SNS to it can do a fan-out pattern or in the case of the FIFO queue, doing an ordered pattern for sequential processing, which those were all great patterns. And even things that AWS has done, such as add things like Lambda destination. Now if you run an asynchronous Lambda function, you still have to write some code or you used to have to write some code that said, "When this is finished processing, now call some other component." And there's just another opportunity for failure there. They basically said, "Well, if it succeeds, then you can actually just forward it off to one of these other services automatically and we'll handle all of the retries and all the failures and that kind of stuff."And those things have been added in to basically give you that warm and fuzzy feeling that if an event doesn't reach where it's supposed to go, that some sort of cloud trickery will kick in and make sure that gets processed. But what that is introduced I think is a cognitive overload for a lot of developers that are designing these systems because you're no longer just writing a script that does X, Y, and Z and makes a few database calls. Now you're saying, okay, I've got to write a script that can massively scale and take the transactions that I need to maybe parallelize or that I maybe need to queue or delay or throttle or whatever, and pass those down to another subsystem. And then that subsystem has to pick those up and maybe that has to parallelize those or maybe there are failure modes in there and I've got all these other things that I have to think about.Just that effect on your average developer, I think you and I think about these things. I would consider myself to be a cloud architect, if that's a thing. But essentially, do you see this being I guess a wall for a lot of developers and something that really requires quite a bit of education to ramp them up to be able to start designing these systems?Gojko: One of the topics we touched upon is the cyclic nature of things, and I think we're going back to where moving from apps working on a single machine to client server architectures was a massive brain melt for a lot of people, and three-tier architectures, which is later, we're not just client server, but three-tier architectures ended up with their own host of problems and then design problems and things like that. That's where a lot of these architectural patterns and design patterns emerged like circuit breakers and things like that. I think there's a whole body of knowledge there for people to research. It's not something that's entirely new and I think you can get started with Lambda quite easily and not necessarily make a mess, but make something that won't necessarily scale well and then start improving it later.That's why I was mentioning that earlier in the discussion where, as long as the protocol makes sense, you can salvage almost anything late. Designing that protocol is important, but then we're going to good software design. I think teaching people how to do that is something that every 10 years, we have to recycle and reinvent and figure it out because people don't like to read books from more than 10 years ago. All of this stuff like designing fault tolerance systems and fail-safe systems, and things like that. There's a ton of books about that from 20 years ago, from 10 years ago. Amazon, for people listening to you and me, they probably use Amazon more for compute than they use for getting books. But Amazon has all these books. Use it for what Amazon was originally intended for and then get some books there and read through this stuff. And I think looking at design of distributed systems and stuff like that becomes really, really critical for Lambdas.Jeremy: Yeah, definitely. All right, we've got a few minutes left and I'd love to go back to something we were talking about a little bit earlier and that was everything moving onto a few of these major cloud providers. And one of the things, you've got scale. Scale is a problem when we talked about oh, we can spin up as many VMs as we want to, and now with serverless, we have unlimited capacity really. I know we didn't say that, but I think that's the general idea. The cloud just provides this unlimited capacity.Gojko: Until something else decides it's not unlimited.Jeremy: And that's my point here where every major cloud provider that I've been involved with and I've heard the stories of, where you start to move the needle at all, there's always an SA that reaches out to you and really wants to understand what your usage is going to be, and what your patterns were going to be. And that's because they need to make sure that where you're running your applications, that they provision enough capacity because there is not enough capacity, or there's not unlimited capacity in the cloud.Gojko: It's physically limited. There's only so much buildings where you can have data centers on the surface of Earth.Jeremy: And I guess that's where my question comes in because you always hear these things about lock-in. Like, well serverless, if you use Lambda, you're going to be locked in. And again, if you're using Oracle, you're locked in. Or, you're using MySQL you're locked in. Or, you're using any of the other things, you're locked in.Gojko: You're actually not locked in physically. There's a key and a lock.Jeremy: Right, but this idea of being locked in not to a specific cloud provider, but just locked into a cloud in general and relying on the cloud to do that scaling for you, where do you think the limitations there are?Gojko: I think again, going back to cyclic, cyclic, cyclic. The PC revolution started when a lot more edge compute was needed on mainframes, and people wanted to get stuff done on their own devices. And I think probably, if we do ever see the limitations of this and it goes into a next cycle, my best guess it's going to be driven by lots of tiny devices connected to a cloud. Not necessarily computers as we know computers today. I pulled out some research preparing for this from IDC. They are predicting basically from 18.3 zettabytes of data needed for IOT in 2019, to be 73.1 zettabytes by 2025. That's like times three in a space of six years. If you went to Amazon now and told them, "You need to have three times more data space in three years," I'm not sure how they would react to that.This stuff, everything is taking more and more data, and everything is more and more connected to the cloud. The impact of something like that going down now is becoming totally crazy. There was a case in 2017 where S3 started getting a bit more latency than usual in U.S. East 1, in I think February of 2018, or something like that. There were cases where people couldn't turn the lights on in their houses because the management software was working on S3 and depending on S3. Expecting S3 to be indestructible. Last year, in November, Kinesis pretty much went offline as far as everybody else outside AWS concerend for about 15 hours I think. There were people on Twitter that they can't go back into their house because their smart lock is no longer that smart.And I think we are getting to places where there will be more need for compute on the edge. First of all, there's going to be a lot more demand for data centers and cloud power and I think that's going to keep going on for the next five, ten years. But then people will realize they've hit some limitation of that, and they're going to start moving towards the edge. And we're going from mainframe back into client server computing I think. We're getting these products now. I assume most of your listeners have seen one like all these fancy ubiquity Wi-Fi thingies that are costing hundreds of dollars and they look like pieces of furniture that's just sitting discretely on the wall. And there was a massive security breach yesterday published. Somebody took their AWS keys and took all the customer data and everything.The big advantage over all the ugly routers was that it's just like a thin piece of glass that sits on your wall, and it's amazing and it looks good, but the reason why they could do a very thin piece of glass is the minimal amount of software is running on that piece of glass, the rest is running the cloud. It's not just locking in terms of is it on Amazon or Google, it's that it's so tightly coupled with something totally outside of your home, where your network router needs Amazon to be alive now in a very specific region of Amazon where everybody's been deploying for the last 15 years, and it's running out of capacity very often. Not very often but often enough.There's some really interesting questions that I guess we'll answer in the next five, ten years. We're on the verge of IOT I think exploding because people are trying to come up with these new products that you wouldn't even think before that you'd have smart shoes and smart whatnot. Smart glasses and things like that. And when that gets into consumer technology, we're no longer going to have five or ten computer devices per person, we'll have dozens and dozens of computing. I guess think about it this way, fifteen years ago, how many computer devices were you carrying with yourself? Probably mobile phone and laptop. Probably not more. Now, in the headphones you have there that's Bose ...Jeremy: Watch.Gojko: ... you have a microprocessor in the headphones, you have your watch, you have a ton of other stuff carrying with you that's low-powered, all doing a bit of processing there. A lot of that processing is probably happening on the cloud somewhere.Jeremy: Or, it's just sending data. It's just sending, hey here's the information. And you're right. For me, I got my Apple Watch, my thermostat is connected to Wi-Fi and to the cloud, my wife just bought a humidifier for our living room that is connected to Wi-Fi and I'm assuming it's sending data to the cloud. I'm not 100% sure, but the question is, I don't know why we need to keep track of the humidity in my living room. But that's the kind of thing too where, you mentioned from a security standpoint, I have a bunch of AWS access keys on my computer that I send over the network, and I'm assuming they're secure. But if I've got another device that can access my network and somebody hacked something on the cloud side and then they can get in, it gets really dangerous.But you're right, the amount of data that we are now generating and compute that we're using in the cloud for probably some really dumb things like humidity in my living room, is that going to get to a point where... You said there's going to be a limitation like five years, ten years, whatever it is. What does the cloud do then? What does the cloud do when it can no longer keep up with the pace of these IOT devices?Gojko: Well, if history is repeating and we'll see if history is repeating, people will start getting throttled and all of a sudden, your unlimited supply of Lambdas will no longer be unlimited supply of Lambdas. It will be something that you have to reserve upfront and pay upfront, and who knows, we'll see when we get there. Or, we get things that we have with power networks like you had a Texas power cut there that was completely severe, and you get a IT cut. I don't know. We'll see. The more we go into utility, the more we'll start seeing parallels between compute and power networks. And maybe power networks are something that you can look at and later name. That's why I think the next cycle is probably going to be some equivalent of client server computing reemerging.Jeremy: Yeah. All right, well, I got one more question for you and this is just something where it may be a little bit of a tongue-in-cheek question. Because we talked it a little bit ... we talked about the merging of Lambda, and of Fargate, and some of these other things. But just from your perspective, serverless in five years from now, where do you see that going? Do you see that just becoming the main ... This idea of utility computing, on-demand computing without setting up servers and managing ops and some of these other things, do you see that as the future of serverless and it just becoming just the way we build applications? Or do you think that it's got a different path?Gojko: There was a tweet by Simon Wardley. You mentioned Simon Wardley earlier in the talk. There was a tweet a few days ago where he mentioned some data. I'm not sure where he pulled it from. This might be unverified, but generally Simon knows what he's talking about. Amazon itself is deploying roughly 50% of all new apps they're building on serverless. I think five years from now, that way of running stuff, I'm not sure if it's Lambda or some new service that Amazon starts and gives it some even more confusing name that runs in parallel to everything. But, that kind of stuff where the operator takes care of all the ops, which they really should be doing, is going to be the default way of getting utility compute out.I think a lot of these other things will probably remain useful for specialists' use cases, where you can't really deploy it in that way, or you need more stability, or it's not transient and things like that. My best guess is first of all, we'll get Lambda's that run for longer, and I assume that after we get Lambdas that run for longer, we'll probably get some ways of controlling routing to Lambdas because you already can set up pre-provisioned Lambdas and hot Lambdas and reserved capacity and things like that. When you have reserved capacity and you have longer running Lambdas, the next logical thing there is to have session stickiness, and routing, and things like that. And I think we'll get a lot of the stuff that was really complicated to do earlier, and you had to run EC2 instances or you had to run complicated networks of services, you'll be able to do in Lambda.And Lambda is, I wouldn't be surprised if they launch a totally new service with some AWS cloud socket, whatever. Something that is a implementation of the same principle, just in a different way, that becomes a default we are running computer for lots of people. And I think GPUs are still a bit limited. I don't think you can run GPU utility anywhere now, and that's limiting for a whole host of use cases. And I think again, it's not like they don't have the technology to do it, it's just they probably didn't get around to doing it yet. But I assume in five years time, you'll be able to do GPUs on-demand, and processing GPUs, and things like that. I think that the buzzword itself will lose really any special meaning and that's going to just be a way of running stuff.Jeremy: Yeah, absolutely. Totally agree. Well, listen Gojko, thank you so much for spending the time chatting with me. Always great to talk with you.Gojko: You, too.Jeremy: If people want to get in touch with you, find out more about what you're doing, how do they do that?Gojko: Well, I'm very easy to find online because there's not a lot of people called Gojko. Type Gojko into Google, you'll find me. And gojko.networks, gojko.com works, gojko.org works, and all these other things. I was lucky enough to get all those domains.Jeremy: That's G-O-J-K-O ...Gojko: Yes, G-O-J-K-O.Jeremy: ... for people who need the spelling.Gojko: Excellent. Well, thanks very much for having me, this was a blast.Jeremy: All right, yeah. And make sure you check out ... You mentioned Narakeet. It's a speech thing?Gojko: Yeah, for developers that want to build videos without hassle, and want to put videos in continuous integration, and things like that. Narakeet, that's like parakeet with an N for narration. Check that out and thanks for plugging it.Jeremy: Awesome. And then, check out MindMup as well. Awesome stuff. I've got all the stuff in the show notes. Thanks again, Gojko.Gojko: Thank you. Bye-bye.
Czy można się czegoś nauczyć słuchając podcastów Od czasu, kiedy zacząłem słuchać podcastów, w moim życiu wiele się zmieniło. Z mojej perspektywy na plus, o czym już wcześniej pisałem i mówiłem. Na tę chwilę jest to moja największa pasja, która zarazem jest bardzo wartościowa. Działa bezpośrednio i pośrednio.Bezpośrednio, bo sam wyciągam z niej wiele dla siebie, o czym właśnie nagrałem ten materiał.Uczę się, przekazuję tę wiedzę i doświadczenia dalej, co dodatkowo wzmacnia zapamiętywanie. Poniżej wrzucam mapę myśli, która pomagała mi podczas tego odcinka, a czego też się uczę. Moje wcześniejsze notatki były bardziej chaotyczne i czasem, zamiast pomagać, przeszkadzały. Czasem, co wstyd przyznać, nie miałem notatek, czego efektem było poświęcenie znacznie większej ilości czasu na edycję i przygotowanie odcinka. Shame! Shame! (Gra o tron)Ale co tam.Nie ma ludzi idealnych, a nawet nie ma na świecie niczego, co mogłoby zostać nazwane idealnym, więc nie ma się co biczować. To są te błędy, które szybko da się naprawić i myślę, że taka mapa myśli może wiele zmienić, a jej przygotowanie nie zajmuje wiele czasu. Ma swoją strukturę, a samo narzędzie jest darmowe i można je podpiąć do Google Drive, co oznacza, że pracujesz z nim na każdym urządzeni z dostępem do internetu.10 rzeczy, których nauczyłem się od swoich gości cz. I – narzędzie nazywa się MindMup 2.0Jeśli chcesz zobaczyć, a nie tylko usłyszeć ten materiał, to zapraszam na YouTube – pamiętaj, żeby za subskrybować kanał i skomentować, najlepiej tak, żebym wiedział, nad czym powinienem popracować. Wiem, że oświetlenie wymaga dopracowania, bo w okularach sporo się odbija i to może przeszkadzać. Pracuję nad tym i w kolejnych materiałach powinno być lepiej.To był wpływ bezpośredniPośrednio podcast działa na słuchaczy, a zupełnie przy okazji, także na mojego syna, który montuje moje podcasty. Montując, jest poniekąd zmuszony do słuchania, a zatem jest szansa, że wyciągnie z tych treści coś dla siebie. Ja wiem, że wyciąga.Wiem, że słuchacze także wyciągają. Dobrze jest dostać od słuchaczy wiadomość, czy maila, że to, co nagrywam, w jakimś sensie ludziom pomaga.
Today's episode of Research Like a Pro is about organizing your DNA matches by creating diagrams. Charting your DNA matches in a pedigree showing most recent common ancestor can help you visualize your DNA results like never before. We'll talk about two online charting options, charting using Ancestry.com's trees, and also an offline method. There are many more. Join us as we talk with Robin Wirthlin about how to chart your DNA matches! Links What Do You Want to Know? 3 Steps to Focus Your DNA Research by Robin at Family Locket Creating an Objective for a DNA Research Project by Diana at Family Locket LucidChart.com MindMup.com Ancestry.com Research Like a Pro eCourse Study Group - more information and email list Research Like a Pro: A Genealogist's Guide by Diana Elder with Nicole Dyer on Amazon.com Thank you Thanks for listening! We hope that you will share your thoughts about our podcast and help us out by doing the following: Share an honest review on iTunes or Stitcher. You can easily write a review with Stitcher, without creating an account. Just scroll to the bottom of the page and click "write a review." You simply provide a nickname and an email address that will not be published. We value your feedback and your ratings really help this podcast reach others. If you leave a review, we will read it on the podcast and answer any questions that you bring up in your review. Thank you! Leave a comment in the comment or question in the comment section below. Share the episode on Twitter, Facebook, or Pinterest. Subscribe on iTunes, Stitcher, Google Play, or your favorite podcast app. Sign up for our newsletter to receive notifications of new episodes. Check out this list of genealogy podcasts from Feedspot: Top 20 Genealogy Podcasts
01:32 - Clare’s Superpower: Collecting and Sharing Useful Information 04:31 - Llewellyn’s Superpower: The Ability to Collaborate with Others 08:01 - Pairing Together: C++ Version of ApprovalTests (https://github.com/approvals/ApprovalTests.cpp) 12:15 - Pairing Retrospectives: What emotions did you feel? MindMup (https://www.mindmup.com/) 16:21 - Kinship Formed Through Working Together 18:55 - Working Asynchronously vs Live Pairing 20:15 - Writing Documentation for Pairing Sessions and Working to Improve the C++ Community Culture #include (https://www.includecpp.org/) 30:44 - Safeguarding: Harnessing Pain For Good Safeguarding: A step-by-step guide (http://llewellynfalco.blogspot.com/2018/12/safeguarding-step-by-step-guide.html) MarkdownSnippets (https://github.com/simonCropp/MarkdownSnippets) 35:04 - Documentation Cont’d Turning “Error Messages” Into “Help Messages” Healthy Abstractions Testing Communication 45:08 - Asking “Why” Questions vs “What” Questions: Observability Reflections: John: The idea of using a retrospective in such a small scale. Also, the difference in the level of community while pairing: building kinship. Clare: Read more about the paradigm framing effect. Llewellyn: Being appreciative of the people you pair with. Arty: Taking the time to think about what you’re doing from the perspective of sharing affects what you do. This episode was brought to you by @therubyrep (https://twitter.com/therubyrep) of DevReps, LLC (http://www.devreps.com/). To pledge your support and to join our awesome Slack community, visit patreon.com/greaterthancode (https://www.patreon.com/greaterthancode) To make a one-time donation so that we can continue to bring you more content and transcripts like this, please do so at paypal.me/devreps (https://www.paypal.me/devreps). You will also get an invitation to our Slack community this way as well. Amazon links may be affiliate links, which means you’re supporting the show when you purchase our recommendations. Thanks! Special Guests: Clare Macrae and Llewellyn Falco.
In our podcast episode today, Diana and I discuss one of our new favorite tools, Lucid Chart! After Robin Wirthlin, our genetic genealogist friend and guest blogger, wrote about using LucidChart, and helped Nicole get started using it, we quickly realized how useful it is when doing client projects involving DNA matches. We talked about how Diana found her sister's biological parents with DNA diagramming complex relationships of matches with MindMup, a free open source Mind Map program. Now she uses LucidChart. We also mentioned some other alternatives. Links Seeing the Big Picture: 3 Ways to Chart Your DNA Matches - by Robin Wirthlin at Family Locket LucidChart.com - our favorite way to diagram DNA matches Draw.io - free open source software like LucidChart MindMup - the mind map program Diana used in her sister's case Using DNA to Find Biological Parents: 3 Tips to Get Started and a Case Study - Diana's search for her sister's biological parents Solving an Adoptee Case with DNA Networks and Mind Mapping PowerPoint Smart Art - Hierarchy - another way to chart DNA matches Draw.io - free open source software like LucidChart Research Like a Pro eCourse Study Group - more information and email list Research Like a Pro: A Genealogist's Guide by Diana Elder with Nicole Dyer on Amazon.com Thank you Thanks for listening! We hope that you will share your thoughts about our podcast and help us out by doing the following: Share an honest review on iTunes or Stitcher. You can easily write a review with Stitcher, without creating an account. Just scroll to the bottom of the page and click "write a review." You simply provide a nickname and an email address that will not be published. We value your feedback and your ratings really help this podcast reach others. If you leave a review, we will read it on the podcast and answer any questions that you bring up in your review. Thank you! Leave a comment in the comment or question in the comment section below. Share the episode on Twitter, Facebook, or Pinterest. Subscribe on iTunes, Stitcher, Google Play, or your favorite podcast app. Sign up for our newsletter to receive notifications of new episodes.
Hola a todos! Ya tenemos aquí un nuevo episodio de Negocios y WordPress. Dedicamos este capítulo a la creación de documentos orientados a cumplir una función concreta, ya que no podremos cubrir todas las necesidades con un simple editor de texto. Nos habíamos dejado un gadget por comentar de la MWC. Se trata de Holo Lens 2, la nueva versión del visor de realidad mixta (o superaumentada) de...Origen
Copywriter Sarah Grear is back for a second appearance on The Copywriter Club Podcast. Kira and Rob wanted to learn more about how she is shifting to offer more consulting in addition to copywriting, the tools she uses to land clients and how she structures her business so she gets paid even while on vacation. It this episode (#105 for those who are keeping score) we talked all about: • how she made six figures last year (and took four months off) • what Sarah’s accomplished since we last talked with her • what she does to help her clients have massively successful launches • the “gift” she gives her clients that closes the deal • what it takes to create a launch map and feel confident about sharing with her clients • the five phases of a launch plan • the ins and outs of a successful “launch debrief” and how she sells the next project • how she continues to get herself on stage (and what she teaches) • why she publicly celebrates every win today • the strategies Sarah uses to create more freedom in her personal life • how you can leverage your strengths to add consulting to your copy business • her “mindset” advice for copywriters who want to up-level to consultant There’s lots to love in this episode. To hear it, click the play button below, or scroll down for a full transcript. You can also find it at iTunes, Stitcher and on your favorite podcast app. The people and stuff we mentioned on the show: The first Sarah episode (#32) MindMup for G Suite Abbey Woodcock Tarzan Val Geisler SarahGrear.com/copy Kira’s website Rob’s website The Copywriter Club Facebook Group Intro: Content (for now) Outro: Gravity Full Transcript: Rob: What if you could hang out with seriously talented copywriters and other experts, ask them about their successes and failures, their work processes and their habits, then steal an idea or two to inspire your own work? That's what Kira and I do every week at The Copywriter Club Podcast. Kira: You're invited to join the Club for Episode 105 as we chat for a second time with freelance copywriter, Sarah Grier, about what it takes to grow a copywriting business past six figures, her recipe for launch success, why she books two projects at a time and spreads payments over six months, and how to add consulting to the services you offer your clients. Hey, Sarah. Welcome back. Rob: Hey Sarah. Sarah: Hey, thanks for having me. It's so fun. I can't believe you guys have done 106 interviews. And you're still standing. Rob: Barely. We're actually ... I think we're both sitting right now. Kira: Sitting all day long. Which we need to work on. So why don't you just give us a quick update. What have you been working on and what's happened since last time you were on our show? Rob: And that was Episode 32, for anybody who wants to check that out, because it was a really good one. So, yeah, check that out. Sarah: I know. I became the take four months off in your business woman since then. But, yeah, I've done that. I took four months off last year, intermittently. If you listen to the old episode you can hear how. So, I'll leave that as a tease. Since then, in 2017, I worked on 52 projects for 19 clients, and still managed to take all that time off. Kira: What? Rob: Wow. Sarah: I know. Rob: It's crazy. Kira: That is crazy. Sarah: When you have systems in place it makes a huge difference. But also I had this astronomical launch that stood out from all the other ones. We did seven figures in a single launch. Sarah: And it was the first time we had worked together. Basically, that changed the way that I was showing up with my clients, because I realized when my clients grow to that level or grow that quickly, they don't always need a copywriter at that point because they usually hire an in-house production team. And so I started doing small percentage of consultant work alongside the copywriting work t...
Dans cet épisode 5 des carnets d'un inlassable curieux, je fais le tour des applications et outils que j'utilise au quotidien sur mon chromebook :- Docs de Google : https://docs.google.com/- Sheet de Google : https://docs.google.com/spreadsheets/- Keep : https://keep.google.com/- OneNote : https://www.onenote.com/- MindMup : https://www.mindmup.com/- Xodo : https://www.xodo.com/- Comic'Screen : https://play.google.com/store/apps/details?id=com.viewer.comicscreen&hl=fr- PowerDirector : https://play.google.com/store/apps/details?id=com.cyberlink.powerdirector.DRA140225_01&hl=fr- Wave Pad : https://play.google.com/store/apps/details?id=com.nchsoftware.pocketwavepad_free&hl=fr- Beautiful : https://chrome.google.com/webstore/detail/beautiful-audio-editor/okiblndpcefmebnkjnjfplijnelbcjmm- Gestionnaire de fichiers Asus : https://play.google.com/store/apps/details?id=com.asus.filemanager&hl=fr- Dashlane - gestionnaire de mots de passe : https://www.dashlane.com/- Feedly : https://feedly.com/- Actualités de Google : https://play.google.com/store/apps/details?id=com.google.android.apps.genie.geniewidget&hl=frMon twitter : @overb62Mon Blog : https://overbblog.wordpress.com/
Dans cet épisode 5 des carnets d'un inlassable curieux, je fais le tour des applications et outils que j'utilise au quotidien sur mon chromebook :- Docs de Google : https://docs.google.com/- Sheet de Google : https://docs.google.com/spreadsheets/- Keep : https://keep.google.com/- OneNote : https://www.onenote.com/- MindMup : https://www.mindmup.com/- Xodo : https://www.xodo.com/- Comic'Screen : https://play.google.com/store/apps/details?id=com.viewer.comicscreen&hl=fr- PowerDirector : https://play.google.com/store/apps/details?id=com.cyberlink.powerdirector.DRA140225_01&hl=fr- Wave Pad : https://play.google.com/store/apps/details?id=com.nchsoftware.pocketwavepad_free&hl=fr- Beautiful : https://chrome.google.com/webstore/detail/beautiful-audio-editor/okiblndpcefmebnkjnjfplijnelbcjmm- Gestionnaire de fichiers Asus : https://play.google.com/store/apps/details?id=com.asus.filemanager&hl=fr- Dashlane - gestionnaire de mots de passe : https://www.dashlane.com/- Feedly : https://feedly.com/- Actualités de Google : https://play.google.com/store/apps/details?id=com.google.android.apps.genie.geniewidget&hl=frMon twitter : @overb62Mon Blog : https://overbblog.wordpress.com/
Moving from your business strategy to product design using impact mapping to connect development roadmap to business goals. Some of the things we mention in the episode are: MindMup (https://www.mindmup.com/) - brilliant online mind mapping tool that works especially well for running impact mapping sessions Impact Mapping by Gojko Adzic (https://www.amazon.co.uk/Impact-Mapping-Software-Products-Projects/dp/0955683645/ref=sr_1_1) - short, approachable, pragmatic volume on how to get started with the technique
Introduction FreelanceRemoteConf Content marketing that does not involve the written word 4:30: What Is Content Marketing? Showing expertise Helping people Providing value 6:20: Podcasting Screencast Creating a Twitter Clone 10:30: Missing out on client work? Ruby on Rails “Giving away the farm.” 16:40: Highly scripted video UberConference John Sonmez 22:00: Casual video or audio Facebook Live Aaron Walker Facebook community YouTube Live Fullscope.tv Publish on a consistent schedule 34:45: Case Studies YouTube or Google Hangouts 39:50: Practicalities Search engine rankings Transcription services Comparing yourself to others 47:50: Infographics Picks: Ditching Hourly (Reuven) Limony Snicket’s A Series of Unfortunate Events (Reuven) Rev.com (Philip) Trustvelocity.com (Philip) Born to Win by Zig Ziglar (Charles) Mindmup.com (Charles) devchat.tv/conferences (Charles)
Introduction FreelanceRemoteConf Content marketing that does not involve the written word 4:30: What Is Content Marketing? Showing expertise Helping people Providing value 6:20: Podcasting Screencast Creating a Twitter Clone 10:30: Missing out on client work? Ruby on Rails “Giving away the farm.” 16:40: Highly scripted video UberConference John Sonmez 22:00: Casual video or audio Facebook Live Aaron Walker Facebook community YouTube Live Fullscope.tv Publish on a consistent schedule 34:45: Case Studies YouTube or Google Hangouts 39:50: Practicalities Search engine rankings Transcription services Comparing yourself to others 47:50: Infographics Picks: Ditching Hourly (Reuven) Limony Snicket’s A Series of Unfortunate Events (Reuven) Rev.com (Philip) Trustvelocity.com (Philip) Born to Win by Zig Ziglar (Charles) Mindmup.com (Charles) devchat.tv/conferences (Charles)
TOPICS: 03:08 The level of difficulty in determining code creators on the Internet 04:28 How to determine if code has been copied 10:00 What defines a trade secret 12:11 The pending Oracle v Google lawsuit 25:29 Nintendo v Atari 27:38 The pros and cons of a patent 29:59 Terrible patents 33:48 Fighting patent infringement and dealing with “patent trolls” 39:00 How a company tried to steal Bob Zeidman’s software 44:13 How to know if you can use open source codes 49:15 Using detective work to determine who copied whom 52:55 Extreme examples of unethical behavior 56:03 The state of patent laws PICKS: Cognitive Bias Cheat Sheet Blog Post Bagels by P28 Foods Let’s Encrypt Indigogo Generosity Campaign Super Cartography Bros Album MicroConf 2017 MindMup Mind Mapping Tool Words with Friends Game Upcoming Conferences via Devchat.tv Good Intentions Book by Bob Zeidman Horror Flick Book by Bob Zeidman Silicon Valley Napkins
TOPICS: 03:08 The level of difficulty in determining code creators on the Internet 04:28 How to determine if code has been copied 10:00 What defines a trade secret 12:11 The pending Oracle v Google lawsuit 25:29 Nintendo v Atari 27:38 The pros and cons of a patent 29:59 Terrible patents 33:48 Fighting patent infringement and dealing with “patent trolls” 39:00 How a company tried to steal Bob Zeidman’s software 44:13 How to know if you can use open source codes 49:15 Using detective work to determine who copied whom 52:55 Extreme examples of unethical behavior 56:03 The state of patent laws PICKS: Cognitive Bias Cheat Sheet Blog Post Bagels by P28 Foods Let’s Encrypt Indigogo Generosity Campaign Super Cartography Bros Album MicroConf 2017 MindMup Mind Mapping Tool Words with Friends Game Upcoming Conferences via Devchat.tv Good Intentions Book by Bob Zeidman Horror Flick Book by Bob Zeidman Silicon Valley Napkins
TOPICS: 03:08 The level of difficulty in determining code creators on the Internet 04:28 How to determine if code has been copied 10:00 What defines a trade secret 12:11 The pending Oracle v Google lawsuit 25:29 Nintendo v Atari 27:38 The pros and cons of a patent 29:59 Terrible patents 33:48 Fighting patent infringement and dealing with “patent trolls” 39:00 How a company tried to steal Bob Zeidman’s software 44:13 How to know if you can use open source codes 49:15 Using detective work to determine who copied whom 52:55 Extreme examples of unethical behavior 56:03 The state of patent laws PICKS: Cognitive Bias Cheat Sheet Blog Post Bagels by P28 Foods Let’s Encrypt Indigogo Generosity Campaign Super Cartography Bros Album MicroConf 2017 MindMup Mind Mapping Tool Words with Friends Game Upcoming Conferences via Devchat.tv Good Intentions Book by Bob Zeidman Horror Flick Book by Bob Zeidman Silicon Valley Napkins
MindMup is super-simple free effortless way to create mind maps in moments. It's Web-based without having to download anything or open an account. Using inside Google Drive you can share your work, you can export it to .png or FreeMind .mm formats, or you can simply share the link to MindMup. Anyone clicking on the link will see your mind maps and be able to make changes. If you like to plan and brainstorm by creating mind maps to link together ideas, MindMup is a great browser-based program that helps you get organized with lots of features. Tech to share? Go to this link ask.savvylandlord.me or go to www.savvyradioshow.com and leave a voice mail!
Steve Dotto, Mike Vardy and Erik Fisher discuss the benefits and application of Mindmapping. Mentioned in this episode: Mindmeister Mindnode iThoughts X Mind MindJet Mohio map MindMup Scrivener Scapple Meister task Asana DigiSpoke Trello Please connect with me Subscribe, rate, and review in iTunes Follow @ErikJFisher Check out more Noodle.mx Network showsThe Audacity to Podcast: "How-to" podcast about podcastingBeyond the To-Do List: Personal and professional productivityThe Productive Woman: Productivity for busy womenONCE: Once Upon a Time podcastWelcome to Level Seven: Agents of SHIELD and Marvel’s cinematic universe podcastAre You Just Watching?: Movie reviews with Christian critical thinkingthe Ramen Noodle: Family-friendly clean comedy
http://olivierrebiere.com/3-minute-solution/ Découvrez les cartes mentales et le logiciel en ligne mindmup.com, en 3 minutes !
This week, Dave and Gunnar talk about Le PRISM, Slashdot Gunnarbait, OpenStack Security Guide, the Indie Web, a petabyte of tax data, and an interview with the creator of CommaFeed. Subscribe via RSS or iTunes. Welcome to Texas, Gunnar. Le PRISM: France Has A PRISM-Like Program With Millions Of Trillions Of Metadata Elements PRISM & Big Data: Big Data and Analytics: The Hero or the Villain? PRISM Break: EFF’s list of free, open, secure alternatives to proprietary software Gunnarbait: NSA Backdoors In Open Source and Open Standards: What Are the Odds? The OpenStack Security Guide is up! When almost every networking vendor works togeter on the OpenDaylight project, they have to tell the DOJ Why Automakers Should Stop the Infotainment Arms Race LibreOffice Accelerates Open Source Spreadsheets, Thanks to AMD El Reg encounters mObi: R2-D2 for retailers Microsoft to shut down TechNet subscription service Red Hat Developer Tools & Services are available Red Hat is Developer Wonderland Young Coders at PyOhio 2013 Akron LUG August 1: Teaching your kids to code with Scratch on Raspberry Pi by Lauren Egts Intuit runs RH Storage, could his 1PB this year Linux Journal white paper: Using an Open Source Framework to Catch the Bad Guy by Red Hat superstar Mark St. Laurent The Alamo Drafthouse Ticketbot An Open Source Project We Like: CommaFeed from Jérémie Panzer PC Magazine 4 out of 5 star review! Eric Mill’s definitive guide to owning your online identity Why you should look at IndieWebCamp PermitRootLogin forced-commands-only is basically magic Term of the week: The Purdie Shuffle Made famous by Bernard “Pretty” Purdie Dave wants to learn whatever he’s teaching: Led Zeppelin’s “Fool in the Rain” from the 1979 album In Through the Out Door John Bonham’s isolated drum track and awesome article discussing other Purdie Shuffle variations by Steely Dan and Death Cab for Cutie Toto’s “Rosanna” from the 1982 album Toto IV Toto drummer Jeff Porcaro (RIP) on the Rosanna shuffle Bonus link: Mother of All Funk Chords featuring Bernard “Pretty” Purdie and a dude with a mullet playing the theremin at 2:43 Cutting Room Floor A Citizen’s Guide to Open Government, E-Government, and Government 2.0 Avira says farewell to Linux German antivirus company Avira is discontinuing its Linux products in order to focus more on developing its Mac OS X and Windows lines. The company says small businesses and consumer systems “almost exclusively rely upon Windows or Mac operating systems” and that “Linux installations have been declining steadily for years.” Sign that the Linux desktop is declining, or that the Linux desktop doesn’t need commercial antivirus since it has AIDE, Tripwire, and ClamAV? Pi-Rex – Bark Activated Door Opening System with Raspberry Pi New Breed of Banking Malware Hijacks Text Messages Tricks people to install a 3rd party app on their phones to intercept SMS messages and forward them LinkedIn, Twitter, and banks use SMS for 2 factor authentication SMS transmission alternatives which may aid in two factor authentication A Standard for the Transmission of IP Datagrams on Avian Carriers 256 milligram MTU! Lauren asked Dave if it mattered if you used an African or European swallow IP over Avian Carriers with Quality of Service Adaptation of RFC 1149 for IPv6 Doubling down on Markdown for science Prior art: Superman intvented 3D printing in 1964 A New Way to Heal Broken Bones: 3D-Printed Casts MindMup: Open source browser based mind mapping Where the Egts family went on vacation two years ago: The National Museum of Computing History (TNMOC) in Bletchley Park We Give Thanks The authors of the OpenStack Security Guide Jérémie Panzer for all his work on CommaFeed and taking the time to let us interview him Jason Hibbets for the Citizen’s Guide tip Adam Clater for the IP over Avian Carrier tips
© 2020-2025 Ivy Podcast Discovery LLC
