Visible mass of liquid droplets or frozen crystals suspended in the atmosphere
Topics: False Accusations, Adultery, Parenting, Physical Abuse, Newlyweds, Dating, Grief, Work Issues Hosts: Steve Arterburn, Dr. Jill Hubbard, Milan Yerkovich Caller Questions: When I was 11yo, I was falsely accused of molesting kids. My separated husband accused me of being an adulterer for getting remarried; am I? He has been married several times, watches porn, and is a minister. What's an appropriate age to talk to The post New Life Live: October 15, 2021 appeared first on New Life.
This week we discuss the real-world use of containers, recap the Google Cloud Next announcements and make some Apple predications. Plus, how often do you wash jeans…? Rundown Containers in the Real World 10 trends in real world container use (https://www.datadoghq.com/container-report/) What Workloads Do Businesses Run on Kubernetes? (https://thenewstack.io/what-workloads-do-businesses-run-on-kubernetes/) Google Cloud Next `21 What's New at Google Cloud Next ‘21 (https://cloud.google.com/blog/topics/google-cloud-next/whats-new-at-next) Introducing Google Distributed Cloud—in your data center, at the edge, and in the cloud (https://cloud.google.com/blog/topics/hybrid-cloud/announcing-google-distributed-cloud-edge-and-hosted) Introducing Anthos for VMs and tools to simplify the developer experience (https://cloud.google.com/blog/topics/hybrid-cloud/introducing-anthos-for-vms-and-other-app-modernization-tools) Build a more secure future with Google Cloud (https://cloud.google.com/blog/products/identity-security/next21-how-google-cloud-secures-the-world) Google Cloud will show users their gross carbon emissions (https://www.engadget.com/google-cloud-platform-carbon-footprint-emissions-environment-163339146.html) GKE AutoPilot not new but mentioned (https://cloud.google.com/kubernetes-engine/docs/concepts/autopilot-overview#security) Google Cloud launches a managed Spark service (https://techcrunch.com/2021/10/12/google-cloud-launches-a-managed-spark-service/) Weave & Chick-fil-A: Managing Fleets of Kubernetes Clusters... (https://youtu.be/ta9jJc-RVvE) Relevant to your interests Eating the Cloud from Outside In (https://www.swyx.io/cloudflare-go/) The Confidential Computing Consortium Year in Review, 2021 - Confidential Computing Consortium (https://confidentialcomputing.io/2021/10/06/the-confidential-computing-consortium-year-in-review-2021/) Experts Discuss Top Kubernetes Trends and Production Challenges (https://www.infoq.com/articles/kubernetes-trends-and-challenges/) Microsoft and Amazon reach truce allowing former AWS executive Charlie Bell to start in new role (https://www.geekwire.com/2021/microsoft-amazon-reach-truce-allowing-former-aws-executive-charlie-bell-start-new-role/?utm_source=newsletter&utm_medium=email&utm_campaign=newsletter_axioslogin&stream=top) Series A Funding Announcement | cloudtamer.io (https://www.cloudtamer.io/announcing-our-series-a/) Reddit hires former Google Cloud exec as its first chief product officer (https://techcrunch.com/2021/10/11/reddit-hires-former-google-cloud-exec-as-its-first-chief-product-officer/) The next big thing in podcasts is talking back (https://www.theverge.com/2021/10/12/22722468/spotify-amazon-facebook-audio-podcast-polls-interact) 1Password's new feature lets you safely share passwords using just a link (https://techcrunch.com/2021/10/12/1passwords-new-feature-lets-you-safely-share-passwords-using-just-a-link/) Coinbase is launching its own NFT platform to take on OpenSea – TechCrunch (https://techcrunch.com/2021/10/12/coinbase-is-launching-its-own-nft-platform-to-take-on-opensea/) The Air Force's First Software Chief Stepped Down—But He Won't Be Quiet (https://www.nextgov.com/cio-briefing/2021/10/air-forces-first-software-chief-stepped-down-he-wont-be-quiet/186047/) Nonsense Tesla is moving its headquarters to Austin, Texas (https://www.theverge.com/22715458/tesla-move-headquarters-to-austin-texas) VC firm associate has built a crypto marketplace designed for fantasy startup investing (https://twitter.com/KateClarkTweets/status/1445830869151748101The> Confidential Computing Consortium Year in Review, 2021 - Confidential Computing Consortium) Musk vs. Bezos in a Tweet (https://twitter.com/elonmusk/status/1447426189660880898?s=20) Pon agrees to buy Dorel Sports for $810 million (https://www.bicycleretailer.com/industry-news/2021/10/11/pon-agrees-buy-dorel-sports-810-million#.YWWYtC-B0dk) The first USB-C iPhone is here thanks to a mod (https://www.theverge.com/2021/10/12/22722123/first-iphone-usb-c-port-robotics-engineering-student-custom) Sponsors strongDM — Manage and audit remote access to infrastructure. Start your free 14-day trial today at strongdm.com/SDT (http://strongdm.com/SDT) CBT Nuggets — Training available for IT Pros anytime, anywhere. Start your 7-day Free Trial today at cbtnuggets.com/sdt (https://cbtnuggets.com/sdt) Conferences GitOpsDays Community Special: GitOps One-Stop Shop Event October 20 (https://www.gitopsdays.com/) TriggerMesh Open Source Software Webinar (https://www.triggermesh.com/oss-intro) - October 28, 2021 MongoDB.local London 2021 (https://events.mongodb.com/dotlocallondon) - November 9, 2021 THAT Conference comes to Texas January 17-20, 2022 (https://that.us/activities/call-for-counselors/tx/2022) Listener Feedback Ed wants you to be Product Manager at VMware based in Spain (https://vmware.wd1.myworkdayjobs.com/VMware/job/ESP-Seville-Av-de-Republica-Argentina/Product-Manager-for-RabbitMQ_R2111712) Brian wants you to be a Senior Product Manager - Pipelines in Bangalore (https://global-redhat.icims.com/jobs/89894/senior-product-manager---technical/job?mobile=false&width=1140&height=500&bga=true&needsRedirect=false&jan1offset=-300&jun1offset=-240) or Senior Product Manager - GitOps in Remote, UK (https://global-redhat.icims.com/jobs/89893/senior-product-manager---gitops/job) Brian recommends this jump box (https://www.amazon.com/gp/product/B082ZZ2W14/ref=ppx_yo_dt_b_search_asin_title?ie=UTF8&psc=1) TriggerMesh is hiring! (https://twitter.com/sebgoa/status/1437722696536797185) SDT news & hype Join us in Slack (http://www.softwaredefinedtalk.com/slack). Send your postal address to firstname.lastname@example.org (mailto:email@example.com) and we will send you free laptop stickers! Follow us on Twitch (https://www.twitch.tv/sdtpodcast), Twitter (https://twitter.com/softwaredeftalk), Instagram (https://www.instagram.com/softwaredefinedtalk/), LinkedIn (https://www.linkedin.com/company/software-defined-talk/) and YouTube (https://www.youtube.com/channel/UCi3OJPV6h9tp-hbsGBLGsDQ/featured). Brandon built the Quick Concall iPhone App (https://itunes.apple.com/us/app/quick-concall/id1399948033?mt=823) and he wants you to buy it for $0.99. Use the code SDT to get $20 off Coté's book, (https://leanpub.com/digitalwtf/c/sdt) Digital WTF (https://leanpub.com/digitalwtf/c/sdt), so $5 total. Become a sponsor of Software Defined Talk (https://www.softwaredefinedtalk.com/ads)! Recommendations Brandon: Universel Dual Monitor Arm with Pistons (https://www.bestar.com/product/dual-monitor-arm-ak-ma01d-17/) Coté: A Carnival of Snackery (https://www.audible.com/pd/A-Carnival-of-Snackery-Audiobook/1549108212), new David Sederis diaries, audio of course. Tasty Meats Paul's Whole Hair Thing (https://twitter.com/bridgetkromhout/status/1448351873614827521). Also (https://twitter.com/cote/status/1448556155266084866). Photo Credits Header Image (https://unsplash.com/photos/3oejsU5OQVk) Show Artwork (https://cdn.thenewstack.io/media/2021/09/dbdf6555-image4.png) Show Artwork (https://imgix.datadoghq.com/img/container-report/2021-container-orchestration-report-FACT-10_part-1v3.png?ch=Width,DPR,Save-Data&fit=max&fm=png&auto=format)
We've got a star-studded cast this hour. MIke Gelfand. Adrian Washington. Jimmy Francis. And of course, Jit from Maharaja's. Each a different ethnicity, each Minnesotan. And we didn't even have to pay a Chief Officer of Diversity a salary to achieve it. Makes you think. The name of the hour is good vibes. Adrian brings the comedy at Annandale this weekend and St. Cloud the next. Jit brings the love. Jimmy and Gelfand are conspiring to rule this state with a dysfunctional fist. Sadly, it would be a major improvement. See omnystudio.com/listener for privacy information.
In this episode of RadioFreeHPC, Dan, Henry, and Shahin talk about the death of a Jedi, more specifically the cancellation of the Pentagon JEDI contract. Listen in for the details, as well as a full breakdown on multivendor competition and the complexity behind these agreements. RadioFreeHPC is produced by the computer science department at Faber College,… Read More »Fall of the JEDI
Today we take you into a low orbit with Tyler Browder of the Kubos Corporation and how they utilize open source and cloud native to provide a smarter satellite management suite. Destination Linux Network (https://destinationlinux.network) Sudo Show Website (https://sudo.show) Sponsor: Bitwarden (https://bitwarden.com/dln) Sponsor: Digital Ocean (https://do.co/dln-mongo) Sudo Show Swag (https://sudo.show/swag) Contact Us: DLN Discourse (https://sudo.show/discuss) Email Us! (mailto:firstname.lastname@example.org) Sudo Matrix Room (https://sudo.show/matrix) Follow our Hosts: Brandon's Website (https://open-tech.net) Eric's Website (https://itguyeric.com) Red Hat Streaming (https://www.redhat.com/en/livestreaming) Kubos (https://www.kubos.com) Medium: Kubos, A Software Platform for Space (https://medium.com/kubos-tech/kubos-a-software-platform-for-space-30d211062919) BizJournals: Mission Control Startup Snags 2.8M (https://www.bizjournals.com/portland/news/2021/02/08/mission-control-startup-snags-2-8m.html) Dallas Innovates: Denton-Based Kubos Corp. Launches Software into Space for the First Time (https://dallasinnovates.com/denton-based-kubos-corp-launches-software-into-space-for-the-first-time/) Podcast: Ground Control Checking In (https://kubos.com/podcast) NASA's Core Flight System (https://cfs.gsfc.nasa.gov) SatNOGS: Open Source Ground Station (https://satnogs.org) Chapters 00:00 Intro 00:43 Welcome 02:07 Sponsor - Digital Ocean 03:14 Sponsor - Bitwarden 04:40 Meet Tyler Browder 07:18 Kubos Corporation 12:05 Managing IT in Space 20:58 Journey to Cloud Native 30:51 Kubos Outreach 35:47 Wrap Up Special Guest: Tyler Browder.
About EwereCloud, DevOps Engineer, Blogger and AuthorLinks: Infrastructure Monitoring with Amazon CloudWatch: https://www.amazon.com/Infrastructure-Monitoring-Amazon-CloudWatch-infrastructure-ebook/dp/B08YS2PYKJ LinkedIn: https://www.linkedin.com/in/ewere/ Twitter: https://twitter.com/nimboya Medium: https://medium.com/@nimboya My Cloud Series: https://mycloudseries.com TranscriptAnnouncer: Hello, and welcome to Screaming in the Cloud with your host, Chief Cloud Economist at The Duckbill Group, Corey Quinn. This weekly show features conversations with people doing interesting work in the world of cloud, thoughtful commentary on the state of the technical world, and ridiculous titles for which Corey refuses to apologize. This is Screaming in the Cloud.Corey: This episode is sponsored in part by Honeycomb. When production is running slow, it's hard to know where problems originate: is it your application code, users, or the underlying systems? I've got five bucks on DNS, personally. Why scroll through endless dashboards, while dealing with alert floods, going from tool to tool to tool that you employ, guessing at which puzzle pieces matter? Context switching and tool sprawl are slowly killing both your team and your business. You should care more about one of those than the other, which one is up to you. Drop the separate pillars and enter a world of getting one unified understanding of the one thing driving your business: production. With Honeycomb, you guess less and know more. Try it for free at Honeycomb.io/screaminginthecloud. Observability, it's more than just hipster monitoring.Corey: This episode is sponsored in part by Liquibase. If you're anything like me, you've screwed up the database part of a deployment so severely that you've been banned from touching every anything that remotely sounds like SQL, at at least three different companies. We've mostly got code deployments solved for, but when it comes to databases we basically rely on desperate hope, with a roll back plan of keeping our resumes up to date. It doesn't have to be that way. Meet Liquibase. It is both an open source project and a commercial offering. Liquibase lets you track, modify, and automate database schema changes across almost any database, with guardrails to ensure you'll still have a company left after you deploy the change. No matter where your database lives, Liquibase can help you solve your database deployment issues. Check them out today at liquibase.com. Offer does not apply to Route 53.Corey: Welcome to Screaming in the Cloud. I'm Corey Quinn. I periodically make observations that monitoring cloud resources has changed somewhat since I first got started in the world of monitoring. My experience goes back to the original Call of Duty. That's right: Nagios.When you set instances up, it would theoretically tell you when they were unreachable or certain thresholds didn't work. It was janky but it kind of worked, and that was sort of the best we have. The world has progressed as cloud has become more complicated, as technologies have become more sophisticated, and here today to talk about this is the first AWS Hero from Africa and author of a brand new book, Ewere Diagboya. Thank you for joining me.Ewere: Thanks for the opportunity.Corey: So, you recently published a book on CloudWatch. To my understanding, it is the first such book that goes in-depth with not just how to wind up using it, but how to contextualize it as well. How did it come to be, I guess is my first question?Ewere: Yes, thanks a lot, Corey. The name of the book is Infrastructure Monitoring with Amazon CloudWatch, and the book came to be from the concept of looking at the ecosystem of AWS cloud computing and we saw that a lot of the things around cloud—I mostly talked about—most of this is [unintelligible 00:01:49] compute part of AWS, which is EC2, the containers, and all that, you find books on all those topics. They are all proliferated all over the internet, you know, and videos and all that.But there is a core behind each of these services that no one actually talks about and amplifies, which is the monitoring part, which helps you to understand what is going on with the system. I mean, knowing what is going on with the system helps you to understand failures, helps you to predict issues, helps you to also envisage when a failure is going to happen so that you can remedy it and also [unintelligible 00:02:19], and in some cases, even give you a historical view of the system to help you understand how a system has behaved over a period of time.Corey: One of the articles that I put out that first really put me on AWS's radar, for better or worse, was something that I was commissioned to write for Linux Journal, back when that was a print publication. And I accidentally wound up getting the cover of it with my article, “CloudWatch is of the devil, but I must use it.” And it was a painful problem that people generally found resonated with them because no one felt they really understood CloudWatch; it was incredibly expensive; it didn't really seem like it was at all intuitive, or that there was any good way to opt out of it, it was just simply there, and if you were going to be monitoring your system in a cloud environment—which of course you should be—it was just sort of the cost of doing business that you then have to pay for a third-party tool to wind up using the CloudWatch metrics that it was gathering, and it was just expensive and unpleasant all around. Now, a lot of the criticisms I put about CloudWatch's limitations in those days, about four years ago, have largely been resolved or at least mitigated in different ways. But is CloudWatch still crappy, I guess, is my question?Ewere: Um, yeah. So, at the moment, I think, like you said, CloudWatch has really evolved over time. I personally also had that issue with CloudWatch when I started using CloudWatch; I had the challenge of usability, I had the challenge of proper integration, and I will talk about my first experience with CloudWatch here. So, when I started my infrastructure work, one of the things I was doing a lot was EC2, basically. I mean, everyone always starts with EC2 at the first time.And then we had a downtime. And then my CTO says, “Okay, [Ewere 00:04:00], check what's going on.” And I'm like, “How do I check?” [laugh]. I mean, I had no idea of what to do.And he says, “Okay, there's a tool called CloudWatch. You should be able to monitor.” And I'm like, “Okay.” I dive into CloudWatch, and boom, I'm confused again. And you look at the console, you see, it shows you certain metrics, and yet [people 00:04:18] don't understand what CPU metric talks about, what does network bandwidth talks about?And here I am trying to dig, and dig, and dig deeper, and I still don't get [laugh] a sense of what is actually going on. But what I needed to find out was, I mean, what was wrong with the memory of the system, so I delved into trying to install the CloudWatch agent, get metrics and all that. But the truth of the matter was that I couldn't really solve my problem very well, but I had [unintelligible 00:04:43] of knowing that I don't have memory out of the box; it's something that has to set up differently. And trust me, after then I didn't touch CloudWatch [laugh] again. Because, like you said, it was a problem, it was a bit difficult to work with.But fast forward a couple of years later, I could actually see someone use CloudWatch for a lot of beautiful stuff, you know? It creates beautiful dashboards, creates some very well-aggregated metrics. And also with the aggregated alarms that CloudWatch comes with, [unintelligible 00:05:12] easy for you to avoid what to call incident fatigue. And then also, the dashboards. I mean, there are so many dashboards that simplified to work with, and it makes it easy and straightforward to configure.So, the bootstrapping and the changes and the improvements on CloudWatch over time has made CloudWatch a go-to tool, and most especially the integration with containers and Kubernetes. I mean, CloudWatch is one of the easiest tools to integrate with EKS, Kubernetes, or other container services that run in AWS; it's just, more or less, one or two lines of setup, and here you go with a lot of beautiful, interesting, and insightful metrics that you will not get out of the box, and if you look at other monitoring tools, it takes a lot of time for you to set up, for you to configure, for you to consistently maintain and to give you those consistent metrics you need to know what's going on with your system from time to time.Corey: The problem I always ran into was that the traditional tools that I was used to using in data centers worked pretty well because you didn't have a whole lot of variability on an hour-to-hour basis. Sure, when you installed new servers or brought up new virtual machines, you had to update the monitoring system. But then you started getting into this world of ephemerality with auto-scaling originally, and later containers, and—God help us all—Lambda now, where it becomes this very strange back-and-forth story of, you need to be able to build something that, I guess, is responsive to that. And there's no good way to get access to some of the things that CloudWatch provides, just because we didn't have access into AWS's systems the way that they do. The inverse, though, is that they don't have access into things running inside of the hypervisor; a classic example has always been memory: memory usage is an example of something that hasn't been able to be displayed traditionally without installing some sort of agent inside of it. Is that still the case? Are there better ways of addressing those things now?Ewere: So, that's still the case, I mean, for EC2 instances. So before, now, we had an agent called a CloudWatch agent. Now, there's a new agent called Unified Cloudwatch Agent which is, I mean, a top-notch from CloudWatch agent. So, at the moment, basically, that's what happens on the EC2 layer. But the good thing is when you're working with containers, or more or less Kubernetes kind of applications or systems, everything comes out of the box.So, with containers, we're talking about a [laugh] lot of moving parts. The container themselves with their own CPU, memory, disk, all the metrics, and then the nodes—or the EC2 instance of the virtual machines running behind them—also having their own unique metrics. So, within the container world, these things are just a click of a button. Everything happens at the same time as a single entity, but within the EC2 instance and ecosystem, you still find this there, although the setup process has been a bit easier and much faster. But in the container world, that problem has totally been eliminated.Corey: When you take a look at someone who's just starting to get a glimmer of awareness around what CloudWatch is and how to contextualize it, what are the most common mistakes people make early on?Ewere: I also talked about this in my book, and one of the mistakes people make in terms of CloudWatch, and monitoring in generalities: “What am I trying to figure out?” [laugh]. If you don't have that answer clearly stated, you're going to run into a lot of problems. You need to answer that question of, “What am I trying to figure out?” I mean, monitoring is so broad, monitoring is so large that if you do not have the answer to that question, you're going to get yourself into a lot of trouble, you're going to get yourself into a lot of confusion, and like I said, if you don't understand what you're trying to figure out in the first place, then you're going to get a lot of data, you're going to get a lot of information, and that can get you confused.And I also talked about what I call alarm fatigues or incident fatigues. This happens when you configure so many alarms, so many metrics, and you're getting a lot of alarms hitting and notification services—whether it's Slack, whether it's an email—and it causes fatigue. What happens here is the person who should know what is going on with the system gets a ton of messages and in that scenario can miss something very important because there's so many messages coming in, so many integrations coming in. So, you should be able to optimize appropriately, to be able to, like you said, conceptualize what you're trying to figure out, what problems are you trying to solve? Most times you really don't figure this out for a start, but there are certain bare minimums you need to know about, and that's part of what I talked about in the book.One of the things that I highlighted in the book when I talked about monitoring of different layers is, when you're talking about monitoring of infrastructure, say compute services, such as virtual machines, or EC2 instances, the certain baseline and metrics you need to take note of that are core to the reliability, the scalability, and the efficiency of your system. And if you focus on these things, you can have a baseline starting point before you start going deeper into things like observability and knowing what's going on entirely with your system. So, baseline understanding of—baseline metrics, and baseline of what you need to check in terms of different kinds of services you're trying to monitor is your starting point. And the mistake people make is that they don't have a baseline. So, we do not have a baseline; they just install a monitoring tool, configure a CloudWatch, and they don't know the problem they're trying to solve [laugh] and that can lead to a lot of confusion.Corey: So, what inspired you from, I guess, kicking the tires on CloudWatch—the way that we all do—and being frustrated and confused by it, all the way to the other side of writing a book on it? What was it that got you to that point? Were you an expert on CloudWatch before you started writing the book, or was it, “Well, by the time this book is done, I will certainly know [laugh] more about the service than I did when I started.”Ewere: Yeah, I think it's a double-edged sword. [laugh]. So, it's a combination of the things you just said. So, first of all, I have experienced with other monitoring tools; I have love for reliability and scalability of a system. I started Kubernetes at some of the early times Kubernetes came out, when it was very difficult to deploy, when it was very difficult to set up.Because I'm looking at how I can make systems a little bit more efficient, a little bit more reliable than having to handle a lot of things like auto-scaling, having to go through the process of understanding how to scale. I mean, that's a school of its own that you need to prepare yourself for. So, first of all, I have a love for making sure systems are reliable and efficient, and second of all, I also want to make sure that I know what is going on with my system per time, as much as possible. The level of visibility of a system gives you the level of control and understanding of what your system is doing per time. So, those two things are very core to me.And then thirdly, I had a plan of a streak of books I want to write based on AWS, and just like monitoring is something that is just new. I mean, if you go to the package website, this is the first book on infrastructure monitoring AWS with CloudWatch; it's not a very common topic to talk about. And I have other topics in my head, and I really want to talk about things like networking, and other topics that you really need to go deep inside to be able to appreciate the value of what you see in there with all those scenarios because in this book, every chapter, I created a scenario of what a real-life monitoring system or what you need to do looks like. So, being that I have those premonitions, I know that whenever it came to, you know, to share with the world what I know in monitoring, what I've learned in monitoring, I took a [unintelligible 00:12:26]. And then secondly, as this opportunity for me to start telling the world about the things I learned, and then I also learned while writing the book because there are certain topics in the book that I'm not so much of an expert in things, like big data and all that.I had to also learn; I had to take some time to do more research, to do more understanding. So, I use CloudWatch, okay? I'm kind of good in CloudWatch, and also, I also had to do more learning to be able to disseminate this information. And also, hopefully, X-Ray some parts of monitoring and different services that people do not really pay so much attention into.Corey: What do you find that is still the most, I guess, confusing to you as you take a look across the ecosystem of the entire CloudWatch space? I mean, every time I play with it, I take a look, and I get lost in, “Oh, they have contributor analyses, and logs, and metrics.” And it's confusing, and every time I wind up, I guess, spiraling out of control. What do you find that, after all of this, is a lot easier for you, and what do you find that's a lot more understandable?Ewere: I'm still going to go back to the containers part. I'm sorry, I'm in love containers. [laugh].Corey: No, no, it's fair. Containers are very popular. Everyone loves them. I'm just basically anti-container based upon no better reason than I'm just stubborn and bloody-minded most of the time.Ewere: [laugh]. So, pretty much like I said, I kind of had experience with other monitoring tools. Trust me, if you want to configure proper container monitoring for other tools, trust me, it's going to take you at least a week or two to get it properly, from the dashboards, to the login configurations, to the piping of the data to the proper storage engine. These are things I talked about in the book because I took monitoring from the ground up. I mean, if you've never done monitoring before, when you take my book, you will understand the basic principles of monitoring.And [funny 00:14:15], you know, monitoring has some big data process, like an ETL process: extraction, transformation, and writing of data into an analytic system. So, first of all, you have to battle that. You have to talk about the availability of your storage engine. What are you using? An Elasticsearch? Are you using an InfluxDB? Where do you want to store your data? And then you have to answer the question of how do I visualize the data? What method do I realize this data? What kind of dashboards do I want to use? What methods of representation do I need to represent this data so that it makes sense to whoever I'm sharing this data with. Because in monitoring, you definitely have to share data with either yourself or with someone else, so the way you present the data needs to make sense. I've seen graphs that do not make sense. So, it requires some level of skill. Like I said, I've [unintelligible 00:15:01] where I spent a week or two having to set up dashboards. And then after setting up the dashboard, someone was like, “I don't understand, and we just need, like, two.” And I'm like, “Really?” [laugh]. You know? Because you spend so much time. And secondly, you discover that repeatability of that process is a problem. Because some of these tools are click and drag; some of them don't have JSON configuration. Some do, some don't. So, you discover that scalability of this kind of system becomes a problem. You can't repeat the dashboards: if you make a change to the system, you need to go back to your dashboard, you need to make some changes, you need to update your login, too, you need to make some changes across the layer. So, all these things is a lot of overhead [laugh] that you can cut off when you use things like Container Insights in CloudWatch—which is a feature of CloudWatch. So, for me, that's a part that you can really, really suck out so much juice from in a very short time, quickly and very efficiently. On the flip side, when you talk about monitoring for big data services, and monitoring for a little bit of serverless, there might be a little steepness in the flow of the learning curve there because if you do not have a good foundation in serverless, when you get into [laugh] Lambda Insights in CloudWatch, trust me, you're going to be put off by that; you're going to get a little bit confused. And then there's also multifunction insights at the moment. So, you need to have some very good, solid foundation in some of those topics before you can get in there and understand some of the data and the metrics that CloudWatch is presenting to you. And then lastly, things like big data, too, there are things that monitoring is still being properly fleshed out. Which I think that in the coming months and years to come, they will become more proper and they will become more presentable than they are at the moment.Corey: This episode is sponsored by our friends at Oracle HeatWave is a new high-performance accelerator for the Oracle MySQL Database Service. Although I insist on calling it “my squirrel.” While MySQL has long been the worlds most popular open source database, shifting from transacting to analytics required way too much overhead and, ya know, work. With HeatWave you can run your OLTP and OLAP, don't ask me to ever say those acronyms again, workloads directly from your MySQL database and eliminate the time consuming data movement and integration work, while also performing 1100X faster than Amazon Aurora, and 2.5X faster than Amazon Redshift, at a third of the cost. My thanks again to Oracle Cloud for sponsoring this ridiculous nonsense.Corey: The problem I've always had with dashboards is it seems like managers always want them—“More dashboards, more dashboards”—then you check the usage statistics of who's actually been viewing the dashboards and the answer is, no one since you demoed it to the execs eight months ago. But they always claim to want more. How do you square that?I guess, slicing between what people asked for and what they actually use.Ewere: [laugh]. So yeah, one of the interesting things about dashboards in terms of most especially infrastructure monitoring, is the dashboards people really want is a revenue dashboards. Trust me, that's what they want to see; they want to see the money going up, up, up, [laugh] you know? So, when it comes to—Corey: Oh, yes. Up and to the right, then everyone's happy. But CloudWatch tends to give you just very, very granular, low-level metrics of thing—it's hard to turn that into something executives care about.Ewere: Yeah, what people really care about. But my own take on that is, the dashboards are actually for you and your team to watch, to know what's going on from time to time. But what is key is setting up events across very specific and sensitive data. For example, when any kind of sensitive data is flowing across your system and you need to check that out, then you tie a metric to that, and in turn alarm to it. That is actually the most important thing for anybody.I mean, for the dashboards, it's just for you and your team, like I said, for your personal consumption. “Oh, I can see all the RDS connections are getting too high, we need to upgrade.” Oh, we can see that all, the memory, there was a memory spike in the last two hours. I know that's for you and your team to consume; not for the executive team. But what is really good is being able to do things like aggregate data that you can share.I think that is what the executive team would love to see. When you go back to the core principles of DevOps in terms of the DevOps Handbook, you see things like a mean time to recover, and change failure rate, and all that. The most interesting thing is that all these metrics can be measured only by monitoring. You cannot change failure rates if you don't have a monitoring system that tells you when there was a failure. You cannot know your release frequency when you don't have a metric that measures number of deployments you have and is audited in a particular metric or a particular aggregator system.So, we discovered that the four major things you measure in DevOps are all tied back to monitoring and metrics, at minimum, to understand your system from time to time. So, what the executive team actually needs is to get a summary of what's going on. And one of the things I usually do for almost any company I work for is to share some kind of uptime system with them. And that's where CloudWatch Synthetics Canary come in. So, Synthetic Canary is a service that helps you calculate that helps you check for uptime of the system.So, it's a very simple service. It does a ping, but it is so efficient, and it is so powerful. How is it powerful? It does a ping to a system and it gets a feedback. Now, if the status code of your service, it's not 200 or not 300, it considers it downtime.Now, when you aggregate this data within a period of time, say a month or two, you can actually use that data to calculate the uptime of your system. And that uptime [unintelligible 00:19:50] is something you can actually share to your customers and say, “Okay, we have an SLA of 99.9%. We have an SLA of 99.8%.” That data should not be doctored data; it should not be a data you just cook out of your head; it should be based on your system that you have used, worked with, monitored over a period of time so that the information you share with your customers are genuine, they are truthful, and they are something that they can also see for themselves.Hence companies are using [unintelligible 00:20:19] like status page to know what's going on from time to time whenever there is an incident and report back to their customers. So, these are things that executives will be more interested in than just dashboards, [laugh] dashboards, and more dashboards. So, it's more or less not about what they really ask for, but what you know and what you believe you are going to draw value from. I mean, an executive in a meeting with a client and says, “Hey, we got a system that has 99.9% uptime.”He opens the dashboard or he opens the uptime system and say, “You see our uptime? For the past three months, this has been our metric.” Boom. [snaps fingers]. That's it. That's value, instantly. I'm not showing [laugh] the clients and point of graphs, you know? “Can you explain the memory metric?” That's not going to pass the message, send the message forward.Corey: Since your book came out, I believe, if not, certainly by the time it was finished being written and it was in review phase, they came out with Managed Prometheus and Managed Grafana. It looks almost like they're almost trying to do a completely separate standalone monitoring stack of AWS tooling. Is that a misunderstanding of what the tools look like, or is there something to that?Ewere: Yeah. So, I mean by the time those announced at re:Invent, I'm like, “Oh, snap.” I almost told my publisher, “You know what? We need to add three more chapters.” [laugh]. But unfortunately, we're still in review, in preview.I mean, as a Hero, I kind of have some privilege to be able to—a request for that, but I'm like, okay, I think it's going to change the narrative of what the book is talking about. I think I'm going to pause on that and make sure this finishes with the [unintelligible 00:21:52], and then maybe a second edition, I can always attach that. But hey, I think there's trying to be a galvanization between Prometheus, Grafana, and what CloudWatch stands for. Because at the moment, I think it's currently on pre-release, it's not fully GA at the moment, so you can actually use it. So, if you go to Container Insights, you can see that you can still get how Prometheus and Grafana is presenting the data.So, it's more or less a different view of what you're trying to see. It's trying to give you another perspective of how your data is presented. So, you're going to have CloudWatch: it's going to have CloudWatch dashboards, it's going to have CloudWatch metrics, but hey, this different tools, Prometheus, Grafana, and all that, they all have their unique ways of presenting the data. And part of the reason I believe AWS has Prometheus and Grafana there is, I mean, Prometheus is a huge cloud-native open-source monitoring, presentation, analytics tool; it packs a lot of heat, and a lot of people are so used to it. Everybody like, “Why can't I have Prometheus in CloudWatch?”I mean—so instead of CloudWatch just being a simple monitoring tool, [unintelligible 00:22:54] CloudWatch has become an ecosystem of monitoring tool. So, we got—we're not going to see cloud [unintelligible 00:23:00], or just [unintelligible 00:23:00] log, analytics, metrics, dashboards, no. We're going to see it as an ecosystem where we can plug in other services, and then integrate and work together to give us better performance options, and also different perspectives to the data that is being collected.Corey: What do you think is next, as you take a look across the ecosystem, as far as how people are thinking about monitoring and observability in a cloud context? What are they missing? Where's the next evolution lead?Ewere: Yeah, I think the biggest problem with monitoring, which is part of the introduction part of the book, where I talked about the basic types of monitoring—which is proactive and reactive monitoring—is how do we make sure we know before things happen? [laugh]. And one of the things that can help with that is machine learning. There is a small ecosystem that is not so popular at the moment, which talks about how we can do a lot of machine learning in DevOps monitoring observability. And that means looking at historic data and being able to predict on the basic level.Looking at history, [then are 00:24:06] being able to predict. At the moment, there are very few tools that have models running at the back of the data being collected for monitoring and metrics, which could actually revolutionize monitoring and observability as we see it right now. I mean, even the topic of observability is still new at the moment. It's still very integrated. Observability just came into Cloud, I think, like, two years ago, so it's still being matured.But one thing that has been missing is seeing the value AI can bring into monitoring. I mean, this much [unintelligible 00:24:40] practically tell us, “Hey, by 9 p.m. I'm going to go down. I think your CPU or memory is going down. I think I'm line 14 of your code [laugh] is a problem causing the bug. Please, you need to fix it by 2 p.m. so that by 6 p.m., things can run perfectly.” That is going to revolutionize monitoring. That's going to revolutionize observability and bring a whole new level to how we understand and monitor the systems.Corey: I hope you're right. If you take a look right now, I guess, the schism between monitoring and observability—which I consider to be hipster monitoring, but they get mad when I say that—is there a difference? Is it just new phrasing to describe the same concepts, or is there something really new here?Ewere: In my book, I said, monitoring is looking at it from the outside in, observability is looking at it from the inside out. So, what monitoring does not see under, basically, observability sees. So, they are children of the same mom. That's how I put it. One actually needs the other and both of them cannot be separated from each other.What we've been working with is just understanding the system from the surface. When there's an issue, we go to the aggregated results that come out of the issue. Very basic example: you're in a Java application, and we all know Java is very memory intensive, on the very basic layer. And there's a memory issue. Most times, infrastructure is the first hit with the resultant of that.But the problem is not the infrastructure, it's maybe the code. Maybe garbage collection was not well managed; maybe they have a lot of variables in the code that is not used, and they're just filling up unnecessary memory locations; maybe there's a loop that's not properly managed and properly optimized; maybe there's a resource on objects that has been initialized that has not been closed, which will cause a heap in the memory. So, those are the things observability can help you track. Those are the things that we can help you see. Because observability runs from within the system and send metrics out, while basic monitoring is about understanding what is going on on the surface of the system: memory, CPU, pushing out logs to know what's going on and all that.So, on the basic level, observability helps gives you, kind of, a deeper insight into what monitoring is actually telling you. It's just like the result of what happened. I mean, we are told that the symptoms of COVID is coughing, sneezing, and all that. That's monitoring. [laugh].But before we know that you actually have COVID, we need to go for a test, and that's observability. Telling us what is causing the sneezing, what is causing the coughing, what is causing the nausea, all the symptoms that come out of what monitoring is saying. Monitoring is saying, “You have a cough, you have a runny nose, you're sneezing.” That is monitoring. Observability says, “There is a COVID virus in the bloodstream. We need to fix it.” So, that's how both of them act.Corey: I think that is probably the most concise and clear definition I've ever gotten on the topic. If people want to learn more about what you're up to, how you view about these things—and of course, if they want to buy your book, we will include a link to that in the [show notes 00:27:40]—where can they find you?Ewere: I'm on LinkedIn; I'm very active on LinkedIn, and I also shared the LinkedIn link. I'm very active on Twitter, too. I tweet once in a while, but definitely, when you send me a message on Twitter, I'm also going to be very active.I also write blogs on Medium, I write a couple of blogs on Medium, and that was part of why AWS recognized me as a Hero because I talk a lot about different services, I help with comparing services for you so you can choose better. I also talk about setting basic concepts, too; if you just want to get your foot wet into some stuff and you need something very summarized, not AWS documentation per se, something that you can just look at and know what you need to do with the service, I talk about them also in my blogs. So yeah, those are the two basic places I'm in: LinkedIn and Twitter.Corey: And we will, of course, put links to that in the [show notes 00:28:27]. Thank you so much for taking the time to speak with me. I appreciate it.Ewere: Thanks a lot.Corey: Ewere Diagboya, head of cloud at My Cloud Series. I'm Cloud Economist Corey Quinn, and this is Screaming in the Cloud. If you've enjoyed this podcast, please leave a five-star review on your podcast platform of choice, whereas if you hated this podcast, please leave a five-star review on your podcast platform of choice along with a comment telling me how many more dashboards you would like me to build that you will never look at.Corey: If your AWS bill keeps rising and your blood pressure is doing the same, then you need The Duckbill Group. We help companies fix their AWS bill by making it smaller and less horrifying. The Duckbill Group works for you, not AWS. We tailor recommendations to your business and we get to the point. Visit duckbillgroup.com to get started.Announcer: This has been a HumblePod production. Stay humble.
On today's episode, Kunle is joined by Erik Huberman, Founder & CEO of Hawke Media, a LA-based full-service marketing consultancy. The company has serviced over 2000 brands of all sizes, ranging from startups to household names like Red Bull, Verizon, and Alibaba.Businesses traditionally make annual plans for functions like Finance, HR and Marketing. Marketing, like everything else, is measured month-on-month. But this traditional way of planning and reporting could very well be holding you back. With access to tons of real time data and tools to analyse this data, the game has changed. If you aren't taking an iterative approach to your marketing plans then you risk getting left behind.In this episode, Kunle and Erik talk about leveraging marketing data to create an iterative marketing strategy. You will get to hear about the 3 pillars of the Hawke Method, fallout of privacy-driven changes, best channels for raising brand awareness and nurturing your audience, and what could be in store for us in Q4. This is a great episode for marketers and business owners.-----------SPONSORS:This episode is brought to you by:Klaviyo This episode is brought to you by Klaviyo – a growth marketing platform that powers over 25,000 online businesses. Direct-to-Consumer brands like ColourPop, Huckberry, and Custom Ink rely on Klaviyo.Klaviyo helps you own customer experience and grow high-value customer relationships right from a shopper's first impression through to each subsequent purchase, Klaviyo understands every single customer interaction and empowers brands to create more personalized marketing moments.Find out more on klaviyo.com/2x. RewindThis episode is brought to you by Rewind - the #1 Backup and Recovery App for Shopify and BigCommerce stores that powers over 80,000 online businesses.Direct-to-Consumer brands like Gymshark and MVMT Watches rely on Rewind.Cloud based ecommerce platforms like Shopify and BigCommerce do not have automatic backup features. Rewind protects your store against human error, misbehaving apps, or collaborators gone bad with Automatic backups!For a free 30-day trial, Go to Rewind Backups, reach out to the Rewind team via chat or email and mention '2x ecommerce'GorgiasThis episode is brought to you by Gorgias, the leading helpdesk for Shopify, Magento and BigCommerce merchants. Gorgias combines all your communication channels including email, SMS, social media, livechat, and phone, into one platform.This saves your team hours per day & makes managing customer orders a breeze. It also integrates seamlessly with your existing tech stack, so you can access customer information and even edit, return, refund or create an order, right from your helpdesk.Go to Gorgias.com and mention 2x ecommerce podcast for two months free.CloudwaysCloudways is the hosting platform of choice for thousands of ecommerce merchants, SMBs, and agencies all around the globe. They offer a high-performing custom stack, top-notch security, the choice between 5 cloud solution providers, ease of scalability, affordable pricing plans, and so much more.Cloudways also offers support for all PHP-based applications like Magento, WooCommerce, WordPress, Laravel, and others.Experience an unbeatable managed cloud hosting experience with Cloudways today. For a $20 Free Hosting Credit use the Coupon code: **BOOSTMAG**
Topics: Estrangement, Affairs, Borderline, PTSD, Childhood Trauma, Dating, Controllers Hosts: Becky Brown, Dr. Alice Benton, Chris Williams Caller Questions: My dad died a few years ago; should I pursue a relationship with my toxic stepmother if she hasn't responded to me since then? How do I fix myself 20yrs after my husband had an affair and a child? What is the best treatment The post New Life Live: October 14, 2021 appeared first on New Life.
Tony Robinson (@da_667) Thought we'd put in a little news to round out the show https://www.bbc.com/news/world-us-canada-58863678 - nuclear secrets hidden in a peanut butter sandwich https://www.theregister.com/2018/04/20/rsa_security_conference_insecure_mobile_app/ https://www.vice.com/en/article/jg8w9b/the-twitch-hack-is-worse-for-streamers-than-for-twitch https://nakedsecurity.sophos.com/2021/10/08/apache-patch-proves-patchy-now-you-need-to-patch-the-patch/ https://www.securityweek.com/fontonlake-linux-malware-used-targeted-attacks https://securityaffairs.co/wordpress/123182/breaking-news/medtronic-recalled-insulin-pumps-controllers.html Similar device on ebay: https://www.ebay.com/itm/324762812721 https://www.zdnet.com/article/brewdog-exposed-data-of-200000-shareholders-for-over-a-year/ https://tpetersonkth.github.io/cve/2021/10/02/Analysis-of-CVE-2019-9053.html https://0xdf.gitlab.io/ www.leanpub.com/avatar2 MSRP = $30 USD Book changes What is the end goal? Upskill? Independent consultant? Promotion? Bug bounties? Lab setup - Lab setup types Cloud based - Desktop/laptop/NUC - Server - Good VMs to https://developer.microsoft.com/en-us/microsoft-edge/tools/vms/ - 90 day WIndows machines What other home lab equipment have would be helpful?Testing IoT/embedded devices? Car hacking? Malware analysis? https://bazaar.abuse.ch/ Virus Total Intelligence Honeypots @malware_traffic - https://twitter.com/malware_traffic/status/1446627364147023877 Analyzing binaries? Patch analysis (patch tuesday, print nightmare, etc)? https://wumb0.in/extracting-and-diffing-ms-patches-in-2020.html https://www.netresec.com/?page=networkminer Soldering? Oscillators for voltage checks? Wireless? Old cellphones (mobile apps, don't need cellular) Personal assistant devices (used IoT devices?) Accessing data stored on devices Specific software licenses? Burp? If I'm trying to break into infosec, how do I use my lab to sell myself to an employer? Does the employer care? How can someone show what they've learned in a way that shows the value?
This week on the podcast, we start in Sportsball where the Ravens have a huge comeback win over the Colts on Monday Night Football, and Jon Gruden e-mails leak which show a long history of racism, sexism, and homophobia. We ask when we can expect to see more e-mails from other higher ups in the league, and wonder if we will see Kyrie Irving at all this season after NYC keeps him from playing any home games until he gets vaccinated, at a cost to him of $380,000 a game. After that we get into the news of January 6th subpoenas, the cause of death is announced in the Gabby Petito case, and is Southwest Airlines going to the unvaccinated airline? OTA Podcast Episode 392: Three Yards and a Cloud of Epithets Find more O The Anthem OTheAnthem.com facebook.com/OTheAnthem twitter.com/OTheAnthem instagram.com/OTheAnthem Cover image includes work originally attributed to Travis AFB on Flickr https://www.flickr.com/photos/99847360@N07/43899578092
Topics: Teens, Suicide, Depression, Dating Hosts: Steve Arterburn, Becky Brown, Dr. Jill Hubbard Caller Questions: How do I help my ADHD teen daughter who is depressed, anxious, and tried to take her life? I'm in a new dating relationship, and a friend I used to have feelings for came to me and told me now she has feelings for me. What The post New Life Live: October 13, 2021 appeared first on New Life.
In today's episode, Gerhard is talking to Sam Alba, Docker's first employee, and Solomon Hykes, the Docker co-founder. Together with Andrea Luzzardi, they are the creators of Dagger, a universal deployment engine that trades YAML for CUE, and uses Buildkit as the runtime. Why? Because we should stop rewriting the same application deployment logic in scripts, makefiles or continuous delivery configuration. That's right, this is the YAML vaccine that we have all been waiting for. Gerhard believes that one day, Dagger will become just as meaningful for application delivery, as Docker is today for application code.
In this episode of RadioFreeHPC, a full discussion on quantum computing, its applications, and what the world might look like in the quantum age. RadioFreeHPC is made possible by a grant from the Barnum & Baily Foundation for Good Scientific Understand and Stuff and distributed in partnership with HPCwire. *Download the MP3 * Follow us… Read More »World of Quantum
Author Anthony Doerr won the Pulitzer Prize in Fiction for his 2014 novel All The Light We Cannot See. His new novel, Cloud Cuckoo Land, tells a story spanning centuries and continents from fifteenth century Constantinople to present day Idaho. He joins us to discuss.
About TimTim's tech career spans over 20 years through various sectors. Tim's initial journey into tech started as a US Marine. Later, he left government contracting for the private sector, working both in large corporate environments and in small startups. While working in the private sector, he honed his skills in systems administration and operations for largeUnix-based datastores.Today, Tim leverages his years in operations, DevOps, and Site Reliability Engineering to advise and consult with clients in his current role. Tim is also a father of five children, as well as a competitive Brazilian Jiu-Jitsu practitioner. Currently, he is the reigning American National and 3-time Pan American Brazilian Jiu-Jitsu champion in his division.Links: Twitter: https://twitter.com/elchefe The Duckbill Group: https://duckbillgroup.com TranscriptAnnouncer: Hello, and welcome to Screaming in the Cloud with your host, Chief Cloud Economist at The Duckbill Group, Corey Quinn. This weekly show features conversations with people doing interesting work in the world of cloud, thoughtful commentary on the state of the technical world, and ridiculous titles for which Corey refuses to apologize. This is Screaming in the Cloud.Corey: This episode is sponsored in part by Honeycomb. When production is running slow, it's hard to know where problems originate: is it your application code, users, or the underlying systems? I've got five bucks on DNS, personally. Why scroll through endless dashboards, while dealing with alert floods, going from tool to tool to tool that you employ, guessing at which puzzle pieces matter? Context switching and tool sprawl are slowly killing both your team and your business. You should care more about one of those than the other, which one is up to you. Drop the separate pillars and enter a world of getting one unified understanding of the one thing driving your business: production. With Honeycomb, you guess less and know more. Try it for free at Honeycomb.io/screaminginthecloud. Observability, it's more than just hipster monitoring.Corey: Welcome to Screaming in the Cloud. I'm Corey Quinn. Periodically, I have a whole bunch of guests come on up, second time. Now, it's easy to take the naive approach of assuming that it's because it's easier for me to find a guest if I know them and don't have to reach out to brand new people all the time. This is absolutely correct; I'm exceedingly lazy. But I don't have too many folks on a third time, but that changes today.My guest is Tim Banks. I've had him on the show twice before, both times it led to really interesting conversations around a wide variety of things. Since those episodes, Tim has taken the job as a principal cloud economist here at The Duckbill Group. Yes, that is probably the strangest interview process you can imagine, but here we are. Tim, thank you so much for joining me both on the show and in the business.Tim: My pleasure, Corey. It was definitely an interesting interview process, you know, but I was glad to be here. So, I'm happy to be here a third time. I don't know if you get a jacket like you do in Saturday Night Live, if you host, like, a fifth time, but we'll see. Maybe it's a vest. A cool vest would be nice.Corey: We can come up with something.[ effectively, it can be like reverse hangman where you wind up getting a vest and every time you come on after that you get a sleeve, then you get a second sleeve, and then you get a collar, and we can do all kinds of neat stuff.Tim: I actually like that idea a lot.Corey: So, I'm super excited to be able to have this conversation with you because I don't normally talk a lot on this show about what cloud economics is because my guest usually is not as deep into the space as I am, and that's fine; people should never be as deep into this space as I am, in the general sense, unless they work here. Awesome. But I do guest on other shows, and people ask me all kinds of questions about AWS billing and cloud economics, and that's fine, it's great, but they don't ask the questions about the space in the same way that I would and the way that I think about it. So, it's hard for me to interview myself. Now, I'm not saying I won't try it someday, but it's challenging. But today, I get to take the easy path out and talk to you about it. So Tim, what the hell is a principal cloud economist?Tim: So, a principal cloud economist, is a cloud computing expert, both in architecture and practice, who looks at cloud cost in the same way that a lot of folks look at cloud security, or cloud resilience, or cloud performance. So, the same engineering concerns you have about making sure that your API stays up all the time, or to make sure that you don't have people that are able to escape containers or to make sure that you can have super, super low response times, is the same engineering fundamentals that I look at when I'm trying to find a way to reduce your AWS bill.Corey: Okay. When we say cloud cost and cloud economics, the natural picture that leads to mind is, “Oh, I get it. You're an Excel jockey.” And sometimes, yeah, we all kind of play those roles, but what you're talking about is something else entirely. You're talking about engineering expertise.And sure enough, if you look at the job postings we have for roles on the team from time to time, we have not yet hired anyone who does not have an engineering and architecture background. That seems odd to folks who do not spend a lot of time thinking about the AWS bill. I'm told those people are what is known as ‘happy.' But here we are. Why do we care about the engineering aspect of any of this?Tim: Well, I think first and foremost because what we're doing in essence, is still engineering. People aren't putting construction paper up on [laugh] AWS; sometimes they do put recipes up on there, but it still involves working on a computer, and writing code, and deploying it somewhere. So, to have that basic understanding of what it is that folks are doing on the platform, you have to have some engineering experience, first and foremost. Secondly, the fact of the matter is that most cost optimization, in my opinion, can be done on the whiteboard, before anything else, and really I think should be done on the whiteboard before anything else. And so the Excel aspect of it is always reactive. “We have now spent this much. How much was it? Where did it go?” And now we have to figure out where it went.I like to figure out and get a ballpark on how much something is going to cost before I write the first line of code. I want to know, hey, we have a tier here, we're using this kind of storage, it's going to take this kind of instance types. Okay, well, I've got an idea of how much it's going to cost. And I was like, “You know, that's going to be expensive. Before we do anything, is there a way that we can reduce costs there?”And so I'm reverse engineering that on already deployed workloads. Or when customers want to say, “Hey, we were thinking about doing this, and this is our proposed architecture,” I'm going to look at it and say, “Well, if you do this and this and this and this, you can save money.”Corey: So, it sounds like you and I have a bit of a philosophical disagreement in some ways. One of my recurring talking points has always been that, “Oh, by and large, application developers don't need to think overly much about cloud cost. What they need to know generally fits on an index card.” It's, okay, big things cost more than small things; if you turn something on, it will never get turned off and will bill you in perpetuity; data transfer has some weird stuff; and if you store data, you pay for data, like, that level of baseline understanding. When I'm trying to build something out my immediate thought is, great, is this thing possible?Because A, I don't always know that it is, and B, I'm super bad at computers so for me, it may absolutely not be, whereas you're talking about baking cost assessments into the architecture as a day one type of approach, even when sketching ideas out on the whiteboard. I'm curious as to how we diverge there. Can you talk more about your philosophy?Tim: Sure. And the reason I do that is because, as most folks that have an engineering background in cloud infrastructure will tell you, you want to build resilience in, on the whiteboard. You certainly want to build performance in, on the whiteboard, right? And security folks will tell you you want to do security on the whiteboard. Because those things are hard to fix after they're deployed.As soon as they're deployed, without that, you now have technical debt. If you don't consider cost optimization and cost efficiency on the whiteboard, and then you try and do it after it's deployed, you not only have technical debt, you may have actual real debt.Corey: One of the comments I tend to give a lot is that architecture and cost are the same thing in the world of cloud. And I think that we might be in violent agreement, as Liz Fong-Jones is fond of framing it, where I am acutely aware of aspects of cost and that does factor into how I build things on the whiteboard—let's also be very clear, most of the things that I build are very small scale; the largest cost by a landslide is the time I spend building it—in practice, that's an awful lot of environments; people are always more expensive than the AWS environment they're working on. But instead, it's about baking in the assumptions and making sure you're not coming up with something that is going to just be wasteful and horrible out of the gate, and I guess part of that also is the fact that I am at a level of billing understanding that I sort of absorbed these concepts intrinsically. Because to me, there is no difference between cost and architecture in an environment like this. You're right, there's always an inherent trade-off between cost and durability. On the one hand, I don't like that. On the other, it feels like it's been true forever and I don't see a way out of it.Tim: It is inescapable. And it's interesting because you talk about the level of an application developer or something like that, like what is your level of concern, but retroactively, we'll go in for cost optimization houses—and I've done this as far back as when I was working at AWS has a TAM—and I'll ask the question to an application developer or database administrator, and I'm like, “Why do you do this? What do you have a string value for something that could be a Boolean?” And you'll ask, “Well, what difference does that make?” Well, it makes a big difference when you're talking about cycles for CPU.You can reduce your CPU consumption on a database instance by changing a string to a Boolean, you need fewer instances, or you need a less powerful instance, or you need less memory. And now you can run a less expensive instance for your database architecture. Well, maybe for one node it's not that biggest difference, but if you're talking about something that's multi-AZ and multi-node, I mean, that can be a significant amount of savings just by making one simple change.Corey: And that might be the difference right there. I didn't realize that, offhand. It makes sense if you think about it, but just realizing that I've made that mistake on one of my DynamoDB tables. It costs something like seven cents a month right now, so it's not something I'm rushing to optimize, but you're right, expand that out by a factor of a million or so, and we're talking serious money, and then that sort of optimization makes an awful lot of sense. I think that my position on it is that when you're building out something small scale as a demo or a proof of concept, spending time on optimizations like this is not the best use of anyone's time or brain sweat, for lack of a better term. How do you wind up deciding when it's time to focus on stuff like that?Tim: Well, first, I will say that—I daresay that somewhere in the 80% of production workloads are just—were the POC, [laugh] right? Because, like, “It worked for this to get funding, let's run it,” right?Corey: Let they who does not have a DynamoDB table in production with the word ‘test' or ‘dev' in it cast the first stone.Tim: It's certainly not me. So, I understand how some of those decisions get made. And that's why I think it's better to think about it early. Because as I mentioned before, when you start something and say, “Hey, this works for now,” and you don't give consideration to that in the future, or consideration for what it's going to be like in the future, and when you start doing it, you'll paint yourself into corners. That's how you get something like static values put in somewhere, or that's how you get something like, well, “We have to run this instance type because we didn't build in the ability to be more microservice-based or stateless or anything like that.”You've seen people that say, “Hey, we could save you a lot of money if you can move this thing off to a different tier.” And it's like, “Well, that would be an extensive rewrite of code; that'd be very expensive.” I daresay that's the main reason why most AS/400s are still being used right now is because it's too expensive to rewrite the code.Corey: Yeah, and there's no AWS/400 that they can migrate to. Yet. Re:Invent is nigh.Tim: So, I think that's why, even at the very beginning, even if you were saying, “Well, this is something we will do later.” Don't make it impossible for you to do later in your code. Don't make it impossible for you to do later in your architecture. Make things as modular as possible, so that way you can say, “Hey”—later on down the road—“Oh, we can switch this instance type.” Or, “Here's a new managed service that we can maybe save money on doing this.”And you allow yourself to switch things out, or turn different knobs, or change the way you do things, and give yourself more options in the future, whether those options are for resilience, or those options or for security, or those options are for performance, or they're for cost optimizations. If you make binding decisions earlier on, you're going to have debt that's going to build up at some point in the future, and then you're going to have to pay the piper. Sometimes that piper is going to be AWS.Corey: One thing that I think gets lost in a lot of conversations about cloud economics—because I know that it happened to me when I first started this place—where I am planning to basically go out and be the world's leading expert in AWS cost analysis and understanding and optimization. Great. Then I went out into the world and started doing some of my first engagements, and they looked a lot less like far-future cost attribution projections and a lot more like, “What's a reserved instance?” And, “We haven't bought any of those in 18 months.” And, “Oh, yeah, we shut down an entire project six months ago. We should probably delete all the resources, huh?”The stuff that I was preparing for at the high end of the maturity curve are great and useful and terrific to have conversations about in some very nuanced depth, but very often there's a walk before you can run style of conversation where, okay, let's do the easy stuff first before we start writing a whole bunch of bespoke internal stuff that maps your business needs to the AWS bill. How do you, I guess, reconcile those things where you're on the one hand, you see the easy stuff and on the other, you see some of the just the absolutely challenging, very hard, five-years-of-engineering-effort-style problems on the other?Tim: Well, it's interesting because I've seen one customer very recently who has brilliant analyses as to their cost; just well-charted, well-tagged, well-documented, well—you know, everything is diagrammed quite nicely and everything like that, and they're very, very aware of their costs, but they leave test instances running all weekend, you know, and their associated volumes and things like that. And that's a very easy thing to fix. That is a very, very low-hanging fruit. And so sometimes, you just have to look at where they're spending their efforts where sometimes they do spend so much time chasing those hard to do things because they are hard to do and they're exciting in an engineering aspect, and then something as simple as, “Hey, how about we delete these old volumes?” It just isn't there.Or, “How about we switch to your S3 bucket storage type?” Those are easy, low-hanging fruits, and you would be surprised how sometimes they just don't get that. But at the same time, sometimes customers have, like, “Hey, we could knock this thing out, we knock this thing out,” because it's Trusted Advisor. Every AI cost optimization recommendation you can get will tell you these five things to do, no matter who you are or where you are, but they don't do the conceptual things like understanding some of the principles behind cost optimization and cost optimization architecture, and proactive cost optimization versus react with cost optimizations. So, you're doing very conceptual education and conversations with folks rather than the, “Do these five things.” And I've not often found a customer that you have to do both on; it's usually one or the other.Corey: It's funny that you made that specific reference to that example. One of my very first projects—not naming names. Generally, when it comes to things like this, you can tell stories or you can name names; I bias for stories—I was talking to a company who was convinced that their developer environments were incredibly overwrought, expensive, et cetera, and burning money. Okay, great. So, I talked about the idea of turning those things off at night or between test runs, deleting volumes to snapshot, and restore them on a schedule when people come in in the morning because all your developers sit in the same building in the same time zones. Great. They were super on board with the idea, and it was going to be a little bit of work, but all right, this was in the days before the EC2 Instance Scheduler, for example.But first, let's go ahead and do some analysis. This is one of those early engagements that really reinforced my idea of, yeah, before we start going too far down the rabbit hole, let's double-check what's going on in the account. Because periodically you encounter things that surprise people. Like, “What's up with those Australia instances?” “Oh, we don't have anything in that region.” “I believe you're being sincere when you say this, however, the API generally doesn't tell lies.”So, that becomes a, oh, security incident time. But looking at this, they were right; they had some fairly sizable developer instances that were running all the time, but doing some analysis, their developer environment was 3% of their bill at the time and they hadn't bought RIs in a year-and-a-half. And looking at what they were doing, there was so much easier stuff that they could do to generate significant savings without running the potential of turning a developer environment off at night in the middle of an incident or something like that. The risk factor and effort were easier just do the easy stuff, then do another pass and look at the deep stuff. And to be clear, they weren't lying to me; they weren't wrong.Back when they started building this stuff out, their developer environments were significantly large and were a significant portion of their spend. And then they hit product-market fit, and suddenly their production environment had to scale significantly in a short period of time. Which, yay, cloud. It's good at that. Then it just became such a small portion that developer environments weren't really a thing. But the narrative internally doesn't get updated very often because once people learn something, they don't go back to relearn whether or not it's still true. It's a constant mistake; I make it myself frequently.Tim: I think it's interesting, there are things that we really need to put into buckets as far as what's an engineering effort and what's an administrative effort. And when I say ‘administrative effort,' I mean if I can save money with a stroke of a pen, well, that's going to be pretty easy, and that's usually going to be RIs; that's going to be EDPs, or PPAs or something like that, that don't require engineering effort. It just requires administrative effort, I think RIs being the simplest ones. Like, “Oh, all I have to do is go in here and click these things four times and I'm going to save money?” “Well, let's do that.”And it's surprising how often people don't do that. But you still have to understand that, and whether it's RIs or whether it's a savings plan, it's still a commitment of some kind, but if you are willing to make that commitment, you can save money with no engineering effort whatsoever. That's almost free money.Corey: So, much of what we do here comes down to psychology, in many ways, more than it does math. And a lot of times you're right, everything you say is right, but in a large-scale environment, go ahead and click that button to buy the savings plan or the reserved instance, and that's a $20 million purchase. And companies will stall for months trying to run a different series of analyses on this and what if this happens, what if that happens, and I get it because, “Yeah, I'm going to click this button that's going to cost more money than I'll make in my lifetime,” that's a scary thing to do; I get it. But you're going to spend the money, one way or the other, with the provider, and if you believe that number is too high, I get it; I am right there with you. Buy half of them right now and then you can talk about the rest until you get to a point of being comfortable with it.Do it incrementally; it's not all or nothing, you have one shot to make the buy. Take pieces out of it that makes sense. You know you're probably not going to turn off your database cluster that handles all of production in the next year, so go ahead and go for it; it saves some money. Do the thing that makes sense. And that doesn't require deep-dive analytics that requires, on some level, someone who's seen a lot of these before who gets what customers are going through. And honestly, it's empathy in many respects, becomes one of those powerful things that we can apply to our customer accounts.Tim: Absolutely. I mean, people don't understand that decision paralysis, about making those commitments costs you money. You can spend months doing analysis, but those months doing analysis, you're going to spend 30, 40, 50, 60, 70% more on your EC2 instances or other compute than you would otherwise, and that can be quite significant. But it's one of those cases where we talk about psychology around perfect being the enemy of good. You don't have to make the perfect purchase of RIs or savings plans and have that so tuned perfectly that you're going to get one hundred percent utilization and zero—like, you don't have to do that.Just do something. Do a little bit. Like you said, buy half; buy anything; just something, and you're going to save money. And then you can run analysis later on, while you're saving money [laugh] and get a little better and tune it up a little more and get more analysis on and maybe fine-tune it, but you don't actually ever need to have it down to the penny. Like, it never has to be that good.Corey: At some point, one of the value propositions we have for our customers has always been that we tell you when to stop focusing on saving money because there's a theoretical cap of a hundred percent of the cloud bill that you can save, but you can make so much more than that by launching the right feature to the right market a little sooner; focus on that. Be responsible stewards of the money that's invested with you, but by and large, as a general piece of guidance, at some point, stop cutting and go back to doing the thing that makes your company work. It's not all about saving money at all costs for almost all of us. It is for us, but we're sort of a special case.Tim: Well, it's a conversation I often have. It's like, all right, are you trying to save money on AWS or are you trying to save money overall? So, if you're going to spend $400,000 worth of engineering effort to save $10,000 on your AWS bill, that doesn't make no sense. So—[laugh]—Corey: Right. There has to be a strategic reason to do things like that—Tim: Exactly.Corey: —and make sure you understand the value of what you're getting for this. One reason that we wind up charging the way that we do—and we've gotten questions on this for a while—has been that we charge a fixed fee for what we do on engagements. And similarly—people have asked this, but haven't tied the two things together—you talk about cost optimization, but never cost-cutting. Why is that? Is that just a negative term?And the answer has been no, they're aligned. What we do focuses on what is best for the customer. Once that fixed fee is decided upon, every single thing that we say is what we would do if we were in the customer's position. There are times we'll look at what they have going on and say, “Ah, you really should spend more money here for resiliency, or durability,” or, “Okay, that is critical data that's not being backed up. You should consider doing that.”It's why we don't take percentages of things because, at that point, we're not just going with the useful stuff, it's, well we're going to basically throw the entire kitchen sink at you. We had an early customer and I was talking to their AWS account manager about what we were going to be doing and their comment was, “Oh, saving money on AWS bills is great, make sure you check the EBS snapshots.” Yeah, I did that. They were spending 150 bucks a month on EBS snapshots, which is basically nothing. It's one of those stories where if, in the course of an hour-long meeting, I can pay for that entire service, by putting a quarter on the table, I'm probably not going to talk about it barring [laugh] some extenuating circumstances.Focus on the big things, not the things that worked in a different environment with a different account and different constraints. It's hard to context switch like that, but it gets a lot easier when it is basically the entirety of what we do all day.Tim: The difference I draw between cost optimization and cost-cutting is that cost optimization is ensuring that you're not spending money unnecessarily, or that you're maximizing your dollar. And so sometimes we get called in there, and we're just validation for the measures they've already done. Like, “Your team is doing this exactly right. You're doing the things you should be doing. We can nitpick if you want to; we're going to save you $7 a year, but who cares about that? But y'all are doing what you should be doing. This is great. Going forward, you want to look for these things and look for these things and look for these things. We're going to give you some more concepts so that you are cost-optimized in the future.” But it doesn't necessarily mean that we have to cut your bill. Because if you're already spending efficiently, you don't need your bill cut; you're already cost-optimized.Corey: Oh, we're not going to nitpick on that, you're mostly optimized there. It's like, “Yeah, that workload's $140 million a year and rising; please, pick nits.” At which point? “Okay, great.” That's the strategic reason to focus on something. But by and large, it comes down to understanding what the goals of clients are. I think that is widely misunderstood about what we do and how we do it.The first question I always ask when someone does outreach of, “Hey, we'd like to talk about coming in here and doing a consulting engagement with us.” “Great.” I always like to ask the quote-unquote, “Foolish question” of, “Why do you care about the AWS bill?” And occasionally I'll get people who look at me like I have two heads of, “Why wouldn't I care about the AWS bill?” Because there are more important things to care about for the business, almost certainly.Tim: One of the things I try and do, especially when we're talking about cost optimization, especially trying to do something for the right now so they can do things going forward, it's like, you know, all right, so if we cut this much from your bill—if you just do nothing else, but do reserved instances or buy a savings plan, right, you're going to save enough money to hire four engineers. Think about what four engineers would do for your overall business? And that's how I want you to frame it; I want you to look at what cost optimization is going to allow you to do in the future without costing you any more money. Or maybe you save a little more money and you can shift it; instead of paying for your AWS bill, maybe you can train your developers, maybe you can get more developers, maybe you can get some ProServ, maybe you can do whatever, buy newer computers for your people so they can do—whatever it is, right? We're not saying that you no longer have to spend this money, but saying, “You can use this money to do something other than give it to Jeff Bezos.”Corey: This episode is sponsored in part by Liquibase. If you're anything like me, you've screwed up the database part of a deployment so severely that you've been banned from touching every anything that remotely sounds like SQL, at at least three different companies. We've mostly got code deployments solved for, but when it comes to databases we basically rely on desperate hope, with a roll back plan of keeping our resumes up to date. It doesn't have to be that way. Meet Liquibase. It is both an open source project and a commercial offering. Liquibase lets you track, modify, and automate database schema changes across almost any database, with guardrails to ensure you'll still have a company left after you deploy the change. No matter where your database lives, Liquibase can help you solve your database deployment issues. Check them out today at liquibase.com. Offer does not apply to Route 53.Corey: There was an article recently, as of the time of this recording, where Pinterest discussed what they had disclosed in one of their regulatory filings which was, over the next eight years, they have committed to pay AWS $3.2 billion. And in this article, they have the head of engineering talking to the reporter about how they're thinking about these things, how they're looking at things that are relevant to their business, and they're talking about having a dedicated team that winds up doing a whole bunch of data analysis and running some analytics on all of these things, from piece to piece to piece. And that's great. And I worry, on some level, that other companies are saying, “Oh, Pinterest is doing that. We should, too.” Yeah, for the course of this commitment, a 1% improvement is $32 million, so yeah, at that scale I'm going to hire a team of data scientists, too, look at these things. Your bill is $50,000 a month. Perhaps that's not worth the effort you're going to put into it, barring other things that contribute to it.Tim: It's interesting because we will get folks that will approach us that have small accounts—very small, small spend—and like, “Hey, can you come in and talk to us about this whatever.” And we can say very honestly, “Look, we could, but the amount of money we're going to charge you is going to—it's not going to be worth your while right now. You could probably get by on the automated recommendations, on the things that already out there on the internet that everybody can do to optimize their bill, and then when you grow to a point where now saving 10% is somebody's salary, that's when it, kind of, becomes more critical.” And it's hard to say what point that is in anyone's business, but I can say sometimes, “Hey, you know what? That's not really what you need to focus on.” If you need to save $100 a month on your AWS bill, and that's critical, you've got other concerns that are not your AWS bill.Corey: So, back when you were interviewing to work here, one of the areas of focus that you kept bringing up was the concept of observability, and my response to this was, “Ah, hell. Another one.” Because let's be clear, Mike Julian—my business partner and our CEO—has written a book called Practical Monitoring, and apparently what we learned from this is as soon as you finish writing a book on the topic, you never want to talk about that topic ever again, which yeah, in hindsight makes sense. Why do you care about observability when you're here to look at cloud costs?Tim: Because cloud costs is another metric, just like you would use for performance, or resilience, or security. You do real-time monitoring to see if somebody has compromised the system, you do real-time monitoring to see if you have bad performance, if response times are too slow. You do real-time monitoring to know if something has gone down and then you need to make adjustments, or that the automated responses you have in response to that downtime are working. But cloud costs, you send somebody a report at the end of the month. Can you imagine, if you will—just for a second—if you got a downtime report at the end of month, and then you can react to something that has gone down?Or if you get a security report at the end of the month, and then you can react to the fact that somebody has your root keys? Or if you get [laugh] a report at the end of month, this said, “Hey, the CPU on this one was pegged. You should probably scale up.” That's outrageous to anybody in this industry right now. But why do we accept that for cloud cost?Corey: It's worse than that. There are a number of startups that talk about, “Oh, real-time cloud cost monitoring. Okay, the only way you're going to achieve such a thing is if you build an API shim that interprets everything that you're telling your cloud control plane to do, taking cost metrics out of it, and then passing it on to the actual cloud control plane.” Otherwise, you're talking about it showing up in the billing record in—ideally, eight hours; in practice, several days, or you're talking about the CloudTrail events, which is not holistic but gives you some rough idea, but it's also in some cases, 5 to 20 minutes delayed. There's no real-time way to do this without significant disruption to what's going on in your environment.So, when I hear about, “Oh, we do real-time bill analysis.” Yeah, it feels—to be very direct—you don't know enough about the problem space you're working within to speak intelligently about it because anyone who's played in this space for a while knows exactly how hard it is to get there. Now, I've talked to companies that have built real-time-ish systems that take that shim approach and acts sort of as a metadata sidecar ersatz billing system that tracks all of this so they can wind up intercepting potentially very expensive configuration mistakes. And that's great. That's also a bit beyond for a lot of folks today, but it's where the industry is going. But there is no way to get there today, short of effectively intercepting all of those calls, in a way that is cohesive and makes sense. How do you square that circle given the complete lack of effective tooling?Tim: Honestly, I'm going to point that right back at the cloud provider because they know how much you're spending, real-time. They know exactly how much you spend in real-time. They've figured it out. They have the buckets, they have APIs for it internally. I'm sure they do; it would make no sense for them not to. Without giving anything anyway, I know that when I was at AWS, I knew how much they were spending, almost real-time.Corey: That's impressive. I wish that existed. My never having worked at AWS perspective on it is that they, of course, have the raw data effective immediately, or damn close to it, but the challenge for the billing system is distilling and summarizing and attributing all of that in a reasonable timeframe; it is an exabyte-scale problem. I've talked to folks there who have indicated it is comfortably north of a petabyte in raw data per day. And that was a couple of years ago, so one can only imagine as the footprint has increased, so has all of this.I mean, the billing system is fundamentally magic from the outside. I'm not saying it's good magic, but it is magic, and it's something that is unappreciated, that every customer uses, and is one of those areas that doesn't get the attention it deserves. Because, let's be clear, here, we talk about observability; the bill is still the only thing that AWS offers that gives you a holistic overview of everything running in your account, in one place.Tim: What I think is interesting is that you talk about this, the scale of the problem and that it makes it difficult to solve. At the same time, I can have a conversation with my partner about kitty litter, and then all of a sudden, I'm going to start getting ads about kitty litter within minutes. So, I feel like it's possible to emit cost as a metric like you would CPU or disk. And if I'm going to look at who's going to do that, I'm going to look right back at AWS. The fun part about that, though, is I know from AWS's business model, that if that's something they were to emit, it would also cost you, like, 25 cents per call, and then you would actually, like, triple your cloud costs just trying to figure out how much it costs you.Corey: Only with 16 other billing dimensions because of course it would. And again, I'm talking about stuff, because of how I operate and how I think about this stuff, that is inherently corner case, or [vertex 00:31:39] case in many cases. But for the vast majority of folks, it's not the, “Oh, you have this really weird data transfer paradigm between these two resources,” which yeah, that's a problem that needs to be addressed in an awful lot of cases because data transfer pricing is bonkers, but instead it's the, “Huh. You just spun up a big cluster that's going to cost $20,000 a month.” You probably don't need to wait a full day to flag that.And you also can't put this on the customer in the sense of, “Oh, just set some budget alarms, that's great. That's the first thing you should do in a new AWS account.” “Well, jackhole, I've done an awful lot of first things I'm supposed to do in an AWS account, in my dedicated test account for these sorts of things. It's been four months, I'm not done yet with all of those first things I'm supposed to do.” It's incredibly secure, increasingly expensive, and so far all it runs is a single EC2 instance that is mostly there just so that everything else doesn't error out trying to divide by zero.Tim: There are some things that are built-in. If I stand up an EC2 instance and it goes down, I'm going to get an alert that this instance terminated for some reason. It's just going to show up informationally.Corey: In the console. You're not going to get called about it or paged about it, unless—Tim: Right.Corey: —you have something else in the business that will, like a boss that screams at you two o'clock in the morning. This is why we have very little that's production-facing here.Tim: But if I know that alert exists somewhere in the console, that's easy for me to write a trap for. That's easy for me to write, say hey, I'm going to respond to that because this call is going to come out somewhere; it's going to get emitted somewhere. I can now, as an engineer, write a very easy trap that says, “Hey, pop this in the Slack. Send an alert. Send a page.”So, if I could emit a cost metric, and I could say, “Wow. Somebody has spun up this thing that's going to cost X amount of money. Someone should get paged about this.” Because if they don't page about this and we wait eight hours, that's my month's salary. And you would do that if your database server went down; you would do that if someone rooted that database server; you would do that if the database server was [bogging 00:33:48] you to scale up another one. So, why can't you do that if that database server was all of sudden costing you way more than you had calculated?Corey: And there's a lot of nuance here because what you're talking about makes perfect sense for smaller-scale accounts, but even some of the very large accounts where we're talking hundreds of millions a year in spend, you can set compromised keys up on GitHub, put them in Payspin, whatever, and then people start spinning up Bitcoin miners everywhere. Great. It takes a long time to materially move the needle on that level of spend; it gets lost in the background noise. I lose my mind when I wind up leaving a managed NAT gateway running and it cost me 70 bucks a month in my $5 a month test account. Yeah, but you realize you could basically buy an island and it gets lost in the AWS bill at some of the high watermarks for some of these larger accounts.“Oh, someone spun up a cluster that's going to cost $400,000 a year?” Yeah, do I need to re-explain to you what a data science team does? They light money on fire in return for questionable returns, as a general rule. You knew that when you hired them; leave them alone. Whereas someone in their developer account does this, yeah, you kind of want to flag that immediately.It always comes down to rules and context. But I'd love to have some templates ready to go of, “I'm a starving student, please alert me anytime it looks like I might possibly exceed the free tier,” or better yet, “Don't let me, and if I do, it's on you and you eat the cost.” Conversely, it's, “Yeah, this is a Netflix sub-account or whatnot. Maybe don't bother me for anything whatsoever because freedom and responsibility is how we roll.” I imagine that's what they do internally on a lot of their cloud costing stuff because freedom and responsibility is ingrained in their culture. It's great. It's the freedom from having to think about cloud bills and the responsibility for paying it, of the cloud bill.Tim: Yeah, we will get internally alerted if things are [laugh] up too long, and then we will actually get paged, and then our manager would get paged, [laugh] and it would go up the line. If you leave something that's running too expensive, too long. So, there is a system there for it.Corey: Oh, yeah. The internal AWS systems for employees are probably my least favorite AWS service, full stop. And I've seen things posted about it; I believe it's called Isengard, for spinning up internal accounts and the rest—there's a separate one, I think, called Conduit, but I digress—that you spin something up, and apparently if it doesn't wind up—I don't need you to comment on this because you worked there and confidentiality is super important, but to my understanding it's, great, it has a whole bunch of formalized stuff like that and it solves for a whole lot of nifty features that bias for the way that AWS focuses on accounts and how they've view security and the rest. And, “Oh, well, we couldn't possibly ship this to customers because it's not how they operate.” And that's great.My problem with this internal provisioning system is it isolates and insulates AWS employees from the real pain of working with multiple accounts as a customer. You don't have to deal with the provisioning process of Control Tower or whatnot; you have your own internal thing. Eat your own dog food, gargle your own champagne, whatever it takes to wind up getting exposure to the pain that hits customers and suddenly you'll see those things improve. I find that the best way to improve a product is to make the people building it live with the painful parts.Tim: I think it's interesting that the stance is, “Well, it's not how the customers operate, and we wouldn't want the customers to have to deal with this.” But at the same time, you have to open up, like, 100 accounts if you need more than a certain number of S3 buckets. So, they are very comfortable with burdening the customer with a lot of constraints, and they say, “Well, constraints drive innovation.” Certainly, this is a constraint that you could at least offer and let the customers innovate around that.Corey: And at least define who the customer is. Because yeah, “I'm a Netflix sub-account is one story,” “I'm a regulated bank,” is another story, and, “I'm a student in my dorm room, trying to learn how this whole cloud thing works,” is another story. From risk tolerance, from a data protection story, from a billing surprise story, from a, “I'm trying to learn what the hell this is, and all these other service offerings you keep talking to me about confuse the hell out of me; please streamline the experience.” There's a whole universe of options and opportunity that isn't being addressed here.Tim: Well, I will say it very simply like this: we're talking about a multi-trillion dollar company versus someone who, if their AWS bill is too high, they don't pay rent; maybe they don't eat; maybe they have other issues, they don't—medical bill doesn't get paid; child care doesn't get paid. And if you're going to tell me that this multi-trillion dollar company can't solve for that so that doesn't happen to that person and tells them, “Well, if you come in afterwards, after your bill gets there, maybe we can do something about it, but in the meantime, suffer through this.” That's not ethical. Full stop.Corey: There are a lot of things that AWS gets right, and I want to be clear that I'm not sitting here trying to cast blame and say that everything they're doing is terrible. I feel like every time I talk about billing in any depth, I have to throw this disclaimer in. Ninety to ninety-five percent of what they do is awesome. It's just the missing piece that is incredibly painful for customers, and that's what I spend most of my time focusing on. It should not be interpreted to think that I hate the company.I just want them to do better than they are, and what they're doing now is pretty decent in most respects. I just want to fix the painful parts. Tim, thank you for joining me for a third time here. I'm certain I'll have you back in the somewhat near future to talk about more aspects of this, but until then, where can people find you slash retain your services?Tim: Well, you can find me on Twitter at @elchefe. If you want to retain my services for which you would be very, very happy to have, you can go to duckbillgroup.com and fill out a little questionnaire, and I will magically appear after an exchange of goods and services.Corey: Make sure to reference Tim by name just so that we can make our sales team facepalm because they know what's coming next. Tim, thank you so much for your time; it's appreciated.Tim: Thank you so much, Corey. I loved it.Corey: Principal cloud economist here at The Duckbill Group, Tim Banks. I'm Cloud Economist Corey Quinn, and this is Screaming in the Cloud. If you've enjoyed this podcast, please leave a five-star review on your podcast platform of choice whereas if you've hated this podcast, please leave a five-star review on your podcast platform of choice, wait at least eight hours—possibly as many as 48 to 72—and then leave a comment explaining what you didn't like.Corey: If your AWS bill keeps rising and your blood pressure is doing the same, then you need The Duckbill Group. We help companies fix their AWS bill by making it smaller and less horrifying. The Duckbill Group works for you, not AWS. We tailor recommendations to your business and we get to the point. Visit duckbillgroup.com to get started.Announcer: This has been a HumblePod production. Stay humble.
E-mail us at DreamWarriorReview@gmail.com or check us out on Twitter - @DWReview or Facebook/DWReview Don't forget to follow us and send us your comments!! Be sure to check us out on YouTube if you want to see our pretty faces! https://www.youtube.com/channel/UCfMH4aYtCSUTf4ej8BnktFQ/videos In this episode we review "Shadow in the Cloud" (2020) Thanks to Cryptamnesia for providing awesome music! Check out Cryptamnesia out at the following link and pick up their new album! https://cryptamnesia.bandcamp.com/ BIG Thanks to our Sponsor Brownspace Films check out their page at https://www.facebook.com/brownspacefilms/ Thanks Brandon Lane For providing our amazing logo! For more info on his Rants From the Black Lodge Podcast...check out this link! juicykrueger.com Thanks Niev Strawn for providing great graphics, we have never looked better! The Dream Warrior Review podcast series with Mick Strawn and Kurt Thomas. Featuring Reviews of Horror and Science Fiction Films. Also Featuring Story Time With Mick and sometimes Story Time with Kurt. E-mail us at DreamWarriorReview@gmail.com or check us out on Twitter or Facebook@DWReview Don't forget to follow us and send us your comments!!
Al Roker sits down with climate activist Greta Thunberg — the action she wants to see taken now and her hope for the future. Plus, Craig Melvin, Sheinelle Jones, Jacob Soboroff and Al are checking in with Dylan Dreyer! Meet her baby boy, Rusty, and learn all about her very first children's book, “Misty the Cloud: A Very Stormy Day.” Also ahead, “Project Runway” stars, Christian Siriano and Nina Garcia are chatting all about the new season.
Topics: Grief, Dating, Pride, Avoiders, PTSD, Infertility Hosts: Steve Arterburn, Dr. Jill Hubbard, Milan Yerkovich Caller Questions: My difficult husband passed away 9mos ago. There's a gentleman from church I want to bring over, but my adult kids don't want to talk to or even look at him. How do I identify pride in me when I just don't see it? How do I The post New Life Live: October 12, 2021 appeared first on New Life.
On this episode of Hashmap on Tap, host Kelly Kohlleffel is joined by Andrew Reichman, Director of Market Intelligence with Snowflake. Over local craft beers, they talk about the Snowflake Data Cloud, Snowflake's differentiation, and how they continue to elevate the bar for cloud data platforms. Show Notes: Learn more about what's going on at Snowflake: https://www.snowflake.com/ See more Hashmap and Snowflake content: https://www.hashmapinc.com/snowflake Connect with Andrew on LinkedIn: https://www.linkedin.com/in/areichman/ Check out our 2021 Cloud Data Platform Benchmark Analysis: https://www.hashmapinc.com/snowflake-benchmarking On tap for today's episode: Real Ale Brewing's Oktoberfest & Strata Fresh Hop Pale Ale by Flying Lion Contact Us: https://www.hashmapinc.com/reach-out
In this episode of RadioFreeHPC the entire crew is back to talk the UK Met Office buying 1.2 billion pounds worth of Azure credits, responsibility when dealing with ransomware, and Elon Musk. RadioFreeHPC is produced by a pack of mildly rabid dogs who have gained the ability to manipulate technology for their own mad agenda.… Read More »The Met Office
In-your-face, feminist, political, party rap duo Glitter Moneyyy (TayyySlayyy and Queen Trashley) join me to talk about DRUUUUUUGS. Their funeral planning includes mandatory drug-taking, and their visions of the afterlife get pretty stoner-y. They also talk about the break-up (an old one) and pandemic (the current one) that rearranged their lives. Check out Glitter Moneyyy's extended episode at https://www.patreon.com/davemaher (patreon.com/davemaher), and make it so I can continue to produce This Is Your Afterlife ad-free! Follow Glitter Moneyyy: @glittermoneyyy on https://twitter.com/GLITTERMONEYYY (Twitter) and https://www.instagram.com/glittermoneyyy/ (Instagram). Follow them on https://open.spotify.com/artist/6hk1hVB6LnJGREnKvmk7sV?si=Guha_zWRStiembjBgFT7dA&dl_branch=1 (Spotify), https://music.apple.com/us/artist/glitter-moneyyy/1294749949 (Apple Music), and https://glittermoneyyy.bandcamp.com/ (Bandcamp). And GO TO https://lh-st.com/shows/11-06-2021-glitter-moneyyy/ (THEIR SHOW AT LINCOLN HALL IN CHICAGO) ON NOVEMBER 6! Transcript: https://app.podscribe.ai/series/1246109 (This Is Your Afterlife on Podscribe) --- Follow me @thisisdavemaher on https://www.instagram.com/thisisdavemaher/ (Instagram) and https://twitter.com/ThisIsDaveMaher (Twitter), and subscribe to my weekly newsletter, Hella Immaculate, at http://thisisdavemaher.com/ (thisisdavemaher.com). Want to learn more about or sign up for my Unblock or Personal Story Workshops? Email email@example.com. --- Intro Song = Future: "Use Me" Transitional Music = James Blackshaw: "The Cloud of Unknowing" Outro Song = Johnnie Frierson: "Miracles" Support this podcast
Created by Maiya Gaint, Black Girls Smell Good is an online community that rolls 115K members deep (across platforms) for Black women to share, obsess, and learn about all things fragrance. In this ep, I am joined by Maiya herself and WOW, it's a juicy one. Having previously spent time in beauty retail as both a sales associate and educator, Maiya spills the secrets on the behind-the-scenes of department store beauty departments. Spoiler alert: there's a reason you're guided towards certain fragrances and not others. We also discuss how Cloud is NOT a dupe for BR 540, the weird Internet obsession over the latter, how Maiya got into fragrance, her inspiration for creating BGSG, her first date perfume picks, the art of ASMR in fragrance reviews, Rihanna's Fenty fragrance, and the fine line between collecting vs. hoarding (hard to say where we fall on that one), and Maiya reveals her current relationship status… with her perfumes ;) FRAGS MENTIONED: Fragrance Du Bois NY 5th Ave, Penhaligon's Cairo, The Body Shop White Musk Lover, The Body Shop Black Musk, Nemat Amber, By Rosie Jane Rosie, Pure Instincts, Le Labo Rose 31, Montale Sensual Instincts, Tom Ford Lost Cherry, Kilian Princess, Baccarat Rouge 540, Alt Crystal No. 23, Ariana Grande Cloud, Estee Lauder Pleasures, Ocean Pacific OP Juice, Estee Lauder Youth Dew, Vera Wang Princess, Kilian Princess, Viktor & Rolf Flowerbomb, Tom Ford Fucking Fabulous, Kilian's Kissing, MFK Gentle Fluidity Gold, Pinrose Pillowtalk Poet, JHAG Not A Perfume, Clean Reserve Warm Cotton, Montale Wild Pears, Montale So Iris Intense, Kilian After Sunset, Fenty Fenty, Kilian Love Don't Be Shy, Rihanna Reb'l Fleur, Vacation Inc by Arquiste, Tom Ford Beau de Jour, Giorgio by Giorgio Beverly Hills, Mugler Angel PERFUME 101: Cypriol Oil FOLLOW MAIYA: IG: @blackgirlssmellgood TT: @blackgirlssmellgood Follow Perfume Room: IG: @perfumeromopod @emmvern TT: @emma_vern
Ivan Pittaluga, CTO at Arcserve provides his view and details on filesystem theory, why you should understand the metadata of very large filesystems especially Network Accessible Filesystems, and a few nuggets of using tape and immutable storage.
Join #CloudNClear today! This all-new episode includes our very own Miles Ward, CTO, SADA, as he interviews a special guest and partner Rob Martin, Chief Architect, Google Cloud for #Games. They discuss Rob's pivotal role in scaling up global #videogames on #cloudinfrastructure. Learn more about how #GoogleCloud is powering the #gamingindustry with innovative product offerings. Unpack what it means to run Triple-A and #mobilegames on the #cloud, why it's so hard to manage the varying #infrastructure needs, and how the organization is accelerating its #technology to support #cloudgaming. Host: Miles Ward Guests: Rob Martin Connect on Twitter: https://twitter.com/cloudnclear https://twitter.com/SADA https://twitter.com/milesward https://twitter.com/cloudrobx Connect on LinkedIn: https://www.linkedin.com/company/sada/ https://www.linkedin.com/in/milesward/ https://www.linkedin.com/in/cloudrobx/
Topics: Drug Addiction, Hoarding, Blended Families, Christian Walk, Father Issues, Grief, Boundaries, Forgiveness, Reconciliation Hosts: Steve Arterburn, Dr. Jill Hubbard, Dr. Sheri Keffer Caller Questions: I feel like I am addicted to my prescription drug to help me sleep; do I need to go to rehab? My second wife calls me a hoarder; how do I make it up to her for not helping her with cleaning The post New Life Live: October 11, 2021 appeared first on New Life.
We talk about the new Switch OLED model the only way we know how: browsing YouTube videos for low resolution teardowns and trying to look up part data sheets to try and figure out why Ethernet is so bad on the Switch. Show Notes: 00:05:39 - OLED Display Concerns 00:21:53 - Ethernet Discourse Jim Ryan is Wrong: Jim Ryan: “I would love a world where hundreds of millions enjoy our games” No, Jim Ryan - Gaming In The Middle East Existed Long Before PlayStation Switch OLED: Display Uses PWM to control brightness, appears to go full throttle from 0-50% brightness OLED Switch uses PWM dimming below 50% brightness: NintendoSwitch Explanation on what PWM is https://www.reddit.com/r/apple/comments/7uv6m3/iphone_x_uses_pulse_width_modulation_which_is_a/dto2o9l/ iPhone 13 for context begins around from under 25% brightness Nintendo is shipping the display with a “vibrant” profile enabled out of box, burying the more color accurate “standard” mode in settings The OLED Nintendo Switch doesn't have a Pentile screen Ethernet: From this teardown it appears to be a gigabit port with a full ethernet controller Switch OLED Full Teardown! Dock Can Upscale?! OLED vs Switch vs Lite However real world tests are showing far less than gigabit speeds Switch OLED hardwired still has incredible bad and embarrassing speeds: NintendoSwitch https://twitter.com/llaffer2/status/1446587410700292109 Nintendo Switch Teardown Using the original Switch teardown as guidance and Nintendo's never ending ability to be cheap as forecast, assuming the Switch OLED has the same USB controller PI3USB30532 (USB Switches) USB 3.2 Gen 1 5Gb/s Super Speed and DP 1.2 5.4Gb/s switching to USB Type C connector The Switch OLED dock per the teardown above has a HDMI 2.0 controller on the new dock HDMI 2.0 technically can cap out at 18Gb/s Which is almost 4x what the USB controller on the Switch itself supports for bandwidth on the USB and DP side (~10Gb/s theoretical) In theory this bottleneck could be causing the shit Ethernet Speeds However nintendo could just be nintendo and doing a nintendo MCDP2900 DisplayPort1.4a to HDMI2.0b Protocol Converter with HDCP2.3 Repeater Newer version of the HDMI to DP converter used on the dock board Switch 4K gaming could be added with new dock chip swap, AI upscaling A brief aside on the Nintendo Switch Wi-Fi Broadcom BCM4356 is the part used per the ifixit teardown ThinkPad Yoga 260 ThinkPad L560 I don't really have more commentary than the fact that Nintendo is shipping wifi used in Windows laptops in a 2x2 config and it's still absolute shit Contact: Cristian Online Sadiq Online Subscribe on: Apple Podcasts | Google Podcasts | Spotify | Overcast| Pocketcasts | RSS
Get tips for visibility and management of your cloud spend in Azure using your endpoint of choice, from the Azure Cost Management portal, Power BI for custom views and reporting, to API-based integration that feeds cost data into your existing financial system. Matt McSpirit, Senior Program Manager for Microsoft Azure, joins Jeremy Chapman to share how you can configure your Azure environment to meet specific cost reporting needs. Whether you're from the IT team or the finance team, choose from a number of options: Azure Cost Management in the Azure portal- Gives you the most comprehensive access to cost management views and reports. Azure Cost Management Power BI app- Great visibility with pre-built views out-of-the-box to track your Azure spend at the account, subscription, and resource group level. Power BI desktop connector- For more custom reporting, take our base Power BI template files and customize by building your own views. API-based integration- For ultimate control and customization, use APIs directly to integrate the data within your internal apps and financial systems. ► QUICK LINKS: 00:00 - Introduction 01:29 - See your options 03:32 - Assess spend by department or business unit 05:22 - Configure cost tracking at granular workload level 07:14 - Establish management groups or tags retrospectively 08:38 - Options for Power BI 10:57 - Leverage APIs 11:51 - Wrap up ► Link References: Watch our episode on cloud economics essentials to understand the fundamentals of cloud costs at https://aka.ms/MechanicsAzureCloudEconomics Get tips on naming your tags at https://aka.ms./CAFTagging Download our cost management app at https://aka.ms/ACMApp For guidance on the Azure Cost Management connector in Power BI desktop, go to https://aka.ms/ACMPowerBI Learn more about configuring resources in Azure with the Azure setup guide at https://aka.ms/AzureSetupGuide Find more tools, templates, and guidance at https://azure.com/cloudeconomics ► Unfamiliar with Microsoft Mechanics? We are Microsoft's official video series for IT. You can watch and share valuable content and demos of current and upcoming tech from the people who build it at #Microsoft. Subscribe to our YouTube: https://www.youtube.com/c/MicrosoftMechanicsSeries?sub_confirmation=1 Join us on the Microsoft Tech Community: https://techcommunity.microsoft.com/t5/microsoft-mechanics-blog/bg-p/MicrosoftMechanicsBlog Watch or listen via podcast here: https://microsoftmechanics.libsyn.com/website ► Keep getting this insider knowledge, join us on social: Follow us on Twitter: https://twitter.com/MSFTMechanics Follow us on LinkedIn: https://www.linkedin.com/company/microsoft-mechanics/
It was our Birthday last week, and with that we took some time to reflect on where we are at now, what it took to get us here, and who helped us along the way. It's easy to get somewhere when you've got help along the way. The Cat & Cloud Coffee Podcast: Chis Baca and Jared Truby, two of the founders of Cat & Cloud coffee share their insights of leadership and owning a small business, through the lens of the specialty coffee industry. It's not just about whats in the cup, but the intention behind how it was put there. With new episodes weekly, listen in as there's always little nuggets of wisdom. Where to listen Apple Podcast: https://podcasts.apple.com/us/podcast/cat-cloud-podcast/id1021859870 spotify: https://open.spotify.com/show/1Ca5vz73UcyAHCAYmWKpl5?si=d8whB74aRjmgU-ld_0qZfQ&dl_branch=1 Watch here on youtube! https://youtube.com/playlist?list=PLKAafL6q_RiChNcnVZh3_uW0fKBJ6gImB If you want even more insights from Chris and Jared, consider becoming a member over on Patreon. each week get even more, as well as exclusive access to a likeminded community, with plenty of benefits to come. It's just the price of a latte a month, and we think there is a lot of value in that. So check it out. https://www.patreon.com/catandcloud The usual suspects. Instagram: https://www.instagram.com/catcloudcoffee/ Cat & Cloud: https://catandcloud.com/ Your hosts: Baca's Blog: https://www.realchrisbaca.com/ Jared's Website: https://www.jaredtruby.com/ Your editor: justphred We are Cat & Cloud Coffee. Started by three friends trying to pursue their passions, with Integrity and intentionally, and it's our mission to inspire connection, by creating memorable experiences. We're a small independent business and this is our story. Enjoy!
Chief Security Architect Rich Wickersham rejoins co-host Andy Bonillo on Episode #169 of Task Force Radio to provide insights on making the move to the cloud securely, the importance of threat modeling, and the importance of architecture patterns to understand what is normal. Rich also discusses how misconfigurations are the greatest threats to the cloud, as well as providing his perspective on the Solarwinds breach and supply chain risk. All this and much, much more on Episode #169 of Task Force 7 Radio.
Episode 82 - Rebuilding a Championship Contender October 10th, 2021 St. Cloud, MN YouTube: https://youtu.be/DBZu2Xiqsoo Apple Podcasts: https://podcasts.apple.com/us/podcast/the-huskies-warming-house-podcast/id1499278131 Episode 82 of the CenterIceView News and Notes segment features a discussion in a season-long theory of building a contender in the NCAA. First, it's a discussion about the hockey landscape… then, St. Cloud State University Men's hockey earned a hard-fought split in Mankato (26:29). Next, St. Cloud State Women's hockey was unable to climb back against Wisconsin, some Mack Motzko talk, and what do the final roster cuts mean for the Minnesota Wild (34:13)? Finally, our Extra Ice session talks about what it takes for SCSU to repeat last year's success on the men's hockey side (49:25). All this and more in another week in the Den! As always, find us on Apple Podcasts, Podbean, Spotify, TuneIn, iHeartRadio, Google Podcasts and Youtube + more. Visit us at huskieswarminghousepodcast.com, and check out our affiliate at centericeview.com. The latest news is on Twitter and Facebook @warminghouseden, and email us at @firstname.lastname@example.org.
Leon Kuperman discusses AI-driven cloud optimization and how organizations can reduce their cloud spending and boost their application development efforts. Leon is the co-founder and CTO of CAST.AI, a technology startup that combines AI with Kubernetes to provide savings and competitive advantage. Listen for three action items you can use today. Host, Kevin Craine Do you want to be a guest?
The build-to-rent trend is creating intense competition for land. There are reports that land brokers are getting a growing number of calls from investor groups who want to build single-family rental communities. And there's a limited amount of suitable tracts of land, so competition is fierce.Hi, I'm Kathy Fettke and this is Real Estate News for Investors. If you like our podcast, please subscribe and leave us a review.Forbes just published an article on this build-to-rent “land rush.” It says that for every veteran buyer, land brokers are getting 50 calls from groups who are new to this residential construction niche.BTR “Land Rush”Because there just aren't enough existing homes on the market to meet investor demand, the build-to-rent trend is gaining traction. And that has off a stampede of sorts, for land. Forbes says that “a site that is well-suited for build-to-rent will typically get between 10 and 25 offers.”This is also a new situation for land brokers. They have traditionally sold to developers who build homes to sell to the public. But now they are catering to investors who want land for single-family rentals.One land broker told Forbes that between 5% and 10% of his land sales today are for new single-family rental communities. And he says that percentage is growing month after month. In fact, he says he expects those numbers to “double or triple in the next couple of years.”And it isn't just the big institutional groups pouring money into this market. The majority of them are smaller lesser-known groups, although the deep pocket investor groups do snag headlines.The Forbes article was written by housing economist, Brad Hunter, who helps investors and builders with site-specific market data and analysis. He says the BTR groups also have different preferences for the kinds of communities they want to build. They range from low-density communities with just 4 to 5 rental homes per acre to high-density strategies with 11 to 12 homes per acre. But he says, a density that's in the middle of that range is most popular.BTR Investors vs. HomebuildersThis BTR “land rush” is creating a lot of competition with traditional homebuilders, because of skyrocketing rental returns. Rents are rising in large and small markets across the country, and that's providing a strong motive for BTR investors.Because they are well-funded, Hunter says that BTR investors are often able to outbid homebuilders. And, they are gaining more traction in markets where rents are rising the fastest. He says demand for BFR land is rising the fastest in bigger metros like Augusta, Savannah, San Antonio, and St. Paul. He also says there's also growing demand in smaller cities St. Cloud, Pensacola, and Port Charlotte in Florida.In addition to a limit on land, local ordinances are holding some investors back because there's just more demand than local zoning laws will allow. Some of that is due to a general bias against rentals and local officials who are worried about how voters will react. Because of a perception that renters won't make good neighbors, the NIMBY syndrome is strong in many areas. Hunter says that perception is changing however, because a lot of today's renters are highly paid professionals who don't want to be homeowners and prefer to rent.Despite those headwinds, demand is there for single-family rental homes. According to Hunter and his company, Hunter Housing Economics, there are five things driving this demand.Top Five Reasons for BTR Demand1 - Household formation rates are pushing past 1.6 million per year2 - Millennials want to raise their kids in the suburbs with good schools3 - High rate of dog ownership and desire for yard space4 - Remote work has created a demand for home office space5 - Home prices are too high for young families to buy their own homesHunter says: “The potential for growth is enormous.” His company sees production ramping up over the next five years, with an increase in BTR starts each year. By 2025, Hunter's company is predicting 180,000 starts, with demand still outpacing production. You'll find links to the Forbes article in the show notes at newsforinvestors.com. You can also learn more about single-family rentals at our website by joining RealWealth for free. As a member, you have access to the Investor Portal where you can view sample property pro-formas and connect with our network of resources. That includes experienced investment counselors, property teams, lenders, 1031 exchange facilitators, attorneys, CPAs and more.And please remember to hit the subscribe button, and leave a review!Thanks for listening. I'm Kathy Fettke.Link:1 -https://www.forbes.com/sites/bradhunter/2021/09/09/the-built-for-rent-land-rush-is-intensifying-here-are-five-drivers/?sh=16cc3ae5560c2 -https://magazine.realtor/daily-news/2021/09/13/the-race-is-on-for-built-for-rent-land
Topics: Social Media, Christian Walk, Same-Sex Attraction, Masturbation, Teens, Parenting, Hosts: Becky Brown, Dr. Alice Benton, Chris Williams Caller Questions: If I share spiritual things on Facebook, am I coming across as hypocritical? If I don't share, am I denying the Lord? My 25yo daughter told us that she is gay; how should we respond to her? What's a biblical response to The post New Life Live: October 8, 2021 appeared first on New Life.
We know humans are behind climate change, thanks to this Nobel Physics laureate's work; New Nobel laureate in chemistry reflects on how his discovery catalyzed his field; Researchers investigate an ‘ultra-hot Jupiter' with iron rain and calcium wind; Canadian concept to pump carbon into subsea rock could sequester gigatons of CO2; Cloud-based sunscreen could help protect the Great Barrier Reef from future heat damage; How watching water bears walk could help us make small and squishy robots.
October 8, 2021: End users are getting better about not treating the EHR like a giant post-it note. And we're seeing much better data quality. Consistently delivering trusted, comprehensive data can create competitive advantages for your organization. Learn how to strategically manage and mobilize data with Intermountain's Castell Health and Arcadia, who have partnered to elevate value-based care performance. Joining us is David Dirks and Michael Meucci. What are common issues that arise from a poorly managed data supply chain? What is required for data to be trusted and fit for use in healthcare? And how can you master good data governance, strong data provenance management, and effective infrastructure?Key Points:The compounded annual growth rate of healthcare data is 36% [00:03:22] We cannot hire computer scientist folks with engineering backgrounds fast enough. It's an extremely hot labor market. [00:41:07] HIMSS: Activating Your Healthcare Data Supply Chain Castell Arcadia David Dirks: email@example.comMichael Meucci: firstname.lastname@example.org
We were right this time. Atelier Sophie 2: The Alchemist of the Mysterious Dream will launch Feb 24 in Japan and the next day worldwide for PS4, PC, and Switch. I give all the details and wrap up our coverage of Tokyo Game Show 2021. At the end of the podcast I'll share an interview with Sophie's director on the influences of this game, why she got a sequel, and the Ryza effect on the game. Also covered in this show: Relayer, Sin Chronicle, Blue Reflection Second Light, and the 20th Anniversary of Kingdom Hearts, with all titles coming to Switch soon via the Cloud. I share a few others headlines and outline the podcast release schedule with me on vacation next week. But fear not we have a fun mailbag show to hold you over until I return! I'm off to JRPG Island! Please consider funding the show via Patreon or the Anchor link at the bottom of the description. Support the podcast here https://www.patreon.com/JRPGReport or click link at bottom for listener support Paypal: Direct support available via email@example.com Leave us a review on Apple or your favorite listening place. Like our Facebook Page We now have a website! www.jrpgreport.com Follow us on Twitter @Jrpgreport Daily JRPG videos and Livestreams on Youtube Email me at firstname.lastname@example.org Check out these fine sources for more information on the stories I cover: https://www.gematsu.com/ and https://www.siliconera.com --- Send in a voice message: https://anchor.fm/jrpgreport/message Support this podcast: https://anchor.fm/jrpgreport/support
About JasonJason is now the Managing Director at Redpoint Ventures.Links: GitHub: https://github.com/ @jasoncwarner: https://twitter.com/jasoncwarner GitHub: https://github.com/jasoncwarner Jasoncwarner/ama: https://github.com/jasoncwarner/ama TranscriptAnnouncer: Hello, and welcome to Screaming in the Cloud with your host, Chief Cloud Economist at The Duckbill Group, Corey Quinn. This weekly show features conversations with people doing interesting work in the world of cloud, thoughtful commentary on the state of the technical world, and ridiculous titles for which Corey refuses to apologize. This is Screaming in the Cloud.Corey: This episode is sponsored in part by Honeycomb. When production is running slow, it's hard to know where problems originate: is it your application code, users, or the underlying systems? I've got five bucks on DNS, personally. Why scroll through endless dashboards, while dealing with alert floods, going from tool to tool to tool that you employ, guessing at which puzzle pieces matter? Context switching and tool sprawl are slowly killing both your team and your business. You should care more about one of those than the other, which one is up to you. Drop the separate pillars and enter a world of getting one unified understanding of the one thing driving your business: production. With Honeycomb, you guess less and know more. Try it for free at Honeycomb.io/screaminginthecloud. Observability, it's more than just hipster monitoring.Corey: This episode is sponsored in part by Liquibase. If you're anything like me, you've screwed up the database part of a deployment so severely that you've been banned from touching every anything that remotely sounds like SQL, at at least three different companies. We've mostly got code deployments solved for, but when it comes to databases we basically rely on desperate hope, with a roll back plan of keeping our resumes up to date. It doesn't have to be that way. Meet Liquibase. It is both an open source project and a commercial offering. Liquibase lets you track, modify, and automate database schema changes across almost any database, with guardrails to ensure you'll still have a company left after you deploy the change. No matter where your database lives, Liquibase can help you solve your database deployment issues. Check them out today at liquibase.com. Offer does not apply to Route 53.Corey: Welcome to Screaming in the Cloud. I'm Corey Quinn. I'm joined this week by Jason Warner, the Chief Technology Officer at GifHub, although he pronounces it differently. Jason, welcome to the show.Jason: Thanks, Corey. Good to be here.Corey: So, GitHub—as you insist on pronouncing it—is one of those companies that's been around for a long time. In fact, I went to a training conducted by one of your early folks, Scott Chacon, who taught how Git works over the course of a couple of days, and honestly, I left more confused than I did when I entered. It's like, “Oh, this is super awful. Good thing I'll never need to know this because I'm not really a developer.” And I'm still not really a developer and I still don't really know how Git works, but here we are.And it's now over a decade later; you folks have been acquired by Microsoft, and you are sort of the one-stop-shop, from the de facto perspective of, “I'm going to go share some code with people on the internet. I'll use GitHub to do it.” Because, you know, copying and pasting and emailing Microsoft Word documents around isn't ideal.Jason: That is right. And I think that a bunch of things that you mentioned there, played into, you know, GitHub's early and sustained success. But my God, do you remember the old days when people had to email tar files around or drop them in weird spots?Corey: What the hell do you mean, by, “Old days?” It still blows my mind that the Linux kernel is managed by—they use Git, obviously. Linus Torvalds did write Git once upon a time—and it has the user interface you would expect for that. And the way that they collaborate is not through GitHub or anything like that. No, they use Git to generate patches, which they then email to the mailing list. Which sounds like I'm making it up, like, “Oh, well, yeah, tell another one, but maybe involve a fax machine this time.” But no, that is actually what they do.Jason: It blew my mind when I saw that, too, by the way. And you realize, too, that workflows are workflows, and people will build interesting workflows to solve their use case. Now, obviously, anyone that you would be talking to in 2021, if you walked in and said, “Yeah, install Git. Let's set up an email server and start mailing patches to each other and we're going to do it this way.” They would just kind of politely—or maybe impolitely—show you out of the room, and rightfully [laugh] so. But it works for one of the most important software projects in history: Linux.Corey: Yeah, and it works almost in spite of itself to some extent. You've come a long way as a company because initially, it was, “Oh, there's this amazing, decentralized version control system. How do we make it better? I know, we're going to take off the decentralized part of it and give it a central point that everything can go through.” And collaboratively, it works well, but I think that viewing GitHub as a system that is used to sell free Git repositories to people is rather dramatically missing the point. It feels like it's grown significantly beyond just code repository hosting. Tell me more about that.Jason: Absolutely. I remember talking to a bunch of folks right around when I was joining GitHub, and you know, there was still talk about GitHub as, you know, GitHub for lawyers, or GitHub for doctors, or what could you do in a different way? And you know, social coding as an aspect, and maybe turning into a social network with a resume. And all those things are true to a percentage standpoint. But what GitHub should be in the world is the world's most important software development platform, end-to-end software development platform.We obviously have grown a bunch since me joining in that way which we launched dependency management packages, Actions with built-in CI, we've got some deployment mechanisms, we got advanced security underneath it, we've Codespaces in beta and alpha on top of it now. But if you think about GitHub as, join, share, and see other people's code, that's evolution one. If you see it as world's largest, maybe most developed software development platform, that's evolution two, and in my mind, its natural place where it should be, given what it has done already in the world, is become the world's most important software company. I don't mean the most profitable. I just mean the most important.Corey: I would agree. I had a blog post that went up somewhat recently about the future of cloud being Microsoft's to lose. And it's not because Azure is the best cloud platform out there, with respect, and I don't need you to argue the point. It is very clearly not. It is not like other clouds, but I can see a path to where it could become far better than it is.But if I'm out there and I'm just learning how to write code—because I make terrible life choices—and I go to a boot camp or I follow a tutorial online or I take a course somewhere, I'm going to be writing code probably using VS Code, the open-source editor that you folks launched after the acquisition. And it was pretty clear that Atom wasn't quite where the world was going. Great. Then I'm going to host it on GitHub, which is a natural evolution. Then you take a look at things like GitHub Actions that build in CI/CD pipelines natively.All that's missing is a ‘Deploy to Azure' button that is the next logical step, and you're mostly there for an awful lot of use cases. But you can't add that button until Azure itself gets better. Done right, this has the potential to leave, effectively, every other cloud provider in the dust because no one can touch this.Jason: One hundred percent. I mean, the obvious thing that any other cloud should be looking at with us—or should have been before the acquisition, looking at us was, “Oh, no, they could jump over us. They could stop our funnel.” And I used internal metrics when I was talking to them about partnership that led to the sale, which was I showed them more about their running business than they knew about themselves. I can tell them where they were stacked-ranked against each other, based on the ingress and egress of all the data on GitHub, you know, and various reactions to that in those meetings was pretty astounding.And just with that data alone, it should tell you what GitHub would be capable of and what Azure would be capable of in the combination of those two things. I mean, you did mention the ‘Deploy to Azure' button; this has been a topic, obviously, pre and post-acquisition, which is, “When is that coming?” And it was the one hard rule I set during the acquisition was, there will be no ‘Deploy to Azure' button. Azure has to earn the right to get things deployed to, in my opinion. And I think that goes to what you're saying is, if we put a ‘Deploy to Azure' button on top of this and Azure is not ready for that, or is going to fail, ultimately, that looks bad for all of us. But if it earned the right and it gets better, and it becomes one of those, then, you know, people will choose it, and that is, to me, what we're after.Corey: You have to choose the moment because if you do it too soon, you'll set the entire initiative back five years. Do it too late, and you get leapfrogged. There's a golden window somewhere and finding it is going to be hard. And I think it's pretty clear that the other hyperscalers in this space are learning, or have learned, that the next 10 years of cloud or 15 years of cloud or whatever they want to call it, and the new customers that are going to come are not the same as the customers that have built the first half of the business. And they're trying to wrap their heads around that because a lot of where the growth is going to come from is established blue chips that are used to thinking in very enterprise terms.And people think I'm making fun of them when I say this, but Microsoft has 40 years' experience apologizing to enterprises for computer failures. And that is fundamentally what cloud is. It's about talking computers to business executives because as much as we talk about builders, that is not the person at an established company with an existing IT estate, who gets to determine where $50 million a year in cloud-spend is going to go.Jason: It's [laugh] very, [laugh] very true. I mean, we've entered a different spot with cloud computing in the bell curve of adoption, and if you think that they will choose the best technology every time, well, history of computing is littered with better technologies that have failed because the distribution was better on one side. As you mentioned, Microsoft has 40 years, and I wager that Microsoft has the best sales organizations and the best enterprise accounts and, you know, all that sort of stuff, blah, blah, blah, on that side of the world than anyone in the industry. They can sell to enterprises better than almost anyone in the industry. And the other hyperscalers—there's a reason why [TK 00:08:34] is running Google Cloud right now. And Amazon, classically, has been very, very bad assigned to the enterprises. They just happened to be the first mover.Corey: In the early days, it was easy. You'd have an Amazon salesperson roll up to a company, and the exec would say, “Great, why should we consider running things on AWS?” And the answer was, “Oh, I'm sorry, wrong conversation. Right now you have 80 different accounts scattered throughout your org. I'm just here to help you unify them, get some visibility into it, and possibly give you a discount along the way.” And it was a different conversation. Shadow IT was the sole driver of cloud adoption for a long time. That is no longer true. It has to go in the front door, and that is a fundamental shift in how you go to market.Jason: One hundred percent true, and it's why I think that Microsoft has been so successful with Azure, in the last, let's call it five years in that, is that the early adopters in the second wave are doing that; they're all enterprise IT, enterprise dev shops who are buying from the top down. Now, there is still the bottoms-up adoption that going to be happening, and obviously, bottom-up adoption will happen still going forward, but we've entered the phase where that's not the primary or sole mechanism I should say. The sole mechanism of buying in. We have tops-down selling still—or now.Corey: When Microsoft announced it was acquiring GitHub, there was a universal reaction of, “Oh, shit.” Because it's Microsoft; of course they're going to ruin GitHub. Is there a second option? No, unless they find a way to ruin it twice. And none of it came to pass.It is uniformly excellent, and there's a strong argument that could be made by folks who are unaware of what happened—I'm one of them, so maybe I'm right, maybe I'm wrong—that GitHub had a positive effect on Microsoft more than Microsoft had an effect on GitHub. I don't know if that's true or not, but I could believe it based upon what I've seen.Jason: Obviously, the skepticism was well deserved at the time of acquisition, let's just be honest with it, particularly given what Microsoft's history had been for about 15—well, 20 years before, previous to Satya joining. And I was one of those people in the late '90s who would write ‘M$' in various forums. I was 18 or 19 years old, and just got into—Corey: Oh, hating Microsoft was my entire personality.Jason: [laugh]. And it was, honestly, well-deserved, right? Like, they had anti-competitive practices and they did some nefarious things. And you know, I talked about Bill Gates as an example. Bill Gates is, I mean, I don't actually know how old he is, but I'm going to guess he's late '50s, early '60s, but he's basically in the redemption phase of his life for his early years.And Microsoft is making up for Ballmer years, and later Gates years, and things of that nature. So, it was well-deserved skepticism, and particularly for a mid-career to older-career crowd who have really grown to hate Microsoft over that time. But what I would say is, obviously, it's different under Satya, and Scott, and Amy Hood, and people like that. And all we really telling people is give us a chance on this one. And I mean, all of us. The people who were running GitHub at the time, including myself and, you know, let Scott and Satya prove that they are who they say they are.Corey: It's one of those things where there's nothing you could have said that would have changed the opinion of the world. It was, just wait and see. And I think we have. It's now, I daresay, gotten to a point where Microsoft announces that they're acquiring some other beloved company, then people, I think, would extend a lot more credit than they did back then.Jason: I have to give Microsoft a ton of credit, too, on this one for the way in which they handled acquisitions, like us and others. And the reason why I think it's been so successful is also the reason why I think so many others die post-acquisition, which is that Microsoft has basically—I'll say this, and I know I won't get fired because it feels like it's true. Microsoft is essentially a PE holding company at this point. It is acquired a whole bunch of companies and lets them run independent. You know, we got LinkedIn, you got Minecraft, Xbox is its own division, but it's effectively its own company inside of it.Azure is run that way. GitHub's got a CEO still. I call it the archipelago model. Microsoft's the landmass underneath the water that binds them all, and finance, and HR, and a couple of other things, but for the most part, we manifest our own product roadmap still. We're not told what to go do. And I think that's why it's successful. If we're going to functionally integrate GitHub into Microsoft, it would have died very quickly.Corey: You clearly don't mix the streams. I mean, your gaming division writes a lot of interesting games and a lot of interesting gaming platforms. And, like, one of the most popularly played puzzle games in the world is a Microsoft property, and that is, of course, logging into a Microsoft account correctly. And I keep waiting for that to bleed into GitHub, but it doesn't. GitHub is a terrific SAML provider, it is stupidly easy to log in, it's great.And at some level, I wish that would bleed into other aspects, but you can't have everything. Tell me what it's like to go through an acquisition from a C-level position. Because having been through an acquisition before, the process looks a lot like a surprise all-hands meeting one day after the markets close and, “Listen up, idiots.” And [laugh] there we go. I have to imagine with someone in your position, it's a slightly different experience.Jason: It's definitely very different for all C-levels. And then myself in particular, as the primary driver of the acquisition, obviously, I had very privy inside knowledge. And so, from my position, I knew what was happening the entire time as the primary driver from the inside. But even so, it's still disconcerting to a degree because, in many ways, you don't think you're going to be able to pull it off. Like, you know, I remember the months, and the nights, and the weekends, and the weekend nights, and all the weeks I spent on the road trying to get all the puzzle pieces lined up for the Googles, or the Microsofts, or the eventually AWSs, the VMwares, the IBMs of the world to take seriously, just from a product perspective, which I knew would lead to, obviously, acquisition conversations.And then, once you get the call from the board that says, “It's done. We signed the letter of intent,” you basically are like, “Oh. Oh, crap. Okay, hang on a second. I actually didn't—I don't actually believe in my heart of hearts that I was going to actually be able to pull that off.” And so now, you probably didn't plan out—or at least I didn't. I was like, “Shit if we actually pulled this off what comes next?” And I didn't have that what comes next, which is odd for me. I usually have some sort of a loose plan in place. I just didn't. I wasn't really ready for that.Corey: It's got to be a weird discussion, too, when you start looking at shopping a company around to be sold, especially one at the scale of GitHub because you're at such a high level of visibility in the entire environment, where—it's the idea of would anyone even want to buy us? And then, duh, of course they would. And you look the hyperscalers, for example. You have, well, you could sell it to Amazon and they could pull another Cloud9, where they shove it behind the IAM login process, fail to update the thing meaningfully over a period of years, to a point where even now, a significant portion of the audience listening to this is going to wonder if it's a service I just made up; it sounds like something they might have done, but Cloud9 sounds way too inspired for an AWS service name, so maybe not. And—which it is real. You could go sell to Google, which is going to be awesome until some executive changes roles, and then it's going to be deprecated in short order.Or then there's Microsoft, which is the wild card. It's, well, it's Microsoft. I mean, people aren't really excited about it, but okay. And I don't think that's true anymore at all. And maybe I'm not being fair to all the hyperscalers there. I mean, I'm basically insulting everyone, which is kind of my shtick, but it really does seem that Microsoft was far and away the best acquirer possible because it has been transformative. My question—if you can answer it—is, how the hell did you see that beforehand? It's only obvious—even knowing what I know now—in hindsight.Jason: So, Microsoft was a target for me going into it, and the reason why was I thought that they were in the best overall position. There was enough humility on one side, enough hubris on another, enough market awareness, probably, organizational awareness to, kind of, pull it off. There's too much hubris on one side of the fence with some of the other acquirers, and they would try to hug us too deeply, or integrate us too quickly, or things of that nature. And I think it just takes a deep understanding of who the players are and who the egos involved are. And I think egos has actually played more into acquisitions than people will ever admit.What I saw was, based on the initial partnership conversations, we were developing something that we never launched before GitHub Actions called GitHub Launch. The primary reason we were building that was GitHub launches a five, six-year journey, and it's got many, many different phases, which will keep launching over the next couple of years. The first one we never brought to market was a partnership between all of the clouds. And it served a specific purpose. One, it allowed me to get into the room with the highest level executive at every one of those companies.Two allow me to have a deep economic conversation with them at a partnership level. And three, it allowed me to show those executives that we knew what GitHub's value was in the world, and really flip the tables around and say, “We know what we're worth. We know what our value is in the world. We know where we sit from a product influence perspective. If you want to be part of this, we'll allow it.” Not, “Please come work with us.” It was more of a, “We'll allow you to be part of this conversation.”And I wanted to see how people reacted to that. You know how Amazon reacted that told me a lot about how they view the world, and how Google reacted to that showed me exactly where they viewed it. And I remember walking out of the Google conversation, feeling a very specific way based upon the reaction. And you know, when I talked to Microsoft, got a very different feel and it, kind of, confirmed a couple of things. And then when I had my very first conversation with Nat, who have known for a while before that, I realized, like, yep, okay, this is the one. Drive hard at this.Corey: If you could do it all again, would you change anything meaningful about how you approached it?Jason: You know, I think I got very lucky doing a couple of things. I was very intentional aspects of—you know, I tried to serendipitously show up, where Diane Greene was at one point, or a serendipitously show up where Satya or Scott Guthrie was, and obviously, that was all intentional. But I never sold a company like this before. The partnership and the product that we were building was obviously very intentional. I think if I were to go through the sale, again, I would probably have tried to orchestrate at least one more year independent.And it's not—for no other reason alone than what we were building was very special. And the world sees it now, but I wish that the people who built it inside GitHub got full credit for it. And I think that part of that credit gets diffused to saying, “Microsoft fixed GitHub,” and I want the people inside GitHub to have gotten a lot more of that credit. Microsoft obviously made us much better, but that was not specific to Microsoft because we're run independent; it was bringing Nat in and helping us that got a lot of that stuff done. Nat did a great job at those things. But a lot of that was already in play with some incredible engineers, product people, and in particular our sales team and finance team inside of GitHub already.Corey: When you take a look across the landscape of the fact that GitHub has become for a certain subset of relatively sad types of which I'm definitely one a household name, what do you think the biggest misconception about the company is?Jason: I still think the biggest misconception of us is that we're a code host. Every time I talk to the RedMonk folks, they get what we're building and what we're trying to be in the world, but people still think of us as SourceForge-plus-plus in many ways. And obviously, that may have been our past, but that's definitely not where we are now and, for certain, obviously, not our future. So, I think that's one. I do think that people still, to this day, think of GitLab as one of our main competitors, and I never have ever saw GitLab as a competitor.I think it just has an unfortunate naming convention, as well as, you know, PRs, and MRs, and Git and all that sort of stuff. But we take very different views of the world in how we're approaching things. And then maybe the last thing would be that what we're doing at the scale that we're doing it as is kind of easy. When I think that—you know, when you're serving almost every developer in the world at this point at the scale at which we're doing it, we've got some scale issues that people just probably will never thankfully encounter for themselves.Corey: Well, everyone on Hacker News believes that they will, as soon as they put up their hello world blog, so Kubernetes is the only way to do anything now. So, I'm told.Jason: It's quite interesting because I think that everything breaks at scale, as we all know about from the [hyperclouds 00:20:54]. As we've learned, things are breaking every day. And I think that when you get advice, either operational, technical, or managerial advice from people who are running 10 person, 50 person companies, or X-size sophisticated systems, it doesn't apply. But for whatever reason, I don't know why, but people feel inclined to give that feedback to engineers at GitHub directly, saying, “If you just…” and in many [laugh] ways, you're just like, “Well, I think that we'll have that conversation at some point, you know, but we got a 100-plus-million repos and 65 million developers using us on a daily basis.” It's a very different world.Corey: This episode is sponsored by our friends at Oracle HeatWave is a new high-performance accelerator for the Oracle MySQL Database Service. Although I insist on calling it “my squirrel.” While MySQL has long been the worlds most popular open source database, shifting from transacting to analytics required way too much overhead and, ya know, work. With HeatWave you can run your OLTP and OLAP, don't ask me to ever say those acronyms again, workloads directly from your MySQL database and eliminate the time consuming data movement and integration work, while also performing 1100X faster than Amazon Aurora, and 2.5X faster than Amazon Redshift, at a third of the cost. My thanks again to Oracle Cloud for sponsoring this ridiculous nonsense.Corey: One of the things that I really appreciate personally because, you know, when you see something that company does, it's nice to just thank people from time to time, so I'm inviting the entire company on the podcast one by one, at some point, to wind up thanking them all individually for it, but Codespaces is one of those things that I think is transformative for me. Back in the before times, and ideally the after times, whenever I travel the only computer I brought with me for a few years now has been an iPad or an iPad Pro. And trying to get an editor on that thing that works reasonably well has been like pulling teeth, my default answer has just been to remote into an EC2 instance and use vim like I have for the last 20 years. But Code is really winning me over. Having to play with code-server and other things like that for a while was obnoxious, fraught, and difficult.And finally, we got to a point where Codespaces was launched, and oh, it works on an iPad. This is actually really slick. I like this. And it was the thing that I was looking for but was trying to have to monkey patch together myself from components. And that's transformative.It feels like we're going back in many ways—at least in my model—to the days of thin clients where all the heavy lifting was done centrally on big computers, and the things that sat on people's desks were mostly just, effectively, relatively simple keyboard, mouse, screen. Things go back and forth and I'm sure we'll have super powerful things in our pockets again soon, but I like the interaction model; it solves for an awful lot of problems and that's one of the things that, at least from my perspective, that the world may not have fully wrapped it head around yet.Jason: Great observation. Before the acquisition, we were experimenting with a couple of different editors, that we wanted to do online editors. And same thing; we were experimenting with some Action CI stuff, and it just didn't make sense for us to build it; it would have been too hard, there have been too many moving parts, and then post-acquisition, we really love what the VS Code team was building over there, and you could see it; it was just going to work. And we had this one person, well, not one person. There was a bunch of people inside of GitHub that do this, but this one person at the highest level who's just obsessed with make this work on my iPad.He's the head of product design, his name's Max, he's an ex-Heroku person as well, and he was just obsessed with it. And he said, “If it works on my iPad, it's got a chance to succeed. If it doesn't work on my iPad, I'm never going to use this thing.” And the first time we booted up Codespaces—or he booted it up on the weekend, working on it. Came back and just, “Yep. This is going to be the one. Now, we got to work on those, the sanding the stones and those fine edges and stuff.”But it really does unlock a lot for us because, you know, again, we want to become the software developer platform for everyone in the world, you got to go end-to-end, and you got to have an opinion on certain things, and you got to enable certain functionality. You mentioned Cloud9 before with Amazon. It was one of the most confounding acquisitions I've ever seen. When they bought it I was at Heroku and I thought, I thought at that moment that Amazon was going to own the next 50 years of development because I thought they saw the same thing a lot of us at Heroku saw, and with the Cloud9 acquisition, what they were going to do was just going to stomp on all of us in the space. And then when it didn't happen, we just thought maybe, you know, okay, maybe something else changed. Maybe we were wrong about that assumption, too. But I think that we're on to it still. I think that it just has to do with the way you approach it and, you know, how you design it.Corey: Sorry, you just said something that took me aback for a second. Wait, you mean software can be designed? It's not this emergent property of people building thing on top of thing? There's actually a grand plan behind all these things? I've only half kidding, on some level, where if you take a look at any modern software product that is deployed into the world, it seems impossible for even small aspects of it to have been part of the initial founding design. But as a counterargument, it would almost have to be for a lot of these things. How do you square that circle?Jason: I think you have to, just like anything on spectrums and timelines, you have to flex at various times for various things. So, if you think about it from a very, very simple construct of time, you just have to think of time horizons. So, I have an opinion about what GitHub should look like in 10 years—vaguely—in five years much more firmly, and then very, very concretely, for the next year, as an example. So, a lot of the features you might see might be more emergent, but a lot of long-term work togetherness has to be loosely tied together with some string. Now, that string will be tightened over time, but it loosely has to see its way through.And the way I describe this to folks is that you don't wake up one day and say, “I'm going on vacation,” and literally just throw a finger on the map. You have to have some sort of vague idea, like, “Hey, I want to have a beach vacation,” or, “I want to have an adventure vacation.” And then you can kind of pick a destination and say, “I'm going to Hawaii,” or, “I'm going to San Diego.” And if you're standing on the East Coast knowing you're going to San Diego, you basically know that you have to just start marching west, or driving west, or whatever. And now, you don't have to have the route mapped out just yet, but you know that hey, if I'm going due southeast, I'm off course, so how do I reorient to make sure I'm still going in the right direction?That's basically what I think about as high-level, as scale design. And it's not unfair to say that a lot of the stuff is not designed today. Amazon is very famous for not designing anything; they design a singular service. But there's no cohesiveness to what Amazon—or AWS specifically, I should say, in this case—has put out there. And maybe that's not what their strategy is. I don't know the internal workings of them, but it's very clear.Corey: Well, oh, yeah. When I first started working in the AWS space and looking through the console, it like, “What is this? It feels like every service's interface was designed by a different team, but that would—oh…” and then the light bulb went on. Yeah. You ship your culture.Jason: It's exactly it. It works for them, but I think if you're going to try to do something very, very, very different, you know, it's going to look a certain way. So, intentional design, I think, is part of what makes GitHub and other products like it special. And if you think about it, you have to have an end-to-end view, and then you can build verticals up and down inside of that. But it has to work on the horizontal, still.And then if you hire really smart people to build the verticals, you get those done. So, a good example of this is that I have a very strong opinion about the horizontal workflow nature of GitHub should look like in five years. I have a very loose opinion about what the matrix build system of Actions looks like. Because we have very, very smart people who are working on that specific problem, so long as that maps back and snaps into the horizontal workflows. And that's how it can work together.Corey: So, when you look at someone who is, I don't know, the CTO of a wildly renowned company that is basically still catering primarily to developers slash engineers, but let's be honest, geeks, it's natural to think that, oh, they must be the alpha geek. That doesn't really apply to you from everything I've been able to uncover. Am I just not digging deeply enough, or are you in fact, a terrible nerd?Jason: [laugh]. I am. I'm a terrible nerd. I am a very terrible nerd. I feel very lucky, obviously, to be in the position I'm in right now, in many ways, and people call me up and exactly that.It's like, “Hey, you must be king of the geeks.” And I'm like, “[laugh], ah, funny story here.” But um, you know, I joke that I'm not actually supposed to be in tech in first place, the way I grew up, and where I did, and how, I wasn't supposed to be here. And so, it's serendipitous that I am in tech. And then turns out I had an aptitude for distributed systems, and complex, you know, human systems as well. But when people dig in and they start talking about topics, I'm confounded. I never liked Star Wars, I never like Star Trek. Never got an anime, board games, I don't play video games—Corey: You are going to get letters.Jason: [laugh]. When I was at Canonical, oh, my goodness, the stuff I tried to hide about myself, and, like, learn, like, so who's this Boba Fett dude. And, you know, at some point, obviously, you don't have to pretend anymore, but you know, people still assume a bunch stuff because, quote, “Nerd” quote, “Geek” culture type of stuff. But you know, some interesting facts that people end up being surprised by with me is that, you know, I was very short in high school and I grew in college, so I decided that I wanted to take advantage of my newfound height and athleticism as you grow into your body. So, I started playing basketball, but I obsessed over it.I love getting good at something. So, I'd wake up at four o'clock in the morning, and go shoot baskets, and do drills for hours. Well, I got really good at it one point, and I end up playing in a Pro-Am basketball game with ex-NBA Harlem Globetrotter legends. And that's just not something you hear about in most engineering circles. You might expect that out of a salesperson or a marketing person who played pro ball—or amateur ball somewhere, or college ball or something like that. But not someone who ends up running the most important software company—from a technical perspective—in the world.Corey: It's weird. People counterintuitively think that, on some level, that code is the answer to all things. And that, oh, all this human interaction stuff, all the discussions, all the systems thinking, you have to fit a certain profile to do that, and anyone outside of that is, eh, they're not as valuable. They can get ignored. And we see that manifesting itself in different ways.And even if we take a look at people whose profess otherwise, we take a look at folks who are fresh out of a boot camp and don't understand much about the business world yet; they have transformed their lives—maybe they're fresh out of college, maybe didn't even go to college—and 18 weeks later, they are signing up for six-figure jobs. Meanwhile, you take a look at virtually any other business function, in order to have a relatively comparable degree of earning potential, it takes years of experience and being very focused on a whole bunch of other things. There's a massive distortion around technical roles, and that's a strange and difficult thing to wrap my head around. But as you're talking about it, it goes both ways, too. It's the idea of, “Oh, I'll become technical than branch into other things.” It sounded like you started off instead with a non-technical direction and then sort of adopted that from other sides. Is that right, or am I misremembering exactly how the story unfolds?Jason: No, that's about right. People say, “Hey, when did I start programming?” And it's very in vogue, I think, for a lot of people to say, “I started programming at three years old,” or five years old, or whatever, and got my first computer. I literally didn't get my first computer until I was 18-years-old. And I started programming when I got to a high school co-op with IBM at 17.It was Lotus Notes programming at the time. Had no exposure to it before. What I did, though, in college was IBM told me at the time, they said, “If you get a computer science degree will guarantee you a job.” Which for a kid who grew up the way I grew up, that is manna from heaven type of deal. Like, “You'll guarantee me a job inside where don't have to dig ditches all day or lay asphalt? Oh, my goodness. What's computer science? I'll go figure it out.”And when I got to school, what I realized was I was really far behind. Everyone was that ubergeek type of thing. So, what I did is I tried to hack the system, and what I said was, “What is a topic that nobody else has an advantage on from me?” And so I basically picked the internet because the internet was so new in the mid-'90s that most people were still not fully up to speed on it. And then the underpinnings in the internet, which basically become distributed systems, that's where I started to focus.And because no one had a real advantage, I just, you know, could catch up pretty quickly. But once I got into computers, it turned out that I was probably a very average developer, maybe even below average, but it was the system's thinking that I stood out on. And you know, large-scale distributed systems or architectures were very good for me. And then, you know, that applies not, like, directly, but it applies decently well to human systems. It's just, you know, different types of inputs and outputs. But if you think about organizations at scale, they're barely just really, really, really complex and kind of irrational distributed systems.Corey: Jason, thank you so much for taking the time to speak with me today. If people want to learn more about who you are, what you're up to, how you think about the world, where can they find you?Jason: Twitter's probably the best place at this point. Just @jasoncwarner on Twitter. I'm very unimaginative. My name is my GitHub handle. It's my Twitter username. And that's the best place that I, kind of, interact with folks these days. I do an AMA on GitHub. So, if you ever want to ask me anything, just kind of go to jasoncwarner/ama on GitHub and drop a question in one of the issues and I'll get to answering that. Yeah, those are the best spots.Corey: And we will, of course, include links to those things in the [show notes 00:33:52]. Thank you so much for taking the time to speak with me today. I really appreciate it.Jason: Thanks, Corey. It's been fun.Corey: Jason Warner, Chief Technology Officer at GitHub. I'm Cloud Economist Corey Quinn, and this is Screaming in the Cloud. If you've enjoyed this podcast, please leave a five-star review on your podcast platform of choice, whereas if you've hated this podcast, please leave a five-star review in your podcast platform of choice anyway, along with a comment that includes a patch.Corey: If your AWS bill keeps rising and your blood pressure is doing the same, then you need The Duckbill Group. We help companies fix their AWS bill by making it smaller and less horrifying. The Duckbill Group works for you, not AWS. We tailor recommendations to your business and we get to the point. Visit duckbillgroup.com to get started.Announcer: This has been a HumblePod production. Stay humble.
On today's episode, Kunle is joined by Guy Hanson, VP for Customer Engagement, Validity, a data integrity platform that enables constant assessment of customer data quality coupled with marketing analytics.Apple is soon going to alter the Email marketing landscape with the iOS 15 update. This comes hot on the heels of iOS which changed the game for performance marketing. Apple's Mail Privacy Protection (MPP) update will significantly reduce data available to marketers. Even though these changes are sweeping, there is still light at the end of the tunnel.In this episode, Kunle and Guy talk about the upcoming changes to Apple mail and their impact on Email marketing. You will get to hear about what this change really is, how it will affect you and possible solutions to cope with it. This is a great episode for email marketers and any business that sends emails to customers.-----------SPONSORS:This episode is brought to you by:Klaviyo This episode is brought to you by Klaviyo – a growth marketing platform that powers over 25,000 online businesses. Direct-to-Consumer brands like ColourPop, Huckberry, and Custom Ink rely on Klaviyo.Klaviyo helps you own customer experience and grow high-value customer relationships right from a shopper's first impression through to each subsequent purchase, Klaviyo understands every single customer interaction and empowers brands to create more personalized marketing moments.Find out more on klaviyo.com/2x. RewindThis episode is brought to you by Rewind - the #1 Backup and Recovery App for Shopify and BigCommerce stores that powers over 80,000 online businesses.Direct-to-Consumer brands like Gymshark and MVMT Watches rely on Rewind.Cloud based ecommerce platforms like Shopify and BigCommerce do not have automatic backup features. Rewind protects your store against human error, misbehaving apps, or collaborators gone bad with Automatic backups!For a free 30-day trial, Go to Rewind Backups, reach out to the Rewind team via chat or email and mention '2x ecommerce'ShipBob This episode is brought to you by ShipBob. ShipBob is an end-to-end global fulfilment provider trusted by thousands of DTC brands. With the recent launch of their first UK fulfilment centre, in London, merchants that work with ShipBob now have access to ecommerce markets in Europe as well as North America. ShipBob was ranked the #1 Fulfilment Tech Platform by AdWeek's Retail Award and enables affordable 2-day shipping. Get your products picked, packed, and shipped. Go to Shipbob.com/2x to get $500 in free shipping credits today.GorgiasThis episode is brought to you by Gorgias, the leading helpdesk for Shopify, Magento and BigCommerce merchants. Gorgias combines all your communication channels including email, SMS, social media, livechat, and phone, into one platform.This saves your team hours per day & makes managing customer orders a breeze. It also integrates seamlessly with your existing tech stack, so you can access customer information and even edit, return, refund or create an order, right from your helpdesk.Go to Gorgias.com and mention 2x ecommerce podcast for two months free.CloudwaysCloudways is the hosting platform of choice for thousands of ecommerce merchants, SMBs, and agencies all around the globe. They offer a high-performing custom stack, top-notch security, the choice between 5 cloud solution providers, ease of scalability, affordable pricing plans, and so much more.Cloudways also offers support for all PHP-based applications like Magento, WooCommerce, WordPress, Laravel, and others.Experience an unbeatable managed cloud hosting experience with Cloudways today. For a $20 Free Hosting Credit use the Coupon code: **BOOSTMAG**
Topics: Pornography, Dating, Same-Sex Attraction, Disclosure, Guilt Hosts: Dr. Alice Benton, Dr. Sheri Keffer, Larry Sonnenburg Caller Questions: I broke off my engagement to my fiancé because he was a pastor addicted to porn. What is my next step? What are some ways to effectively communicate with my 38yo daughter who told me she's in a relationship with a woman? I've been The post New Life Live: October 7, 2021 appeared first on New Life.
Tom Murtaugh is Vice President of Go-To-Market Operations at BigID, a data governance, security, and privacy platform and Forbes 2021 Cloud 100 company. In this episode, hear about Tom's work on territory modeling, a subject that is near and dear to the hearts of both Jeremey and his guest co-host Jenna Sacks, Salesloft's Director of Revenue Strategy. Visit Salesloft.com for show notes and insights from this episode.
Windows 11 is here, as is Mary Jo's Bloomberry ice cream. Windows 11 is Generally Available Windows 11 Review: Fresh, Familiar, Incomplete Microsoft's Windows 11: How to get it now (or later) Windows 11's Broken Promises Let's Fix Windows 11 Mozilla Firefox is Coming to the Microsoft Store A new generation of Surface PCs and devices arrives Microsoft Surface Pro 8 First Impressions Hands-On with the Surface Pro Signature Keyboard Hands-On with the Surface Slim Pen 2 Hands-On with the Microsoft Ocean Plastic Mouse Mary Jo Foley tries Windows 11 Bloomberry ice cream Microsoft 365 Microsoft's new non-subscription Office 2021 starts at $150 and arrives on October 5 Microsoft to add new education-focused M365 A1 per-device subscription plan Microsoft's Cloud for Financial Services to be generally available November 1 Xbox Xbox Console Shortage to Last Into 2022 Microsoft Announces First Game Pass Titles for October Xbox Cloud Gaming Expands to New Countries Microsoft Reveals Forza Horizon 5 PC Requirements Xbox Game Pass Ultimate Members with EA Play Can Join the Battlefield 2042 Open Beta Starting Today - Xbox Wire Twitch Suffers from Massive Leak Tips and picks Tip of the week: Turn off installed apps in Start's Recommended section in Windows 11 App pick of the week: Start11 gets a big update Enterprise pick of the week: Windows 11 Security Baseline is now available Codename pick of the week: Project Beluga Beer pick of the week: Transmitter S1X Wild Blueberry Saison Hosts: Leo Laporte, Mary Jo Foley, and Paul Thurrott Download or subscribe to this show at https://twit.tv/shows/windows-weekly Get episodes ad-free with Club TWiT at https://twit.tv/clubtwit Check out Paul's blog at thurrott.com Check out Mary Jo's blog at AllAboutMicrosoft.com The Windows Weekly theme music is courtesy of Carl Franklin. Sponsors: itpro.tv/windows use code WW30 Melissa.com/twit plextrac.com/twit
Topics: Narcissist, Guilt, Grief, Alcohol, Trauma, Trust, Pornography Hosts: Steve Arterburn, Dr. Jill Hubbard, Dr. Sheri Keffer Caller Questions: Is there hope for me as a narcissist? I've been separated from my husband for 5yrs. How do I speak to my husband who lost his company after 30yrs and is drinking and using tobacco to deal with it? Due to past trauma, I have a The post New Life Live: October 6, 2021 appeared first on New Life.
How does a company building a product from an open-source project get off the ground? How does it communicate its value, attract contributors, and develop a user base? And how does it spread the word without turning off engineers with typical tech marketing? Guest Emily Omier is a positioning consultant who helps companies and projects get it right. The post Day Two Cloud 118: Growing Your Open-Source Community appeared first on Packet Pushers.
On this episode of The Dr. Cloud Show: Geri is nearly out of debt and is getting anxiety that she'll fall back to her irresponsible ways. Abby is separated from her husband after his infidelity. How can she stay firm that this is a necessary ending when the people around her aren't supportive? Jane needs to give up the parenting role with her 29 year old son. Get daily coaching videos from Dr. Cloud and access to 90+ courses. Head over to www.boundaries.me and get a free 14-day subscription.
Today, we are breaking down the cloud and SaaS trailblazer, Salesforce. Founded by Marc Benioff in 1999, Salesforce has grown rapidly to become the global leader in the $100 billion CRM market. The business has 150,000 customers, including 90% of the Fortune 500, and is currently valued north of $270 billion. To break down Salesforce, Patrick O'Shaughnessy is joined by Matt Garratt, general partner at VC firm CRV and former head of Salesforce Ventures, where he led investments in companies like Snowflake, Twilio, and Zoom. In our conversation, we discuss the attributes that make Marc Benioff special, how he pushed against convention to usher in a new era of cloud-based businesses, and ways in which he has built a world around Salesforce's product lines. We also cover decision-making in the company, why its culture derives from the beaches of Hawaii, and how it's transitioning from builder to buyer. Please enjoy this breakdown of Salesforce. For the full show notes, transcript, and links to the best content to learn more, check out the episode page here. ----- This episode is brought to you by Quartr. With Quartr, you can access conference calls, investor presentations, transcripts, and earnings reports – straight from your pocket. Quartr is 100% free and includes companies from 12 markets including the US, the UK, Canada, India, and all the Scandanavian countries. Quartr is available for both iOS and Android, so check out the app today. ----- This episode is brought to you by Brex. Brex began as the first corporate card for startups and now offers a full financial stack built for scale. Get 10-20x higher credit limits, uncapped rewards, easy deposits and payments, and expense management all in one. Grow your business faster with Brex. ----- Business Breakdowns is a property of Colossus, Inc. For more episodes of Business Breakdowns, visit joincolossus.com/episodes. Stay up to date on all our podcasts by signing up to Colossus Weekly, our quick dive every Sunday highlighting the top business and investing concepts from our podcasts and the best of what we read that week. Sign up here. Follow us on Twitter: @JoinColossus | @patrick_oshag | @jspujji | @zbfuss Show Notes [00:03:14] - [First question] - What Salesforce is and what it does [00:04:55] - The scale and revenue scope of the business today [00:06:13] - Driving variables of revenue growth and their current model [00:09:10] - The unique founding story and becoming the first SaaS company [00:11:06] - What about Marc Benioff made him so compelling and successful [00:14:20] - An experience in his time at Salesforce that changed and moved him [00:15:16] - The first buyer and what they were served as a product [00:17:07] - Overview of Salesforce as a software platform [00:19:58] - The core database that powers their infrastructure and user experience [00:21:26] - Transitioning from being mostly a builder to largely a buyer and acquirer [00:23:46] - Why building trust early on is so crucial when doing something new [00:25:45] - What is Dreamforce, and how it's evolved over time [00:27:24] - The connection between Hawaiian culture and Salesforce [00:29:14] - How they continue to market and acquire customers and spend so much on marketing [00:30:44] - Their current addressable market and plans to expand into those areas [00:35:05] - How priorities are set, picked, and followed through on [00:35:58] - What is V2MOM and the role it plays with the executive team [00:38:08] - The philosophy behind Salesforce Ventures and the function it serves [00:40:27] - Potential risks the business faces going forward [00:44:24] - Key characteristics that separate Salesforce from other businesses out there [00:46:47] - Lessons for investors and builders when studying Salesforce's story
On this episode: Roz is the intermediary in a dispute between her sisters. When should she step in and when should she step back? Wendy's son is about to come into an inheritance. She's worried it will worsen his problem behaviors. Trigger Warning: Suicide is discussed in detail. Margaret has suffered the loss of her son to suicide and is feeling very alone. Head over to www.boundaries.me and get a free 14-day subscription. Get daily coaching videos from Dr. Cloud and access to 90+ courses.
The heroes get the jump on a trio of cloud giants, but a fog cloud and cunning tactics may stymie the team.Check out more from the crew by visiting us at www.glasscannonnetwork.com.For exclusive content and more, subscribe to our Patreon at www.patreon.com/glasscannon.And watch us live every week at www.twitch.tv/theglasscannon.