Podcasts about windows

Share on
Share on Facebook
Share on Twitter
Share on Reddit
Copy link to clipboard

Family of computer operating systems developed by Microsoft

  • 8,064PODCASTS
  • 35,984EPISODES
  • 51mAVG DURATION
  • 10+DAILY NEW EPISODES
  • Jan 22, 2022LATEST
windows

POPULARITY

20122013201420152016201720182019202020212022


Best podcasts about windows

Show all podcasts related to windows

Latest podcast episodes about windows

mixxio — podcast diario de tecnología

Se acabó G-Suite gratuito / El Patreon de Instagram / Viajes turísticos en VTOL / Google Play Games para PC / Garmin Fenix 7 / Wine 7.0 / Bug feo en Android Auto Patrocinador: Cuidado con las Macros Ocultas https://www.cuidadoconlasmacrosocultas.com/ es un podcast de divulgación tecnológica para empresas impulsado por Cuatroochenta que responde a preguntas clave de nuestra época en cada episodio: ¿Cómo es un ciberataque desde dentro?, ¿cuál es el impacto medioambiental de la nube?, ¿qué cambiará realmente la IA? — Suscríbete en Spotify https://open.spotify.com/episode/1IyJTLfo2XlrwNwwm0q2gp?si=2gOAVIqdR3yDHLlRU3CX5g, Apple https://podcasts.apple.com/es/podcast/cuidado-con-las-macros-ocultas/id1582767310?i=1000547511042, Ivoox https://www.ivoox.com/m05-automatismos-robots-avatares-el-nuevo-digital-audios-mp3_rf_80668395_1.html, Google https://podcasts.google.com/feed/aHR0cHM6Ly9vbW55LmZtL3Nob3dzL2N1aWRhZG8tY29uLWxhcy1tYWNyb3Mtb2N1bHRhcy9wbGF5bGlzdHMvcG9kY2FzdC5yc3M/episode/ZjgxYjg5MDQtODAyYi00MjI5LTk3Y2ItYWUwODAwOTdhZWVi?ep=14, etc. Se acabó G-Suite gratuito / El Patreon de Instagram / Viajes turísticos en VTOL / Google Play Games para PC / Garmin Fenix 7 / Wine 7.0 / Bug feo en Android Auto

Equity
Wordle's Blizzard of transparency

Equity

Play Episode Listen Later Jan 21, 2022 29:52


Despite the fact that it is a holiday week here in the United States, tech news was, well, as nuts as it usually is. At this point anything else would be a shock.So what did we get to? All of this and more:Rebundle's incredibly neat startup idea, and funding round. We love a Midwest startup here on the show thanks to Alex's roots, which means that when we got to talk about banana fiber, hair extensions, venture capital, and St. Louis all at once, we were hype.Wheel reinvented itself again with a $150 million Series C, while Gale Health played matchmaker with understaffed shifts and nurses. Plaid's buy of Cognito, a fintech startup, for around $250 million. The deal had us thinking about the power of APIs, the future of fintech, and why we don't hear about more startup M&A.Part of the why to that question could be anti-trust pressures, the sort of which that Microsoft is going to hit with its purchase attempt of Activision Blizzard, a gaming company. Microsoft already owns several gaming studios (Mojang, Bethesda), its own gaming platform (Xbox), and has long owned and operated the key PC gaming operating system (Windows). How much more does it need to own?We also touched on Wordle, free gaming, and the open web in our gaming chat, so lots to unpack there, frankly! Send us your go-to starter word. Finally, no time like the present to return to no code. At times tech is a bunch of shiny rebrands, but at other times, basic angles become non-negotiable strategies. No code, like AI and ML, is one of them. And companies like Walnut and Softr are snapping up the resulting rewards.  Whew! What a week. If you are tired already, do not look at the calendar. It will only terrify you.

All CNET Video Podcasts (HD)
Amazon apparel store coming, Google opens up Android games to Windows

All CNET Video Podcasts (HD)

Play Episode Listen Later Jan 21, 2022


In today's top stories, Amazon plans to open a brick-and-mortar clothing store later this year. Meanwhile, some Windows users can play their Android games via a limited beta.

Loop Matinal
Sexta-feira, 21/1/2022

Loop Matinal

Play Episode Listen Later Jan 21, 2022 10:32


Patrocínio: Podcast Startup Life O seu podcast sobre negócios, tecnologia e inovação. Em cada episódio, os anfitriões, Layon Lopes e Cristiane Serra, receberam importantes players do mercado brasileiro para debater ideias, projetos e tudo o que cerca as mais novas soluções do ecossistema de tecnologia e inovação. Acesse: https://link.chtbl.com/startup-loop. -------------------------------- Sobre o Podcast O Loop Matinal é um podcast do Loop Infinito que traz as notícias mais importantes do mundo da tecnologia para quem não tem tempo de ler sites e blogs de tecnologia. Marcus Mendes apresenta um resumo rápido e conciso das notícias mais importantes, sempre com bom-humor e um toque de acidez. Confira as notícias das últimas 24h, e até amanhã! -------------------------------- Apoie o Loop Matinal! O Loop Matinal está no apoia.se/loopmatinal e no picpay.me/loopmatinal! Se você quiser ajudar a manter o podcast no ar, é só escolher a categoria que você preferir e definir seu apoio mensal. Obrigado em especial aos ouvintes Advogado Junio Araujo, Alexsandra Romio, Alisson Rocha, Anderson Barbosa, Anderson Cazarotti, Angelo Almiento, Arthur Givigir, Breno Farber, Caio Santos, Carolina Vieira, Christophe Trevisani, Claudio Souza, Dan Fujita, Daniel Ivasse, Daniel Cardoso, Diogo Silva, Edgard Contente, Edson  Pieczarka Jr, Fabian Umpierre, Fabio Brasileiro, Felipe, Francisco Neto, Frederico Souza, Gabriel Souza, Guilherme Santos, Henrique Orçati, Horacio Monteiro, Igor Antonio, Igor Silva, Ismael Cunha, Jeadilson Bezerra, Jorge Fleming, Jose Junior, Juliana Majikina, Juliano Cezar, Juliano Marcon, Leandro Bodo, Luis Carvalho, Luiz Mota, Marcus Coufal, Mauricio Junior, Messias Oliveira, Nilton Vivacqua, Otavio Tognolo, Paulo Sousa, Ricardo Mello, Ricardo Berjeaut, Ricardo Soares, Rickybell, Roberto Chiaratti, Rodrigo Rosa, Rodrigo Rezende, Samir da Converta Mais, Teresa Borges, Tiago Soares, Victor Souza, Vinícius Lima, Vinícius Ghise e Wilson Pimentel pelo apoio! -------------------------------- Amazon lança loja física de roupas: https://www.geekwire.com/2022/amazon-to-try-another-tech-infused-retail-concept-with-amazon-style-its-first-physical-fashion-store/ Amazon detalha série de Senhor dos Anéis: 
https://edition.cnn.com/2022/01/19/entertainment/lord-of-the-rings-series-name-amazon-cec/index.html Relatório mostra concorrência no mundo do streaming de música: https://www.theverge.com/2022/1/20/22892939/music-streaming-services-market-share-q2-2021-spotify-apple-amazon-tencent-youtube 99 Moto é suspenso na Paraíba: 
https://tecnoblog.net/noticias/2022/01/19/99-moto-justica-suspende-mototaxi-na-pb-apos-queixa-de-empresas-de-onibus/ Telegram pode ser banido no Brasil: https://tecnoblog.net/noticias/2022/01/19/tse-cogita-banir-telegram-no-brasil-para-combater-fake-news-nas-eleicoes/ Sony pressiona a Microsoft por competitividade após compra da AB: https://www.theverge.com/2022/1/20/22892860/sony-microsoft-activision-blizzard-acquisition-comment-response Google Play Games ganha beta no Windows: 
https://www.androidpolice.com/google-play-games-pc-beta/?scrolla=5eb6d68b7fedc32c19ef33b4 Google vai acabar com a G Suite grátis: https://support.google.com/a/answer/60217?hl=pt-BR Google Labs ganha iniciativas de blockchain: https://www.bloomberg.com/news/articles/2022-01-19/google-forms-blockchain-group-under-newly-appointed-executive Crypto confirma invasão: https://www.theverge.com/2022/1/19/22891949/crypto-ceo-confirms-hundreds-accounts-hacked-bloomberg-ethereum Crypto diz que US$30 milhões foram roubados: https://www.theverge.com/2022/1/20/22892958/crypto-com-exchange-hack-bitcoin-ethereum-security Twitter para Android ganha Comunidades: https://www.theverge.com/2022/1/20/22892904/twitter-communities-android-release Conta oficial de Comunidades do Twitter: https://twitter.com/HiCommunities Facebook e Instagram terão vendas de NFTs: https://t.co/CJ4bLXhGEa Instagram testa assinaturas pagas: https://macmagazine.com.br/post/2022/01/19/instagram-testa-recurso-de-assinatura-com-alguns-criadores/ WhatsApp para Desktop ganha pausa de gravação de áudio: https://9to5mac.com/2022/01/20/whatsapp-desktop-pause-resume-recording-voice-messages/ Ericsson processa a Apple: 
https://www.marketwatch.com/story/ericsson-sues-apple-over-patent-infringement-271642515180 Apple processa a Ericsson: http://www.techmeme.com/220120/p14#a220120p14 -------------------------------- Site do Loop Matinal: http://www.loopmatinal.com Anuncie no Loop Matinal: comercial@loopinfinito.net Marcus Mendes: https://www.twitter.com/mvcmendes Loop Infinito: https://www.youtube.com/oloopinfinito

Do By Friday
Moist, Succulent, Craveable

Do By Friday

Play Episode Listen Later Jan 20, 2022 105:21


This week's challenge: make an Apple Watch face.You can hear the after show and support Do By Friday on Patreon!------Edited by Quinn RoseEngineered by Cameron Bopp------Show LinksMore notes on Podcast Notes automation – Six ColorsThe Theme SystemAmazon.com: Canvas One Line a Day: A Five-Year Memory Book (Yearly Memory Journal and Diary, Natural Canvas Cover): 9781452174792: Chronicle Books: BooksField Notes | Front Page Reporter's NotebookButton Creator for Stream Deck on the App StoreAmazon.com: Elgato Stream Deck XL - Advanced Stream Control with 32 Customizable LCD Keys, for Windows 10 and macOS 10.13 or Later (10GAT9901) : ElectronicsAmazon.com : Gold Bond Ultimate Healing Hand Cream, 3 oz., Lasts Through Handwashing : Beauty & Personal Carealexcox.meAnfernee - YouTubeUnsubscribe from emails, instantly - Unroll.MeTwo Headed GirlDocumentation for Visual Studio CodeYellowjackets (TV series) - WikipediaShoah (film) - WikipediaThe Ring (2002 film) - WikipediaCome and See - WikipediaKum & Go: Where & Means MoreTaskPaper – Plain text to-do lists for MacTickTick: Todo list, checklist and task manager app for Android, iPhone and WebDrafts | Where Text StartsGitHub Desktop | Simple collaboration from your desktopGit and GitHub for Poets - YouTubeThoughtAsylumGaslighting - WikipediaApple Unveils Apple Watch—Apple's Most Personal Device Ever - AppleCARROT Weather for iOS and AndroidApple Watch faces and their features - Apple SupportIntroducing Watchsmith - David Smith, Independent iOS DeveloperFlighty — A new way to track flightsHRV Tracker for Watch on the App StoreHeartWatch: Heart Rate Monitor on the App StoreSleepWatch — The Best Sleep Is Made.(Recorded Wednesday January 19, 2021)Next week's challenge: identify tasks that you would like to do on a regular basis. 

Accidental Tech Podcast
466: There's Probably a Wizard for It

Accidental Tech Podcast

Play Episode Listen Later Jan 20, 2022 107:49


Pre-show: Windows woes and the challenges of loading modern trucks TPM yt-dlp DeCSS SGX FairPlay Pirated movie release types Follow-up: Printer Murder Rooms John Tsombakos Richard Smith LG UltraFine 5K Repair Video (via Brian Almeida) Microsoft to Acquire Activision Blizzard for $68.7 billion Wall Street Journal Activision Blizzard’s abhorrent culture Prior acquisitions (via Jon Erlichman) Activision Blizzard: $68.7b LinkedIn: $26.2b Nuance: $19.7b Skype: $8.5b ZeniMax: $7.5b GitHub: $7.5b Nokia (phone unit): $7.2b aQuantive: $6.3b Mojang (Minecraft): $2.5b Perfect Dark Green bubbles ruin everything

Sophos Podcasts
S3 Ep66: Cybercrime busts, wormable Windows, and the crisis of featuritis

Sophos Podcasts

Play Episode Listen Later Jan 20, 2022 28:51


Russia busts Revil. Romance scammer sent to prison. Wormable Windows hole patched. Memories of the HAPPY99 virus. Linux disk encryption trouble. Apple browsers leak personal data. And how (not) to paint a computer. https://nakedsecurity.sophos.com/revil-ransomware-crew-allegedly-busted https://nakedsecurity.sophos.com/romance-scammer-who-targeted-670-women https://nakedsecurity.sophos.com/wormable-windows-http-hole https://nakedsecurity.sophos.com/serious-security-linux-full-disk-encryption-bug https://nakedsecurity.sophos.com/serious-security-apple-safari-leaks-private-data With Paul Ducklin and Doug Aamoth. Original music by Edith Mudge (https://www.edithmudge.com) Got questions/suggestions/stories to share? Email: tips@sophos.com Twitter: NakedSecurity (https://twitter.com/nakedsecurity) Instagram: NakedSecurity (https://instagram.com/nakedsecurity)

Screaming in the Cloud
Learning to Give in the Cloud with Andrew Brown

Screaming in the Cloud

Play Episode Listen Later Jan 20, 2022 38:40


About AndrewI create free cloud certification courses and somehow still make money.Links: ExamPro Training, Inc.: https://www.exampro.co/ PolyWork: https://www.polywork.com/andrewbrown LinkedIn: https://www.linkedin.com/in/andrew-wc-brown Twitter: https://twitter.com/andrewbrown TranscriptAndrew: 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 our friends at Redis, the company behind the incredibly popular open source database that is not the bind DNS server. If you're tired of managing open source Redis on your own, or you're using one of the vanilla cloud caching services, these folks have you covered with the go to manage Redis service for global caching and primary database capabilities; Redis Enterprise. To learn more and deploy not only a cache but a single operational data platform for one Redis experience, visit redis.com/hero. Thats r-e-d-i-s.com/hero. And my thanks to my friends at Redis for sponsoring my ridiculous non-sense.  Corey: This episode is sponsored in part by our friends at Rising Cloud, which I hadn't heard of before, but they're doing something vaguely interesting here. They are using AI, which is usually where my eyes glaze over and I lose attention, but they're using it to help developers be more efficient by reducing repetitive tasks. So, the idea being that you can run stateless things without having to worry about scaling, placement, et cetera, and the rest. They claim significant cost savings, and they're able to wind up taking what you're running as it is in AWS with no changes, and run it inside of their data centers that span multiple regions. I'm somewhat skeptical, but their customers seem to really like them, so that's one of those areas where I really have a hard time being too snarky about it because when you solve a customer's problem and they get out there in public and say, “We're solving a problem,” it's very hard to snark about that. Multus Medical, Construx.ai and Stax have seen significant results by using them. And it's worth exploring. So, if you're looking for a smarter, faster, cheaper alternative to EC2, Lambda, or batch, consider checking them out. Visit risingcloud.com/benefits. That's risingcloud.com/benefits, and be sure to tell them that I said you because watching people wince when you mention my name is one of the guilty pleasures of listening to this podcast.Corey: Welcome to Screaming in the Cloud. I'm Corey Quinn. My guest today is… well, he's challenging to describe. He's the co-founder and cloud instructor at ExamPro Training, Inc. but everyone knows him better as Andrew Brown because he does so many different things in the AWS ecosystem that it's sometimes challenging—at least for me—to wind up keeping track of them all. Andrew, thanks for joining.Andrew: Hey, thanks for having me on the show, Corey.Corey: How do I even begin describing you? You're an AWS Community Hero and have been for almost two years, I believe; you've done a whole bunch of work as far as training videos; you're, I think, responsible for #100daysofcloud; you recently started showing up on my TikTok feed because I'm pretending that I am 20 years younger than I am and hanging out on TikTok with the kids, and now I feel extremely old. And obviously, you're popping up an awful lot of places.Andrew: Oh, yeah. A few other places like PolyWork, which is an alternative to LinkedIn, so that's a space that I'm starting to build up on there as well. Active in Discord, Slack channels. I'm just kind of everywhere. There's some kind of internet obsession here. My wife gets really mad and says, “Hey, maybe tone down the social media.” But I really enjoy it. So.Corey: You're one of those folks where I have this challenge of I wind up having a bunch of different AWS community Slacks and cloud community, Slacks and Discords and the past, and we DM on Twitter sometimes. And I'm constantly trying to figure out where was that conversational thread that I had with you? And tracking it down is an increasingly large search problem. I really wish that—forget the unified messaging platform. I want a unified search platform for all the different messaging channels that I'm using to talk to people.Andrew: Yeah, it's very hard to keep up with all the channels for myself there. But somehow I do seem to manage it, but just with a bit less sleep than most others.Corey: Oh, yeah. It's like trying to figure out, like, “All right, he said something really useful. What was that? Was that a Twitter DM? Was it on that Slack channel? Was it that Discord? No, it was on that brick that he threw through my window with a note tied to it. There we go.”That's always the baseline stuff of figuring out where things are. So, as I mentioned in the beginning, you are the co-founder and cloud instructor at ExamPro, which is interesting because unlike most of the community stuff that you do and are known for, you don't generally talk about that an awful lot. What's the deal there?Andrew: Yeah, I think a lot of people give me a hard time because they say, Andrew, you should really be promoting yourself more and trying to make more sales, but that's not why I'm out here doing what I'm doing. Of course, I do have a for-profit business called ExamPro, where we create cloud certification study courses for things like AWS, Azure, GCP, Terraform, Kubernetes, but you know, that money just goes to fuel what I really want to do, is just to do community activities to help people change their lives. And I just decided to do that via cloud because that's my domain expertise. At least that's what I say because I've learned up on in the last four or five years. I'm hoping that there's some kind of impact I can make doing that.Corey: I take a somewhat similar approach. I mean, at The Duckbill Group, we fixed the horrifying AWS bill, but I've always found that's not generally a problem that people tend to advertise having. On Twitter, like, “Oh, man, my AWS bill is killing me this month. I've got to do something about it,” and you check where they work, and it's like a Fortune 50. It's, yeah, that moves markets and no one talks about that.So, my approach was always, be out there, be present in the community, talk about this stuff, and the people who genuinely have billing problems will eventually find their way to me. That was always my approach because turning everything I do into a sales pitch doesn't work. It just erodes confidence, it reminds people of the used mattress salesman, and I just don't want to be that person in that community. My approach has always been if I can help someone with a 15-minute call or whatnot, yeah, let's jump on a phone call. I'm not interested in nickel-and-diming folks.Andrew: Yeah. I think that if you're out there doing a lot of hard work, and a lot of it, it becomes undeniable the value you're putting out there, and then people just will want to give you money, right? And for me, I just feel really bad about taking anybody's money, and so even when there's some kind of benefit—like my courses, I could charge for access for them, but I always feel I have to give something in terms of taking somebody's money, but I would never ask anyone to give me their money. So, it's bizarre. [laugh] so.Corey: I had a whole bunch of people a year or so after I started asking, like, “I really find your content helpful. Can I buy you a cup of coffee or something?” And it's, I don't know how to charge people a dollar figure that doesn't have a comma in it because it's easy for me to ask a company for money; that is the currency of effort, work, et cetera, that companies are accustomed to. People view money very differently, and if I ask you personally for money versus your company for money, it's a very different flow. So, my solution to it was to build the annual charity t-shirt drive, where it's, great, spend 35 bucks or whatever on a snarky t-shirt once a year for ten days and all proceeds go to benefit a nonprofit that is, sort of, assuaged that.But one of my business philosophies has always been, “Work for free before you work for cheap.” And dealing with individuals and whatnot, I do not charge them for things. It's, “Oh, can you—I need some advice in my career. Can I pay you to give me some advice?” “No, but you can jump on a Zoom call with me.” Please, the reason I exist at all is because people who didn't have any reason to did me favors, once upon a time, and I feel obligated to pay that forward.Andrew: And I appreciate, you know, there are people out there that you know, do need to charge for their time. Like—Corey: Oh. Oh, yes.Andrew: —I won't judge anybody that wants to. But you know, for me, it's just I can't do it because of the way I was raised. Like, my grandfather was very involved in the community. Like, he was recognized by the city for all of his volunteer work, and doing volunteer work was, like, mandatory for me as a kid. Like, every weekend, and so for me, it's just like, I can't imagine trying to take people's money.Which is not a great thing, but it turns out that the community is very supportive, and they will come beat you down with a stick, to give you money to make sure you keep doing what you're doing. But you know, I could be making lots of money, but it's just not my priority, so I've avoided any kind of funding so like, you know, I don't become a money-driven company, and I will see how long that lasts, but hopefully, a lot longer.Corey: I wish you well. And again, you're right; no shade to anyone who winds up charging for their time to individuals. I get it. I just always had challenges with it, so I decided not to do it. The only time I find myself begrudging people who do that are someone who picked something up six months ago and decided, oh, I'm going to build some video course on how to do this thing. The end. And charge a bunch of money for it and put myself out as an expert in that space.And you look at what the content they're putting out is, and one, it's inaccurate, which just drives me up a wall, and two, there's a lack of awareness that teaching is its own skill. In some areas, I know how to teach certain things, and in other areas, I'm a complete disaster at it. Public speaking is a great example. A lot of what I do on the public speaking stage is something that comes to me somewhat naturally. So, can you teach me to be a good public speaker? Not really, it's like, well, you gave that talk and it was bad. Could you try giving it only make it good? Like, that is not a helpful coaching statement, so I stay out of that mess.Andrew: Yeah, I mean, it's really challenging to know, if you feel like you're authority enough to put something out there. And there's been a few courses where I didn't feel like I was the most knowledgeable, but I produced those courses, and they had done extremely well. But as I was going through the course, I was just like, “Yeah, I don't know how any this stuff works, but this is my best guess translating from here.” And so you know, at least for my content, people have seen me as, like, the lens of AWS on top of other platforms, right? So, I might not know—I'm not an expert in Azure, but I've made a lot of Azure content, and I just translate that over and I talk about the frustrations around, like, using scale sets compared to AWS auto-scaling groups, and that seems to really help people get through the motions of it.I know if I pass, at least they'll pass, but by no means do I ever feel like an expert. Like, right now I'm doing, like, Kubernetes. Like, I have no idea how I'm doing it, but I have, like, help with three other people. And so I'll just be honest about it and say, “Hey, yeah, I'm learning this as well, but at least I know I passed, so you know, you can pass, too.” Whatever that's worth.Corey: Oh, yeah. Back when I was starting out, I felt like a bit of a fraud because I didn't know everything about the AWS billing system and how it worked and all the different things people can do with it, and things they can ask. And now, five years later, when the industry basically acknowledges I'm an expert, I feel like a fraud because I couldn't possibly understand everything about the AWS billing system and how it works. It's one of those things where the more you learn, the more you realize that there is yet to learn. I'm better equipped these days to find the answers to the things I need to know, but I'm still learning things every day. If I ever get to a point of complete and total understanding of a given topic, I'm wrong. You can always go deeper.Andrew: Yeah, I mean, by no means am I even an expert in AWS, though people seem to think that I am just because I have a lot of confidence in there and I produce a lot of content. But that's a lot different from making a course than implementing stuff. And I do implement stuff, but you know, it's just at the scale that I'm doing that. So, just food for thought for people there.Corey: Oh, yeah. Whatever, I implement something. It's great. In my previous engineering life, I would work on large-scale systems, so I know how a thing that works in your test environment is going to blow up in a production scale environment. And I bring those lessons, written on my bones the painful way, through outages, to the way that I build things now.But the stuff that I'm building is mostly to keep my head in the game, as opposed to solving an explicit business need. Could I theoretically build a podcast transcription system on top of Transcribe or something like that for these episodes? Yeah. But I've been paying a person to do this for many years to do it themselves; they know the terms of art, they know how this stuff works, and they're building a glossary as they go, and understanding the nuances of what I say and how I say it. And that is the better business outcome; that's the answer. And if it's production facing, I probably shouldn't be tinkering with it too much, just based upon where the—I don't want to be the bottleneck for the business functioning.Andrew: I've been spending so much time doing the same thing over and over again, but for different cloud providers, and the more I do, the less I want to go deep on these things because I just feel like I'm dumping all this information I'm going to forget, and that I have those broad strokes, and when I need to go deep dive, I have that confidence. So, I'd really prefer people were to build up confidence in saying, “Yes, I think I can do this.” As opposed to being like, “Oh, I have proof that I know every single feature in AWS Systems Manager.” Just because, like, our platform, ExamPro, like, I built it with my co-founder, and it's a quite a system. And so I'm going well, that's all I need to know.And I talk to other CTOs, and there's only so much you need to know. And so I don't know if there's, like, a shift between—or difference between, like, application development where, let's say you're doing React and using Vercel and stuff like that, where you have to have super deep knowledge for that technical stack, whereas cloud is so broad or diverse that maybe just having confidence and hypothesizing the work that you can do and seeing what the outcome is a bit different, right? Not having to prove one hundred percent that you know it inside and out on day one, but have the confidence.Corey: And there's a lot of validity to that and a lot of value to it. It's the magic word I always found in interviewing, on both sides of the interview table, has always been someone who's unsure about something start with, “I'm not sure, but if I had to guess,” and then say whatever it is you were going to say. Because if you get it right, wow, you're really good at figuring this out, and your understanding is pretty decent. If you're wrong, well, you've shown them how you think but you've also called them out because you're allowed to be wrong; you're not allowed to be authoritatively wrong. Because once that happens, I can't trust anything you say.Andrew: Yeah. In terms of, like, how do cloud certifications help you for your career path? I mean, I find that they're really well structured, and they give you a goal to work towards. So, like, passing that exam is your motivation to make sure that you complete it. Do employers care? It depends. I would say mostly no. I mean, for me, like, when I'm hiring, I actually do care about certifications because we make certification courses but—Corey: In your case, you're a very specific expression of this that is not typical.Andrew: Yeah. And there are some, like, cases where, like, if you work for a larger cloud consultancy, you're expected to have a professional certification so that customers feel secure in your ability to execute. But it's not like they were trying to hire you with that requirement, right? And so I hope that people realize that and that they look at showing that practical skills, by building up cloud projects. And so that's usually a strong pairing I'll have, which is like, “Great. Get the certifications to help you just have a structured journey, and then do a Cloud project to prove that you can do what you say you can do.”Corey: One area where I've seen certifications act as an interesting proxy for knowledge is when you have a company that has 5000 folks who work in IT in varying ways, and, “All right. We're doing a big old cloud migration.” The certification program, in many respects, seems to act as a bit of a proxy for gauging where people are on upskilling, how much they have to learn, where they are in that journey. And at that scale, it begins to make some sense to me. Where do you stand on that?Andrew: Yeah. I mean, it's hard because it really depends on how those paths are built. So, when you look at the AWS certification roadmap, they have the Certified Cloud Practitioner, they have three associates, two professionals, and a bunch of specialties. And I think that you might think, “Well, oh, solutions architect must be very popular.” But I think that's because AWS decided to make the most popular, the most generic one called that, and so you might think that's what's most popular.But what they probably should have done is renamed that Solution Architect to be a Cloud Engineer because very few people become Solutions Architect. Like that's more… if there's Junior Solutions Architect, I don't know where they are, but Solutions Architect is more of, like, a senior role where you have strong communications, pre-sales, obviously, the role is going to vary based on what companies decide a Solution Architect is—Corey: Oh, absolutely take a solutions architect, give him a crash course in finance, and we call them a cloud economist.Andrew: Sure. You just add modifiers there, and they're something else. And so I really think that they should have named that one as the cloud engineer, and they should have extracted it out as its own tier. So, you'd have the Fundamental, the Certified Cloud Practitioner, then the Cloud Engineer, and then you could say, “Look, now you could do developer or the sysops.” And so you're creating this path where you have a better trajectory to see where people really want to go.But the problem is, a lot of people come in and they just do the solutions architect, and then they don't even touch the other two because they say, well, I got an associate, so I'll move on the next one. So, I think there's some structuring there that comes into play. You look at Azure, they've really, really caught up to AWS, and may I might even say surpass them in terms of the quality and the way they market them and how they construct their certifications. There's things I don't like about them, but they have, like, all these fundamental certifications. Like, you have Azure Fundamentals, Data Fundamentals, AI Fundamentals, there's a Security Fundamentals.And to me, that's a lot more valuable than going over to an associate. And so I did all those, and you know, I still think, like, should I go translate those over for AWS because you have to wait for a specialty before you pick up security. And they say, like, it's intertwined with all the certifications, but, really isn't. Like—and I feel like that would be a lot better for AWS. But that's just my personal opinion. So.Corey: My experience with AWS certifications has been somewhat minimal. I got the Cloud Practitioner a few years ago, under the working theory of I wanted to get into the certified lounge at some of the events because sometimes I needed to charge things and grab a cup of coffee. I viewed it as a lounge pass with a really strange entrance questionnaire. And in my case, yeah, I passed it relatively easily; if not, I would have some questions about how much I actually know about these things. As I recall, I got one question wrong because I was honest, instead of going by the book answer for, “How long does it take to restore an RDS database from a snapshot?”I've had some edge cases there that give the wrong answer, except that's what happened. And then I wound up having that expire and lapse. And okay, now I'll do it—it was in beta at the time, but I got the sysops associate cert to go with it. And that had a whole bunch of trivia thrown into it, like, “Which of these is the proper syntax for this thing?” And that's the kind of question that's always bothered me because when I'm trying to figure things like that out, I have entire internet at my fingertips. Understanding the exact syntax, or command-line option, or flag that needs to do a thing is a five-second Google search away in most cases. But measuring for people's ability to memorize and retain that has always struck me as a relatively poor proxy for knowledge.Andrew: It's hard across the board. Like Azure, AWS, GCP, they all have different approaches—like, Terraform, all of them, they're all different. And you know, when you go to interview process, you have to kind of extract where the value is. And I would think that the majority of the industry, you know, don't have best practices when hiring, there's, like, a superficial—AWS is like, “Oh, if you do well, in STAR program format, you must speak a communicator.” Like, well, I'm dyslexic, so that stuff is not easy for me, and I will never do well in that.So like, a lot of companies hinge on those kinds of components. And I mean, I'm sure it doesn't matter; if you have a certain scale, you're going to have attrition. There's no perfect system. But when you look at these certifications, and you say, “Well, how much do they match up with the job?” Well, they don't, right? It's just Jeopardy.But you know, I still think there's value for yourself in terms of being able to internalize it. I still think that does prove that you have done something. But taking the AWS certification is not the same as taking Andrew Brown's course. So, like, my certified cloud practitioner was built after I did GCP, Oracle Cloud, Azure Fundamentals, a bunch of other Azure fundamental certifications, cloud-native stuff, and then I brought it over because was missing, right? So like, if you went through my course, and that I had a qualifier, then I could attest to say, like, you are of this skill level, right?But it really depends on what that testament is and whether somebody even cares about what my opinion of, like, your skillset is. But I can't imagine like, when you have a security incident, there's going to be a pop-up that shows you multiple-choice answer to remediate the security incident. Now, we might get there at some point, right, with all the cloud automation, but we're not there yet.Corey: It's been sort of thing we've been chasing and never quite get there. I wish. I hope I live to see it truly I do. My belief is also that the value of a certification changes depending upon what career stage someone is at. Regardless of what level you are at, a hiring manager or a company is looking for more or less a piece of paper that attests that they're to solve the problem that they are hiring to solve.And entry-level, that is often a degree or a certification or something like that in the space that shows you have at least the baseline fundamentals slash know how to learn things. After a few years, I feel like that starts to shift into okay, you've worked in various places solving similar problems on your resume that the type that we have—because the most valuable thing you can hear when you ask someone, “How would we solve this problem?” Is, “Well, the last time I solved it, here's what we learned.” Great. That's experience. There's no compression algorithm for experience? Yes, there is: Hiring people with experience.Then, at some level, you wind up at the very far side of people who are late-career in many cases where the piece of paper that shows that they know what they're doing is have you tried googling their name and looking at the Wikipedia article that spits out, how they built fundamental parts of a system like that. I think that certifications are one of those things that bias for early-career folks. And of course, partners when there are other business reasons to get it. But as people grow in seniority, I feel like the need for those begins to fall off. Do you agree? Disagree? You're much closer to this industry in that aspect of it than I am.Andrew: The more senior you are, and if you have big names under your resume there, no one's going to care if you have certification, right? When I was looking to switch careers—I used to have a consultancy, and I was just tired of building another failed startup for somebody that was willing to pay me. And I'm like—I was not very nice about it. I was like, “Your startup's not going to work out. You really shouldn't be building this.” And they still give me the money and it would fail, and I'd move on to the next one. It was very frustrating.So, closed up shop on that. And I said, “Okay, I got to reenter the market.” I don't have a computer science degree, I don't have big names on my resume, and Toronto is a very competitive market. And so I was feeling friction because people were not valuing my projects. I had, like, full-stack projects, I would show them.And they said, “No, no. Just do these, like, CompSci algorithms and stuff like that.” And so I went, “Okay, well, I really don't want to be doing that. I don't want to spend all my time learning algorithms just so I can get a job to prove that I already have the knowledge I have.” And so I saw a big opportunity in cloud, and I thought certifications would be the proof to say, “I can do these things.”And when I actually ended up going for the interviews, I didn't even have certifications and I was getting those opportunities because the certifications helped me prove it, but nobody cared about the certifications, even then, and that was, like, 2017. But not to say, like, they didn't help me, but it wasn't the fact that people went, “Oh, you have a certification. We'll get you this job.”Corey: Yeah. When I'm talking to consulting clients, I've never once been asked, “Well, do you have the certifications?” Or, “Are you an AWS partner?” In my case, no, neither of those things. The reason that we know what we're doing is because we've done this before. It's the expertise approach.I question whether that would still be true if we were saying, “Oh, yeah, and we're going to drop a dozen engineers on who are going to build things out of your environment.” “Well, are they certified?” is a logical question to ask when you're bringing in an external service provider? Or is this just a bunch of people you found somewhere on Upwork or whatnot, and you're throwing them at it with no quality control? Like, what is the baseline level experience? That's a fair question. People are putting big levels of trust when they bring people in.Andrew: I mean, I could see that as a factor of some clients caring, just because like, when I used to work in startups, I knew customers where it's like their second startup, and they're flush with a lot of money, and they're deciding who they want to partner with, and they're literally looking at what level of SSL certificate they purchased, right? Like now, obviously, they're all free and they're very easy to get to get; there was one point where you had different tiers—as if you would know—and they would look and they would say—Corey: Extended validation certs attend your browser bar green. Remember those?Andrew: Right. Yeah, yeah, yeah. It was just like that, and they're like, “We should partner with them because they were able to afford that and we know, like…” whatever, whatever, right? So, you know, there is that kind of thought process for people at an executive level. I'm not saying it's widespread, but I've seen it.When you talk to people that are in cloud consultancy, like solutions architects, they always tell me they're driven to go get those professional certifications [unintelligible 00:22:19] their customers matter. I don't know if the customers care or not, but they seem to think so. So, I don't know if it's just more driven by those people because it's an expectation because everyone else has it, or it's like a package of things, like, you know, like the green bar in the certifications, SOC 2 compliance, things like that, that kind of wrap it up and say, “Okay, as a package, this looks really good.” So, more of an expectation, but not necessarily matters, it's just superficial; I'm not sure.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: You've been building out certifications for multiple cloud providers, so I'm curious to get your take on something that Forrest Brazeal, who's now head of content over at Google Cloud, has been talking about lately, the idea that as an engineer is advised to learn more than one cloud provider; even if you have one as a primary, learning how another one works makes you a better engineer. Now, setting aside entirely the idea that well, yeah, if I worked at Google, I probably be saying something fairly similar.Andrew: Yeah.Corey: Do you think there's validity to the idea that most people should be broad across multiple providers, or do you think specialization on one is the right path?Andrew: Sure. Just to contextualize for our listeners, Google Cloud is highly, highly promoting multi-cloud workloads, and one of their flagship products is—well, they say it's a flagship product—is Anthos. And they put a lot of money—I don't know that was subsidized, but they put a lot of money in it because they really want to push multi-cloud, right? And so when we say Forrest works in Google Cloud, it should be no surprise that he's promoting it.But I don't work for Google, and I can tell you, like, learning multi-cloud is, like, way more valuable than just staying in one vertical. It just opened my eyes. When I went from AWS to Azure, it was just like, “Oh, I'm missing out on so much in the industry.” And it really just made me such a more well-rounded person. And I went over to Google Cloud, and it was just like… because you're learning the same thing in different variations, and then you're also poly-filling for things that you will never touch.Or like, I shouldn't say you never touch, but you would never touch if you just stayed in that vertical when you're learning. So, in the industry, Azure Active Directory is, like, widespread, but if you just stayed in your little AWS box, you're not going to notice it on that learning path, right? And so a lot of times, I tell people, “Go get your CLF-C01 and then go get your AZ-900 or AZ-104.” Again, I don't care if people go and sit the exams. I want them to go learn the content because it is a large eye-opener.A lot of people are against multi-cloud from a learning perspective because say, it's too much to learn all at the same time. But a lot of people I don't think have actually gone across the cloud, right? So, they're sitting from their chair, only staying in one vertical saying, “Well, you can't learn them all at the same time.” And I'm going, “I see a way that you could teach them all at the same time.” And I might be the first person that will do it.Corey: And the principles do convey as well. It's, “Oh, well I know how SNS works on AWS, so I would never be able to understand how Google Pub/Sub works.” Those are functionally identical; I don't know that is actually true. It's just different to interface points and different guarantees, but fine. You at least understand the part that it plays.I've built things out on Google Cloud somewhat recently, and for me, every time I do, it's a refreshing eye-opener to oh, this is what developer experience in the cloud could be. And for a lot of customers, it is. But staying too far within the bounds of one ecosystem does lend itself to a loss of perspective, if you're not careful. I agree with that.Andrew: Yeah. Well, I mean, just the paint more of a picture of differences, like, Google Cloud has a lot about digital transformation. They just updated their—I'm not happy that they changed it, but I'm fine that they did that, but they updated their Google Digital Cloud Leader Exam Guide this month, and it like is one hundred percent all about digital transformation. So, they love talking about digital transformation, and those kind of concepts there. They are really good at defining migration strategies, like, at a high level.Over to Azure, they have their own cloud adoption framework, and it's so detailed, in terms of, like, execution, where you go over to AWS and they have, like, the worst cloud adoption framework. It's just the laziest thing I've ever seen produced in my life compared to out of all the providers in that space. I didn't know about zero-trust model until I start using Azure because Azure has Active Directory, and you can do risk-based policy procedures over there. So, you know, like, if you don't go over to these places, you're not going to get covered other places, so you're just going to be missing information till you get the job and, you know, that job has that information requiring you to know it.Corey: I would say that for someone early career—and I don't know where this falls on the list of career advice ranging from, “That is genius,” to, “Okay, Boomer,” but I would argue that figuring out what companies in your geographic area, or the companies that you have connections with what they're using for a cloud provider, I would bias for learning one enough to get hired there and from there, letting what you learn next be dictated by the environment you find yourself in. Because especially larger companies, there's always something that lives in a different provider. My default worst practice is multi-cloud. And I don't say that because multi-cloud doesn't exist, and I'm not saying it because it's a bad idea, but this idea of one workload—to me—that runs across multiple providers is generally a challenge. What I see a lot more, done intelligently, is, “Okay, we're going to use this provider for some things, this other provider for other things, and this third provider for yet more things.” And every company does that.If not, there's something very strange going on. Even Amazon uses—if not Office 365, at least exchange to run their email systems instead of Amazon WorkMail because—Andrew: Yeah.Corey: Let's be serious. That tells me a lot. But I don't generally find myself in a scenario where I want to build this application that is anything more than Hello World, where I want it to run seamlessly and flawlessly across two different cloud providers. That's an awful lot of work that I struggle to identify significant value for most workloads.Andrew: I don't want to think about securing, like, multiple workloads, and that's I think a lot of friction for a lot of companies are ingress-egress costs, which I'm sure you might have some knowledge on there about the ingress-egress costs across providers.Corey: Oh, a little bit, yeah.Andrew: A little bit, probably.Corey: Oh, throwing data between clouds is always expensive.Andrew: Sure. So, I mean, like, I call multi-cloud using multiple providers, but not in tandem. Cross-cloud is when you want to use something like Anthos or Azure Arc or something like that where you extend your data plane or control pla—whatever the plane is, whatever plane across all the providers. But you know, in practice, I don't think many people are doing cross-cloud; they're doing multi-cloud, like, “I use AWS to run my primary workloads, and then I use Microsoft Office Suite, and so we happen to use Azure Active Directory, or, you know, run particular VM machines, like Windows machines for our accounting.” You know?So, it's a mixed bag, but I do think that using more than one thing is becoming more popular just because you want to use the best in breed no matter where you are. So like, I love BigQuery. BigQuery is amazing. So, like, I ingest a lot of our data from, you know, third-party services right into that. I could be doing that in Redshift, which is expensive; I could be doing that in Azure Synapse, which is also expensive. I mean, there's a serverless thing. I don't really get serverless. So, I think that, you know, people are doing multi-cloud.Corey: Yeah. I would agree. I tend to do things like that myself, and whenever I see it generally makes sense. This is my general guidance. When I talk to individuals who say, “Well, we're running multi-cloud like this.” And my response is, “Great. You're probably right.”Because I'm talking in the general sense, someone building something out on day one where they don't know, like, “Everyone's saying multi-cloud. Should I do that?” No, I don't believe you should. Now, if your company has done that intentionally, rather than by accident, there's almost certainly a reason and context that I do not have. “Well, we have to run our SaaS application in multiple cloud providers because that's where our customers are.” “Yeah, you should probably do that.” But your marketing, your billing systems, your back-end reconciliation stuff generally does not live across all of those providers. It lives in one. That's the sort of thing I'm talking about. I think we're in violent agreement here.Andrew: Oh, sure, yeah. I mean, Kubernetes obviously is becoming very popular because people believe that they'll have a lot more mobility, Whereas when you use all the different managed—and I'm still learning Kubernetes myself from the next certification I have coming out, like, study course—but, you know, like, those managed services have all different kind of kinks that are completely different. And so, you know, it's not going to be a smooth process. And you're still leveraging, like, for key things like your database, you're not going to be running that in Kubernetes Cluster. You're going to be using a managed service.And so, those have their own kind of expectations in terms of configuration. So, I don't know, it's tricky to say what to do, but I think that, you know, if you have a need for it, and you don't have a security concern—like, usually it's security or cost, right, for multi-cloud.Corey: For me, at least, the lock-in has always been twofold that people don't talk about. More—less lock-in than buy-in. One is the security model where IAM is super fraught and challenging and tricky, and trying to map a security model to multiple providers is super hard. Then on top of that, you also have the buy-in story of a bunch of engineers who are very good at one cloud provider, and that skill set is not in less demand now than it was a year ago. So okay, you're going to start over and learn a new cloud provider is often something that a lot of engineers won't want to countenance.If your team is dead set against it, there's going to be some friction there and there's going to be a challenge. I mean, for me at least, to say that someone knows a cloud provider is not the naive approach of, “Oh yeah, they know how it works across the board.” They know how it breaks. For me, one of the most valuable reasons to run something on AWS is I know what a failure mode looks like, I know how it degrades, I know how to find out what's going on when I see that degradation. That to me is a very hard barrier to overcome. Alternately, it's entirely possible that I'm just old.Andrew: Oh, I think we're starting to see some wins all over the place in terms of being able to learn one thing and bring it other places, like OpenTelemetry, which I believe is a cloud-native Kubernetes… CNCF. I can't remember what it stands for. It's like Linux Foundation, but for cloud-native. And so OpenTelemetry is just a standardized way of handling your logs, metrics, and traces, right? And so maybe CloudWatch will be the 1.0 of observability in AWS, and then maybe OpenTelemetry will become more of the standard, right, and so maybe we might see more managed services like Prometheus and Grafa—well, obviously, AWS has a managed Prometheus, but other things like that. So, maybe some of those things will melt away. But yeah, it's hard to say what approach to take.Corey: Yeah, I'm wondering, on some level, whether what the things we're talking about today, how well that's going to map forward. Because the industry is constantly changing. The guidance I would give about should you be in cloud five years ago would have been a nuanced, “Mmm, depends. Maybe for yes, maybe for no. Here's the story.” It's a lot less hedge-y and a lot less edge case-y these days when I answer that question. So, I wonder in five years from now when we look back at this podcast episode, how well this discussion about what the future looks like, and certifications, and multi-cloud, how well that's going to reflect?Andrew: Well, when we look at, like, Kubernetes or Web3, we're just seeing kind of like the standardized boilerplate way of doing a bunch of things, right, all over the place. This distributed way of, like, having this generic API across the board. And how well that will take, I have no idea, but we do see a large split between, like, serverless and cloud-natives. So, it's like, what direction? Or we'll just have both? Probably just have both, right?Corey: [Like that 00:33:08]. I hope so. It's been a wild industry ride, and I'm really curious to see what changes as we wind up continuing to grow. But we'll see. That's the nice thing about this is, worst case, if oh, turns out that we were wrong on this whole cloud thing, and everyone starts exodusing back to data centers, well, okay. That's the nice thing about being a small company. It doesn't take either of us that long to address the reality we see in the industry.Andrew: Well, that or these cloud service providers are just going to get better at offering those services within carrier hotels, or data centers, or on your on-premise under your desk, right? So… I don't know, we'll see. It's hard to say what the future will be, but I do believe that cloud is sticking around in one form or another. And it basically is, like, an essential skill or table stakes for anybody that's in the industry. I mean, of course, not everywhere, but like, mostly, I would say. So.Corey: Andrew, I want to thank you for taking the time to speak with me today. If people want to learn more about your opinions, how you view these things, et cetera. Where can they find you?Andrew: You know, I think the best place to find me right now is Twitter. So, if you go to twitter.com/andrewbrown—all lowercase, no spaces, no underscores, no hyphens—you'll find me there. I'm so surprised I was able to get that handle. It's like the only place where I have my handle.Corey: And we will of course put links to that in the [show notes 00:34:25]. Thanks so much for taking the time to speak with me today. I really appreciate it.Andrew: Well, thanks for having me on the show.Corey: Andrew Brown, co-founder and cloud instructor at ExamPro Training and so much more. 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, along with an angry comment telling me that I do not understand certifications at all because you're an accountant, and certifications matter more in that industry.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.

Windows Weekly (Video HI)
WW 760: The Activision Acquisition - Microsoft's largest acquisition, PC 2021 sales, Surface Laptop SE

Windows Weekly (Video HI)

Play Episode Listen Later Jan 19, 2022 122:47


Microsoft is acquiring Activision Blizzard, the makers of WoW, CoD, Overwatch, and Candy Crush, among other gaming hits. Microsoft's $68.7 billion acquisition is the biggest in the company's history. Sony shares stumble as the firm cedes $20 billion in value overnight Windows 11 SE devices are rolling out for the education market, starting as cheap as $219. Surface Laptop SE is now available for schools to purchase. PC sales, in a third consecutive year of growth, increased 16% in 2021. Windows 11 Insider Preview Build 22538 announced and released to the Dev channel. New updates roll out for Pixel 6 and Pixel 6 Pro phones. Game Pass titles for January include Death's Door and Nobody Saves the World Tips & Picks: Tip of the week: Programming Windows articles and projects App pick of the week: .NETpad Enterprise pick of the week: Microsoft fixes yet another botched Patch Tuesday update Codename pick of the week: Nickel Beer pick of the week: Shacksbury The Vermonter Cider 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: hackerrank.com/WW CDW.com/IntelClient

Windows Weekly (MP3)
WW 760: The Activision Acquisition - Microsoft's largest acquisition, PC 2021 sales, Surface Laptop SE

Windows Weekly (MP3)

Play Episode Listen Later Jan 19, 2022 122:12


Microsoft is acquiring Activision Blizzard, the makers of WoW, CoD, Overwatch, and Candy Crush, among other gaming hits. Microsoft's $68.7 billion acquisition is the biggest in the company's history. Sony shares stumble as the firm cedes $20 billion in value overnight Windows 11 SE devices are rolling out for the education market, starting as cheap as $219. Surface Laptop SE is now available for schools to purchase. PC sales, in a third consecutive year of growth, increased 16% in 2021. Windows 11 Insider Preview Build 22538 announced and released to the Dev channel. New updates roll out for Pixel 6 and Pixel 6 Pro phones. Game Pass titles for January include Death's Door and Nobody Saves the World Tips & Picks: Tip of the week: Programming Windows articles and projects App pick of the week: .NETpad Enterprise pick of the week: Microsoft fixes yet another botched Patch Tuesday update Codename pick of the week: Nickel Beer pick of the week: Shacksbury The Vermonter Cider 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: hackerrank.com/WW CDW.com/IntelClient

All TWiT.tv Shows (MP3)
Windows Weekly 760: The Activision Acquisition

All TWiT.tv Shows (MP3)

Play Episode Listen Later Jan 19, 2022 122:12


Microsoft is acquiring Activision Blizzard, the makers of WoW, CoD, Overwatch, and Candy Crush, among other gaming hits. Microsoft's $68.7 billion acquisition is the biggest in the company's history. Sony shares stumble as the firm cedes $20 billion in value overnight Windows 11 SE devices are rolling out for the education market, starting as cheap as $219. Surface Laptop SE is now available for schools to purchase. PC sales, in a third consecutive year of growth, increased 16% in 2021. Windows 11 Insider Preview Build 22538 announced and released to the Dev channel. New updates roll out for Pixel 6 and Pixel 6 Pro phones. Game Pass titles for January include Death's Door and Nobody Saves the World Tips & Picks: Tip of the week: Programming Windows articles and projects App pick of the week: .NETpad Enterprise pick of the week: Microsoft fixes yet another botched Patch Tuesday update Codename pick of the week: Nickel Beer pick of the week: Shacksbury The Vermonter Cider 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: hackerrank.com/WW CDW.com/IntelClient

Radio Leo (Audio)
Windows Weekly 760: The Activision Acquisition

Radio Leo (Audio)

Play Episode Listen Later Jan 19, 2022 122:12


Microsoft is acquiring Activision Blizzard, the makers of WoW, CoD, Overwatch, and Candy Crush, among other gaming hits. Microsoft's $68.7 billion acquisition is the biggest in the company's history. Sony shares stumble as the firm cedes $20 billion in value overnight Windows 11 SE devices are rolling out for the education market, starting as cheap as $219. Surface Laptop SE is now available for schools to purchase. PC sales, in a third consecutive year of growth, increased 16% in 2021. Windows 11 Insider Preview Build 22538 announced and released to the Dev channel. New updates roll out for Pixel 6 and Pixel 6 Pro phones. Game Pass titles for January include Death's Door and Nobody Saves the World Tips & Picks: Tip of the week: Programming Windows articles and projects App pick of the week: .NETpad Enterprise pick of the week: Microsoft fixes yet another botched Patch Tuesday update Codename pick of the week: Nickel Beer pick of the week: Shacksbury The Vermonter Cider 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: hackerrank.com/WW CDW.com/IntelClient

Tactical Crouch - Your Source for Overwatch League News, Interviews, & More!
Can Microsoft Save Overwatch Esports & Are PVP Talents Good? | Tactical Crouch Ep. 210

Tactical Crouch - Your Source for Overwatch League News, Interviews, & More!

Play Episode Listen Later Jan 19, 2022 120:26


Did anyone have Microsoft acquire Activision Blizzard for 68.7 billion dollars on their 2022 bingo card? After surviving the whiplash of the week, AVRL, Yiska and Volamel attempt to tackle the daunting question of if our new Windows-based overlords will impact Overwatch esports in a positive or negative way. And the community drops a line; would PVP talents work in Overwatch 2, what makes a player “great”, and who would be better in GOATS--Gladiators with Fissure or Shanghai with Fate?

The Bodybuilding Dietitians
#148 How To Track Meals Out, Post-Workout Windows & What To Do Before You Compete In Bodybuilding

The Bodybuilding Dietitians

Play Episode Listen Later Jan 19, 2022 35:56


Welcome back for episode 148 of The Bodybuilding Dietitians Podcast! On this week's episode Tyarra and Jack answer and discuss various topics including: - Advice for tracking meals out - Does tan and oil make a bodybuilding stage slippery? - What we recommend to do BEFORE you consider competing - How soon should you eat your post-workout meal? - Does meal timing matter more in prep compared to the improvement season? - TEA HACK Link for TBD Tees: https://www.thebodybuildingdietitians.com/tbdapparel/qhk1uy9fz085ldg2jbeofrobnre9u6 Thank you again for tuning into the podcast and we hope you enjoy! We would greatly appreciate if you would please subscribe to the channel, give us a rating, leave us a review and tell your friends about the podcast! The more people we can reach out to and help the better! Stay tuned for more podcasts released on a weekly basis! Business Website: www.thebodybuildingdietitians.com Tyarra's Instagram: www.instagram.com/tyarranelson/?hl=en Jack's Instagram: www.instagram.com/jack.radfordsmith/?hl=en The Bodybuilding Dietitians Instagram: www.instagram.com/thebodybuildingdietitians/?hl=en YouTube: www.youtube.com/channel/UC9Why7CvHSXNMG8Aws6dnww 10% Off Marmadukes Peanut Butter Powder (discount code TBD10): www.marmadukes.com.au/discount/TBD10 VPA 10% off codes used at checkout: www.vpa.com.au/ TYARRA JACK

mixxio — podcast diario de tecnología
El contenido es el rey

mixxio — podcast diario de tecnología

Play Episode Listen Later Jan 19, 2022 15:59


Microsoft compra Activision Blizzard / Más de 500 millones de abonados a música en streaming / YouTube cierra Originals / El CEO de Airbnb "se va de Airbnb" / Intel presenta un minero de Bitcoin / AdBlock Plus gana el juicio / Primera candidata real de exoluna Patrocinador: Cuidado con las Macros Ocultas https://www.cuidadoconlasmacrosocultas.com/ es un podcast de divulgación tecnológica para empresas impulsado por Cuatroochenta que responde a preguntas clave de nuestra época en cada episodio: ¿Cómo es un ciberataque desde dentro?, ¿cuál es el impacto medioambiental de la nube?, ¿qué cambiará realmente la IA? — Suscríbete en Spotify https://open.spotify.com/episode/1IyJTLfo2XlrwNwwm0q2gp?si=2gOAVIqdR3yDHLlRU3CX5g, Apple https://podcasts.apple.com/es/podcast/cuidado-con-las-macros-ocultas/id1582767310?i=1000547511042, Ivoox https://www.ivoox.com/m05-automatismos-robots-avatares-el-nuevo-digital-audios-mp3_rf_80668395_1.html, Google https://podcasts.google.com/feed/aHR0cHM6Ly9vbW55LmZtL3Nob3dzL2N1aWRhZG8tY29uLWxhcy1tYWNyb3Mtb2N1bHRhcy9wbGF5bGlzdHMvcG9kY2FzdC5yc3M/episode/ZjgxYjg5MDQtODAyYi00MjI5LTk3Y2ItYWUwODAwOTdhZWVi?ep=14, etc. Microsoft compra Activision Blizzard / Más de 500 millones de abonados a música en streaming / YouTube cierra Originals / El CEO de Airbnb "se va de Airbnb" / Intel presenta un minero de Bitcoin / AdBlock Plus gana el juicio / Primera candidata real de exoluna

Lock and Code
Why we don't patch, with Jess Dodson

Lock and Code

Play Episode Listen Later Jan 18, 2022 46:51


In 2017, the largest ransomware attack ever recorded hit the world, infecting more than 230,000 computers across more than 150 countries in just 24 hours. And it could have been solved with a patch that was released nearly two months prior. This was the WannaCry ransomware attack, and its final, economic impact—in ransoms paid but also in downtime and recovery efforts—has been estimated at about $4 billion. All of it could have been avoided if every organization running a vulnerable version of Windows 7 had patched that vulnerability, as Microsoft recommended. But that obviously didn't happen. Why is that? In today's episode of Lock and Code with host David Ruiz, we speak with cybersecurity professional Jess Dodson about why patching is so hard to get right for so many organizations, and what we could all do to better improve our patching duties.

Microsoft Cloud Show
Episode 442 | New Azure Features, TLS Changes & SDKs for Developers

Microsoft Cloud Show

Play Episode Listen Later Jan 18, 2022 51:37


Tune in to episode 442 and hear Andrew Connell & Chris Johnson cover the latest news related to Microsoft Azure products & services, Microsoft Teams, and what's new from Microsoft 365!What’s New With Microsoft 365 MC306666: Pairing naming convention between Teams channels and corresponding SharePoint folders MC306669: Self-service trials for Microsoft Project and Microsoft Visio MC309911: Automatically Detect Music MC312490: Yammer Cross-geo external collaboration support on External Networks for the EU News Azure Storage TLS: Critical changes are almost here! (…and why you should care) Accelerate your websites with Azure Static Web Apps enterprise-edge Updates to Azure Files: NFS v4.1, higher performance limits, and reserved instance pricing Introducing the new Azure SDK management libraries for JavaScript/TypeScript 3 ways technology can help rebuild your frontline workforce Microsoft Teams: Chat with Teams personal account users First Microsoft Pluton-powered Windows 11 PCs to start rolling out this year Microsoft should sell Office and Windows to boost cloud business, former executive says Best CEO of 2021 goes to… Qualcomm Announces Collaboration with Microsoft to Expand and Accelerate AR to Usher in New Gateways to the Metaverse Ask HN: Are Microsoft development stack and Azure a dead-end career path? Picks AC’s Pick An Unanswered Question at the Heart of the U.S.'s Nuclear Arsenal CJ’s Pick Looking for a Apartment to Share: Seattle(Redmond) Area

mixxio — podcast diario de tecnología
Viaje al centro de la Tierra

mixxio — podcast diario de tecnología

Play Episode Listen Later Jan 18, 2022 15:57


El volcán de Tonga rompe cables submarinos / El núcleo terrestre está más frío de lo esperado / Rusia moderniza el Tupolev 160 / Bombardeo casero con drones / Representantes de OnlyFans / 25 GW de eólica en Escocia Patrocinador: Cuidado con las Macros Ocultas https://www.cuidadoconlasmacrosocultas.com/ es un podcast de divulgación tecnológica para empresas impulsado por Cuatroochenta que responde a preguntas clave de nuestra época en cada episodio: ¿Cómo es un ciberataque desde dentro?, ¿cuál es el impacto medioambiental de la nube?, ¿qué cambiará realmente la IA? — Suscríbete en Spotify https://open.spotify.com/episode/1IyJTLfo2XlrwNwwm0q2gp?si=2gOAVIqdR3yDHLlRU3CX5g, Apple https://podcasts.apple.com/es/podcast/cuidado-con-las-macros-ocultas/id1582767310?i=1000547511042, Ivoox https://www.ivoox.com/m05-automatismos-robots-avatares-el-nuevo-digital-audios-mp3_rf_80668395_1.html, Google https://podcasts.google.com/feed/aHR0cHM6Ly9vbW55LmZtL3Nob3dzL2N1aWRhZG8tY29uLWxhcy1tYWNyb3Mtb2N1bHRhcy9wbGF5bGlzdHMvcG9kY2FzdC5yc3M/episode/ZjgxYjg5MDQtODAyYi00MjI5LTk3Y2ItYWUwODAwOTdhZWVi?ep=14, etc. El volcán de Tonga rompe cables submarinos / El núcleo terrestre está más frío de lo esperado / Rusia moderniza el Tupolev 160 / Bombardeo casero con drones / Representantes de OnlyFans / 25 GW de eólica en Escocia

Broken Silicon
136. Nvidia Kills MSRP w/ 3080 12GB, RX 6500 XT AIB Pricing, Intel Raptor Lake in Q3

Broken Silicon

Play Episode Listen Later Jan 17, 2022 116:38


Inflation has changed AMD Low End, Meteor Lake is coming for ZEN 4, and RADEON Super Resolution! [SPON: brokensilicon = -30% off Windows, dieshrink = -3% off Everything: https://biitt.ly/shbSk] [SPON: Get 10% off Tasty Vite Ramen with Code “brokensilicon” at: https://bit.ly/3oyv4tR] 0:00 Everyone has COVID, RDNA 3 Naming, Metaverse (Intro Banter) 10:11 Rembrandt Segmentation, OLED vs Mini-LED Monitors (Corrections & Omissions) 22:22 Nvidia Ends MSRP with the 3080 12GB Launch 29:37 RTX 3090 Ti Production Halted – and no one cares. 39:20 Why hasn't AMD brought Navi 21 to laptop? 41:08 RX 6500 XT AIB Pricing & Launch Clarifications 51:40 The reality of pricing due to inflation, why AMD used Navi 24 outside Laptop 1:00:00 Will AMD & Nvidia learn from their supply mistakes in 2021? 1:07:00 RADEON Super Resolution to deliver 70% Improvement in Most Games 1:12:00 Intel Raptor Lake Q3 Release Date, Zen 4 will compete with Meteor Lake 1:24:00 AM5 to last 4 Years and share cooler compatibility with AM4 1:29:00 DDR4 to DDR5 Converter, PS4 Production Continued, Intel Ohio Fab (Wrap Up) 1:44:50 Will High End Laptops do 4K120+ soon? Xilinx use to AMD? (Final Reader Mail) https://youtu.be/xSi6wf4V_CA https://youtu.be/tS7lx5us1fg https://youtu.be/oBDFtJ4lR2c https://twitter.com/mooreslawisdead/status/1480774660950216705 https://twitter.com/VideoCardz/status/1481953608614793218 https://www.tweaktown.com/news/83990/geforce-rtx-3090-ti-production-halted-trouble-in-silicon-paradise/index.html https://twitter.com/cdemerjian/status/1480597930780229633?s=21 https://hothardware.com/news/radeon-rx-6500-xt-only-supports-pcie-x4 https://youtu.be/qm_yHEr-d6U https://wccftech.com/nvidia-geforce-rtx-3050-8-gb-custom-model-from-galax-listed-online-for-over-400-us-sold-out-within-hours/ https://www.notebookcheck.net/AMD-Radeon-Super-Resolution-to-deliver-up-to-70-performance-improvements-for-most-games.591804.0.html https://youtu.be/Qa7mPr5TMLM https://twitter.com/mooreslawisdead/status/1481470432792436739 https://videocardz.com/newz/amd-am5-to-be-a-long-lived-platform-backward-compatibility-with-am4-coolers-confirmed https://wccftech.com/amd-talks-next-gen-am5-ryzen-7000-platform-longevity-why-ryzen-7-5800x3d-is-the-only-v-cache-option-how-radeon-rx-6500-xt-tackles-miners-hint-at-8-gb-option/ https://www.pcgamer.com/asus-develops-a-ddr4-to-ddr5-adapter-card/ https://hardocp.com/blog/gpu-msrp-is-not-meaningless https://www.polygon.com/22880166/ps5-demand-sales-ps4-supported-production-sony https://www.tomshardware.com/news/intel-to-spend-up-to-120-billion-on-new-us-manufacturing-hub https://videocardz.com/newz/inno3d-confirms-geforce-rtx-3050-features-ga106-150-gpu https://www.techpowerup.com/290102/amds-upcoming-x670-chipset-could-be-a-dual-b650-package-very-difficult-for-itx-board-integration https://twitter.com/9550pro/status/1473228052666925060 https://videocardz.com/newz/adata-shows-off-pcie-gen5-m-2-ssds-with-up-to-14-gb-s-sequential-read-speed https://www.hardwaretimes.com/nvidia-pays-tsmc-7-billion-to-secure-5nm-chips-for-rtx-4080-4090-gpus/ https://videocardz.com/newz/intel-core-i9-12900hk-alder-lake-h-cpu-performance-demonstrated-during-pcworlds-podcast https://wccftech.com/tsmcs-3d-tech-supply-manufacturing-woes-may-cause-limited-amd-ryzen-7-5800x3d-availability-could-also-explain-no-3d-variants-of-5900x-5950x/ https://www.theverge.com/2022/1/13/22881211/microsoft-discontinues-xbox-one-consoles-2020

#WeNeedToTalk
Episode 2: Inez Ribustello

#WeNeedToTalk

Play Episode Listen Later Jan 17, 2022 33:06


On Episode 2 Malynda chats with former Windows on the World employee Inez Ribustello. They chat about her narrowly missing 9/11, how 20 years later she has managed to heal, and her new memoir Life after Windows that chronicles her life in  New York before, during and after 9/11. Eastern North Carolina native, Inez Ribustello, got her start in the world of food and wine after moving to New York City to pursue a career in cooking.  Her wine career took a huge leap forward when she became an Assistant Cellar Master at the renowned World Trade Center restaurant Windows on the World. In a very short time, she was promoted to Beverage Director, putting her in the position as wine buyer for the largest grossing restaurant in North America.    The terrorist attacks on September 11, 2001 impacted her both personally and professionally.Having lost friends, colleagues, and her job in the attacks, she had to face her future.In September of 2021, Inez releases her self-published memoir Life After Windows, a book she has been working on for the past 20 years.    

The Modern Therapist's Survival Guide with Curt Widhalm and Katie Vernoy
Who's in the Room? Siri, Alexa, and Confidentiality

The Modern Therapist's Survival Guide with Curt Widhalm and Katie Vernoy

Play Episode Listen Later Jan 17, 2022 29:19


Who's in the Room? Siri, Alexa, and Confidentiality Curt and Katie chat about how therapists can maintain confidentiality in a world of AI assistants and smart devices. What duty do clinicians have to inform clients? How can we balance confidentiality with the reality of how commonly these devices are involved in therapy? Can telehealth therapy be completely confidential and data secure? We discuss our shift in clinical responsibility, best practices, and how we can minimize exposure of clinical data to ensure the confidentiality our clients expect and deserve. In this podcast episode we talk about something therapists might not consider: smart devices and AI assistants We received a couple of requests to talk about the impact of smart devices on confidentiality and their compliance with HIPAA within a therapeutic environment. We tackle this question in depth: What are best practices for protecting client confidentiality with smart devices? Turning off the phone, or placing the phone on “airplane mode” Warning clients about their own smart devices and confidentiality risks The ethical responsibilities to inform about limits of confidentiality and take precautions It's all about giving clients choice and information What should therapists consider when smart devices and AI assistants are in the room? “It's not to say we have to be luddites, it's that we have to disclose the potential limits of confidentiality that clients have come to expect.”  – Curt Widhalm Whistle-blower reports on how often these devices are actually listening Turning off your phone is a lot cheaper than identity theft Consider your contacts, geolocation, and Wi-Fi connection Some of this, as we progress into a more technological world, might be unavoidable How do Alexa and Siri impact HIPAA compliance for therapists? The importance of end-to-end encryption for all HIPAA activities (and your smart device may not be compliant) The cost of HIPAA violations if identity theft can be traced back Understand the risks you are taking, do what you can, and remember no one is perfect What can modern therapists do with their smart devices? “Whether it's convenience or practicality that has you putting your client's contacts into your phone, we have to think beyond that because it really can harm our ability to keep that data safe.” – Katie Vernoy GPS location services can be left on for a safety reason, emergency services use GPS location Adjusting settings for voice activation, data sharing, when apps are running, locations, etc. Turning off and airplane mode are also options Always let the client know the limits of confidentiality Our Generous Sponsor for this episode of the Modern Therapist's Survival Guide: Buying Time LLC Buying Time is a full team of Virtual Assistants, with a wide variety of skill sets to support your business. From basic admin support, customer service, and email management to marketing and bookkeeping. They've got you covered. Don't know where to start? Check out the systems inventory checklist which helps business owners figure out what they don't want to do anymore and get those delegated asap. You can find that checklist at http://buyingtimellc.com/systems-checklist/ Buying Time's VA's support businesses by managing email communications, CRM or automation systems, website admin and hosting, email marketing, social media, bookkeeping and much more. Their sole purpose is to create the opportunity for you to focus on supporting those you serve while ensuring that your back office runs smoothly. With a full team of VA's it gives the opportunity to hire for one role and get multiple areas of support. There's no reason to be overwhelmed with running your business with this solution available. Book a consultation to see where and how you can get started getting the support you need - https://buyingtimellc.com/book-consultation/ Resources for Modern Therapists mentioned in this Podcast Episode: We've pulled together resources mentioned in this episode and put together some handy-dandy links. Please note that some of the links below may be affiliate links, so if you purchase after clicking below, we may get a little bit of cash in our pockets. We thank you in advance! Psychotherapy in Ontario: How Confidential is my Therapy? By Beth Mares, Registered Psychotherapist The Privacy Problem with Digital Assistants by Kaveh Waddell Hey Siri and Alexa: Let's Talk Privacy Practices by Elizabeth Weise, USA Today Patient and Consumer Safety Risks When Using Conversational Assistants for Medical Information: An Observational Study of Siri, Alexa, and Google Assistant, 2018 Hey Siri: Did you Break Confidentiality, or did I? By Nicole M. Arcuri Sanders, Counseling Today Alexa, Siri, Google Assistant Not HIPAA Compliant, Psychiatry Advisor Hey Alexa, are you HIPAA compliant? 2018 Person-Centered Tech   Relevant Episodes of MTSG Podcast: Which Theoretical Orientation Should You Choose? Is Your Practice Ready for Paid Digital Marketing? An Interview with John Sanders Waiving Goodbye to Telehealth Progress: An interview with Dr. Ben Caldwell, LMFT Malpractice is No Joke   Who we are: Curt Widhalm, LMFT Curt Widhalm is in private practice in the Los Angeles area. He is the cofounder of the Therapy Reimagined conference, an Adjunct Professor at Pepperdine University and CSUN, a former Subject Matter Expert for the California Board of Behavioral Sciences, former CFO of the California Association of Marriage and Family Therapists, and a loving husband and father. He is 1/2 great person, 1/2 provocateur, and 1/2 geek, in that order. He dabbles in the dark art of making "dad jokes" and usually has a half-empty cup of coffee somewhere nearby. Learn more at: www.curtwidhalm.com Katie Vernoy, LMFT Katie Vernoy is a Licensed Marriage and Family Therapist, coach, and consultant supporting leaders, visionaries, executives, and helping professionals to create sustainable careers. Katie, with Curt, has developed workshops and a conference, Therapy Reimagined, to support therapists navigating through the modern challenges of this profession. Katie is also a former President of the California Association of Marriage and Family Therapists. In her spare time, Katie is secretly siphoning off Curt's youthful energy, so that she can take over the world. Learn more at: www.katievernoy.com A Quick Note: Our opinions are our own. We are only speaking for ourselves – except when we speak for each other, or over each other. We're working on it. Our guests are also only speaking for themselves and have their own opinions. We aren't trying to take their voice, and no one speaks for us either. Mostly because they don't want to, but hey. Stay in Touch with Curt, Katie, and the whole Therapy Reimagined #TherapyMovement: www.mtsgpodcast.com www.therapyreimagined.com https://www.facebook.com/therapyreimagined/ https://twitter.com/therapymovement https://www.instagram.com/therapyreimagined/ Consultation services with Curt Widhalm or Katie Vernoy: The Fifty-Minute Hour Connect with the Modern Therapist Community: Our Facebook Group – The Modern Therapists Group   Modern Therapist's Survival Guide Creative Credits: Voice Over by DW McCann https://www.facebook.com/McCannDW/ Music by Crystal Grooms Mangano http://www.crystalmangano.com/ Transcript for this episode of the Modern Therapist's Survival Guide podcast (Autogenerated): Curt Widhalm 00:00 This episode of the modern therapist Survival Guide is sponsored by buying time Katie Vernoy  00:04 Buying Time has a full team of virtual assistants with a wide variety of skill sets to support your business. From basic admin support customer service and email management to marketing and bookkeeping, they've got you covered. Don't know where to start, check out the system's inventory checklist, which helps business owners figure out what they don't want to do anymore and get those delegated ASAP. You can find that checklist at buying time. llc.com forward slash systems stash checklist. Curt Widhalm  00:31 Listen at the end of the episode for more information. Announcer  00:34 You're listening to the modern therapist survival guide where therapists live, breathe, and practice as human beings. To support you as a whole person and a therapist. Here are your hosts, Curt Widhalm and Katie Vernoy. Curt Widhalm  00:50 Welcome back modern therapists. This is the modern therapist Survival Guide. I'm Curt Widhalm, with Katie Vernoy. And this is the podcast for therapists about all things therapy, the things that we consider the things that we don't. And stay is one of those days where we're going to be talking about some of the things that we might not consider. And this really comes with some of those smart devices in our homes, our offices, potentially even in our clients homes, and what it means for confidentiality, especially in terms of compliance with things like HIPAA, and who's always listening. And you know, Google a few years ago changed kind of their motto from do no evil to whatever it is. Now I just know that they're, they're no longer committing to not doing evil. But I want to start with kind of this idea of when we especially start with telehealth clients, but this is also going to be true when it comes to our in person sessions with things like smartphones and just kind of being cool in the modern era and having things like Amazon echoes or Google Docs, or any of these kinds of things in our offices of are those things always listening, and what does this mean for client data?   Katie Vernoy  02:07 That's a big intro. Yeah, I, I've worried about this for a while. And that's why I don't have a any kind of AI in my office, although after reading some of these articles I actually do because I have my phone in my office because I receive messages. And I do all kinds of stuff. So it's a little bit scary to think about what might be listening.   Curt Widhalm  02:33 So I mean, this is where I think any of us who have a Windows laptop, there's Cortana, if you have one of these Amazon devices, there's Alexa, if somebody you know, has Siri, these things are listening. And well, some of the tech stuff, you know, might say that they're only listening for key words that would activate them articles that we're looking at here is what we're going to dive into today. As far as does this mean that our sessions with clients are actually as confidential as we're talking about? And what does this mean for our own best practices as we go forward, having smart devices in our offices in our homes, and potentially even in our client's homes. And the way that this conversation initially came up was I was at a dinner party with some other therapists and talking about great dinner party talk that happens wherever I'm at with other therapists, which is,   Katie Vernoy  03:34 Yeah, only although therapists with me, I tend to   Curt Widhalm  03:37 Get people asking a lot ethics questions. And one of the questions that was up for discussion was our duties when it comes to talking with clients about confidentiality, particularly when it comes to telehealth. And I was describing that we have a responsibility to talk with our clients about the limits of confidentiality, that may include privacy in their own homes, if there's potentially somebody who's walking down the hallway, outside their bedroom or office door, wherever they're doing sessions from, and one of the other therapists at this party said, Well, what about any of the smart devices? Do you ever warn them about Google or Alexa or Siri actually listening? And that's what sparked this. So if you ever want a podcast episode, I am available for dinner parties for you to float ideas by.   Katie Vernoy  04:28 Okay, okay, there we go. And so this   Curt Widhalm  04:31 Has led to some research on our part here as far as what is our responsibility? And what do we need to do with our clients as it pertains to some of this AI discussion, even when we don't think that it's happening?   Katie Vernoy  04:47 Well, to me, when you propose this idea for the podcast, the first thing that came to mind was really around convenience versus confidentiality. Because when we're looking at a lot of these things, When we don't turn off voice activation, when we don't make sure that we're not connected to everything through our phones, and all of the contacts and everything within our phones, data is at risk. I mean, even if it says little as a GPA, GPS colocation, it could be a contact could be content that you're actually discussing. I mean, there's, there's a lot of different ways that folks use their phones kind of just live their lives and the convenience of having Google read through your emails, or, you know, whatever it is to be able to scan for things that need to go on your calendar, or to scan for things. You know, like, I love that I can, you know, in the before times when I was traveling, I loved that Google knew where I was flying to what flight I was on, and I would be able to get that information and notifications like you should be leaving for the airport right now. So I think it's something where the convenience of having the AI tracking us and listening to us and reading our emails, and all of that has sometimes trumped our need for privacy.   Curt Widhalm  06:09 The first article that I came across in this is an article from counseling today. This is publication of the American Counseling Association. This article was by Nicole R. Curry Sanders called Hey, Siri, did you break confidentiality? Or did I in this article, Dr. Curry Sanders actually cites an article from The Guardian newspaper, talking about an apple contractor who's a whistleblower. And this contractor is quoted as saying that they regularly hear confidential medical information, drug deals, recordings of couples having sex as a part of this contractors job providing quality control. So these devices are, at least historically have listened. Now, this flies in the face of what some of the tech articles that I'm seeing out there who say that these devices are only listening for those keywords that activate them, but that they're actually constantly on. And according to this contractors cited in this Guardian article, they are recording and sharing this information. So it's very theoretically easily believed that it's also listening in on your therapy sessions. If that's the case, with Apple having this information, everybody who's got an iPhone, that's either bringing it into your session, these devices are potentially listening to everything that's being discussed in your sessions, which is scary, because I imagine that most therapists are not talking about this as a potential breaking of the limits of confidentiality and the promise of confidentiality that makes therapy so sacred.   Katie Vernoy  07:55 And I think that as a society, we have kind of cosign on this lack of privacy, I mean, Siri, or Alexa or Google or whatever, potentially are, they're constantly listening to all of us. And that's part of life. And so are we, are we responsible above this risk that all of us are willing to take by having phones in our pockets,   Curt Widhalm  08:20 And I don't think many of us are, and we'll include the links to what we're talking about here in our show notes. You can find those over at MTS g podcast.com. The next thing that I'm looking at here is a blog post on psychiatry, advisor.com called Alexa Siri, Google Assistant are not HIPAA compliant, and it warns against. Obviously, we all at this point should know that you shouldn't be doing your notes onto one of these devices using some of these voice prompts. But if this article also warns about don't add clients to your schedule using one of these either because it's not an end to end encrypted sort of device, which is one of the requirements of HIPAA, and that HIPAA violations can cost people hundreds or 1000s of dollars. If identity theft can be traced back to them think of how convenient it is to just turn off your phone. So that way, and how much potential money this may end up saving you by just doing the simplest of things.   Katie Vernoy  09:28 Yes, yes, I again, but I still want to you know, we're I know we're   Curt Widhalm  09:34 Any good one ethics discussion should leave people anxious.   Katie Vernoy  09:39 But my question still stands. If I do my part because I am a HIPAA provider. I put my phone on Do Not Disturb or whatever I airplane mode. I put my phone on airplane mode. I don't have any other devices with listening capability in my room, and I only use my electronic health record for scheduling and communication and HIPAA compliant email, blah, blah, blah, like I do all the things, and my client still has a smartphone in their pocket, like do I actually need to warn them about that smartphone in their pocket, because they already theoretically are agreeing to this constant surveillance. By having that smartphone in their pocket,   Curt Widhalm  10:22 I think that we have a duty. And this is reflected in our ethics codes. And we have a duty to tell our clients even things that they may not consider as it pertains to therapy about, okay, where limits of confidentiality may lie? Well, there may be the constant surveillance of these devices in everyday life, but to further prompt them, at least, and especially in our first telehealth session with them that, hey, just in case you haven't considered this, your smart devices in the room may also be listening to your therapy session. And well, you know, it's not the same thing as a sibling or somebody else, brother, parents child's, you know, walking down the hallway, there is the potential that some of this information may be transmitted to people that you don't want to and if that's a consideration, if you want to unplug those devices in the general listening area right now, now would be the time to do so.   Katie Vernoy  11:24 Okay. I mean, that seems fair, I think there's going to be people talking about this, now that we've put this podcast episode out. So I think we also don't want to freak people out. I mean, I think about also there, yes, the data is being transmitted, but it's kind of like how much data are people actually looking at. I mean, it's, it's such an inundation of all of this surveillance data, that the likelihood of someone honing in on a therapy session feels small as part of quality control. And I'm not saying we shouldn't do anything about it, I'm just saying, I'm gonna. Curt Widhalm  11:59 Wave your argument away and saying that the likelihood of somebody breaking into your office and working at client files is also very small. But that does not absolve you of your responsibility to take the precautions to let our clients know about the limits of confidentiality,   Katie Vernoy  12:17 I think it's I think, in talking about it with clients, the way you just said, it sounded a little paranoid, you   Curt Widhalm  12:22 Are being listened to. Katie Vernoy  12:25 You're being listened to. It's I think there's potentially a clinical clinically relevant way to talk about it. I mean, I think, as you know, smart devices that have voice activation potentially can get activated by words that we use, you may want to turn those on, or turn them off their devices in your room, turn them off, turn off voice activation, whatever. But like, there are devices listening in your room, you may want to unplug them. You sounded a little paranoid. It's true. But But I think we want to I don't know, it just it feels a little bit. I don't know paranoid to me, I don't I don't know what   Curt Widhalm  13:03 Your paranoia is my legal precaution of that. And it doesn't have to be presented in that paranoid sort of way. It's just, you know, hey, it's known at this point, like little disclosure, here, we have a little you know, Alexa thing sitting in our living room, sometimes our TV activates it. And then we get little ads on the Alexa based on whatever show that's activated Alexa. So all of a sudden, we're getting, you know, Airbnb recommendations of, you know, wherever the TV show we just watched was located, it's not that much of a stretch of the imagination to think these things are listening, it's happened a couple of times with my phone, just in this episode, it doesn't have to be done in a paranoia sort of way. It's just kind of a, hey, if your privacy means that much to you, and you're gonna be talking about these sensitive things, you might want to consider shutting off those voice activated things in your room.   Katie Vernoy  13:55 Well, I mean, the other thing that we talked about before starting to record is also the the geolocation and potentially contacts on your phone. And so to me, I feel like, at some point there, if we are going to be in a technological society, there may be things that we just cannot avoid. And maybe I'm wrong. I mean, maybe do I do I just never turn on my phone when another person's in my office, like, I feel like being able to not have, you know, if someone's actually physically coming to my office, and our phones have crossed GPS, and all of our apps say like, Oh, they're in the same room, they must like the same things and then start feeding us all of the ads, on the things that either we've talked about, because voice activation is on, or the things that each other have searched for. I mean, it starts to get a little bit nutty, to like, basically be Luddites at the moments during which we're doing therapy.   Curt Widhalm  14:53 It's not to say that we have to be Luddites, it's that we have to disclose the potential So limits of confidentiality that clients may be coming to expect sharing on a Wi Fi network, if you're a well intentioned therapist who has a parent who wants to be, you know, on the Wi Fi network in your office while their kids doing therapy. That's one way that some of these algorithms work to match up people who should be connected on some of the social media sites, if you've got a client's phone number saved in your phone, and you've given third party apps, the permission to scan through your phonebook. These are other ways that you're potentially transmitting data to people that you have maybe lied to people about in your Notice of Privacy Practices that you give to your clients, if the information that you say that what you're doing with it, and how it's going to be shared. And you're sharing this information in inadvertent ways, I'm not aware of any court cases where a therapist has been taken to court on this, but I could see where a therapist could be held liable by having some of this data shared in ways that they never heard that their Notice of Privacy Practices, you know, they take their boilerplate language from somebody down the street, who took it from somebody down the street, who took it from somebody down the street, who took it from actually a paid layer that they actually were responsible with. So since we tend to copy and paste and borrow and pay homage to other people's paperwork, by just borrowing and stealing, and calling it our own, we may not actually be aware of everything in some of these Notice of Privacy Practices that we give out, if what you're doing is transmitting some of this client data, you at least should document that you've had some of these discussions with your clients, as a way of limiting your liability when it comes to having any of these kinds of devices around you. And if the conversation and your own anxieties hasn't pointed it out. So far, we all have these devices, this should be a regular part of the conversation. And should be something where especially talking about a lot of protected health information, especially if you're already a HIPAA covered entity, you have to be aware of this   Katie Vernoy  17:11 Going back to kind of the original thought that I had around this is that whether it's convenience, or practicality that has you put the contacts in your phone, for example, I think that we have to think beyond that. Because it really can harm our ability to keep those that data say I mean, I think about inadvertently, I have done a really good job at keeping my data away from Facebook, I don't take any of the things I don't log into anything with Facebook, I've tried to keep Facebook fairly separate, as well as I use a really old email. And it's not connected to my practice in any way. I'm not sure that anybody else wants to do that. But they're like, I don't share contacts with any of my social media. So my phone is never mind for those things I actively go through and, and deny those permissions. But to me, it could be very simple, even a slip of your of a button press so to speak, where you've shared all your contact to LinkedIn, Twitter, social media, any other social media platform that you allow all of the permissions on your phone, because it's easier because like, oh, well, I'll find my friends, I don't have to go search for them individually. I mean, there's so many ways that are very seductive, that we could do this in an inadvertent data sharing,   Curt Widhalm  18:33 You know, this is no commentary on you. But you identified yourself not as like a super tech savvy person. And yet, I would say that what you just described is more tech savvy than what most people would think about. And that's why we have some of the responsibilities that we do in talking with clients about how their health information may go beyond just our therapy sessions here. Some of these articles that we've seen talk about, you know, don't do things like write your notes, you know, pay Google write in this patient chart, X, Y, and Z. Like, those things would seem obvious, especially to a lot of our modern therapist community who would be like, yeah, that totally makes sense. But just actually having the presence of any of these devices around us, is, you know, a matter of lifestyle for some people and it's knowing to go in and how to shut off some of these things or be able to talk with some of our clients about this because something that's happened during the COVID pandemic and with a lot of telehealth is, we've also become de facto, it people when it comes to explaining to some of our clients just even how to make some of the telehealth stuff work. And so if you know our EHR platforms, and as simple as they get made before for user experiences, if people are still having trouble with those knowing to go in and where to look on a phone for here's where data gets shared back and forth with each other, well, that might be a little bit outside. The scope of what we want to talk about with clients, it's sometimes more simple as far as if you have these devices. And you don't want the conversation of what we're what we're talking about being shared with any of the apps on your phone. Best practice might be just to turn them off during our sessions. But if you leave them on, just know that we can't guarantee complete confidentiality, that's it.   Katie Vernoy  20:20 That seems fair. Um, one of the things that you said earlier, though, struck me because I think that you and I are like, obviously, we wouldn't, you know, kind of transcribe our notes or, you know, kind of do voice over notes on our phone. But that's kind of an accessibility issue for some folks who can't type or handwrite their notes. And I would be very curious on how to protect in that regard. You know, if I've got a voice recorder, that helps me to do my notes, is it within a HIPAA compliant platform that goes directly into my notes? I mean, this might be things that people need to research is how do all of my apps interact? And how do I make sure that I'm not there's not more than what I'm working on open and listening? Because I think that's hard. And I don't know that I wouldn't say I'm tech savvy, I think I actually am. But I think it's something where understanding how privacy and data works, and how things interact with each other how there's data handoffs, I think those types of things feel like they are beyond the scope of being a therapist, but I like what you're saying is like, then just turn these devices off. I guess the only problem is, I have clients that use their phone for their telehealth session. So I don't know if you know, I use simple practice. So I don't know simple practice, then make sure that other apps on the phone are not listening. I don't know if there's even a way to do that. And or if there is a way for people to, you know, like, do you go through and you just kind of disable each of the apps that you don't want to listen, I mean, it feels like there's, there's a challenge here to really having a practical solution, unless we can be certain that the platform that we're using for our video calls on the phone are actually is actually secure. And my assumption is that's the case, I just don't know what else is listening, if and if that's possible.   Curt Widhalm  22:11 And in preparation of this episode, I did not do a deep dive into how, you know, our EHR platforms when they are used on our devices, more popular EHR companies, simple practice, you mentioned those video sessions, if there is a HIPAA compliance, if they have signed a BA agreement with you, those are end to end encrypted communications. Now, what I did not do a deep dive on is does that also prevent other apps and things from also listening, if it is being used on this solitary device that your session is on TBD? You know, follow us on our social media, or whatever. And we'll sort through that through that. It does come back to this point. And especially as we can see some of these tech companies moving more and more into the healthcare space that they're going to make closer and closer approximate efforts to become HIPAA compliant. And this is always kind of a cautionary sort of thing, where I'm a part of a lot of Facebook groups, with therapists, a lot of online communities, and I see a number of people wanting to do things as inexpensively as possible. But without those ba agreements, as business associate agreements, you're not guaranteed to have the same a HIPAA protections if that data does get leaked out or shared in other ways. And so these are your responsibilities as therapists when it comes to confidentiality and this AI conversation.   Katie Vernoy  23:44 And there's a lot of different ways to try to do that. I was one of you were talking, I was thinking about a conversation I had with Roy Huggins from persons under attack, who unfortunately recently just died. And it's a very tragic loss for our profession. And just the way that he would talk about HIPAA compliance. And I'm sure Person Center tech will continue that work was that you have to understand the risks that you're taking, and do what you can and then be comfortable with a risk you're still taking because he's not be perfect. And so I think it's I think it's, it's hard because it can be very scary, because we can't necessarily get to a place where we've we've taken every single precaution. I mean, we could go to a black site, have everyone come in separate ways, no GPS phones are left at their houses, and then be in a room together and then leave. There might be other liability if nobody knows where you are, and you're alone in a room with a client. But I think as a society, I don't think we can protect ourselves from every single thing. But these are things that we can protect ourselves against. pretty simply, I mean, you just turn it off. Um, I think, and that's something that I don't know that a lot of people were thinking about this. Now,   Curt Widhalm  24:57 One of the questions on one of these articles got asked, I think is worth discussing here is for people who are working at sites that require you to have a cell phone on you for safety reasons, whether it be in the floor of a hospital male use system, if you're working for an agency where you go and visit clients houses or whatever, it's what did you see, in kind of the responses to those articles there,   Katie Vernoy  25:26 The main thing is to turn off voice activation, so that there's not a voice activation element. So it's not recording the content, making your phone, a regular cell phone and trying to get rid of some of the other, you know, kind of the smart elements of it, I think can be very helpful. The thing that you can't avoid, if you're trying to go for safety is really, you got to keep GPS on if you need to make an emergency call, they need to be able to ping your cell phone. And so I think there's there are some, some safety issues or not, there are some privacy issues that you can't avoid if you need to have a cell phone. And it's for safety reasons. But I think it's something where the voice assistant technologies, those things are maybe not that easy to find, but but you can, you know, there's some instructions in this, and I'll put this in the show notes so that you can find it. But you know, turning off those voice activation, making sure that you've made yourself as tight as possible. As far as any kind of data that's going out turning off, you know, all of the apps, making sure there's nothing running in the background, even going through your apps and having the permission set to only while the app is on, I think is helpful, because then if Facebook is tracking your location, and Instagram is tracking your location, and Google and whatever, if those are tracking your location all the time, then there's a lot of data being shared. But if you turn those, if you only have those on when you have those apps open, and you consciously close them before you go in my hope is that they're not also running in the background. I've also had something where I put my phone on really low battery use before where it only allows for phone. So it basically shuts down anything running in the background so that you don't have things going that you don't know about. But you know, if you're wanting safety going all the way to turning it off or airplane mode is going to maybe an advisable for safety.   Curt Widhalm  27:24 And in these conversations and what I would suggest is let your clients know what the limits of confidentiality are. And and this doesn't have to be a huge in depth pieces of conversations. Some of your clients may have more interest in what you're talking about, or paranoia depending on why you're seeing those clients. But we would love to hear your experiences with this kind of stuff or thoughts or considerations that you have. You can share those with us on our social media. You can find links to those in our show notes. And once again, those are over at MTS g podcast.com. You can join our Facebook group, the modern therapist group and spill your data to us and Mark Zuckerberg. And until next time, I'm Kurt Wilhelm with Katie Vernoy and Siri.   Katie Vernoy  28:17 Thanks again to our sponsor buying time   Curt Widhalm  28:20 Buying Time's VAs support businesses by managing email communications, CRM or automation systems, website admin and hosting email marketing, social media, bookkeeping and much more. Their sole purpose is to create the opportunity for you to focus on supporting those you serve while ensuring that your back office runs smoothly with a full team of VAs gives the opportunity to hire for one role and get multiple areas of support. There's no reason to be overwhelmed with running your business with this solution available.               Katie Vernoy  28:48 Book a consultation to see where and how you can get started getting the support you need. That's buyingtimellc.com/book-consultation once again, buying time llc.com forward slash book dash consultation.   Announcer  29:04 Thank you for listening to the modern therapist Survival Guide. Learn more about who we are and what we do at mtsgpodcast.com. You can also join us on Facebook and Twitter. And please don't forget to subscribe so you don't miss any of our episodes.

Cafe con Victor
El mundo post pandemia: La digitalización de la sociedad

Cafe con Victor

Play Episode Listen Later Jan 16, 2022 39:25


Todos los hechos sucedidos durante el primer año de pandemia nos llevan sin darnos cuenta a una digitalización extrema de la sociedad. Por un lado, bifurcaciones más hedonistas como pueden ser el auge de las consolas retro, el formato podcast y su derivado de las apps de chats de audio. A la vez, encontramos un cambio en el modelo de negocio audiovisual. El cine es residual y la experiencia offline ya no seduce salvo grandes blockbusters (Spider-man), porque ahora queremos ver los estrenos de manera inmediata desde el salón. También hemos cambiado la oficina por una habitación de nuestra vivienda donde trabajar. Así nacen sistemas operativos como Windows 11, smartphones como iPhone 13, el M1 del Mac, Microsoft Loop y la nueva línea de los Surface --- This episode is sponsored by · Anchor: The easiest way to make a podcast. https://anchor.fm/app --- Send in a voice message: https://anchor.fm/victorabarca/message

Computer Talk with TAB
Cutting The Cable

Computer Talk with TAB

Play Episode Listen Later Jan 15, 2022 39:28


New Mexico town Ransomware attack brings down the jail, school etc, What Router should I get? SYSJOKER provides backdoors to Apple, Windows and Linux Systems, VoIP cutting the cable.  

Screaming in the Cloud
“Cloudash”ing onto Mac with Maciej Winnicki

Screaming in the Cloud

Play Episode Listen Later Jan 13, 2022 34:41


About MaciejMaciej Winnicki is a serverless enthusiast with over 6 years of experience in writing software with no servers whatsoever. Serverless Engineer at Stedi, Cloudash Founder, ex-Engineering Manager, and one of the early employees at Serverless Inc.Links: Cloudash: https://cloudash.dev Maciej Winnicki Twitter: https://twitter.com/mthenw Tomasz Łakomy Twitter: https://twitter.com/tlakomy Cloudash email: hello@cloudash.dev 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 byLaunchDarkly. Take a look at what it takes to get your code into production. I'm going to just guess that it's awful because it's always awful. No one loves their deployment process. What if launching new features didn't require you to do a full-on code and possibly infrastructure deploy? What if you could test on a small subset of users and then roll it back immediately if results aren't what you expect? LaunchDarkly does exactly this. To learn more, visitlaunchdarkly.com and tell them Corey sent you, and watch for the wince.Corey: This episode is sponsored in part by our friends at Rising Cloud, which I hadn't heard of before, but they're doing something vaguely interesting here. They are using AI, which is usually where my eyes glaze over and I lose attention, but they're using it to help developers be more efficient by reducing repetitive tasks. So, the idea being that you can run stateless things without having to worry about scaling, placement, et cetera, and the rest. They claim significant cost savings, and they're able to wind up taking what you're running as it is in AWS with no changes, and run it inside of their data centers that span multiple regions. I'm somewhat skeptical, but their customers seem to really like them, so that's one of those areas where I really have a hard time being too snarky about it because when you solve a customer's problem and they get out there in public and say, “We're solving a problem,” it's very hard to snark about that. Multus Medical, Construx.ai and Stax have seen significant results by using them. And it's worth exploring. So, if you're looking for a smarter, faster, cheaper alternative to EC2, Lambda, or batch, consider checking them out. Visit risingcloud.com/benefits. That's risingcloud.com/benefits, and be sure to tell them that I said you because watching people wince when you mention my name is one of the guilty pleasures of listening to this podcast.Corey: Welcome to Screaming in the Cloud. I'm Cloud Economist Corey Quinn. And my guest today is Maciej Winnicki, who is the founder of Cloudash. Now, before I dive into the intricacies of what that is, I'm going to just stake out a position that one of the biggest painful parts of working with AWS in any meaningful sense, particularly in a serverless microservices way, is figuring out what the hell's going on in the environment. There's a bunch of tools offered to do this and they're all—yeee, they aspire to mediocrity. Maciej, thank you for joining me today.Corey: Welcome to Screaming in the Cloud. I'm Cloud Economist Corey Quinn. And my guest today is Maciej Winnicki, who is the founder of Cloudash. Now, before I dive into the intricacies of what that is, I'm going to just stake out a position that one of the biggest painful parts of working with AWS in any meaningful sense, particularly in a serverless microservices way, is figuring out what the hell's going on in the environment. There's a bunch of tools offered to do this and they're all—yeee, they aspire to mediocrity. Maciej, thank you for joining me today.Maciej: Thank you for having me.Corey: So, I turned out to have accidentally blown up Cloudash, sort of before you were really ready for the attention. You, I think, tweeted about it or put it on Hacker News or something; I stumbled over it because it turns out that anything that vaguely touches cloud winds up in my filters because of awesome technology, and personality defects on my part. And I tweeted about it as I set it up and got the thing running, and apparently this led to a surge of attention on this thing that you've built. So, let me start off with an apology. Oops, I didn't realize it was supposed to be a quiet launch.Maciej: I actually thank you for that. Like, that was great. And we get a lot of attention from your tweet thread, actually because at the end, that was the most critical part. At the end of the twitter, you wrote that you're staying as a customer, so we have it on our website and this is perfect. But actually, as you said, that's correct.Our marketing strategy for releasing Cloudash was to post it on LinkedIn. I know this is not, kind of, the best strategy, but that was our plan. Like, it was like, hey, like, me and my friend, Tomasz, who's also working on Cloudash, we thought like, let's just post it on LinkedIn and we'll see how it goes. And accidentally, I'm receiving a notification from Twitter, “Hey, Corey started tweeting about it.” And I was like, “Oh, my God, I'm having a heart attack.” But then I read the, you know—Corey: Oops.Maciej: [laugh]. Yeah. I read the, kind of, conclusion, and I was super happy. And again, thank you for that because this is actually when Cloudash kind of started rolling as a product and as a, kind of, business. So yeah, that was great.Corey: To give a little backstory and context here is, I write a whole bunch of serverless nonsense. I build API's Gateway, I hook them up to Lambda's Function, and then it sort of kind of works. Ish. From there, okay, I would try and track down what was going on because in a microservices land, everything becomes a murder mystery; you're trying to figure out what's broken, and things have exploded. And I became a paying customer of IOpipe. And then New Relic bought them. Well, crap.Then I became a paying customer of Epsagon. And they got acquired by Cisco, at which point I immediately congratulated the founders, who I know on a social basis, and then closed my account because I wanted to get out before Cisco ruins it because, Cisco. Then it was, what am I going to use next? And right around that time is when I stumbled across Cloudash. And it takes a different approach than any other entity in the space that I've seen because you are a native Mac desktop app. I believe your Mac only, but you seem to be Electron, so I could be way off base on that.Maciej: So, we're Linux as well right now and soon we'll be Windows as well. But yeah, so, right now is Mac OS and Linux. Yeah, that's correct. So, our approach is a little bit different.So, let me start by saying what's Cloudash? Like, Cloudash is a desktop app for, kind of, monitoring and troubleshooting serverless architectures services, like, serverless stuff in general. And the approach that we took is a little bit different because we are not web-based, we're desktop-based. And there's a couple of advantages of that approach. The first one is that, like, you don't need to share your data with us because we're not, kind of, downloading your metrics and logs to our back end and to process them, et cetera, et cetera. We are just using the credentials, the AWS profiles that you have defined on your computer, so nothing goes out of your AWS account.And I think this is, like, considering, like, from the security perspective, this is very crucial. You don't need to create a role that you give us access to or anything like that. You just use the stuff that you have on your desktop, and everything stays on your AWS account. So, nothing—we don't download it, we don't process it, we don't do anything from that. And that's one approach—well, that's the one advantage. The other advantage is, like, kind of, onboarding, as I kind of mentioned because we're using the AWS profiles that you have defined in your computer.Corey: Well, you're doing significantly more than that because I have a lot of different accounts configured different ways, and when I go to one of them that uses SSO, it automatically fires me off to the SSO login page if I haven't logged in that day for a 12 hour session—Maciej: Yes.Corey: —for things that have credentials stored locally, it uses those; and for things that are using role-chaining to use assuming roles from the things I have credentials for, and the things that I just do role assumption in, and it works flawlessly. It just works the way that most of my command-line tools do. I've never seen a desktop app that does this.Maciej: Yeah. So, we put a lot of effort into making sure that this works great because we know that, like, no one will use Cloudash if there's—like, not no one, but like, we're targeting, like, serverless teams, maybe, in enterprise companies, or serverless teams working on some startups. And in most cases, those teams or those engineers, they use SSO, or at least MFA, right? So, we have it covered. And as you said, like, it should be the onboarding part is really easy because you just pick your AWS profile, you just pick region, and just pick, right now, a CloudFormation stack because we get the information about your service based on CloudFormation stack. So yeah, we put a lot of effort in making sure that this works without any issues.Corey: There are some challenges to it that I saw while setting it up, and that's also sort of the nature of the fact you are, in fact, integrating with CloudWatch. For example, it's region specific. Well, what if I want to have an app that's multi-region? Well, you're going to have a bad time because doing [laugh] anything multi-region in AWS means you're going to have a bad time that gets particularly obnoxious and EC2 get to when you're doing something like Lambda@Edge, where, oh, where are the logs live; that's going to be in a CloudFront distribution in whatever region it winds up being accessed from. So, it comes down to what distribution endpoint or point of presence did that particular request go through, and it becomes this giant game of whack-a-mole. It's frustrating, and it's obnoxious, and it's also in no way your fault.Maciej: Yeah, I mean, we are at the beginning. Right now, it's the most straightforward, kind of pe—how people think about stacks of serverless. They're think in terms of regions because I think for us, regions, or replicated stacks, or things like that are not really popular yet. Maybe they will become—like, this is how AWS works as a whole, so it's not surprising that we're kind of following this path. I think my point is that our main goal, the ultimate goal, is to make monitoring, as I said, the troubleshooting serverless app as simple as possible.So, once we will hear from our customers, from our users that, “Hey, we would like to get a little bit better experience around regions,” we will definitely implement that because why not, right? And I think the whole point of Cloudash—and maybe we can go more deep into that later—is that we want to bring context into your metrics and logs. If you're seeing a, for example, X-Ray trace ID in your logs, you should be able with one click just see that the trace. It's not yet implemented in Cloudash, but we are having it in the backlog. But my point is that, like, there should be some journey when you're debugging stuff, and you shouldn't be just, like, left alone having, like, 20 tabs, Cloudash tabs open and trying to figure out where I was—like, where's the Lambda? Where's the API Gateway logs? Where are the CloudFront logs? And how I can kind of connect all of that? Because that's—it's an issue right now.Corey: Even what you've done so far is incredibly helpful compared to the baseline experience that folks will often have, where I can define a service that is comprised of a number of different functions—I have one set up right now that has seven functions in it—I grab any one of those things, and I can set how far the lookback is, when I look at that function, ranging from 5 minutes to 30 days. And it shows me at the top the metrics of invocations, the duration that the function runs for, and the number of errors. And then, in the same pane down below it, it shows the CloudWatch logs. So, “Oh, okay, great. I can drag and zoom into a specific timeframe, and I see just the things inside of that.”And I know this sounds like well, what's the hard part here? Yeah, except nothing else does it in an easy-to-use, discoverable way that just sort of hangs out here. Honestly, the biggest win for me is that I don't have to log in to the browser, navigate through some ridiculous other thing to track down what I'm talking about. It hangs out on my desktop all the time, and whether it's open or not, whenever I fire it up, it just works, basically, and I don't have to think about it. It reduces the friction from, “This thing is broken,” to, “Let me see what the logs say.”Very often I can go from not having it open at all to staring at the logs and having to wait a minute because there's some latency before the event happens and it hits CloudWatch logs itself. I'm pretty impressed with it, and I've been keeping an eye on what this thing is costing me. It is effectively nothing in terms of CloudWatch retrieval charges. Because it's not sitting there sucking all this data up all the time, for everything that's running. Like, we've all seen the monitoring system that winds up costing you more than it costs more than they charge you ancillary fees. This doesn't do that.I also—while we're talking about money, I want to make very clear—because disclaiming the direction the money flows in is always important—you haven't paid me a dime, ever, to my understanding. I am a paying customer at full price for this service, and I have been since I discovered it. And that is very much an intentional choice. You did not sponsor this podcast, you are not paying me to say nice things. We're talking because I legitimately adore this thing that you've built, and I want it to exist.Maciej: That's correct. And again, thank you for that. [laugh].Corey: It's true. You can buy my attention, but not my opinion. Now, to be clear, when I did that tweet thread, I did get the sense that this was something that you had built as sort of a side project, as a labor of love. It does not have VC behind it, of which I'm aware, and that's always going to, on some level, shade how I approach a service and how critical I'm going to be on it. Just because it's, yeah, if you've raised a couple 100 million dollars and your user experience is trash, I'm going to call that out.But if this is something where you just soft launched, yeah, I'm not going to be a jerk about weird usability bugs here. I might call it out as “Ooh, this is an area for improvement,” but not, “What jackwagon thought of this?” I am trying to be a kinder, gentler Corey in the new year. But at the same time, I also want to be very clear that there's room for improvement on everything. What surprised me the most about this is how well you nailed the user experience despite not having a full team of people doing UX research.Maciej: That was definitely a priority. So, maybe a little bit of history. So, I started working on Cloudash, I think it was April… 2019. I think? Yeah. It's 2021 right now. Or we're 2022. [unintelligible 00:11:33].Corey: Yeah. 2022, now. I—Maciej: I'm sorry. [laugh].Corey: —I've been screwing that up every time I write the dates myself, I'm with you.Maciej: [laugh]. Okay, so I started working on Cloudash, in 2020, April 2020.Corey: There we go.Maciej: So, after eight months, I released some beta, like, free; you could download it from GitHub. Like, you can still download on GitHub, but at that time, there was no license, you didn't have to buy a license to run it. So, it was, like, very early, like, 0.3 version that was working, but sort of, like, [unintelligible 00:12:00] working. There were some bugs.And that was the first time that I tweeted about it on Twitter. It gets some attention, but, like, some people started using it. I get some feedback, very initial feedback. And I was like, every time I open Cloudash, I get the sense that, like, this is useful. I'm talking about my own tool, but like, [laugh] that's the thing.So, further in the history. So, I'm kind of service engineer by my own. I am a software engineer, I started focusing on serverless, in, like, 2015, 2016. I was working for Serverless Inc. as an early employee.I was then working as an engineering manager for a couple of companies. I work as an engineering manager right now at Stedi; we're also, like, fully serverless. So I, kind of, trying to fix my own issues with serverless, or trying to improve the whole experience around serverless in AWS. So, that's the main purpose why we're building Cloudash: Because we want to improve the experience. And one use case I'm often mentioning is that, let's say that you're kind of on duty. Like, so in the middle of night PagerDuty is calling you, so you need to figure out what's going on with your Lambda or API Gateway.Corey: Yes. PagerDuty, the original [Call of Duty: Nagios 00:13:04]. “It's two in the morning; who is it?” “It's PagerDuty. Wake up, jackass.” Yeah. We all had those moments.Maciej: Exactly. So, the PagerDuty is calling you and you're, kind of, in the middle of night, you're not sure what's going on. So, the kind of thing that we want to optimize is from waking up into understanding what's going on with your serverless stuff should be minimized. And that's the purpose of Cloudash as well. So, you should just run one tool, and you should immediately see what's going on. And that's the purpose.And probably with one or two clicks, you should see the logs responsible, for example, in your Lambda. Again, like that's exactly what we want to cover, that was the initial thing that we want to cover, to kind of minimize the time you spent on troubleshooting serverless apps. Because as we all know, kind of, the longer it's down, the less money you make, et cetera, et cetera, et cetera.Corey: This episode is sponsored by our friends at Oracle Cloud. Counting the pennies, but still dreaming of deploying apps instead of "Hello, World" demos? Allow me to introduce you to Oracle's Always Free tier. It provides over 20 free services and infrastructure, networking, databases, observability, management, and security. And—let me be clear here—it's actually free. There's no surprise billing until you intentionally and proactively upgrade your account. This means you can provision a virtual machine instance or spin up an autonomous database that manages itself all while gaining the networking load, balancing and storage resources that somehow never quite make it into most free tiers needed to support the application that you want to build. With Always Free, you can do things like run small scale applications or do proof-of-concept testing without spending a dime. You know that I always like to put asterisks next to the word free. This is actually free, no asterisk. Start now. Visit snark.cloud/oci-free that's snark.cloud/oci-free.Corey: One of the things that I appreciate about this is that I have something like five different microservices now that power my newsletter production pipeline every week. And periodically, I'll make a change and something breaks because testing is something that I should really get around to one of these days, but when I'm the only customer, cool. Doesn't really matter until suddenly I'm trying to write something and it doesn't work. Great. Time to go diving in, and always I'm never in my best frame of mind for that because I'm thinking about writing for humans not writing for computers. And that becomes a challenge.And okay, how do I get to the figuring out exactly what is broken this time? Regression testing: It really should be a thing more than it has been for me.Maciej: You should write those tests. [laugh].Corey: Yeah. And then I fire this up, and okay, great. Which sub-service is it? Great. Okay, what happened in the last five minutes on that service? Oh, okay, it says it failed successfully in the logs. Okay, that's on me. I can't really blame you for that. But all right.And then it's a matter of adding more [print or 00:14:54] debug statements, and understanding what the hell is going on, mostly that I'm bad at programming. And then it just sort of works from there. It's a lot easier to, I guess, to reason about this from my perspective than it is to go through the CloudWatch dashboards, where it's okay, here's a whole bunch of metrics on different graphs, most of which you don't actually care about—as opposed to unified view that you offer—and then “Oh, you want to look at logs, that's a whole separate sub-service. That's a different service team, obviously, so go open that up in another browser.” And I'm sitting here going, “I don't know who designed this, but are there any windows in their house? My God.”It's just the saddest thing I can possibly experience when I'm in the middle of trying to troubleshoot. Let's be clear, when I'm troubleshooting, I am in no mood to be charitable to anyone or anything, so that's probably unfair to those teams. But by the same token, it's intensely frustrating when I keep smacking into limitations that get in my way while I'm just trying to get the thing up and running again.Maciej: As you mentioned about UX that, like, we've spent a lot of time thinking about the UX, trying different approaches, trying to understand which metrics are the most important. And as we all know, kind of, serverless simplifies a lot of stuff, and there's, like, way less metrics that you need to look into when something is happening, but we want to make sure that the stuff that we show—which is duration errors, and p95—are probably the most important in most cases, so like, covering most of this stuff. So sorry, I didn't mention that before; it was very important from the very beginning. And also, like, literally, I spent a lot of time, like, working on the colors, which sounds funny, [laugh] but I wanted to get them right. We're not yet working on dark mode, but maybe soon.Anyways, the visual part, it's always close to my heart, so we spent a lot of time going back to what just said. So, definitely the experience around using CloudWatch right now, and CloudWatch logs, CloudWatch metrics, is not really tailored for any specific use case because they have to be generic, right? Because AWS has, like, I don't know, like, 300, or whatever number of services, probably half of them producing logs—maybe not half, maybe—Corey: We shouldn't name a number because they'll release five more between now and when this publishes in 20 minutes.Maciej: [laugh]. So, CloudWatch has to be generic. What we want to do with Cloudash is to take those generic tools—because we use, of course, CloudWatch logs, CloudWatch metrics, we fetch data from them—but make the visual part more tailored for specific use case—in our case, it's the serverless use case—and make sure that it's really, kind of—it shows only the stuff that you need to see, not everything else. So again, like that's the main purpose. And then one more thing, we—like this is also some kind of measurement of success, we want to reduce number of tabs that you need to have open in your browser when you're dealing with CloudWatch. So, we tried to put most important stuff in one view so you don't need to flip between tabs, as you usually do when try to under some kind of broader scope, or broader context of your, you know, error in Lambda.Corey: What inspired you to do this as a desktop application? Because a lot of companies are doing similar things, as SaaS, as webapps. And I have to—as someone who yourself—you're a self-described serverless engineer—it seems to me that building a webapp is sort of like the common description use case of a lot of serverless stuff. And you're sitting here saying, “Nope, it's desktop app time.” Which again, I'm super glad you did. It's exactly what I was looking for. How do you get here?Maciej: I'd been thinking about both kinds of types of apps. So like, definitely webapp was the initial idea how to build something, it was the webapp. Because as you said, like, that's the default mode. Like, we are thinking webapp; like, let's build a webapp because I'm an engineer, right? There is some inspiration coming from Dynobase, which was made by a friend [unintelligible 00:18:55] who also lives in Poland—I didn't mention that; we're based in [Poznań 00:18:58], Poland.And when I started thinking about it, there's a lot of benefits of using this approach. The biggest benefit, as I mentioned, is security; and the second benefit is just most, like, cost-effective because we don't need to run in the backend, right? We don't need to download all your metrics, all your logs. We I think, like, let's think about it, like, from the perspective. Listen, so everyone in the company to start working, they have to download all of your stuff from your AWS account. Like, that sounds insane because you don't need all of that stuff elsewhere.Corey: Store multiple copies of it. Yeah I, generally when I'm looking at this, I care about the last five to ten minutes.Maciej: Exactly.Corey: I don't—Maciej: Exactly.Corey: —really care what happened three-and-a-half years ago on this function. Almost always. But occasionally I want to look back at, “Oh, this has been breaking. How long has it been that way?” But I already have that in the AWS environment unless I've done the right thing and turned on, you know, log expiry.Maciej: Exactly. So, this is a lot of, like, I don't want to be, like, you know, mean to anyone but like, that's a lot of waste. Like, that's a lot of waste of compute power because you need to download it; of cost because you need to get this data out of AWS, which you need to pay for, you know, get metric data and stuff like this. So, you need to—Corey: And almost all of its—what is it? Write once, read never. Because it's, you don't generally look at these things.Maciej: Yeah, yeah. Exactly.Corey: And so much of this, too, for every invocation I have, even though it's low traffic stuff, it's the start with a request ID and what version is running, it tells me ‘latest.' Helpful. A single line of comment in this case says ‘200.' Why it says that, I couldn't tell you. And then it says ‘End request ID.' The end.Now, there's no way to turn that off unless you disabled the ability to write to CloudWatch logs in the function, but ingest on that cost 50 cents a gigabyte, so okay, I guess that's AWS's money-making scam of the year. Good for them. But there's so much of that, it's like looking at—like, when things are working, it's like looking at a low traffic site that's behind a load balancer, where there's a whole—you have gigabytes, in some cases, of load balancer—of web server logs on the thing that's sitting in your auto-scaling group. And those logs are just load balancer health checks. 98% of it is just that.Same type of problem here, I don't care about that, I don't want to pay to store it, I certainly don't want to pay to store it twice. I get it, that makes an awful lot of sense. It also makes your security job a hell of a lot easier because you're not sitting on a whole bunch of confidential data from other people. Because, “Well, it's just logs. What could possibly be confidential in there?” “Oh, my sweet summer child, have you seen some of the crap people put in logs?”Maciej: I've seen many things in logs. I don't want to mention them. But anyways—and also, you know, like, usually when you gave access to your AWS account, it can ruin you. You know, like, there might be a lot of—like, you need to really trust the company to give access to your AWS account. Of course, in most cases, the roles are scoped to, you know, only CloudWatch stuff, actions, et cetera, et cetera, but you know, like, there are some situations in which something may not be properly provisioned. And then you give access to everything.Corey: And you can get an awful lot of data you wouldn't necessarily want out of that stuff. Give me just the PDF printout of last month's bill for a lot of environments, and I can tell you disturbing levels of detail about what your architecture is, just because when you—you can infer an awful lot.Maciej: Yeah.Corey: Yeah, I hear you. It makes your security story super straightforward.Maciej: Yeah, exactly. So, I think just repeat my, like, the some inspiration. And then when I started thinking about Cloudash, like, definitely one of the inspiration was Dynobase, from the, kind of, GUI for, like, more powerful UI for DynamoDB. So, if you're interested in that stuff, you can also check this out.Corey: Oh, yeah, I've been a big fan of that, too. That'll be a separate discussion on a different episode, for sure.Maciej: [laugh]. Yeah.Corey: But looking at all of this, looking at the approach of, the only real concern—well, not even a concern. The only real challenge I have with it for my use case is that when I'm on the road, the only thing that I bring with me for a computer is my iPad Pro. I'm not suggesting by any means that you should build this as a new an iPad app; that strikes me as, like, 15 levels of obnoxious. But it does mean that sometimes I still have to go diving into the CloudWatch console when I'm not home. Which, you know, without this, without Cloudash, that's what I was doing originally anyway.Maciej: You're the only person that requested that. And we will put that into backlog, and we will get to that at some point. [laugh].Corey: No, no, no. Smart question is to offer me a specific enterprise tier pricing—.Maciej: Oh, okay. [laugh].Corey: —that is eye-poppingly high. It's like, “Hey, if you want a subsidize feature development, we're thrilled to empower that.” But—Maciej: [laugh]. Yeah, yeah. To be honest, I like that would be hard to write [unintelligible 00:23:33] implement as iPad app, or iPhone app, or whatever because then, like, what's the story behind? Like, how can I get the credentials, right? It's not possible.Corey: Yeah, you'd have to have some fun with that. There are a couple of ways I can think of offhand, but then that turns into a sandboxing issue, and it becomes something where you have to store credentials locally, regardless, even if they're ephemeral. And that's not great. Maybe turn it into a webapp someday or something. Who knows.What I also appreciate is that we had a conversation when you first launched, and I wound up basically going on a Zoom call with you and more or less tearing apart everything you've built—and ideally constructive way—but looking at a lot of the things you've changed in your website, you listened to an awful lot of feedback. You doubled your pricing, for example. Used to be ten bucks a month; now you're twenty. Great. I'm a big believer in charging more.You absolutely add that kind of value because it's, “Well, twenty bucks a month for a desktop app. That sounds crappy.” It's, “Yeah, jackwagon, what's your time worth?” I was spending seven bucks a month in serverless charges, and 120 or 130 a month for Epsagon, and I was thrilled to pieces to be doing it because the value I got from being able to quickly diagnose what the hell was going on far outstripped what the actual cost of doing these things. Don't fall into the trap of assuming that well, I shouldn't pay for software. I can just do it myself. Your time is never free. People think it is, but it's not.Maciej: That's true. The original price of $9.99, I think that was the price was the launch promo. After some time, we've decided—and after adding more features: API Gateway support—we've decided that this is, like, solving way more problems, so like, you should probably pay a little bit more for that. But you're kind of lucky because you subscribed to it when it was 9.99, and this will be your kind of prize for the end of, you know—Corey: Well, I'm going to argue with you after the show to raise the price on mine, just because it's true. It's the—you want to support the things that you want to exist in the world. I also like the fact that you offered an annual plan because I will go weeks without ever opening the app. And that doesn't mean it isn't adding value. It's that oh, yeah, I will need that now that I'm hitting these issues again.And if I'm paying on a monthly basis, and it shows up with a, “Oh, you got charged again.” “Well, I didn't use it this month; I should cancel.” And [unintelligible 00:25:44] to an awful lot of subscriber churn. But in the course of a year, if I don't have at least one instance in which case, wow, that ten minute span justified the entire $200 annual price tag, then, yeah, you built the wrong thing or it's not for me, but I can think of three incidents so far since I started using it in the past four months that have led to that being worth everything you will charge me a year, and then some, just because it made it so clear what was breaking.Maciej: So, in that regard, we are also thinking about the team licenses, that's definitely on the roadmap. There will be some changes to that. And we definitely working on more and more features. And if we're—like, the roadmap is mostly about supporting more and more AWS services, so right now it's Lambda, API Gateway, we're definitely thinking about SQS, SNS, to get some sense how your messages are going through, probably something, like, DynamoDB metrics. And this is all kind of serverless, but why not going wider? Like, why not going to Fargate? Like, Fargate is theoretically serverless, but you know, like, it's serverless on—Corey: It's serverless with a giant asterisk next to it.Maciej: Yeah, [laugh] exactly. So, but why not? Like, it's exactly the same thing in terms of, there is some user flow, there is some user journey, when you want to debug something. You want to go from API Gateway, maybe to the container to see, I don't know, like, DynamoDB metric or something like that, so it should be all easy. And this is definitely something.Later, why not EC2 metrics? Like, it would be a little bit harder. But I'm just saying, like, first thing here is that you are not, like, at this point, we are serverless, but once we cover serverless, why not going wider? Why not supporting more and more services and just making sure that all those use cases are correctly modeled with the UI and UX, et cetera?Corey: That's going to be an interesting challenge, just because that feels like what a lot of the SaaS monitoring and observability tooling is done. And then you fire this thing up, and it looks an awful lot like the AWS console. And it's, “Yeah, I just want to look at this one application that doesn't use any of the rest of those things.” Again, I have full faith and confidence in your ability to pull this off. You clearly have done that well based upon what we've seen so far. I just wonder how you're going to wind up tackling that challenge when you get there.Maciej: And maybe not EC2. Maybe I went too far. [laugh].Corey: Yeah, honestly, even EC2-land, it feels like that is more or less a solved problem. If you want to treat it as a bunch of EC2, you can use Nagios. It's fine.Maciej: Yeah, totally.Corey: There are tools that have solved that problem. But not much that I've seen has solved the serverless piece the way that I want it solved. You have.Maciej: So, it's definitely a long road to make sure that the serverless—and by serverless, I mean serverless how AWS understands serverless, so including Fargate, for example. So, there's a lot of stuff that we can improve. It's a lot of stuff that can make easier with Cloudash than it is with CloudWatch, just staying inside serverless, it will take us a lot of time to make sure that is all correct. And correctly modeled, correctly designed, et cetera. So yeah, I went too far with EC2 sorry.Corey: Exactly. That's okay. We all go too far with EC2, I assure you.Maciej: Sorry everyone using EC2 instances. [laugh].Corey: If people want to kick the tires on it, where can they find it?Maciej: They can find it on cloudash.dev.Corey: One D in the middle. That one throws me sometimes.Maciej: One D. Actually, after talking to you, we have a double-D domain as well, so we can also try ‘Clouddash' with double-D. [laugh].Corey: Excellent, excellent. Okay, that is fantastic. Because I keep trying to put the double-D in when I'm typing it in my search tool on my desktop, and it doesn't show up. And it's like, “What the—oh, right.” But yeah, we'll get there one of these days.Maciej: Only the domain. It's only the domain. You will be redirected to single-D.Corey: Exactly.Maciej: [laugh].Corey: We'll have to expand later; I'll finance the feature request there. It'll go well. If people want to learn more about what you have to think about these things, where else can they find you?Maciej: On Twitter, and my Twitter handle is @mthenw. M-then-W, which is M-T-H—mthenw. And my co-founder @tlakomy. You can probably add that to [show notes 00:29:35]. [laugh].Corey: Oh, I certainly will. It's fine, yeah. Here's a whole bunch of letters. I hear you. My Twitter handle used to be my amateur radio callsign. It turns out most people don't think like that. And yeah, it's become an iterative learning process. Thank you so much for taking the time to speak with me today and for building this thing. I really appreciate both of them.Maciej: Thank you for having me here. I encourage everyone to visit cloudash.dev, if you have any feature requests, any questions just send us an email at hello@cloudash.dev, or just go to GitHub repository in the issues; just create an issue, describe what you want and we can talk about it.We are always happy to help. The main purpose, the ultimate goal of Cloudash is to make the serverless engineer's life easier, on very high level. And on a little bit lower level, just to make, you know, troubleshooting and debugging serverless apps easier.Corey: Well, from my perspective, you've succeeded.Maciej: Thank you.Corey: Thank you. Maciej Winnicki, founder of Cloudash. 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 along with an angry comment telling me exactly why I'm wrong for using an iPad do these things, but not being able to send it because you didn't find a good way to store the credentials.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.

Python Bytes
#266 Python has a glossary?

Python Bytes

Play Episode Listen Later Jan 13, 2022 26:46


Watch the live stream: Watch on YouTube About the show Sponsored by Datadog: pythonbytes.fm/datadog Brian #1: Python glossary and FAQ Inspired by a tweet by Trey Hunner that referenced the glossary glossary All the Python and programming terms in one place Often refers to other parts of the documentation. Forget what an “abstract base class” is? Just look it up FAQ Has sections on General Python Programming Design and History Library and Extension Extending/Embedding Python on Windows Graphic User Interface “Why is Python Installed on my Computer?” Some decent reading here, actually. Example What is the difference between arguments and parameters? - that's under Programming Michael #2: Any.io Learned about it via asyncer AnyIO is an asynchronous networking and concurrency library that works on top of either asyncio or trio. It implements trio-like structured concurrency (SC) on top of asyncio Works in harmony with the native SC of trio itself Check out the features AnyIO also comes with its own pytest plugin which also supports asynchronous fixtures. Brian #3: Vaex : a high performance Python library for lazy Out-of-Core DataFrames suggested by Glen Ferguson “Vaex is a python library for lazy Out-of-Core DataFrames (similar to Pandas), to visualize and explore big tabular datasets.” out-of-core: “The term out-of-core typically refers to processing data that is too large to fit into a computer's main memory.” - from machinelearning.wtf, a Machine Learning Glossary site. nice tie in, right? Vaex uses memory mapping, a zero memory copy policy, and lazy computations. There's a great intro in the form of a presentation from SciPy 2019 Michael #4: Django Community Survey Results Only 15% of Django developers use it ONLY for work, while two thirds use it both for work and for personal, educational, or side projects. Majority use latest Django Most devs upgrade every stable release Postgres is the primary DB (MongoDB is nowhere in sight) Most sites have Redis caching tiers Michael #5: Extra, Extra, Extra, Extra: Django security releases issued: 4.0.1, 3.2.11, and 2.2.26 Static Sites with Sphinx and Markdown course by Paul Everitt is now out CalDigit Thunderbolt 4 Element Hub review (more info Video by Doc Rock, get it on Amazon here) StreamDeck setup for our live streams Michael's PyBay HTMX talk is up Python Web Conf 2022 - I'll be speaking there and we're media sponsors of the conference so use code PythonBytes@PWC2022 for 15% off, March 21-25. PyCascades 2022 is also happening soon, February 5th-6th, 2022 Joke:

Windows Weekly (MP3)
WW 759: Local Hooch - Windows 11, Microsoft HoloLens, Microsoft 365

Windows Weekly (MP3)

Play Episode Listen Later Jan 12, 2022 104:22


Windows 11, Microsoft HoloLens, Microsoft 365 Microsoft Issues First Windows 11 Build of the New Year Microsoft Issues New Windows 11 Build to the Dev Channel Stardock Releases Start11 v1.1 Tip: Get the New Windows 11 Media Player Now AR/VR/XR Microsoft Hit by Defections as Tech Giants Battle for Talent to Build the Metaverse - WSJ Meta Platforms Halts VR and AR Operating System Project — The Information Magic Leap Targets Medical Customers for Its Augmented Reality Headset - Bloomberg CES 2022: Microsoft, Qualcomm to collaborate on custom augmented-reality chips Microsoft 365 Microsoft is rolling out the ability to chat across personal and business Teams accounts Microsoft adds more Teams, Viva features for frontline workers Microsoft Surface Surface Pro 8 with LTE is now available to order from the Microsoft Store | Windows Central Xbox Report: Microsoft Has Sold 12 Million Xbox Series X|S Consoles Sony to Continue PS4 Production Through 2022 Tips and Picks Tip of the week: How to use the Quick Access menu App pick of the week: Firefox 96 Codename pick of the week: Gibraltar Cocktail pick of the week: Blue Bomber 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: newrelic.com/windows Melissa.com/twit

Windows Weekly (Video HI)
WW 759: Local Hooch - Windows 11, Microsoft HoloLens, Microsoft 365

Windows Weekly (Video HI)

Play Episode Listen Later Jan 12, 2022 104:51


Windows 11, Microsoft HoloLens, Microsoft 365 Microsoft Issues First Windows 11 Build of the New Year Microsoft Issues New Windows 11 Build to the Dev Channel Stardock Releases Start11 v1.1 Tip: Get the New Windows 11 Media Player Now AR/VR/XR Microsoft Hit by Defections as Tech Giants Battle for Talent to Build the Metaverse - WSJ Meta Platforms Halts VR and AR Operating System Project — The Information Magic Leap Targets Medical Customers for Its Augmented Reality Headset - Bloomberg CES 2022: Microsoft, Qualcomm to collaborate on custom augmented-reality chips Microsoft 365 Microsoft is rolling out the ability to chat across personal and business Teams accounts Microsoft adds more Teams, Viva features for frontline workers Microsoft Surface Surface Pro 8 with LTE is now available to order from the Microsoft Store | Windows Central Xbox Report: Microsoft Has Sold 12 Million Xbox Series X|S Consoles Sony to Continue PS4 Production Through 2022 Tips and Picks Tip of the week: How to use the Quick Access menu App pick of the week: Firefox 96 Codename pick of the week: Gibraltar Cocktail pick of the week: Blue Bomber 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: newrelic.com/windows Melissa.com/twit

All TWiT.tv Shows (MP3)
Windows Weekly 759: Local Hooch

All TWiT.tv Shows (MP3)

Play Episode Listen Later Jan 12, 2022 104:22


Windows 11, Microsoft HoloLens, Microsoft 365 Microsoft Issues First Windows 11 Build of the New Year Microsoft Issues New Windows 11 Build to the Dev Channel Stardock Releases Start11 v1.1 Tip: Get the New Windows 11 Media Player Now AR/VR/XR Microsoft Hit by Defections as Tech Giants Battle for Talent to Build the Metaverse - WSJ Meta Platforms Halts VR and AR Operating System Project — The Information Magic Leap Targets Medical Customers for Its Augmented Reality Headset - Bloomberg CES 2022: Microsoft, Qualcomm to collaborate on custom augmented-reality chips Microsoft 365 Microsoft is rolling out the ability to chat across personal and business Teams accounts Microsoft adds more Teams, Viva features for frontline workers Microsoft Surface Surface Pro 8 with LTE is now available to order from the Microsoft Store | Windows Central Xbox Report: Microsoft Has Sold 12 Million Xbox Series X|S Consoles Sony to Continue PS4 Production Through 2022 Tips and Picks Tip of the week: How to use the Quick Access menu App pick of the week: Firefox 96 Codename pick of the week: Gibraltar Cocktail pick of the week: Blue Bomber 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: newrelic.com/windows Melissa.com/twit

Radio Leo (Audio)
Windows Weekly 759: Local Hooch

Radio Leo (Audio)

Play Episode Listen Later Jan 12, 2022 104:22


Windows 11, Microsoft HoloLens, Microsoft 365 Microsoft Issues First Windows 11 Build of the New Year Microsoft Issues New Windows 11 Build to the Dev Channel Stardock Releases Start11 v1.1 Tip: Get the New Windows 11 Media Player Now AR/VR/XR Microsoft Hit by Defections as Tech Giants Battle for Talent to Build the Metaverse - WSJ Meta Platforms Halts VR and AR Operating System Project — The Information Magic Leap Targets Medical Customers for Its Augmented Reality Headset - Bloomberg CES 2022: Microsoft, Qualcomm to collaborate on custom augmented-reality chips Microsoft 365 Microsoft is rolling out the ability to chat across personal and business Teams accounts Microsoft adds more Teams, Viva features for frontline workers Microsoft Surface Surface Pro 8 with LTE is now available to order from the Microsoft Store | Windows Central Xbox Report: Microsoft Has Sold 12 Million Xbox Series X|S Consoles Sony to Continue PS4 Production Through 2022 Tips and Picks Tip of the week: How to use the Quick Access menu App pick of the week: Firefox 96 Codename pick of the week: Gibraltar Cocktail pick of the week: Blue Bomber 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: newrelic.com/windows Melissa.com/twit

Star Wars Time
SWTS: Book of Boba Fett S1E2 Breakdown, Finale Wow Moments, Filoni’s Episode, & 2022 Release Windows

Star Wars Time

Play Episode Listen Later Jan 12, 2022 168:37


The Book of Boba Fett is heating up! We talk about all of the big ticket items from episode 2 and bring in some of our famous speculation for the rest of the series! Strap in for this episode of the Star Wars Time Show! https://www.youtube.com/watch?v=ENdH5TCK0PQ&list=PLW3ledm6i6N8q-otJ7B6fiB_SIPvLz8EI You can find our topics of conversation below: https://starwarstime.net/the-book-of-boba-fett-season-1-episode-2-easter-eggs-references-and-key-moments-the-tribes-of-tatooine/ https://starwarstime.net/rumor-dave-filoni-wrote-chapter-6-of-the-book-of-boba-fett/ https://starwarstime.net/temuera-morrison-teases-the-book-of-boba-fett-finale-will-have-a-wow-moment/ https://starwarstime.net/rumor-release-windows-teased-for-every-star-wars-series-on-disney-in-2022/ https://starwarstime.net/rumor-kotor-to-have-different-play-modes/ https://starwarstime.net/top-5-star-wars-artists-of-the-week-1-3-22-1-10-22/

The KVJ Show
KVJ Cuts- Cleaning Windows World Record Wednesday (01-12-22)

The KVJ Show

Play Episode Listen Later Jan 12, 2022 9:09


Can Jbird Clean The Studio Window Faster Than The World Record? KVJ Puts Him To The Test!

Screaming in the Cloud
Slinging CDK Knowledge with Matt Coulter

Screaming in the Cloud

Play Episode Listen Later Jan 12, 2022 37:37


About MattMatt is an AWS DevTools Hero, Serverless Architect, Author and conference speaker. He is focused on creating the right environment for empowered teams to rapidly deliver business value in a well-architected, sustainable and serverless-first way.You can usually find him sharing reusable, well architected, serverless patterns over at cdkpatterns.com or behind the scenes bringing CDK Day to life.Links: AWS CDK Patterns: https://cdkpatterns.com The CDK Book: https://thecdkbook.com CDK Day: https://www.cdkday.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: It seems like there is a new security breach every day. Are you confident that an old SSH key, or a shared admin account, isn't going to come back and bite you? If not, check out Teleport. Teleport is the easiest, most secure way to access all of your infrastructure. The open source Teleport Access Plane consolidates everything you need for secure access to your Linux and Windows servers—and I assure you there is no third option there. Kubernetes clusters, databases, and internal applications like AWS Management Console, Yankins, GitLab, Grafana, Jupyter Notebooks, and more. Teleport's unique approach is not only more secure, it also improves developer productivity. To learn more visit: goteleport.com. And not, that is not me telling you to go away, it is: goteleport.com.Corey: This episode is sponsored in part by our friends at Rising Cloud, which I hadn't heard of before, but they're doing something vaguely interesting here. They are using AI, which is usually where my eyes glaze over and I lose attention, but they're using it to help developers be more efficient by reducing repetitive tasks. So, the idea being that you can run stateless things without having to worry about scaling, placement, et cetera, and the rest. They claim significant cost savings, and they're able to wind up taking what you're running as it is in AWS with no changes, and run it inside of their data centers that span multiple regions. I'm somewhat skeptical, but their customers seem to really like them, so that's one of those areas where I really have a hard time being too snarky about it because when you solve a customer's problem and they get out there in public and say, “We're solving a problem,” it's very hard to snark about that. Multus Medical, Construx.ai and Stax have seen significant results by using them. And it's worth exploring. So, if you're looking for a smarter, faster, cheaper alternative to EC2, Lambda, or batch, consider checking them out. Visit risingcloud.com/benefits. That's risingcloud.com/benefits, and be sure to tell them that I said you because watching people wince when you mention my name is one of the guilty pleasures of listening to this podcast.Corey: Welcome to Screaming in the Cloud. I'm Corey Quinn. I'm joined today by Matt Coulter, who is a Technical Architect at Liberty Mutual. You may have had the privilege of seeing him on the keynote stage at re:Invent last year—in Las Vegas or remotely—that last year of course being 2021. But if you make better choices than the two of us did, and found yourself not there, take the chance to go and watch that keynote. It's really worth seeing.Matt, first, thank you for joining me. I'm sorry, I don't have 20,000 people here in the audience to clap this time. They're here, but they're all remote as opposed to sitting in the room behind me because you know, social distancing.Matt: And this left earphone, I just have some applause going, just permanently, just to keep me going. [laugh].Corey: That's sort of my own internal laugh track going on. It's basically whatever I say is hilarious, to that. So yeah, doesn't really matter what I say, how I say it, my jokes are all for me. It's fine. So, what was it like being on stage in front of that many people? It's always been a wild experience to watch and for folks who haven't spent time on the speaking circuit, I don't think that there's any real conception of what that's like. Is this like giving a talk at work, where I just walk on stage randomly, whatever I happened to be wearing? And, oh, here's a microphone, I'm going to say words. What is the process there?Matt: It's completely different. For context for everyone, before the pandemic, I would have pretty regularly talked in front of, I don't know, maybe one, two hundred people in Liberty, in Belfast. So, I used to be able to just, sort of, walk in front of them, and lean against the pillar, and use my clicker, and click through, but the process for actually presenting something as big as a keynote and re:Invent is so different. For starters, you think that when you walk onto the stage, you'll actually be able to see the audience, but the way the lights are set up, you can pretty much see about one row of people, and they're not the front row, so anybody I knew, I couldn't actually see.And yeah, you can only see, sort of like, the from the void, and then you have your screens, so you've six sets of screens that tell you your notes as well as what slides you're on, you know, so you can pivot. But other than that, I mean, it feels like you're just talking to yourself outside of whenever people, thankfully, applause. It's such a long process to get there.Corey: I've always said that there are a few different transition stages as the audience size increases, but for me, the final stage is more or less anything above 750 people. Because as you say, you aren't able to see that many beyond that point, and it doesn't really change anything meaningfully. The most common example that you see in the wild is jokes that work super well with a small group of people fall completely flat to large audiences. It's why so much corporate numerous cheesy because yeah, everyone in the rehearsals is sitting there laughing and the joke kills, but now you've got 5000 people sitting in a room and that joke just sounds strained and forced because there's no longer a conversation, and no one has the shared context that—the humor has to change. So, in some cases when you're telling a story about what you're going to say on stage, during a rehearsal, they're going to say, “Well, that joke sounds really corny and lame.” It's, “Yeah, wait until you see it in front of an audience. It will land very differently.” And I'm usually right on that.I would also advise, you know, doing what you do and having something important and useful to say, as opposed to just going up there to tell jokes the whole time. I wanted to talk about that because you talked about how you're using various CDK and other serverless style patterns in your work at Liberty Mutual.Matt: Yeah. So, we've been using CDK pretty extensively since it was, sort of, Q3 2019. At that point, it was new. Like, it had just gone GA at the time, just came out of dev preview. And we've been using CDK from the perspective of we want to be building serverless-first, well-architected apps, and ideally we want to be building them on AWS.Now, the thing is, we have 5000 people in our IT organization, so there's sort of a couple of ways you can take to try and get those people onto the cloud: You can either go the route of being, like, there is one true path to architecture, this is our architecture and everything you want to build can fit into that square box; or you can go the other approach and try and have the golden path where you say this is the paved road that is really easy to do, but if you want to differentiate from that route, that's okay. But what you need to do is feed back into the golden path if that works. Then everybody can improve. And that's where we've started been using CDK. So, what you heard me talk about was the software accelerator, and it's sort of a different approach.It's where anybody can build a pattern and then share it so that everybody else can rapidly, you know, just reuse it. And what that means is effectively you can, instead of having to have hundreds of people on a central team, you can actually just crowdsource, and sort of decentralize the function. And if things are good, then a small team can actually come in and audit them, so to speak, and check that it's well-architected, and doesn't have flaws, and drive things that way.Corey: I have to confess that I view the CDK as sort of a third stage automation approach, and it's one that I haven't done much work with myself. The first stage is clicking around in the console; the second is using CloudFormation or Terraform; the third stage is what we're talking about here is CDK or Pulumi, or something like that. And then you ascend to the final fourth stage, which is what I use, which is clicking around in the AWS console, but then you lie to people about it. ClickOps is poised to take over the world. But that's okay. You haven't gotten that far yet. Instead, you're on the CDK side. What advantages does CDK offer that effectively CloudFormation or something like it doesn't?Matt: So, first off, for ClickOps in Liberty, we actually have the AWS console as read-only in all of our accounts, except for sandbox. So, you can ClickOps in sandbox to learn, but if you want to do something real, unfortunately, it's going to fail you. So.—Corey: I love that pattern. I think I might steal that.Matt: [laugh]. So, originally, we went heavy on CloudFormation, which is why CDK worked well for us. And because we've actually—it's been a long journey. I mean, we've been deploying—2014, I think it was, we first started deploying to AWS, and we've used everything from Terraform, to you name it. We've built our own tools, believe it or not, that are basically CDK.And the thing about CloudFormation is, it's brilliant, but it's also incredibly verbose and long because you need to specify absolutely everything that you want to deploy, and every piece of configuration. And that's fine if you're just deploying a side project, but if you're in an enterprise that has responsibilities to protect user data, and you can't just deploy anything, they end up thousands and thousands and thousands of lines long. And then we have amazing guardrails, so if you tried to deploy a CloudFormation template with a flaw in it, we can either just fix it, or reject the deploy. But CloudFormation is not known to be the fastest to deploy, so you end up in this developer cycle, where you build this template by hand, and then it goes through that CloudFormation deploy, and then you get the failure message that it didn't deploy because of some compliance thing, and developers just got frustrated, and were like, sod this. [laugh].I'm not deploying to AWS. Back the on-prem. And that's where CDK was a bit different because it allowed us to actually build abstractions with all of our guardrails baked in, so that it just looked like a standard class, for developers, like, developers already know Java, Python, TypeScript, the languages off CDK, and so we were able to just make it easy by saying, “You want API Gateway? There's an API Gateway class. You want, I don't know, an EC2 instance? There you go.” And that way, developers could focus on the thing they wanted, instead of all of the compliance stuff that they needed to care about every time they wanted to deploy.Corey: Personally, I keep lobbying AWS to add my preferred language, which is crappy shell scripting, but for some reason they haven't really been quick to add that one in. The thing that I think surprises me, on some level—though, perhaps it shouldn't—is not just the adoption of serverless that you're driving at Liberty Mutual, but the way that you're interacting with that feels very futuristic, for lack of a better term. And please don't think that I'm in any way describing this in a way that's designed to be insulting, but I do a bunch of serverless nonsense on Twitter for Pets. That's not an exaggeration. twitterforpets.com has a bunch of serverless stuff behind it because you know, I have personality defects.But no one cares about that static site that's been a slide dump a couple of times for me, and a running joke. You're at Liberty Mutual; you're an insurance company. When people wind up talking about big enterprise institutions, you're sort of a shorthand example of exactly what they're talking about. It's easy to contextualize or think of that as being very risk averse—for obvious reasons; you are an insurance company—as well as wanting to move relatively slowly with respect to technological advancement because mistakes are going to have drastic consequences to all of your customers, people's lives, et cetera, as opposed to tweets or—barks—not showing up appropriately at the right time. How did you get to the, I guess, advanced architectural philosophy that you clearly have been embracing as a company, while having to be respectful of the risk inherent that comes with change, especially in large, complex environments?Matt: Yeah, it's funny because so for everyone, we were talking before this recording started about, I've been with Liberty since 2011. So, I've seen a lot of change in the length of time I've been here. And I've built everything from IBM applications right the way through to the modern serverless apps. But the interesting thing is, the journey to where we are today definitely started eight or nine years ago, at a minimum because there was something identified in the leadership that they said, “Listen, we're all about our customers. And that means we don't want to be wasting millions of dollars, and thousands of hours, and big trains of people to build software that does stuff. We want to focus on why are we building a piece of software, and how quickly can we get there? If you focus on those two things you're doing all right.”And that's why starting from the early days, we focused on things like, okay, everything needs to go through CI/CD pipelines. You need to have your infrastructure as code. And even if you're deploying on-prem, you're still going to be using the same standards that we use to deploy to AWS today. So, we had years and years and years of just baking good development practices into the company. And then whenever we started to move to AWS, the question became, do we want to just deploy the same thing or do we want to take full advantage of what the cloud has to offer? And I think because we were primed and because the leadership had the right direction, you know, we were just sitting there ready to say, “Okay, serverless seems like a way we can rapidly help our customers.” And that's what we've done.Corey: A lot of the arguments against serverless—and let's be clear, they rhyme with the previous arguments against cloud that lots of people used to make; including me, let's be clear here. I'm usually wrong when I try to predict the future. “Well, you're putting your availability in someone else's hands,” was the argument about cloud. Yeah, it turns out the clouds are better at keeping things up than we are as individual companies.Then with serverless, it's the, “Well, if they're handling all that stuff for you on their side, when they're down, you're down. That's an unacceptable business risk, so we're going to be cloud-agnostic and multi-cloud, and that means everything we build serverlessly needs to work in multiple environments, including in our on-prem environment.” And from the way that we're talking about servers and things that you're building, I don't believe that is technically possible, unless some of the stuff you're building is ridiculous. How did you come to accept that risk organizationally?Matt: These are the conversations that we're all having. Sort of, I'd say once a week, we all have a multi-cloud discussion—and I really liked the article you wrote, it was maybe last year, maybe the year before—but multi-cloud to me is about taking the best capabilities that are out there and bringing them together. So, you know, like, Azure [ID 00:12:47] or whatever, things from the other clouds that they're good at, and using those rather than thinking, “Can I build a workload that I can simultaneously pay all of the price to run across all of the clouds, all of the time, so that if one's down, theoretically, I might have an outage?” So, the way we've looked at it is we embraced really early the well-architected framework from AWS. And it talks about things like you need to have multi-region availability, you need to have your backups in place, you need to have things like circuit breakers in place for if third-party goes down, and we've just tried to build really resilient architectures as best as we can on AWS. And do you know what I think, if [laugh] it AWS is not—I know at re:Invent, there it went down extraordinarily often compared to normal, but in general—Corey: We were all tired of re:Invent; their us-east-1 was feeling the exact same way.Matt: Yeah, so that's—it deserved a break. But, like, if somebody can't buy insurance for an hour, once a year, [laugh] I think we're okay with it versus spending millions to protect that one hour.Corey: And people make assumptions based on this where, okay, we had this problem with us-east-1 that froze things like the global Route 53 control planes; you couldn't change DNS for seven hours. And I highlighted that as, yeah, this is a problem, and it's something to severely consider, but I will bet you anything you'd care to name that there is an incredibly motivated team at AWS, actively fixing that as we speak. And by—I don't know how long it takes to untangle all of those dependencies, but I promise they're going to be untangled in relatively short order versus running data centers myself, when I discover a key underlying dependency I didn't realize was there, well, we need to break that. That's never going to happen because we're trying to do things as a company, and it's just not the most important thing for us as a going concern. With AWS, their durability and reliability is the most important thing, arguably compared to security.Would you rather be down or insecure? I feel like they pick down—I would hope in most cases they would pick down—but they don't want to do either one. That is something they are drastically incentivized to fix. And I'm never going to be able to fix things like that and I don't imagine that you folks would be able to either.Matt: Yeah, so, two things. The first thing is the important stuff, like, for us, that's claims. We want to make sure at any point in time, if you need to make a claim you can because that is why we're here. And we can do that with people whether or not the machines are up or down. So, that's why, like, you always have a process—a manual process—that the business can operate, irrespective of whether the cloud is still working.And that's why we're able to say if you can't buy insurance in that hour, it's okay. But the other thing is, we did used to have a lot of data centers, and I have to say, the people who ran those were amazing—I think half the staff now work for AWS—but there was this story that I heard where there was an app that used to go down at the same time every day, and nobody could work out why. And it was because someone was coming in to clean the room at that time, and they unplugged the server to plug in a vacuum, and then we're cleaning the room, and then plugging it back in again. And that's the kind of thing that just happens when you manage people, and you manage a building, and manage a premises. Whereas if you've heard that happened that AWS, I mean, that would be front page news.Corey: Oh, it absolutely would. There's also—as you say, if it's the sales function, if people aren't able to buy insurance for an hour, when us-east-1 went down, the headlines were all screaming about AWS taking an outage, and some of the more notable customers were listed as examples of this, but the story was that, “AWS has massive outage,” not, “Your particular company is bad at technology.” There's sort of a reputational risk mitigation by going with one of these centralized things. And again, as you're alluding to, what you're doing is not life-critical as far as the sales process and getting people to sign up. If an outage meant that suddenly a bunch of customers were no longer insured, that's a very different problem. But that's not your failure mode.Matt: Exactly. And that's where, like, you got to look at what your business is, and what you're specifically doing, but for 99.99999% of businesses out there, I'm pretty sure you can be down for the tiny window that AWS is down per year, and it will be okay, as long as you plan for it.Corey: So, one thing that really surprised me about the entirety of what you've done at Liberty Mutual is that you're a big enterprise company, and you can take a look at any enterprise company, and say that they have dueling mottos, which is, “I am not going to comment on that,” or, “That's not funny.” Like, the safe mode for any large concern is to say nothing at all. But a lot of folks—not just you—at Liberty have been extremely vocal about the work that you're doing, how you view these things, and I almost want to call it advocacy or evangelism for the CDK. I'm slightly embarrassed to admit that for a little while there, I thought you were an AWS employee in their DevRel program because you were such an advocate in such strong ways for the CDK itself.And that is not something I expected. Usually you see the most vocal folks working in environments that, let's be honest, tend to play a little bit fast and loose with things like formal corporate communications. Liberty doesn't and yet, there you folks are telling these great stories. Was that hard to win over as a culture, or am I just misunderstanding how corporate life is these days?Matt: No, I mean, so it was different, right? There was a point in time where, I think, we all just sort of decided that—I mean, we're really good at what we do from an engineering perspective, and we wanted to make sure that, given the messaging we were given, those 5000 teck employees in Liberty Mutual, if you consider the difference in broadcasting to 5000 versus going external, it may sound like there's millions, billions of people in the world, but in reality, the difference in messaging is not that much. So, to me what I thought, like, whenever I started anyway—it's not, like, we had a meeting and all decided at the same time—but whenever I started, it was a case of, instead of me just posting on all the internal channels—because I've been doing this for years—it's just at that moment, I thought, I could just start saying these things externally and still bring them internally because all you've done is widened the audience; you haven't actually made it shallower. And that meant that whenever I was having the internal conversations, nothing actually changed except for it meant external people, like all their Heroes—like Jeremy Daly—could comment on these things, and then I could bring that in internally. So, it almost helped the reverse takeover of the enterprise to change the culture because I didn't change that much except for change the audience of who I was talking to.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 thing that you've done that I want to say is admirable, and I stumbled across it when I was doing some work myself over the break, and only right before this recording did I discover that it was you is the cdkpatterns.com website. Specifically what I love about it is that it publishes a bunch of different patterns of ways to do things. This deviates from a lot of tutorials on, “Here's how to build this one very specific thing,” and instead talks about, “Here's the architecture design; here's what the baseline pattern for that looks like.” It's more than a template, but less than a, “Oh, this is a messaging app for dogs and I'm trying to build a messaging app for cats.” It's very generalized, but very direct, and I really, really like that model of demo.Matt: Thank you. So, watching some of your Twitter threads where you experiment with new—Corey: Uh oh. People read those. That's a problem.Matt: I know. So, whatever you experiment with a new piece of AWS to you, I've always wondered what it would be like to be your enabling architect. Because technically, my job in Liberty is, I meant to try and stay ahead of everybody and try and ease the on-ramp to these things. So, if I was your enabling architect, I would be looking at it going, “I should really have a pattern for this.” So that whenever you want to pick up that new service the patterns in cdkpatterns.com, there's 24, 25 of them right there, but internally, there's way more than dozens now.The goal is, the pattern is the least amount to code for you to learn a concept. And then that way, you can not only see how something works, but you can maybe pick up one of the pieces of the well-architected framework while you're there: All of it's unit tested, all of it is proper, you know, like, commented code. The idea is to not be crap, but not be gold-plated either. I'm currently in the process of upgrading that all to V2 as well. So, that [unintelligible 00:21:32].Corey: You mentioned a phrase just now: “Enabling architect.” I have to say this one that has not crossed my desk before. Is that an internal term you use? Is that an enterprise concept I've somehow managed to avoid? Is that an AWS job role? What is that?Matt: I've just started saying [laugh] it's my job over the past couple of years. That—I don't know, patent pending? But the idea to me is—Corey: No, it's evocative. I love the term, I'd love to learn more.Matt: Yeah, because you can sort of take two approaches to your architecture: You can take the traditional approach, which is the ‘house of no' almost, where it's like, “This is the architecture. How dare you want to deviate. This is what we have decided. If you want to change it, here's the Architecture Council and go through enterprise architecture as people imagine it.” But as people might work out quite quickly, whenever they meet me, the whole, like, long conversational meetings are not for me. What I want to do is teach engineers how to help themselves, so that's why I see myself as enabling.And what I've been doing is using techniques like Wardley Mapping, which is where you can go out and you can actually take all the components of people's architecture and you can draw them on a map for—it's a map of how close they are to the customer, as well as how cutting edge the tech is, or how aligned to our strategic direction it is. So, you can actually map out all of the teams, and—there's 160, 170 engineers in Belfast and Dublin, and I can actually go in and say, “Oh, that piece of your architecture would be better if it was evolved to this. Well, I have a pattern for that,” or, “I don't have a pattern for that, but you know what? I'll build one and let's talk about it next week.” And that's always trying to be ahead, instead of people coming to me and I have to say no.Corey: AWS Proton was designed to do something vaguely similar, where you could set out architectural patterns of—like, the two examples that they gave—I don't know if it's in general availability yet or still in public preview, but the ones that they gave were to build a REST API with Lambda, and building something-or-other with Fargate. And the idea was that you could basically fork those, or publish them inside of your own environment of, “Oh, you want a REST API; go ahead and do this.” It feels like their vision is a lot more prescriptive than what yours is.Matt: Yeah. I talked to them quite a lot about Proton, actually because, as always, there's different methodologies and different ways of doing things. And as I showed externally, we have our software accelerator, which is kind of our take on Proton, and it's very open. Anybody can contribute; anybody can consume. And then that way, it means that you don't necessarily have one central team, you can have—think of it more like an SRE function for all of the patterns, rather than… the Proton way is you've separate teams that are your DevOps teams that set up your patterns and then separate team that's consumer, and they have different permissions, different rights to do different things. If you use a Proton pattern, anytime an update is made to that pattern, it auto-deploys your infrastructure.Corey: I can see that breaking an awful lot.Matt: [laugh]. Yeah. So, the idea is sort of if you're a consumer, I assume you [unintelligible 00:24:35] be going to change that infrastructure. You can, they've built in an escape hatch, but the whole concept of it is there's a central team that looks to what the best configuration for that is. So, I think Proton has so much potential, I just think they need to loosen some of the boundaries for it to work for us, and that's the feedback I've given them directly as well.Corey: One thing that I want to take a step beyond this is, you care about this? More than most do. I mean, people will work with computers, yes. We get paid for that. Then they'll go and give talks about things. You're doing that as well. They'll launch a website occasionally, like, cdkpatterns.com, which you have. And then you just sort of decide to go for the absolute hardest thing in the world, and you're one of four authors of a book on this. Tell me more.Matt: Yeah. So, this is something that there's a few of us have been talking since one of the first CDK Days, where we're friends, so there's AWS Heroes. There's Thorsten Höger, Matt Bonig, Sathyajith Bhat, and myself, came together—it was sometime in the summer last year—and said, “Okay. We want to write a book, but how do we do this?” Because, you know, we weren't authors before this point; we'd never done it before. We weren't even sure if we should go to a publisher, or if we should self-publish.Corey: I argue that no one wants to write a book. They want to have written a book, and every first-time author I've ever spoken to at the end has said, “Why on earth would anyone want to do this a second time?” But people do it.Matt: Yeah. And that's we talked to Alex DeBrie, actually, about his book, the amazing Dynamodb Book. And it was his advice, told us to self-publish. And he gave us his starter template that he used for his book, which took so much of the pain out because all we had to do was then work out how we were going to work together. And I will say, I write quite a lot of stuff in general for people, but writing a book is completely different because once it's out there, it's out there. And if it's wrong, it's wrong. You got to release a new version and be like, “Listen, I got that wrong.” So, it did take quite a lot of effort from the group to pull it together. But now that we have it, I want to—I don't have a printed copy because it's only PDF at the minute, but I want a copy just put here [laugh] in, like, the frame. Because it's… it's what we all want.Corey: Yeah, I want you to do that through almost a traditional publisher, selfishly, because O'Reilly just released the AWS Cookbook, and I had a great review quote on the back talking about the value added. I would love to argue that they use one of mine for The CDK Book—and then of course they would reject it immediately—of, “I don't know why you do all this. Using the console and lying about it is way easier.” But yeah, obviously not the direction you're trying to take the book in. But again, the industry is not quite ready for the lying version of ClickOps.It's really neat to just see how willing you are to—how to frame this?—to give of yourself and your time and what you've done so freely. I sometimes make a joke—that arguably isn't that funny—that, “Oh, AWS Hero. That means that you basically volunteer for a $1.6 trillion company.”But that's not actually what you're doing. What you're doing is having figured out all the sharp edges and hacked your way through the jungle to get to something that is functional, you're a trailblazer. You're trying to save other people who are working with that same thing from difficult experiences on their own, having to all thrash and find our own way. And not everyone is diligent and as willing to continue to persist on these things. Is that a somewhat fair assessment how you see the Hero role?Matt: Yeah. I mean, no two Heroes are the same, from what I've judged, I haven't met every Hero yet because pandemic, so Vegas was the first time [I met most 00:28:12], but from my perspective, I mean, in the past, whatever number of years I've been coding, I've always been doing the same thing. Somebody always has to go out and be the first person to try the thing and work out what the value is, and where it'll work for us more work for us. The only difference with the external and public piece is that last 5%, which it's a very different thing to do, but I personally, I like even having conversations like this where I get to meet people that I've never met before.Corey: You sort of discovered the entire secret of why I have an interview podcast.Matt: [laugh]. Yeah because this is what I get out of it, just getting to meet other people and have new experiences. But I will say there's Heroes out there doing very different things. You've got, like, Hiro—as in Hiro, H-I-R-O—actually started AWS Newbies and she's taught—ah, it's hundreds of thousands of people how to actually just start with AWS, through a course designed for people who weren't coders before. That kind of thing is next-level compared to anything I've ever done because you know, they have actually built a product and just given it away. I think that's amazing.Corey: At some level, building a product and giving it away sounds like, “You know, I want to never be lonely again.” Well, that'll work because you're always going to get support tickets. There's an interesting narrative around how to wind up effectively managing the community, and users, and demands, based on open-source maintainers, that we're all wrestling with as an industry, particularly in the wake of that whole log4j nonsense that we've been tilting at that windmill, and that's going to be with us for a while. One last thing I want to talk about before we wind up calling this an episode is, you are one of the organizers of CDK Day. What is that?Matt: Yeah, so CDK Day, it's a complete community-organized conference. The past two have been worldwide, fully virtual just because of the situation we're in. And I mean, they've been pretty popular. I think we had about 5000 people attended the last one, and the idea is, it's a full day of the community just telling their stories of how they liked or disliked using the CDK. So, it's not a marketing event; it's not a sales event; we actually run the whole event on a budget of exactly $0. But yeah, it's just a day of fun to bring the community together and learn a few things. And, you know, if you leave it thinking CDK is not for you, I'm okay with that as much as if you just make a few friends while you're there.Corey: This is the first time I'd realized that it wasn't a formal AWS event. I almost feel like that's the tagline that you should have under it. It's—because it sounds like the CDK Day, again, like, it's this evangelism pure, “This is why it's great and why you should use it.” But I love conferences that embrace critical views. I built one of the first talks I ever built out that did anything beyond small user groups was “Heresy in the Church of Docker.”Then they asked me to give that at ContainerCon, which was incredibly flattering. And I don't think they made that mistake a second time, but it was great to just be willing to see some group of folks that are deeply invested in the technology, but also very open to hearing criticism. I think that's the difference between someone who is writing a nuanced critique versus someone who's just [pure-on 00:31:18] zealotry. “But the CDK is the answer to every technical problem you've got.” Well, I start to question the wisdom of how applicable it really is, and how objective you are. I've never gotten that vibe from you.Matt: No, and that's the thing. So, I mean, as we've worked out in this conversation, I don't work for AWS, so it's not my product. I mean, if it succeeds or if it fails, it doesn't impact my livelihood. I mean, there are people on the team who would be sad for, but the point is, my end goal is always the same. I want people to be enabled to rapidly deliver their software to help their customers.If that's CDK, perfect, but CDK is not for everyone. I mean, there are other options available in the market. And if, even, ClickOps is the way to go for you, I am happy for you. But if it's a case of we can have a conversation, and I can help you get closer to where you need to be with some other tool, that's where I want to be. I just want to help people.Corey: And if I can do anything to help along that axis, please don't hesitate to let me know. I really want to thank you for taking the time to speak with me and being so generous, not just with your time for this podcast, but all the time you spend helping the rest of us figure out which end is up, as we continue to find that the way we manage environments evolves.Matt: Yeah. And, listen, just thank you for having me on today because I've been reading your tweets for two years, so I'm just starstruck at this moment to even be talking to you. So, thank you.Corey: No, no. I understand that, but don't worry, I put my pants on two legs at a time, just like everyone else. That's right, the thought leader on Twitter, you have to jump into your pants. That's the rule. Thanks again so much. I look forward to having a further conversation with you about this stuff as I continue to explore, well honestly, what feels like a brand new paradigm for how we manage code.Matt: Yeah. Reach out if you need any help.Corey: I certainly will. You'll regret asking. Matt [Coulter 00:33:06], Technical Architect at Liberty Mutual. 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, write an angry comment, then click the submit button, but lie and say you hit the submit button via an API call.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.

Women of Substance Music Podcast
#1328 Music by Gail Taylor, Cassidy Ladden (writers Marv Conan & Brian Muni), Alison Reynolds, HuDost, Neu Sierra, Lori Citro, Kelly Rae, The Epsan Project, Storied Windows, Shifter X

Women of Substance Music Podcast

Play Episode Listen Later Jan 12, 2022 48:49


To get live links to the music we play and resources we offer, visit This show includes the following songs: Gail Taylor - Crossroads  Cassidy Ladden (writers Marv Conan & Brian Muni) - When You Ride A Dream  Alison Reynolds - Closer To Home  HuDost - Home Is Bigger Than Us  Neu Sierra - Boy Of A 1000 Tears  Lori Citro - Perpetually 25  Kelly Rae - One Light  The Epsan Project - Where Our Love Is Storied Windows - Waves (Stripped Down)  Shifter X - Break The Chains  For Music Biz Resources Visit and Visit our Sponsor Juice The Black Beethoven at Visit our Sponsor Storied Windows at Visit our Sponsor Bandzoogle at:

Integrate & Ignite Podcast
Episode 391: Responding to the Speed of Culture with Mike Westgate of TikTok.

Integrate & Ignite Podcast

Play Episode Listen Later Jan 11, 2022 29:54


“TikTok is making marketers into performing artists.” Listen & Learn: How TikTok changed -- and gained popularity -- during the pandemic. Why TikTok is an entertainment platform rather than a social platform. The platform's product roadmap aimed at highly creative and engaged creators. How brands can find their authentic voice. How TikTok is a multi-sensory platform marketers need to master. On TikTok, content is king. Mike Westgate manages TikTok's US Growth Brand business, supporting hundreds of midmarket brand clients with unique marketing and advertising solutions. Before TikTok, Mike was VP of marketing at Briggo Coffee, the world's first robotic barista, responsible for B2B & B2C brand strategy, PR & communications, product marketing, and retail sales programs. Prior to Briggo, he was VP of Marketing for commercial real estate data marketplace startup, RealMassive. Prior, he led marketing and client engagements for W2O Group, a network of digital marketing agencies supporting Fortune 500 marketers with customer insights, strategy, and analytics. Before W2O Group, Mike spent nearly four years at Microsoft in Windows product marketing and SMB audience marketing roles, both in Seattle and in Austin. He began his career in CPG with five years at Sara Lee and two years at General Mills in a variety of sales and marketing roles.    Content strategies that build your brand's authentic voice. Learn more from Lori Jones by calling today. 303-678-7102.   TO LEARN MORE ABOUT TIK TOK, CLICK HERE. TO FIND MIKE WESTGATE ON LINKEDIN, CLICK HERE.

Broken Silicon
135. R7 5800X3D v i7-12700K, Mini-LED Monitors, Rembrandt, 6500 XT | Hardware Unboxed

Broken Silicon

Play Episode Listen Later Jan 11, 2022 142:06


Tim from Hardware Unboxed joins to discuss QD-OLED Monitors, Ryzen 6000, Zen 4, and much more! [SPON: brokensilicon = -30% off Windows, dieshrink = -3% off Everything: https://biitt.ly/shbSk] [SPON: Get 10% off Tasty Vite Ramen with Code “brokensilicon” at: https://bit.ly/3oyv4tR] 0:00 What were Tim's thoughts on 2021? 4:23 Did the R7 5800X3D announcement surprise us? Are we excited about Zen 4? 7:57 What will the 5800X3D cost? Will Zen 3 get price drops? 14:37 When do we expect Zen 4 to launch? Were we impressed by the demo? 16:58 Quantum Dot OLED Panels - Will these become the new High End Standard? 25:30 How much better Quantum Dot OLED than W-OLED? Is Burn-In fixed? 33:35 Discussing the latest “fake” HDMI 2.1 shenanigans – when is bending the spec ok? 42:59 Mini LED Monitors - Are these going to get cheaper than OLED? How good are they? 54:17 Will AMD Rembrandt compete well with Alder Lake Mobile? Will the MX550 be DOA? 1:08:11 What APU do Tim & Tom wish existed? What APU would WE ask AMD to make? 1:15:36 Intel vs AMD Laptops in 2022 1:22:34 AMD 6000M vs Ampere Laptops 1:27:11 AMD Market Share Mistakes in 2021 - What could they have done better? 1:40:45 RX 6500 XT 4GB - Could they have just launched an RX 590 4GB instead? 1:45:50 RX 6500 XT performance and availability Whispers 1:52:16 Intel ARC - If Alchemist beats the 3070, what should it cost? 1:59:59 What will Lovelace & RDNA 3 likely cost? 2:08:40 Lovelace, RDNA 3, Zen 4, Raptor Lake – What are we most excited for? Subscribe to Hardware Unboxed: https://www.youtube.com/c/Hardwareunboxednow https://www.tomshardware.com/news/viewsonic-launches-4-144hz-mini-led-display https://gadgets.ndtv.com/games/news/msi-meg-271q-gaming-monitor-launch-specifications-nvidia-g-sync-ultimate-300hz-1ms-esports-ces-2022-2692444 https://www.pcgamer.com/amd-unveils-new-radeon-rx-6000s-and-rx-6000m-gpus-for-gaming-laptops/ https://videocardz.com/newz/nvidia-geforce-rtx-3080-12gb-now-rumored-to-announced-on-january-11th https://videocardz.com/newz/inno3d-confirms-geforce-rtx-3050-features-ga106-150-gpu https://www.cnet.com/tech/home-entertainment/samsung-qd-oled-tv-tech-explained-welcome-quantum-dot-era/ https://www.anandtech.com/show/17180/ces-2022-the-asus-rog-zephyrus-g14-for-2022-ryzen-6000-mobile-with-radeon https://www.amd.com/en/products/graphics/amd-radeon-rx-6800s https://www.theverge.com/2022/1/3/22856102/lg-97-42-inch-oled-4k-8k-qned-tvs-announced-features https://www.techpowerup.com/290648/amd-socket-am5-a-long-lived-platform-ceo https://en.wikipedia.org/wiki/HDMI#Version_2.1

Screaming in the Cloud
GCP's Many Profundities with Miles Ward

Screaming in the Cloud

Play Episode Listen Later Jan 11, 2022 42:06


About MilesAs Chief Technology Officer at SADA, Miles Ward leads SADA's cloud strategy and solutions capabilities. His remit includes delivering next-generation solutions to challenges in big data and analytics, application migration, infrastructure automation, and cost optimization; reinforcing our engineering culture; and engaging with customers on their most complex and ambitious plans around Google Cloud.Previously, Miles served as Director and Global Lead for Solutions at Google Cloud. He founded the Google Cloud's Solutions Architecture practice, launched hundreds of solutions, built Style-Detection and Hummus AI APIs, built CloudHero, designed the pricing and TCO calculators, and helped thousands of customers like Twitter who migrated the world's largest Hadoop cluster to public cloud and Audi USA who re-platformed to k8s before it was out of alpha, and helped Banco Itau design the intercloud architecture for the bank of the future.Before Google, Miles helped build the AWS Solutions Architecture team. He wrote the first AWS Well-Architected framework, proposed Trusted Advisor and the Snowmobile, invented GameDay, worked as a core part of the Obama for America 2012 “tech” team, helped NASA stream the Curiosity Mars Rover landing, and rebooted Skype in a pinch.Earning his Bachelor of Science in Rhetoric and Media Studies from Willamette University, Miles is a three-time technology startup entrepreneur who also plays a mean electric sousaphone.Links: SADA.com: https://sada.com Twitter: https://twitter.com/milesward Email: miles@sada.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: It seems like there is a new security breach every day. Are you confident that an old SSH key, or a shared admin account, isn't going to come back and bite you? If not, check out Teleport. Teleport is the easiest, most secure way to access all of your infrastructure. The open source Teleport Access Plane consolidates everything you need for secure access to your Linux and Windows servers—and I assure you there is no third option there. Kubernetes clusters, databases, and internal applications like AWS Management Console, Yankins, GitLab, Grafana, Jupyter Notebooks, and more. Teleport's unique approach is not only more secure, it also improves developer productivity. To learn more visit: goteleport.com. And not, that is not me telling you to go away, it is: goteleport.com.Corey: This episode is sponsored in part by our friends at Redis, the company behind the incredibly popular open source database that is not the bind DNS server. If you're tired of managing open source Redis on your own, or you're using one of the vanilla cloud caching services, these folks have you covered with the go to manage Redis service for global caching and primary database capabilities; Redis Enterprise. To learn more and deploy not only a cache but a single operational data platform for one Redis experience, visit redis.com/hero. Thats r-e-d-i-s.com/hero. And my thanks to my friends at Redis for sponsoring my ridiculous non-sense.  Corey: Welcome to Screaming in the Cloud. I'm Corey Quinn. I am joined today, once again by my friend and yours, Miles Ward, who's the CTO at SADA. However, he is, as I think of him, the closest thing the Google Cloud world has to Corey Quinn. Now, let's be clear, not the music and dancing part that is Forrest Brazeal, but Forrest works at Google Cloud, whereas Miles is a reasonably salty third-party. Miles, thank you for coming back and letting me subject you to that introduction.Miles: Corey, I appreciate that introduction. I am happy to provide substantial salt. It is easy, as I play brass instruments that produce my spit in high volumes. It's the most disgusting part of any possible introduction. For the folks in the audience, I am surrounded by a collection of giant sousaphones, tubas, trombones, baritones, marching baritones, trumpets, and pocket trumpets.So, Forrest threw down the gauntlet and was like, I can play a keyboard, and sing, and look cute at the same time. And so I decided to fail at all three. We put out a new song just a bit ago that's, like, us thanking all of our customers and partners, covering Kool & the Gang “Celebration,” and I neither look good, [laugh] play piano, or smiling, or [capturing 00:01:46] any of the notes; I just play the bass part, it's all I got to do.Corey: So, one thing that I didn't get to talk a lot about because it's not quite in my universe, for one, and for another, it is during the pre re:Invent—pre:Invent, my nonsense thing—run up, which is Google Cloud Next.Miles: Yes.Corey: And my gag a few years ago is that I'm not saying that Google is more interested in what they're building and what they're shipping, but even their conference is called Next. Buh dum, hiss.Miles: [laugh].Corey: So, I didn't really get to spend a lot of attention on the Google Cloud releases that came out this year, but given that SADA is in fact the, I believe, largest Google Cloud partner on the internet, and thus the world—Miles: [unintelligible 00:02:27] new year, three years in a row back, baby.Corey: Fantastic. I assume someone's watch got stuck or something. But good work. So, you have that bias in the way that I have a bias, which is your business is focused around Google Cloud the way that mine is focused on AWS, but neither of us is particularly beholden to that given company. I mean, you do have the not getting fired as partner, but that's a bit of a heavy lift; I don't think I can mouth off well enough to get you there.So, we have a position of relative independence. So, you were tracking Google Next, the same way that I track re:Invent. Well, not quite the same way I track re:Invent; there are some significant differences. What happened at Cloud Next 2021, that the worst of us should be paying attention to?Miles: Sure. I presented 10% of the material at the first re:Invent. There are 55 sessions; I did six. And so I have been at Cloud events for a really long time and really excited about Google's willingness to dive into demos in a way that I think they have been a little shy about. Kelsey Hightower is the kind of notable deep exception to that. Historically, he's been ready to dive into the, kind of, heavy hands-on piece but—Corey: Wait, those were demos? [Thought 00:03:39] was just playing Tetris on stage for the love of it.Miles: [laugh]. No. And he really codes all that stuff up, him and the whole team.Corey: Oh, absol—I'm sorry. If I ever grow up, I wish to be Kelsey Hightower.Miles: [laugh]. You and me both. So, he had kind of led the charge. We did a couple of fun little demos while I was there, but they've really gotten a lot further into that, and I think are doing a better job of packaging the benefits to not just developers, but also operators and data scientists and the broader roles in the cloud ecosystem from the new features that are being launched. And I think, different than the in-person events where there's 10, 20,000, 40,000 people in the audience paying attention, I think they have to work double-hard to capture attention and get engineers to tune in to what's being launched.But if you squint and look close, there are some, I think, very interesting trends that sit in the back of some of the very first launches in what I think are going to be whole veins of launches from Google over the course of the next several years that we are working really hard to track along with and make sure we're extracting maximum value from for our customers.Corey: So, what was it that they announced that is worth paying attention to? Now, through the cacophony of noise, one announcement that [I want to note 00:04:49] was tied to Next was the announcement that GME group, I believe, is going to be putting their futures exchange core trading systems on Google Cloud. At which point that to me—and I know people are going to yell at me, and I don't even slightly care—that is the last nail in the coffin of the idea that well, Google is going to turn this off in a couple years. Sorry, no. That is not a thing that's going to happen. Worst case, they might just stop investing it as aggressively as they are now, but even that would be just a clown-shoes move that I have a hard time envisioning.Miles: Yeah, you're talking now over a dozen, over ten year, over a billion-dollar commitments. So, you've got to just really, really hate your stock price if you're going to decide to vaporize that much shareholder value, right? I mean, we think that, in Google, stock price is a material fraction of the recognition of the growth trajectory for cloud, which is now basically just third place behind YouTube. And I think you can do the curve math, it's not like it's going to take long.Corey: Right. That requires effectively ejecting Thomas Kurian as the head of Google Cloud and replacing him with the former SVP of Bad Decisions at Yahoo.Miles: [laugh]. Sure. Google has no shyness about continuing to rotate leadership. I was there through three heads of Google Cloud, so I don't expect that Thomas will be the last although I think he may well go down in history as having been the best. The level of rotation to the focuses that I think are most critical, getting enterprise customers happy, successful, committed, building macroscale systems, in systems that are critical to the core of the business on GCP has grown at an incredible rate under his stewardship. So, I think he's doing a great job.Corey: He gets a lot of criticism—often from Googlers—when I wind up getting the real talk from them, which is, “Can you tell me what you really think?” Their answer is, “No,” I'm like, “Okay, next question. Can I go out and buy you eight beers and then”— and it's like, “Yeah.” And the answer that I get pretty commonly is that he's brought too much Oracle into Google. And okay, that sounds like a bad thing because, you know, Oracle, but let's be clear here, but what are you talking about specifically? And what they say distills down to engineers are no longer the end-all be-all of everything that Google Cloud. Engineers don't get to make sales decisions, or marketing decisions, or in some cases, product decisions. And that is not how Google has historically been run, and they don't like the change. I get it, but engineering is not the only hard thing in the world and it's not the only business area that builds value, let's be clear on this. So, I think that the things that they don't like are in fact, what Google absolutely needs.Miles: I think, one, the man is exceptionally intimidating and intentionally just hyper, hyper attentive to his business. So, one of my best employees, Brad [Svee 00:07:44], he worked together with me to lay out what was the book of our whole department, my team of 86 people there. What are we about? What do we do? And like I wanted this as like a memoriam to teach new hires as got brought in. So, this is, like, 38 pages of detail about our process, our hiring method, our promotional approach, all of it. I showed that to my new boss who had come in at the time, and he thought some of the pictures looked good. When we showed it to TK, he read every paragraph. I watched him highlight the paragraphs as he went through, and he read it twice as fast as I can read the thing. I think he does that to everybody's documents, everywhere. So, there's a level of just manual rigor that he's brought to the practice that was certainly not there before that. So, that alone, it can be intimidating for folks, but I think people that are high performance find that very attractive.Corey: Well, from my perspective, he is clearly head and shoulders above Adam Selipsky, and Scott Guthrie—the respective heads of AWS and Azure—for one key reason: He is the only one of those three people who follows me on Twitter. And—Miles: [laugh].Corey: —honestly, that is how I evaluate vendors.Miles: That's the thing. That's the only measure, yep. I've worked on for a long time with Selipsky, and I think that it will be interesting to see whether Adam's approach to capital allocation—where he really, I think, thinks of himself as the manager of thousands of startups, as opposed to a manager of a global business—whether that's a more efficient process for creating value for customers, then, where I think TK is absolutely trying to build a much more unified, much more singular platform. And a bunch of the launches really speak to that, right? So, one of the product announcements that I think is critical is this idea of the global distributed cloud, Google Distributed Cloud.We started with Kubernetes. And then you layer on to that, okay, we'll take care of Kubernetes for you; we call that Anthos. We'll build a bunch of structural controls and features into Anthos to make it so that you can really deal with stuff in a global way. Okay, what does that look like further? How do we get out into edge environments? Out into diverse hardware? How do we partner up with everybody to make sure that, kind of like comparing Apple's approach to Google's approach, you have an Android ecosystem of Kubernetes providers instead of just one place you can buy an outpost. That's generally the idea of GDC. I think that's a spot where you're going to watch Google actually leverage the muscle that it already built in understanding open-source dynamics and understanding collaboration between companies as opposed to feeling like it's got to be built here. We've got to sell it here. It's got to have our brand on it.Corey: I think that there's a stupendous and extreme story that is still unfolding over at Google Cloud. Now, re:Invent this year, they wound up talking all about how what they were rolling out was a focus on improving primitives. And they're right. I love their managed database service that they launched because it didn't exist.Miles: Yeah Werner's slide, “It's primitives, not frameworks.” I was like, I think customers want solutions, not frameworks or primitives. [laugh]. What's your plan?Corey: Yeah. However, I take a different perspective on all of this, which is that is a terrific spin on the big headline launches all missed the re:Invent timeline, and… oops, so now we're just going to talk about these other things instead. And that's great, but then they start talking about industrial IOT, and mainframe migrations, and the idea of private 5G, and running fleets of robots. And it's—Miles: Yeah, that's a cool product.Corey: Which one? I'm sorry, they're all very different things.Miles: Private 5G.Corey: Yeah, if someone someday will explain to me how it differs from Wavelength, but that's neither here nor there. You're right, they're all interesting, but none of them are actually doing the thing that I do, which is build websites, [unintelligible 00:11:31] looking for web services, it kind of says it in the name. And it feels like it's very much broadening into everything, and it's very difficult for me to identify—and if I have trouble that I guarantee you customers do—of, which services are for me and which are very much not? In some cases, the only answer to that is to check the pricing. I thought Kendra, their corporate information search thing was for me, then it's 7500 bucks a month to get started with that thing, and that is, “I can hire an internal corporate librarian to just go and hunt through our Google Drive.” Great.Miles: Yeah.Corey: So, there are—or our Dropbox, or our Slack. We have, like, five different information repositories, and this is how corporate nonsense starts, let me assure you.Miles: Yes. We call that luxury SaaS, you must enjoy your dozens of overlapping bills for, you know, what Workspace gives you as a single flat rate.Corey: Well, we have [unintelligible 00:12:22] a lot of this stuff, too. Google Drive is great, but we use Dropbox for holding anything that touches our customer's billing information, just because I—to be clear, I do not distrust Google, but it also seems a little weird to put the confidential billing information for one of their competitors on there to thing if a customer were to ask about it. So, it's the, like, I don't believe anyone's doing anything nefarious, but let's go ahead and just make sure, in this case.Miles: Go further man. Vimeo runs on GCP. You think YouTube doesn't want to look at Vimeo stats? Like they run everything on GCP, so they have to have arrived at a position of trust somehow. Oh, I know how it's called encryption. You've heard of encryption before? It's the best.Corey: Oh, yes. I love these rumors that crop up every now and again that Amazon is going to start scanning all of its customer content, somehow. It's first, do you have any idea how many compute resources that would take and to if they can actually do that and access something you're storing in there, against their attestations to the contrary, then that's your story because one of them just makes them look bad, the other one utterly destroys their entire business.Miles: Yeah.Corey: I think that that's the one that gets the better clicks. So no, they're not doing that.Miles: No, they're not doing that. Another product launch that I thought was super interesting that describes, let's call it second place—the third place will be the one where we get off into the technical deep end—but there's a whole set of coordinated work they're calling Cortex. So, let's imagine you go to a customer, they say, “I want to understand what's happening with my business.” You go, “Great.” So, you use SAP, right? So, you're a big corporate shop, and that's your infrastructure of choice. There are a bunch of different options at that layer.When you set up SAP, one of the advantages that something like that has is they have, kind of, pre-built configurations for roughly your business, but whatever behaviors SAP doesn't do, right, say, data warehousing, advanced analytics, regression and projection and stuff like that, maybe that's somewhat outside of the core wheelhouse for SAP, you would expect like, oh okay, I'll bolt on BigQuery. I'll build that stuff over there. We'll stream the data between the two. Yeah, I'm off to the races, but the BigQuery side of the house doesn't have this like bitching menu that says, “You're a retailer, and so you probably want to see these 75 KPIs, and you probably want to chew up your SKUs in exactly this way. And here's some presets that make it so that this is operable out of the box.”So, they are doing the three way combination: Consultancies plus ISVs plus Google products, and doing all the pre-work configuration to go out to a customer and go I know what you probably just want. Why don't I just give you the whole thing so that it does the stuff that you want? That I think—if that's the very first one, this little triangle between SAP, and Big Query, and a bunch of consultancies like mine, you have to imagine they go a lot further with that a lot faster, right? I mean, what does that look like when they do it with Epic, when they go do it with Go just generally, when they go do it with Apache? I've heard of that software, right? Like, there's no reason not to bundle up what the obvious choices are for a bunch of these combinations.Corey: The idea of moving up the stack and offering full on solutions, that's what customers actually want. “Well, here's a bunch of things you can do to wind up wiring together to build a solution,” is, “Cool. Then I'm going to go hire a company who's already done that is going to sell it to me at a significant markup because I just don't care.” I pay way more to WP Engine than I would to just run WordPress myself on top of AWS or Google Cloud. In fact, it is on Google Cloud, but okay.Miles: You and me both, man. WP Engine is the best. I—Corey: It's great because—Miles: You're welcome. I designed a bunch of the hosting on the back of that.Corey: Oh, yeah. But it's also the—I—well, it costs a little bit more that way. Yeah, but guess what's not—guess what's more expensive than that bill, is my time spent doing the care and feeding of this stuff. I like giving money to experts and making it their problem.Miles: Yeah. I heard it said best, Lego is an incredible business. I love their product, and you can build almost any toy with it. And they have not displaced all other plastic toy makers.Corey: Right.Miles: Some kids just want to buy a little car. [laugh].Corey: Oh, yeah, you can build anything you want out of Lego bricks, which are great, which absolutely explains why they are a reference AWS customer.Miles: Yeah, they're great. But they didn't beat all other toy companies worldwide, and eliminate the rest of that market because they had the better primitive, right? These other solutions are just as valuable, just as interesting, tend to have much bigger markets. Lego is not the largest toy manufacturer in the world. They are not in the top five of toy manufacturers in the world, right?Like, so chasing that thread, and getting all the way down into the spots where I think many of the cloud providers on their own, internally, had been very uncomfortable. Like, you got to go all the way to building this stuff that they need for that division, inside of that company, in that geo, in that industry? That's maybe, like, a little too far afield. I think Google has a natural advantage in its more partner-oriented approach to create these combinations that lower the cost to them and to customers to getting out of that solution quick.Corey: So, getting into the weeds of Google Next, I suppose, rather than a whole bunch of things that don't seem to apply to anyone except the four or five companies that really could use it, what things did Google release that make the lives of people building, you know, web apps better?Miles: This is the one. So, I'm at Amazon, hanging out as a part of the team that built up the infrastructure for the Obama campaign in 2012, and there are a bunch of Googlers there, and we are fighting with databases. We are fighting so hard, in fact, with RDS that I think we are the only ones that [Raju 00:17:51] has ever allowed to SSH into our RDS instances to screw with them.Corey: Until now, with the advent of RDS Custom, meaning that you can actually get in as root; where that hell that lands between RDS and EC2 is ridiculous. I just know that RDS can now run containers.Miles: Yeah. I know how many things we did in there that were good for us, and how many things we did in there that were bad for us. And I have to imagine, this is not a feature that they really ought to let everybody have, myself included. But I will say that what all of the Googlers that I talk to, you know, at the first blush, were I'm the evil Amazon guy in to, sort of, distract them and make them build a system that, you know, was very reliable and ended up winning an election was that they had a better database, and they had Spanner, and they didn't understand why this whole thing wasn't sitting on Spanner. So, we looked, and I read the white paper, and then I got all drooly, and I was like, yes, that is a much better database than everybody else's database, and I don't understand why everybody else isn't on it. Oh, there's that one reason, but you've heard of it: No other software works with it, anywhere in the world, right? It's utterly proprietary to Google. Yes, they were kind—Corey: Oh, you want to migrate it off somewhere else, or a fraction of it? Great. Step one, redo your data architecture.Miles: Yeah, take all of my software everywhere, rewrite every bit of it. And, oh all those commercial applications? Yeah, forget all those, you got, too. Right? It was very much where Google was eight years ago. So, for me, it was immensely meaningful to see the launch at Next where they described what they are building—and have now built; we have alpha access to it—a Postgres layer for Spanner.Corey: Is that effectively you have to treat it as Postgres at all times, or is it multimodal access?Miles: You can get in and tickle it like Spanner, if you want to tickle it like Spanner. And in reality, Spanner is ANSI SQL compliant; you're still writing SQL, you just don't have to talk to it like a REST endpoint, or a GRPC endpoint, or something; you can, you know, have like a—Corey: So, similar to Azure's Cosmos DB, on some level, except for the part where you can apparently look at other customers' data in that thing?Miles: [laugh]. Exactly. Yeah, you will not have a sweeping discovery of incredible security violations in the structure Spanner, in that it is the control system that Google uses to place every ad, and so it does not suck. You can't put a trillion-dollar business on top of a database and not have it be safe. That's kind of a thing.Corey: The thing that I find is the most interesting area of tech right now is there's been this rise of distributed databases. Yugabyte—or You-ji-byte—Pla-netScale—or PlanetScale, depending on how you pronounce these things.Miles: [laugh]. Yeah, why, why is G such an adversarial consonant? I don't understand why we've all gotten to this place.Corey: Oh, yeah. But at the same time, it's—so you take a look at all these—and they all are speaking Postgres; it is pretty clear that ‘Postgres-squeal' is the thing that is taking over the world as far as databases go. If I were building something from scratch that used—Miles: For folks in the back, that's PostgreSQL, for the rest of us, it's okay, it's going to be, all right.Corey: Same difference. But yeah, it's the thing that is eating the world. Although recently, I've got to say, MongoDB is absolutely stepping up in a bunch of really interesting ways.Miles: I mean, I think the 4.0 release, I'm the guy who wrote the MongoDB on AWS Best Practices white paper, and I would grab a lot of customer's and—Corey: They have to change it since then of, step one: Do not use DocumentDB; if you want to use Mongo, use Mongo.Miles: Yeah, that's right. No, there were a lot of customers I was on the phone with where Mongo had summarily vaporized their data, and I think they have made huge strides in structural reliability over the course of—you know, especially this 4.0 launch, but the last couple of years, for sure.Corey: And with all the people they've been hiring from AWS, it's one of those, “Well, we'll look at this now who's losing important things from production?”Miles: [laugh]. Right? So, maybe there's only actually five humans who know how to do operations, and we just sort of keep moving around these different companies.Corey: That's sort of my assumption on these things. But Postgres, for those who are not looking to depart from the relational model, is eating the world. And—Miles: There's this, like, basic emotional thing. My buddy Martin, who set up MySQL, and took it public, and then promptly got it gobbled up by the Oracle people, like, there was a bet there that said, hey, there's going to be a real open database, and then squish, like, the man came and got it. And so like, if you're going to be an independent, open-source software developer, I think you're probably not pushing your pull requests to our friends at Oracle, that seems weird. So instead, I think Postgres has gobbled up the best minds on that stuff.And it works. It's reliable, it's consistent, and it's functional in all these different, sort of, reapplications and subdivisions, right? I mean, you have to sort of squint real hard, but down there in the guts of Redshift, that's Postgres, right? Like, there's Postgres behind all sorts of stuff. So, as an interface layer, I'm not as interested about how it manages to be successful at bossing around hardware and getting people the zeros and ones that they ask for back in a timely manner.I'm interested in it as a compatibility standard, right? If I have software that says, “I need to have Postgres under here and then it all will work,” that creates this layer of interop that a bunch of other products can use. So, folks like PlanetScale, and Yugabyte can say, “No, no, no, it's cool. We talk Postgres; that'll make it so your application works right. You can bring a SQL alchemy and plug it into this, or whatever your interface layer looks like.”That's the spot where, if I can trade what is a fairly limited global distribution, global transactional management on literally ridiculously unlimited scalability and zero operations, I can handle the hard parts of running a database over to somebody else, but I get my layer, and my software talks to it, I think that's a huge step.Corey: This episode is sponsored in part by my friends at Cloud Academy. Something special just for you folks. If you missed their offer on Black Friday or Cyber Monday or whatever day of the week doing sales it is—good news! They've opened up their Black Friday promotion for a very limited time. Same deal, $100 off a yearly plan, $249 a year for the highest quality cloud and tech skills content. Nobody else can get this because they have a assured me this not going to last for much longer. Go to CloudAcademy.com, hit the "start free trial" button on the homepage, and use the Promo code cloud at checkout. That's c-l-o-u-d, like loud, what I am, with a “C” in front of it. It's a free trial, so you'll get 7 days to try it out to make sure it's really a good fit for you, nothing to lose except your ignorance about cloud. My thanks again for sponsoring my ridiculous nonsense.Corey: I think that there's a strong movement toward building out on something like this. If it works, just because—well, I'm not multiregion today, but I can easily see a world in which I'd want to be. So, great. How do you approach the decision between—once this comes out of alpha; let's be clear. Let's turn this into something that actually ships, and no, Google that does not mean slapping a beta label on it for five years is the answer here; you actually have to stand behind this thing—but once it goes GA—Miles: GA is a good thing.Corey: Yeah. How do you decide between using that, or PlanetScale? Or Yugabyte?Miles: Or Cockroach or or SingleStore, right? I mean, there's a zillion of them that sit in this market. I think the core of the decision making for me is in every team you're looking at what skills do you bring to bear and what problem that you're off to go solve for customers? Do the nuances of these products make it easier to solve? So, I think there are some products that the nature of what you're building isn't all that dependent on one part of the application talking to another one, or an event happening someplace else mattering to an event over here. But some applications, that's, like, utterly critical, like, totally, totally necessary.So, we worked with a bunch of like Forex exchange trading desks that literally turn off 12 hours out of the day because they can only keep it consistent in one geographical location right near the main exchanges in New York. So, that's a place where I go, “Would you like to trade all day?” And they go, “Yes, but I can't because databases.” So, “Awesome. Let's call the folks on the Spanner side. They can solve that problem.”I go, “Would you like to trade all day and rewrite all your software?” And they go, “No.” And I go, “Oh, okay. What about trade all day, but not rewrite all your software?” There we go. Now, we've got a solution to that kind of problem.So like, we built this crazy game, like, totally other end of the ecosystem with the Dragon Ball Z people, hysterical; your like—you literally play like Rock, Paper, Scissors with your phone, and if you get a rock, I throw a fireball, and you get a paper, then I throw a punch, and we figure out who wins. But they can play these games like Europe versus Japan, thousands of people on each side, real-time, and it works.Corey: So, let's be clear, I have lobbied a consistent criticism at Google for a while now, which is the Google Cloud global control plane. So, you wind up with things like global service outages from time to time, you wind up with this thing is now broken for everyone everywhere. And that, for a lot of these use cases, is a problem. And I said that AWS's approach to regional isolation is the right way to do it. And I do stand by that assessment, except for the part where it turns out there's a lot of control plane stuff that winds up single tracking through us-east-1, as we learned in the great us-east-1 outage of 2021.Miles: Yeah, when I see customers move from data center to AWS, what they expect is a higher count of outages that lasts less time. That's the trade off, right? There's going to be more weird spurious stuff, and maybe—maybe—if they're lucky, that outage will be over there at some other region they're not using. I see almost exactly the same promise happening to folks that come from AWS—and in particular from Azure—over onto GCP, which is, there will be probably a higher frequency of outages at a per product level, right? So, like sometimes, like, some weird product takes a screw sideways, where there is structural interdependence between quite a few products—we actually published a whole internal structural map of like, you know, it turns out that Cloud SQL runs on top of GCE not on GKE, so you can expect if GKE goes sideways, Cloud SQL is probably not going to go sideways; the two aren't dependent on each other.Corey: You take the status page and Amazon FreeRTOS in a region is having an outage today or something like that. You're like, “Oh, no. That's terrible. First, let me go look up what the hell that is.” And I'm not using it? Absolutely not. Great. As hyperscalers, well, hyperscale, they're always things that are broken in different ways, in different locations, and if you had a truly accurate status page, it would all be red all the time, or varying shades of red, which is not helpful. So, I understand the challenge there, but very often, it's a partition that is you are not exposed to, or the way that you've architected things, ideally, means it doesn't really matter. And that is a good thing. So, raw outage counts don't solve that. I also maintain that if I were to run in a single region of AWS or even a single AZ, in all likelihood, I will have a significantly better uptime across the board than I would if I ran it myself. Because—Miles: Oh, for sure.Corey: —it is—Miles: For sure they're way better at ops than you are. Me, right?Corey: Of course.Miles: Right? Like, ridiculous.Corey: And they got that way, by learning. Like, I think in 2022, it is unlikely that there's going to be an outage in an AWS availability zone by someone tripping over a power cable, whereas I have actually done that. So, there's a—to be clear in a data center, not an AWS facility; that would not have flown. So, there is the better idea of of going in that direction. But the things like Route 53 is control plane single-tracking through the us-east-1, if you can't make DNS changes in an outage scenario, you may as well not have a DR plan, for most use cases.Miles: To be really clear, it was a part of the internal documentation on the AWS side that we would share with customers to be absolutely explicit with them. It's not just that there are mistakes and accidents which we try to limit to AZs, but no, go further, that we may intentionally cause outages to AZs if that's what allows us to keep broader service health higher, right? They are not just a blast radius because you, oops, pulled the pin on the grenade; they can actually intentionally step on the off button. And that's different than the way Google operates. They think of each of the AZs, and each of the regions, and the global system as an always-on, all the time environment, and they do not have systems where one gets, sort of, sacrificed for the benefit of the rest, right, or they will intentionally plan to take a system offline.There is no planned downtime in the SLA, where the SLAs from my friends at Amazon and Azure are explicit to, if they choose to, they decide to take it offline, they can. Now, that's—I don't know, I kind of want the contract that has the other thing where you don't get that.Corey: I don't know what the right answer is for a lot of these things. I think multi-cloud is dumb. I think that the idea of having this workload that you're going to seamlessly deploy to two providers in case of an outage, well guess what? The orchestration between those two providers is going to cause you more outages than you would take just sticking on one. And in most cases, unless you are able to have complete duplication of not just functionality but capacity between those two, congratulations, you've now just doubled your number of single points of failure, you made the problem actively worse and more expensive. Good job.Miles: I wrote an article about this, and I think it's important to differentiate between dumb and terrifyingly shockingly expensive, right? So, I have a bunch of customers who I would characterize as rich, as like, shockingly rich, as producing businesses that have 80-plus percent gross margins. And for them, the costs associated with this stuff are utterly rational, and they take on that work, and they are seeing benefits, or they wouldn't be doing it.Corey: Of course.Miles: So, I think their trajectory in technology—you know, this is a quote from a Google engineer—it's just like, “Oh, you want to see what the future looks like? Hang out with rich people.” I went into houses when I was a little kid that had whole-home automation. I couldn't afford them; my mom was cleaning house there, but now my house, I can use my phone to turn on the lights. Like—Corey: You know, unless us-east-1 is having a problem.Miles: Hey, and then no Roomba for you, right? Like utterly offline. So—Corey: Roomba has now failed to room.Miles: Conveniently, my lights are Philips Hue, and that's on Google, so that baby works. But it is definitely a spot where the barrier of entry and the level of complexity required is going down over time. And it is definitely a horrible choice for 99% of the companies that are out there right now. But next year, it'll be 98. And the year after that, it'll probably be 97. [laugh].And if I go inside of Amazon's data centers, there's not one manufacturer of hard drives, there's a bunch. So, that got so easy that now, of course you use more than one; you got to do—that's just like, sort of, a natural thing, right? These technologies, it'll move over time. We just aren't there yet for the vast, vast majority of workloads.Corey: I hope that in the future, this stuff becomes easier, but data transfer fees are going to continue to be a concern—Miles: Just—[makes explosion noise]—Corey: Oh, man—Miles: —like, right in the face.Corey: —especially with the Cambrian explosion of data because the data science folks have successfully convinced the entire industry that there's value in those mode balancer logs in 2012. Okay, great. We're never deleting anything again, but now you've got to replicate all of that stuff because no one has a decent handle on lifecycle management and won't for the foreseeable future. Great, to multiple providers so that you can work on these things? Like, that is incredibly expensive.Miles: Yeah. Cool tech, from this announcement at Next that I think is very applicable, and recognized the level of like, utter technical mastery—and security mastery to our earlier conversation—that something like this requires, the product is called BigQuery Omni, what Omni allows you to do is go into the Google Cloud Console, go to BigQuery, say I want to do analysis on this data that's in S3, or in Azure Blob Storage, Google will spin up an account on your behalf on Amazon and Azure, and run the compute there for you, bring the result back. So, just transfer the answers, not the raw data that you just scanned, and no work on your part, no management, no crapola. So, there's like—that's multi-cloud. If I've got—I can do a join between a bunch of rows that are in real BigQuery over on GCP side and rows that are over there in S3. The cross-eyedness of getting something like that to work is mind blowing.Corey: To give this a little more context, just because it gets difficult to reason about these things, I can either have data that is in a private subnet in AWS that traverses their horribly priced Managed NAT Gateways, and then goes out to the internet and sent there once, for the same cost as I could take that same data and store it in S3 in their standard tier for just shy of six full months. That's a little imbalanced, if we're being direct here. And then when you add in things like intelligent tiering and archive access classes, that becomes something that… there's no contest there. It's, if we're talking about things that are now approaching exabyte scale, that's one of those, “Yeah, do you want us to pay by a credit card?”—get serious. You can't at that scale anyway—“Invoice billing, or do we just, like, drive a dump truck full of gold bricks and drop them off in Seattle?”Miles: Sure. Same trajectory, on the multi-cloud thing. So, like a partner of ours, PacketFabric, you know, if you're a big, big company, you go out and you call Amazon and you buy 100 gigabit interconnect on—I think they call theirs Direct Connect, and then you hook that up to the Google one that's called Dedicated Interconnect. And voila, the price goes from twelve cents a gig down to two cents a gig; everybody's much happier. But Jesus, you pay the upfront for that, you got to set the thing up, it takes days to get deployed, and now you're culpable for the whole pipe if you don't use it up. Like, there are charges that are static over the course of the month.So, PacketFabric just buys one of those and lets you rent a slice of it you need. And I think they've got an incredible product. We're working with them on a whole bunch of different projects. But I also expect—like, there's no reason the cloud providers shouldn't be working hard to vend that kind of solution over time. If a hundred gigabit is where it is now, what does it look like when I get to ten gigabit? When I get to one gigabit? When I get to half gigabit? You know, utility price that for us so that we get to rational pricing.I think there's a bunch of baked-in business and cost logic that is a part of the pricing system, where egress is the source of all of the funding at Amazon for internal networking, right? I don't pay anything for the switches that connect to this machine to that machine, in region. It's not like those things are cheap or free; they have to be there. But the funding for that comes from egress. So, I think you're going to end up seeing a different model where you'll maybe have different approaches to egress pricing, but you'll be paying like an in-system networking fee.And I think folks will be surprised at how big that fee likely is because of the cost of the level of networking infrastructure that the providers deploy, right? I mean, like, I don't know, if you've gone and tried to buy a 40 port, 40 gig switch anytime recently. It's not like they're those little, you know, blue Netgear ones for 90 bucks.Corey: Exactly. It becomes this, [sigh] I don't know, I keep thinking that's not the right answer, but part of it also is like, well, you know, for things that I really need local and don't want to worry about if the internet's melting today, I kind of just want to get, like, some kind of Raspberry Pi shoved under my desk for some reason.Miles: Yeah. I think there is a lot where as more and more businesses bet bigger and bigger slices of the farm on this kind of thing, I think it's Jassy's line that you're, you know, the fat in the margin in your business is my opportunity. Like, there's a whole ecosystem of partners and competitors that are hunting all of those opportunities. I think that pressure can only be good for customers.Corey: Miles, thank you for taking the time to speak with me. If people want to learn more about you, what you're up to, your bad opinions, your ridiculous company, et cetera—Miles: [laugh].Corey: —where can they find you?Miles: Well, it's really easy to spell: SADA.com, S-A-D-A dot com. I'm Miles Ward, it's @milesward on Twitter; you don't have to do too hard of a math. It's miles@sada.com, if you want to send me an email. It's real straightforward. So, eager to reach out, happy to help. We've got a bunch of engineers that like helping people move from Amazon to GCP. So, let us know.Corey: Excellent. And we will, of course, put links to this in the [show notes 00:37:17] because that's how we roll.Miles: Yay.Corey: Thanks so much for being so generous with your time, and I look forward to seeing what comes out next year from these various cloud companies.Miles: Oh, I know some of them already, and they're good. Oh, they're super good.Corey: This is why I don't do predictions because like, the stuff that I know about, like, for example, I was I was aware of the Graviton 3 was coming—Miles: Sure.Corey: —and it turns out that if your—guess what's going to come up and you don't name Graviton 3, it's like, “Are you simple? Did you not see that one coming?” It's like—or if I don't know it's coming and I make that guess—which is not the hardest thing in the world—someone would think I knew and leaked. There's no benefit to doing predictions.Miles: No. It's very tough, very happy to do predictions in private, for customers. [laugh].Corey: Absolutely. Thanks again for your time. I appreciate it.Miles: Cheers.Corey: Myles Ward, CTO at SADA. 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 and be very angry in your opinion when you write that obnoxious comment, but then it's going to get lost because it's using MySQL instead of Postgres.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.

Chargers Weekly
The Final Drive: 2021 Season Ends in Las Vegas

Chargers Weekly

Play Episode Listen Later Jan 10, 2022 23:21


Chris Hayre and Hayley Elwood recap the Chargers' 35-32 overtime loss to the Raiders in Week 18. Presented by Windows 11.

The WAN Show Podcast
Why so shy Nvidia? - WAN Show January 7, 2022

The WAN Show Podcast

Play Episode Listen Later Jan 10, 2022 145:58


Save money on your phone plan today at https://www.mintmobile.com/wanshow Try FreshBooks free, for 30 days, no credit card required at https://www.freshbooks.com/wan Visit https://www.squarespace.com/WAN and use offer code WAN for 10% off Check out the WAN Show & Podcast Gear: https://lmg.gg/podcastgear Check out the They're Just Movies Podcast: https://lmg.gg/tjmpodcast Timestamps: (Courtesy of NoKi1119) 0:00 - Chapters 2:29 - Intro 3:04 - Merch messages going wild, WAN Sweatpants 4:52 - Topic #1 - Nvidia's CES 2022 5:15 - RTX 3090 Ti specifications, "Tie" discussion 14:12 - Merch message calling out Linus abbreviating 15:09 - RTX 3050 discussion, impact on budget builds 17:12 - New Floatplane features, new creators 20:11 - Topic #2 - Intel's CES 2022 20:28 - Arc Alchemist, 12th Gen KS & non-K specifications 22:16 - AMD's 5800X3D, heated competition 27:46 - Comparing upgrading CPUs today to the past 32:04 - Topic #3 - BMW's color-changing car 33:38 - E-ink display discussion 37:32 - CES 2022 thoughts 38:59 - Sponsor - Squarespace 39:25 - Sponsor - Mint Mobile 40:48 - Topic #4 - Linus mentions NCIX's carrier plan 42:18 - Sponsor - Freshbooks accounting 43:10 - Jake's experience with mobile carriers 43:47 - Topic #5 - Wi-Fi 6 release 2 45:27 - Summarizing USB & HDMI controversy 50:45 - Merch Messages 51:14 - Educating technology & issues with it 57:57 - VR projects to hope for 58:58 - LMG's video resolution, reason behind downgrading 1:00:40 - LTTStore - Backpack pricing, screwdriver, underwear 1:07:31 - LTTStore - Backpack & waterproof jacket showcase, socks 1:15:15 - LTTStore - Winter stealth bottle 1:16:48 - Halo Infinite on AYA NEO 1:23:10 - LTTStore support ticket overflowing, labs discussion 1:27:41 - Discussing future technology projects 1:30:59 - NCIX's management & cash flow, WAN sweatpants & more LTTStore 1:38:57 - LMG staff highlight video idea, meet the team videos 1:39:46 - Google losing patent case, paying royalty 1:44:52 - Luke's Software Discoveries (LSD), Linux vs Windows install 1:47:41 - LTT's Samsung QD-OLED video, Linus didn't know it's sponsored 2:05:21 - Quick firing Merch Messages 2:25:24 - Outro

mixxio — podcast diario de tecnología
Año nuevo, los problemas de siempre

mixxio — podcast diario de tecnología

Play Episode Listen Later Jan 10, 2022 15:10


Las ferias de tecnología sufren por tercer año / James Webb mejor que mejor / Netflix presiona a las familias falsas / Un mejor Telegram para Windows / Brave duplica usuarios / El CES 2022 sorprende lleno de cosas interesantes Sinceramente no sé si se puede hacer un mejor boletín que este. Feliz año nuevo a todos. Os he echado mucho de menos. Las ferias de tecnología sufren por tercer año / James Webb mejor que mejor / Netflix presiona a las familias falsas / Un mejor Telegram para Windows / Brave duplica usuarios / El CES 2022 sorprende lleno de cosas interesantes

The Engadget Podcast
CES 2022: Everything we loved (and hated)

The Engadget Podcast

Play Episode Listen Later Jan 7, 2022 75:11


It's that time of the year again! Cherlynn and Devindra break down some of the best tech they've seen at CES 2022, as well as a bunch of weird and awful products. Get ready for notebooks with hybrid Intel chips and better NVIDIA graphics! And how about a foldable laptop or two? Our big takeaway: it's going to be an interesting year for Windows laptops. Also, we dive into Razer's crazy gaming table and Samsung's wild, rotating 55-inch gaming monitor. Chipmakers at CES: Intel, AMD, and more – 1:19 Laptopapolooza: Lenovo's Thinkbook Plus Gen 3, Dell's XPS 13 Plus sans headphone jack – 10:40.322 Google announces Fast Pair and Android Auto improvements – 37:51 A couple of phones from CES: Samsung Galaxy S21 FE and OnePlus 10 Pro – 43:11 Standout weird stuff: Samsung's Massive Curved Monitor and Razer's new mask – 45:55 Other News – 1:05:04 Pop Culture Picks – 1:08:59

The CyberWire
Log4j and industrial control systems. Regulators consider the software supply chain. Malsmoke hits an old vulnerability. Social engineering via Google Docs. Call spoofing and robocalls.

The CyberWire

Play Episode Listen Later Jan 6, 2022 30:14


ICS vendors address Log4j vulnerabilities. Regulators and legislators think about addressing issues in the software supply chain. Ransomware gangs were quick to exploit Log4shell. An old, and patched, Windows vulnerability is being exploited by the Malsmoke gang. Social engineering of Google Docs users is up. Mr. Klyshin pleads not guilty. Robert M. Lee from Dragos makes the case for salary transparency. Our guest is George Gerchow from Sumo Logic with new approaches for the modern threat landscape. And call spoofing is making robocalls moderately more plausible. For links to all of today's stories check out our CyberWire daily news briefing: https://thecyberwire.com/newsletters/daily-briefing/11/4

Screaming in the Cloud
An Enterprise Level View of Cloud Architecture with Levi McCormick

Screaming in the Cloud

Play Episode Listen Later Jan 6, 2022 33:52


About LeviLevi's passion lies in helping others learn to cloud better.Links: Jamf: https://www.jamf.com Twitter: https://twitter.com/levi_mccormick 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: It seems like there is a new security breach every day. Are you confident that an old SSH key, or a shared admin account, isn't going to come back and bite you? If not, check out Teleport. Teleport is the easiest, most secure way to access all of your infrastructure. The open-source Teleport Access Plane consolidates everything you need for secure access to your Linux and Windows servers, and I assure you there is no third option there. Kubernetes clusters, databases, and internal applications like AWS Management Console, Yankins, GitLab, Grafana, Jupyter Notebooks, and more. Teleport's unique approach is not only more secure, it also improves developer productivity. To learn more visit: goteleport.com. And not, that is not me telling you to go away, it is: goteleport.com.Corey: This episode is sponsored in part by our friends at Rising Cloud, which I hadn't heard of before, but they're doing something vaguely interesting here. They are using AI, which is usually where my eyes glaze over and I lose attention, but they're using it to help developers be more efficient by reducing repetitive tasks. So, the idea being that you can run stateless things without having to worry about scaling, placement, et cetera, and the rest. They claim significant cost savings, and they're able to wind up taking what you're running as it is in AWS with no changes, and run it inside of their data centers that span multiple regions. I'm somewhat skeptical, but their customers seem to really like them, so that's one of those areas where I really have a hard time being too snarky about it because when you solve a customer's problem and they get out there in public and say, “We're solving a problem,” it's very hard to snark about that. Multus Medical, Construx.ai and Stax have seen significant results by using them. And it's worth exploring. So, if you're looking for a smarter, faster, cheaper alternative to EC2, Lambda, or batch, consider checking them out. Visit risingcloud.com/benefits. That's risingcloud.com/benefits, and be sure to tell them that I said you because watching people wince when you mention my name is one of the guilty pleasures of listening to this podcast.Corey: Welcome to Screaming in the Cloud. I'm Corey Quinn. I am known-slash-renowned-slash-reviled for my creative pronunciations of various technologies, company names, et cetera. Kubernetes, for example, and other things that get people angry on the internet. The nice thing about today's guest is that he works at a company where there is no possible way for me to make it more ridiculous than it sounds because Levi McCormick is a cloud architect at Jamf. I know Jamf sounds like I'm trying to pronounce letters that are designed to be silent, but no, no, it's four letters: J-A-M-F. Jamf. Levi, thanks for joining me.Levi: Thanks for having me. I'm super excited.Corey: Exactly. Also professional advice for anyone listening: Making fun of company names is hilarious; making fun of people's names makes you a jerk. Try and remember that. People sometimes blur that distinction.So, very high level, you're a cloud architect. Now, I remember the days of enterprise architects where their IDEs were basically whiteboards, and it was a whole bunch of people sitting in a room. They call it an ivory tower, but I've been in those rooms; I assure you there is nothing elevated about this. It's usually a dank sub-basement somewhere. What do you do, exactly?Levi: Well, I am part of the enterprise architecture team at Jamf. My roles include looking at our use of cloud; making sure that we're using our resources to the greatest efficacy possible; coordinating between many teams, many products, many architectures; trying to make sure that we're using best practices; bringing them from the teams that develop them and learn them, socializing them to other teams; and just trying to keep a handle on this wild ride that we're on.Corey: So, what I find fun is that Jamf has been around for a long time. I believe it is not your first name. I want to say Casper was originally?Levi: I believe so, yeah.Corey: We're Jamf customers. You're not sponsoring this episode or anything, to the best of my knowledge. So, this is not something I'm trying to shill the company, but we're a customer; we use you to basically ensure that all of our company MacBooks, and laptops, et cetera, et cetera, are basically ensured that there's disk encryption turned on, that people have a password, and that screensaver is turned on, basically to mean that if someone gets their laptop stolen, it's a, “Oh, I have to spend more money with Apple,” and not, “Time to sound the data breach alarm,” for reasons that should be blindingly obvious. And it's great not just at the box check, but also fixing the real problem of I [laugh] don't want to lose data that is sensitive for obvious reasons. I always thought of this is sort of a thing that worked on the laptops. Why do you have a cloud team?Levi: Many reasons. First of all, we started in the business of providing the software that customers would run in their own data centers, in their own locations. Sometime in about 2015, we decided that we are properly equipped to run this better than other people, and we started to provide that as a service. People would move in, migrate their services into the cloud, or we would bring people into the cloud to start with.Device management isn't the only thing that we do. We provide some SSO-type services, we recently acquired a company called Wandera, which does endpoint security and a VPN-like experience for traffic. So, there's a lot of cloud powering all of those things.Corey: Are you able to disclose whether you're focusing mostly on AWS, on Azure, on Google Cloud, or are you pretending a cloud with something like IBM?Levi: All of the above, I believe.Corey: Excellent. That tells you it's a real enterprise, in seriousness. It's the—we talk about the idea of going all in on one providers being a general best practice of good place to start. I believe that. And then there are exceptions, and as companies grow and accumulate technical debt, that also is load-bearing and generates money, you wind up with this weird architectural series of anti-patterns, and when you draw it on a whiteboard of, “Here's our architecture,” the junior consultant comes in and says, “What moron built this?” Usually two said quote-unquote, “Moron,” and then they've just pooched the entire engagement.Yeah, most people don't show up in the morning hoping to do a terrible job today, unless they work at Facebook. So, there are reasons things are the way they are; they're constraints that shape these things. Yeah, if people were going to be able to shut down the company for two years and rebuild everything from scratch from the ground up, it would look wildly different. But you can't do that most of the time.Levi: Yeah. Those things are load bearing, right? You can't just stop traffic one day, and re-architect it with the golden image of what it should have been. We've gone through a series of acquisitions, and those architectures are disparate across the different acquired products. So, you have to be able to leverage lessons from all of them, bring them together and try and just slowly, incrementally march towards a better future state.Corey: As we take a look at the challenges we see The Duckbill Group over on my side of the world, where we talk to customers, it's I think it is surprising to folks to learn that cloud economics as I see it is—well, first, cost and architecture the same thing, which inherently makes sense, but there's a lot more psychology that goes into it than math. People often assume I spend most of my time staring into spreadsheets. I assure you that would not go super well. But it has to do with the psychological elements of what it is that people are wrestling with, of their understanding of the environment has not kept pace with reality, and APIs tend to, you know, tell truths.It's always interesting to me to see the lies that customers tell, not intentionally, but the reality of it of, “Okay, what about those big instances you're running in Australia?” “Oh, we don't have any instances in Australia.” “Look, I understand that you are saying that in good faith, however…” and now we're in a security incident mode and it becomes a whole different story. People's understanding always trails. What do you spend the bulk of your time doing? Is it building things? Is it talking to people? Is it trying to more or less herd cats in certain directions? What's the day-to-day?Levi: I would say it varies week-to-week. Depends on if we have a new product rolling out. I spend a lot of my time looking at architectural diagrams, reference architectures from AWS. The majority of the work I do is in AWS and that's where my expertise lies. I haven't found it financially incentivized to really branch out into any of the other clouds in terms of expertise, but I spend a lot of my time developing solutions, socializing them, getting them in front of teams, and then educating.We have a wide range of skills internally in terms of what people know or what they've been exposed to. I'd say a lot of engineers want to learn the cloud and they want to get opportunities to work on it, and their day-to-day work may not bring them those opportunities as often as they'd like. So, a good portion of my time is spent educating, guiding, joining people's sprints, joining in their stand-ups, and just kind of talking through, like, how they should approach a problem.Corey: Whenever you work at a big company, you invariably wind up with—well, microservices becomes the right answer, not because of the technical reasons; because of the people reason, the way that you get a whole bunch of people moving in roughly the same direction. You are a large scale company; who owns services in your idealized view of the world? Is it, “Well, I wrote something and it's five o'clock. Off to production with it. Talk to you in two days, if everything—if we still have a company left because I didn't double-check what I just wrote.”Do you think that the people who are building services necessarily should be the ones supporting it? Like, in other words, Amazon's approach of having the software engineers being responsible for the ones running it in production from an ops perspective. Is that the direction you trend towards, or do you tend to be from my side of the world—which is grumpy sysadmin—where people—developers hurl applications into your yard for you to worry about?Levi: I would say, I'm an extremist in the view of supporting the Amazon perspective. I really like you build it, you run it, you own it, you architect it, all of it. I think the other teams in the organization should exist to support and enable those paths. So, if you have platform teams are a really common thing you see hired right now, I think those platforms should be built to enable the company's perspective on operating infrastructure or services, and then those service teams on top of that should be enabled to—and empowered to make the decisions on how they want to build a service, how they want to provide it. Ultimately, the buck should stop with them.You can get into other operational teams, you could have a systems operation team, but I think there should be an explicit contract between a service team, what they build, and what they hand off, you know, you could hand off, like, a tier one level response, you know, you can do playbooks, you could do, you know, minimal alert, response, routing, that kind of stuff with a team, but I think that even that team should have a really strong contract with, like, here's what our team provides, here's how you engage with our team, here's how you will transition services to our team.Corey: The challenge with doing that, in some shops, has been that if you decide to roll out a, you build it, you own it, approach that has not been there since the beginning, you wind up with a lot of pushback from engineers who until now really enjoyed their 5:30 p.m. quitting time, or whenever it was they wound up knocking off work. And they started pushing back, like, “Working out of hours? That's inhumane.” And the DevOps team would be sitting there going, “We're right here. How dare you? Like, what do you think our job is?” And it's a, “Yes, but you're not people.” And then it leads to this whole back and forth acrimonious—we'll charitably call it a debate. How do you drive that philosophy?Levi: It's a challenge. I've seen many teams fracture, fall apart, disperse, if you will, under the transition of going through, like, an extreme service ownership. I think you balance it out with the carrot of you also get to determine your own future, right? You get to determine the programming language you use, you get to determine the underlying technologies that you use. Again, there's a contract: You have to meet this list of security concerns, you need to meet these operational concerns, and how you do that is up to you.Corey: When you take a look across various teams—let's bound this to the industry because I don't necessarily want you to wind up answering tough questions at work the day this episode airs—what do you see the biggest blockers to achieving, I guess, a functional cultural service ownership?Levi: It comes down to people's identity. They've established their own identity, “As I am X,” right? I'm a operations engineer. I'm a developer, I'm an engineer. And getting people to kind of branch out of that really fixed mindset is hard, and that, to me, is the major blocker to people assuming ownership.I've seen people make the transition from, “I'm just an engineer. I just want to write code.” I hate those lines. That frustrates me so much: “I just want to write code.” Transitioning into that, like, ownership of, “I had an idea. I built the platform or the service. It's a huge hit.” Or you know, “Lots of people are using it.” Like, seeing people go through that transformation become empowered, become fulfilled, I think is great.Corey: I didn't really expect to get called out quite like this, but you're absolutely right. I was against the idea, back when I was a sysadmin type because I didn't know how to code. And if you have developers supporting all of the stuff that they've built, then what does that mean for me? It feels like my job is evaporating. I don't know how to write code.Well, then I started learning how to write code incredibly badly. And then wow, it turns out, everyone does this. And here we are. But it's—I don't build applications, for obvious reasons. I'm bad at it, but I found another way to proceed in the wide world that we live in of high technology.But yeah, it was hard because this idea of my sense of identity being tied to the thing that I did, it really was an evolve-or-die dinosaur kind of moment because I started seeing this philosophy across the board. You take a look, even now at modern SRE is, or modern DevOps folks, or modern sysadmins, what they're doing looks a lot less like logging into Linux systems and tinkering on the command line a lot more like running and building distributed applications. Sure, this application that you're rolling out is the one that orchestrates everything there, but you're still running this in the same way the software engineers do, which is, interestingly.Levi: And that doesn't mean a team has to be only software engineers. Your service team can be multiple disciplines. It should be multiple disciplines. I've seen a traditional ops team broken apart, and those individuals distributed into the services that they were chiefly skilled in supporting in the past, as the ops team, as we transitioned those roles from one of the worst on-call rotations I've ever seen—you know, 13 to 14 alerts a night—transitioning those out to those service teams, training them up on the operations, building the playbooks. That was their role. Their role wasn't necessarily to write software, day one.Corey: I quit a job after six weeks because of that style of, I guess, mismanagement. Their approach was that, oh, we're going to have our monitoring system live in AWS because one of our VPs really likes AWS—let's be clear, this was 2008, 2009 era—latency was a little challenging there. And [unintelligible 00:17:04] he really liked Big Brother, which was—not to—now before that became a TV show and at rest, it was a monitoring system—but network latency was always a weird thing in AWS in those days, so instead, he insisted we set up three of them. And whenever—if we just got one page, it was fine. But if we got three, then we had to jump in. And two was always undefined.And they turned this off from I think, 10 p.m. to 6 a.m. every night, just so the person I call could sleep. And I'm looking at this, like, this might be the worst thing I've ever seen in my life. This was before they released the Managed NAT Gateway, so possibly it was.Levi: And then the flood, right, when you would get—Corey: Oh, God this was the days, too—Levi: Yeah.Corey: —when you were—if you weren't careful, you'd set this up to page you on the phone with a text message and great, now it takes time for my cell provider to wind up funneling out the sudden onslaught of 4000 text messages. No thanks.Levi: If your monitoring system doesn't have the ability to say, you know, the alert flood, funnel them into one alert, or just pause all alerts, while—because we know there's an incident; you know, us-east-1 is down, right? We know this; we don't need to get 500 text messages to each engineer that's on call.Corey: Well, my philosophy at that point was no, I'm going to instead take a step beyond. If I'm not empowered to fix this thing that is waking me up—and sometimes that's the monitoring system, and sometimes it's the underlying application—I'm not on call.Levi: Yes, exactly. And that's why I like the model of extre—you know, the service ownership: Because those alerts should go to the people—the pain should be felt by the people who are empowered to fix it. It should not land anywhere else. Otherwise, that creates misaligned incentives and nothing gets better.Corey: Yeah. But in large distributed systems, very often the person is on call more or less turns into a traffic router.Levi: Right. That's unfair to them.Corey: That's never fun—yeah, that's unfair, and it's not fun, either, and there's no great answer when you've all these different contributory factors.Levi: And how hard is it to keep the team staffed up?Corey: Oh, yeah. It's a, “Hey, you want a really miserable job one week out of every however many there are in the cycle?” Eh, people don't like that.Levi: Exactly.Corey: This episode is sponsored by our friends at Oracle HeatWave, 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 world's most popular open source database, shifting from transacting to analytics required way too much overhead and, you know, work. With HeatWave you can run your OLAP and OLTP—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: So, I've been tracking what you're up to for little while now—you're always a blast to talk with—what is this whole Cloud Builder thing that you were talking about for a bit, and then I haven't seen much about it.Levi: Ah, so at the beginning of the pandemic, our mutual friend, Forrest Brazeal, released the Cloud Resume Challenge. I looked at that, and I thought, this is a fantastic idea. I've seen lots of people going through it. I recommend the people I mentor go through it. Great way to pick up a couple cloud skills here and there, tell an interesting story in an interview, right? It's a great prep.I intended the Cloud Builder Challenge to be a natural kind of progression from that Resume Challenge to the Builder Challenge where you get operational experience. Again, back to that, kind of, extreme service ownership mentality, here's a project where you can build, really modeled on the Amazon GameDays from re:Invent, you build a service, we'll send you traffic, you process those payloads, do some matching, some sorting, some really light processing on these payloads, and then send it back to us, score some points, we'll build a public dashboard, people can high five each other, they can razz each other, kind of competition they want to do. Really low, low pressure, but just a fun way to get more operational experience in an area where there is really no downside. You know, playing like that at work, bad idea, right?Corey: Generally, yes. [crosstalk 00:21:28] production, we used to have one of those environments; oops-a-doozy.Levi: Yeah. I don't see enough opportunities for people to gain that experience in a way that reflects a real workload. You can go out and you can find all kinds of Hello Worlds, you can find all kinds of—like, for front end development, there are tons of activity activities and things you can do to learn the skills, but for the middleware, the back end engineers, there's just not enough playgrounds out there. Now, standing up a Hello World app, you know, you've got your infrastructures code template, you've got your pre-written code, you deploy it, congratulations. But now what, right?And I intended this challenge to be kind of a series of increasingly more difficult waves, if you will, or levels. I really had a whole gamification aspect to it. So, it would get harder, it would get bigger, more traffic, you know, all of those things, to really put people through what it would be like to receive your, “Post got slash-dotted today,” or those kinds of things where people don't get an opportunity to deal with large amounts of traffic, or variable payloads, that kind of stuff.Corey: I love the idea. Where is it?Levi: It is sitting in a bunch of repos, and I am afraid to deploy it. [laugh].Corey: What is it that scares you about it specifically?Levi: The thing that specifically scares me is encouraging early career developers to go out there, deploy this thing, start playing with it, and then incur a huge cloud bill.Corey: Because they failed to secure something or other reasons behind that?Levi: There are many ways that this could happen, yeah. You could accidentally push your access key, secret key up into a public repo. Now, you've got, you know, Bitcoin miners or Monero miners running in your environment. You forget to shut things off, right? That's a really common thing.I went through a SageMaker demo from AWS a couple years ago. Half the room of intelligent, skilled engineers forgot to shut off the SageMaker instances. And everybody ran out of the $25 of credit they had from the demo—Corey: In about ten minutes. Yeah.Levi: In about ten minutes, yeah. And we had to issue all kinds of requests for credits and back and forth. But granted, AWS was accommodating to all of those people, but it was still a lot of stress.Corey: But it was also slow. They're very slow on that, which is fair. Like, if someone's production environment is down, I can see why you care more about that than you do about someone with, “Ah, I did something wrong and lost money.” The counterpoint to that is that for early career folks, that money is everything. We remember earlier this year, that tragic story from the Robinhood customer who committed suicide after getting a notification that he was $730,000 in debt. Turns out it wasn't even accurate; he didn't owe anything when all was said and done.I can see a scenario in which that happens in the AWS world because of their lack of firm price controls on a free tier account. I don't know what the answer on this is. I'm even okay with a, “Cool you will—this is a special kind of account that we will turn you off at above certain levels.” Fine. Even if you hard cap at the 20 or 50 bucks, yeah, it's going to annoy some people, but no one is going to do something truly tragic over that. And I can't believe that Oracle Cloud of all companies is the best shining example of this because you have to affirmatively upgrade your account before they'll charge you a dime. It's the right answer.Levi: It is. And I don't know if you've ever looked at—well, I'm sure you'd have. You've probably looked at the solutions provided by AWS for monitoring costs in your accounts, preventing additional spend. Like, the automation to shut things down, right, it's oftentimes more engineering work to make it so that your systems will shut down automatically when you reach a certain billing threshold than the actual applications that are in place there.Corey: And I don't for the life of me understand why things are the way that they are. But here we go. It's a—[sigh] it just becomes this perpetual strange world. I wish things were better than they are, but they're not.Levi: It makes me terribly sad. I mean, I think AWS is an incredible product, I think the ecosystem is great, and the community is phenomenal; everyone is super supportive, and it makes me really sad to be hesitant to recommend people dive into it on their own dime.Corey: Yeah. And that is a—[sigh] I don't know how you fix that or square that circle. Because I don't want to wind up, I really do not want to wind up, I guess, having to give people all these caveats, and then someone posts about a big bill problem on the internet, and all the comments are, “Oh, you should have set up budgets on that.” Yeah, that's thing still a day behind. So okay, great, instead of having an enormous bill at the end of the month, you just have a really big one two days later.I don't think that's the right answer. I really don't. And I don't know how to fix this, but, you know, I'm not the one here who's a $1.7 trillion company, either, that can probably find a way to fix this. I assure you, the bulk of that money is not coming from a bunch of small accounts that forgot to turn something off or got exploited.Levi: I haven't done my 2021 taxes yet, but I'm pretty sure I'm not there either.Corey: The world in which we live.Levi: [laugh]. I would love this challenge. I would love to put it out there. If I could, on behalf of, you know, early career people who want to learn—if I could issue credits, if I could spin up sandboxes and say, like, “Here's an account, I know you're going to be safe. I have put in a $50 limit.” Right?Corey: Yeah.Levi: “You can't spend more than $50,” like, if I had that control or that power, I would do this in a heartbeat. I'm passionate about getting people these opportunities to play, you know, especially if it's fun, right? If we can make this thing enjoyable, if we can gamify it, we can play around, I think that'd be great. The experience, though, would be a significant amount of engineering on my side, and then a huge amount of outreach, and that to me makes me really sad.Corey: I would love to be able to do something like that myself with a, “Look, if you get a bill, they will waive it, or I will cover it.” But then you wind up with the whole problem of people not operating in good faith as well. Like, “All right, I'm going to mine a bunch of Bitcoin and claim someone else did it.” Or whatnot. And it's just… like, there are problems with doing this, and the whole structure doesn't lend itself to that working super well.Levi: Exactly. I often say, you know, I face a lot of people who want to talk about mining cryptocurrency in the cloud because I'm a cloud architect, right? That's a really common conversation I have with people. And I remind them, like, it's not economical unless you're not paying for it.Corey: Yeah, it's perfectly economical on someone else's account.Levi: Exactly.Corey: I don't know why people do things the way that they do, but here we are. So, re:Invent. What did you find that was interesting, promising there, promising but not there yet, et cetera? What was your takeaway from it? Since you had the good sense not to be there in person?Levi: [laugh]. To me, the biggest letdown was Amplify Studio.Corey: I thought it was just me. Thank you. I just assumed it was something I wasn't getting from the explanation that they gave. Because what I heard was, “You can drag and drop, basically, a front end web app together and then tie it together with APIs on the back end.” Which is exactly what I want, like Retool does; that's what I want only I want it to be native. I don't think it's that.Levi: Right. I want the experience I already have of operating the cloud, knowing the security posture, knowing the way that my users access it, knowing that it's backed by Amazon, and all of their progressively improving services, right? You say it all the time. Your service running on Amazon is better today than it was two years ago. It was better than it was five years ago. I want that experience. But I don't think Amplify Studio delivered.Corey: I wish it had. And maybe it will, in the fullness of time. Again, AWS services do not get worse as they age they get better.Levi: Some gets stale, though.Corey: Yeah. The worst case scenario is they sit there and don't ever improve.Levi: Right. I thought the releases from S3 in terms of, like, the intelligent tiering, were phenomenal. I would love to see everybody turn on intelligent tiering with instant access. Those things to me were showing me that they're thinking about the problem the right way. I think we're missing a story of, like, how do we go from where we're at today—you know, if I've got trillions of objects in storage, how do I transition into that new world where I get the tiering automatically? I'm sure we'll see blog posts about people telling us; that's what the community is great for.Corey: Yeah, they explain these things in a way that the official docs for some reason fail to.Levi: Right. And why don't—Corey: Then again, it's also—I think—I think it's because the people that are building these things are too close to the thing themselves. They don't know what it's like to look at it through fresh eyes.Levi: Exactly. They're often starting from a blank slate, or from a greenfield perspective. There's not enough thought—or maybe there's a lot of thought to it, but there's not enough communication coming out of Amazon, like, here's how you transition. We saw that with Control Tower, we saw that with some of the releases around API Gateway. There's no story for transitioning from existing services to these new offerings. And I would love to see—and maybe Amazon needs a re:Invent Echo, where it's like, okay, here's all the new releases from re:Invent and here's how you apply them to existing infrastructure, existing environments.Corey: So, what's next for you? What are you looking at that's exciting and fun, and something that you want to spend your time chasing?Levi: I spend a lot of my time following AWS releases, looking at the new things coming out. I spend a lot of energy thinking about how do we bring new engineers into the space. I've worked with a lot of operations teams—those people who run playbooks, they hop on machines, they do the old sysadmin work, right—I want to bring those people into the modern world of cloud. I want them to have the skills, the empowerment to know what's available in terms of services and in terms of capabilities, and then start to ask, “Why are we not doing it that way?” Or start looking at making plans for how do we get there.Corey: Levi, I really want to thank you for taking the time to speak with me. If people want to learn more. Where can they find you?Levi: I'm on Twitter. My Twitter handle is @levi_mccormick. Reach out, I'm always willing to help people. I mentor people, I guide people, so if you reach out, I will respond. That's a passion of mine, and I truly love it.Corey: And we'll of course, include a link to that in the [show notes 00:32:28]. Thank you so much for being so generous with your time. I appreciate it.Levi: Thanks, Corey. It's been awesome.Corey: Levi McCormick, cloud architect at Jamf. 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, along with a comment telling me that service ownership is overrated because you are the storage person, and by God, you will die as that storage person, potentially in poverty.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.

Airing the Addisons
Pray In Front of Your Windows!

Airing the Addisons

Play Episode Listen Later Jan 6, 2022 48:07


Windows Weekly (MP3)
WW 758: An Encyclopedia of Chipsets - Azure vs. AWS, Ryzen 6000, Android on Windows

Windows Weekly (MP3)

Play Episode Listen Later Jan 5, 2022 146:28


Azure vs. AWS, Ryzen 6000, Android on Windows CES 2022: Better together with Android and beyond AMD Unveils Its Ryzen 6000 Series Mobile Processors 12th-Generation Intel Core Chipsets Come to Mobile PCs CES 2022: Microsoft, Qualcomm to collaborate on custom augmented-reality chips Intel says foldable screen laptop PCs are coming to market in 2022 | Windows Central Acer Announces the Aspire Vero National Geographic Edition CES 2022: ASUS refreshes its gaming lineup and introduces new form factors, CPUs and GPUs | Windows Experience Blog Dell Announces XPS 13 Plus HP Announces New Dragonfly, Many More Portable and Desktop PCs CES 2022: Lenovo ushers in new looks and approaches for hybrid work, gaming and everything else | Windows Experience Blog First Microsoft Pluton-powered Windows 11 PCs to start rolling out this year Samsung Launches the Galaxy S21 FE at $699 OnePlus Previews the OnePlus 10 Pro Where is the December Update for the Pixel 6 Series? Google Finally Addresses the December 2021 Update for Pixel 6/6 Pro Google Delivers January Update for Pixel, But Not for Pixel 6 Series I'm Switching to the iPhone More Microsoft Report: Microsoft Cloud Still Half the Size of AWS Microsoft issues emergency fix for Exchange Server date-check bug Windows Developer Team Tweets a Programming Mistake Apple is First Company to Hit $3 Trillion Valuation Xbox Microsoft Reveals Games with Gold for January Microsoft Announces First Xbox Game Pass Titles for January Rainbow Six Extraction Coming to Xbox Game Pass on Day One Sony Announces VR2 and VR2 Sense Controller for PlayStation 5 Samsung Gaming Hub to Bring Stadia, More to Samsung TVs Tips and Picks Tip of the week: Understand the history of Windows via software development App and Codename pick of the week: Project Monarch (One Outlook) Enterprise pick of the week: Out of band Win Server and Win 10 Enterprise updates Beer pick of the week: Salted Caramel Barrel Aged Framinghammer 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.

All TWiT.tv Shows (MP3)
Windows Weekly 758: An Encyclopedia of Chipsets

All TWiT.tv Shows (MP3)

Play Episode Listen Later Jan 5, 2022 146:28


Azure vs. AWS, Ryzen 6000, Android on Windows CES 2022: Better together with Android and beyond AMD Unveils Its Ryzen 6000 Series Mobile Processors 12th-Generation Intel Core Chipsets Come to Mobile PCs CES 2022: Microsoft, Qualcomm to collaborate on custom augmented-reality chips Intel says foldable screen laptop PCs are coming to market in 2022 | Windows Central Acer Announces the Aspire Vero National Geographic Edition CES 2022: ASUS refreshes its gaming lineup and introduces new form factors, CPUs and GPUs | Windows Experience Blog Dell Announces XPS 13 Plus HP Announces New Dragonfly, Many More Portable and Desktop PCs CES 2022: Lenovo ushers in new looks and approaches for hybrid work, gaming and everything else | Windows Experience Blog First Microsoft Pluton-powered Windows 11 PCs to start rolling out this year Samsung Launches the Galaxy S21 FE at $699 OnePlus Previews the OnePlus 10 Pro Where is the December Update for the Pixel 6 Series? Google Finally Addresses the December 2021 Update for Pixel 6/6 Pro Google Delivers January Update for Pixel, But Not for Pixel 6 Series I'm Switching to the iPhone More Microsoft Report: Microsoft Cloud Still Half the Size of AWS Microsoft issues emergency fix for Exchange Server date-check bug Windows Developer Team Tweets a Programming Mistake Apple is First Company to Hit $3 Trillion Valuation Xbox Microsoft Reveals Games with Gold for January Microsoft Announces First Xbox Game Pass Titles for January Rainbow Six Extraction Coming to Xbox Game Pass on Day One Sony Announces VR2 and VR2 Sense Controller for PlayStation 5 Samsung Gaming Hub to Bring Stadia, More to Samsung TVs Tips and Picks Tip of the week: Understand the history of Windows via software development App and Codename pick of the week: Project Monarch (One Outlook) Enterprise pick of the week: Out of band Win Server and Win 10 Enterprise updates Beer pick of the week: Salted Caramel Barrel Aged Framinghammer 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.

Radio Leo (Audio)
Windows Weekly 758: An Encyclopedia of Chipsets

Radio Leo (Audio)

Play Episode Listen Later Jan 5, 2022 146:28


Azure vs. AWS, Ryzen 6000, Android on Windows CES 2022: Better together with Android and beyond AMD Unveils Its Ryzen 6000 Series Mobile Processors 12th-Generation Intel Core Chipsets Come to Mobile PCs CES 2022: Microsoft, Qualcomm to collaborate on custom augmented-reality chips Intel says foldable screen laptop PCs are coming to market in 2022 | Windows Central Acer Announces the Aspire Vero National Geographic Edition CES 2022: ASUS refreshes its gaming lineup and introduces new form factors, CPUs and GPUs | Windows Experience Blog Dell Announces XPS 13 Plus HP Announces New Dragonfly, Many More Portable and Desktop PCs CES 2022: Lenovo ushers in new looks and approaches for hybrid work, gaming and everything else | Windows Experience Blog First Microsoft Pluton-powered Windows 11 PCs to start rolling out this year Samsung Launches the Galaxy S21 FE at $699 OnePlus Previews the OnePlus 10 Pro Where is the December Update for the Pixel 6 Series? Google Finally Addresses the December 2021 Update for Pixel 6/6 Pro Google Delivers January Update for Pixel, But Not for Pixel 6 Series I'm Switching to the iPhone More Microsoft Report: Microsoft Cloud Still Half the Size of AWS Microsoft issues emergency fix for Exchange Server date-check bug Windows Developer Team Tweets a Programming Mistake Apple is First Company to Hit $3 Trillion Valuation Xbox Microsoft Reveals Games with Gold for January Microsoft Announces First Xbox Game Pass Titles for January Rainbow Six Extraction Coming to Xbox Game Pass on Day One Sony Announces VR2 and VR2 Sense Controller for PlayStation 5 Samsung Gaming Hub to Bring Stadia, More to Samsung TVs Tips and Picks Tip of the week: Understand the history of Windows via software development App and Codename pick of the week: Project Monarch (One Outlook) Enterprise pick of the week: Out of band Win Server and Win 10 Enterprise updates Beer pick of the week: Salted Caramel Barrel Aged Framinghammer 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.

Broken Silicon
134. RTX 3090 Ti, 5GHz ZEN 4, 5.5GHz i9-12900KS, AMD Rembrandt, PlayStation VR2

Broken Silicon

Play Episode Listen Later Jan 5, 2022 120:49


Nvidia, AMD, & Intel just had their CES Keynotes! We discuss everything announced, & DG3 Battlemage. [SPON: brokensilicon = -30% off Windows, dieshrink = -3% off Everything: https://biitt.ly/shbSk] [SPON: Get 10% off Tasty Vite Ramen with Code “brokensilicon” at: https://bit.ly/3oyv4tR] 0:00 CryEngine vs Dunia Engine (Intro Banter & Corrections) 6:24 Nvidia's Low End RTX 2050, MX550, and MX570 16:23 RTX 3090 Ti, RTX 3050 8GB, RTX 3080 Ti & 3070 Ti Laptop 22:22 RTX 3050 8GB Expected Performance 32:00 Can Nvidia save their laptop market share? 34:45 RX 6500 XT 4GB – What do MLID sources say about availability & performance? 46:11 Intel A380 vs 6500 XT vs RTX 3050 Performance 49:00 AMD 6nm Zen 3+ Rembrandt APU Revealed 58:38 R7 5800X3D & 5GHz ZEN 4 Revealed! 1:04:17 Intel i9-12900KS at 5.5GHz – Why the 5950X3D wouldn't be competitive… 1:10:35 Will there be more ZEN 4 CPUs with Vcache? 1:12:25 Is Intel ARC actually coming out in Q1? What do we think of ADL Mobile? 1:20:20 Did Jensen brag about getting a date? Tie or Ti? Were we disappointed by CES? 1:31:56 Intel DG3 Battlemage Leaked - Intel goes for the GPU crown in 2023! 1:39:53 New Intel Stock Cooler, i7-12700, PlayStation VR2 (Wrap Up) 1:45:39 VR Resolutions, Steam Deck Delay, AMD at SAMSUNG, NFTs in Games (Final Reader Mails) https://www.techpowerup.com/290011/nvidia-announces-three-new-mobile-gpus-with-spring-2022-availability https://videocardz.com/newz/nvidia-geforce-rtx-2050-and-mx500-laptop-gpus-tested-in-3dmark-timespy https://www.nvidia.com/en-us/geforce/news/geforce-rtx-laptop-new-options/ https://www.nvidia.com/en-us/geforce/gaming-laptops/compare-20-series/ https://youtu.be/_rzxrKfNJWQ MLID CES Analysis Video: https://youtu.be/S2J2eabcUGM https://www.notebookcheck.net/AMD-Radeon-RX-Vega-8-Ryzen-5000-GPU-Benchmarks-and-Specs.539159.0.html https://www.techpowerup.com/gpu-specs/geforce-gtx-1650.c3366 https://youtu.be/_jX-hKvUQDU https://youtu.be/6KoscQVKpAQ https://twitter.com/mooreslawisdead/status/1478392722796994560 https://www.intel.com/content/www/us/en/events/intel-ces.html https://www.techspot.com/review/2351-intel-core-i9-12900k/ https://www.tweaktown.com/news/83197/gpu-shipments-are-up-25-over-last-year-what-shortages/index.html https://www.anandtech.com/show/17158/amd-mobile-gpu-2022-update-radeon-6000s-series-6x50m-parts-and-navi-24based-6500m-and-6300m https://videocardz.com/newz/nvidia-announces-geforce-rtx-3090ti-flagship-and-rtx-3050-entry-level-desktop-gpus MLID 3090 Ti and Navi 24 Leak from October: https://youtu.be/bCitvluqTlA https://www.tomshardware.com/news/nvidia-rtx-3050-ti-and-rtx-3050-bring-rt-and-dlss-to-budget-laptops https://www.techpowerup.com/gpu-specs/geforce-rtx-3070.c3674 https://youtu.be/7AQAkErpRFg https://static.techspot.com/articles-info/2378/bench/18.png https://youtu.be/thyG8T-id8I https://www.notebookcheck.net/NVIDIA-GeForce-RTX-3070-Ti-Laptop-GPU-GPU-Benchmarks-and-Specs.588958.0.html https://www.notebookcheck.net/AMD-Radeon-RX-6700M-GPU-Benchmarks-and-Specs.515472.0.html https://www.notebookcheck.net/AMD-Radeon-RX-6000-mobile-specifications-leak-from-the-RX-6300M-to-the-RX-6850M-XT.589841.0.html https://linustechtips.com/topic/200108-news-nvidia-employee-confirms-that-ti-is-pronounced-tye/page/2/?fbclid=IwAR2L3NhI_p-FLGHRhv-VgzeJnr_34EIMoF_1BFkG6PUDxKnLRAU9a37SAn4

Screaming in the Cloud
Fear and Loathing on the re:Invent Show Floor of ‘21 with Aaron Booth

Screaming in the Cloud

Play Episode Listen Later Jan 5, 2022 33:30


About AaronI am a Cloud Focused Product Management and Technical Product Ownership Consultant. I have worked on several Cloud Products & Services including resale, management & governance, cost optimisation, platform management, SaaS, PaaS. I am also recognised as a AWS Community Builder due to my work building cloud communities cross-government in the UK over the last 3 years. I have extensive commercial experience dealing with Cloud Service Providers including AWS, Azure, GCP & UKCloud. I was the Single Point of Contact for Cloud at the UK Home Office and was the business representative for the Home Office's £120m contract with AWS. I have been involved in contract negotiation, supplier relationship management & financial planning such as business cases & cost management.I run a IT Consultancy called Embue, specialising in Agile, Cloud & DevOps consulting, coaching and training. Links: Twitter: https://twitter.com/AaronBoothUK LinkedIn: https://www.linkedin.com/in/aaronboothuk/ Embue: https://embue.co.uk Publicgood.cloud: https://publicgood.cloud 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: It seems like there is a new security breach every day. Are you confident that an old SSH key, or a shared admin account, isn't going to come back and bite you? If not, check out Teleport. Teleport is the easiest, most secure way to access all of your infrastructure. The open-source Teleport Access Plane consolidates everything you need for secure access to your Linux and Windows servers, and I assure you there is no third option there. Kubernetes clusters, databases, and internal applications like AWS Management Console, Yankins, GitLab, Grafana, Jupyter Notebooks, and more. Teleport's unique approach is not only more secure, it also improves developer productivity. To learn more visit: goteleport.com. And not, that is not me telling you to go away, it is: goteleport.com.Corey: This episode is sponsored in part by our friends at Rising Cloud, which I hadn't heard of before, but they're doing something vaguely interesting here. They are using AI, which is usually where my eyes glaze over and I lose attention, but they're using it to help developers be more efficient by reducing repetitive tasks. So, the idea being that you can run stateless things without having to worry about scaling, placement, et cetera, and the rest. They claim significant cost savings, and they're able to wind up taking what you're running as it is in AWS with no changes, and run it inside of their data centers that span multiple regions. I'm somewhat skeptical, but their customers seem to really like them, so that's one of those areas where I really have a hard time being too snarky about it because when you solve a customer's problem and they get out there in public and say, “We're solving a problem,” it's very hard to snark about that. Multus Medical, Construx.ai and Stax have seen significant results by using them. And it's worth exploring. So, if you're looking for a smarter, faster, cheaper alternative to EC2, Lambda, or batch, consider checking them out. Visit risingcloud.com/benefits. That's risingcloud.com/benefits, and be sure to tell them that I said you because watching people wince when you mention my name is one of the guilty pleasures of listening to this podcast.Corey: Welcome to Screaming in the Cloud. I'm Corey Quinn. So, when I went to re:Invent last year, I discovered a whole bunch of things I honestly was a little surprised to discover. One of those things is my guest today, Aaron Booth, who's a cloud consultant with an emphasis on sustainability. Now, you see a number of consultants at things like re:Invent, but what made Aaron interesting was that this was apparently his first time visiting the United States, and he started with not just Las Vegas, but Las Vegas to attend re:Invent. Aaron, thank you for joining me, and honestly, I'm a little surprised you survived.Aaron: Yeah, I think one of the things about going to Las Vegas or Nevada is no one really prepared me for how dry it was. I ended up walking out of re:Invent with my fingers, like, bleeding, and everything else. And there was so much about America that I didn't expect, but that was one thing I wish somebody had warned me about. But yeah, it was my first time in the US, first time at re:Invent, and I really enjoyed it. It was probably the best investment in myself and my business that I think I've done so far.Corey: It's always strange to look at a place that you live and realize, oh, yeah, this is far away for someone else. What would their experience be of coming and learning about the culture we have here? And then you go to Las Vegas, and it's easy to forget there are people who live there. And even the people who live there do not live on the strip, in the casinos, at loud, obnoxious cloud conferences. So, it feels like it's one of those ideas of oh, I'm going to go to a movie for the first time and then watching something surreal, like Memento or whatnot, that leaves everyone very confused. Like, “Is this what movies are like?” “Well, this one, but no others are quite like that.” And I feel that way about Las Vegas and re:Invent, simultaneously.Aaron: I mean, talking about movies, before it came to the US and before I came to Vegas, I was like, “Oh, how can I prepare myself for this trip?” I ended up watching Fear and Loathing in Las Vegas. And I don't know if you ever seen it, with Johnny Depp, but it's probably not the best representation, or the most modern representation what Vegas would be like. And I think halfway through the conference, went down to Fremont Street in the old downtown. And they have this massive, kind of, free block screen in the sky that is lit up and doing all these animations. And you're just thinking, “What world am I on?” And it kind of is interesting as well, from a point of view of, we're at this tech conference; it's in Vegas; what is the reason for that? And there's obviously lots of different things. We want people to have fun, but you know, it is an interesting place to put 30,000 people, especially during a pandemic.Corey: It really is. I imagine it's going to have to stay there because in a couple more years, you're going to need a three block long screen just to list all of the various services that AWS offers because they don't believe in turning anything off. Now, it would be remiss for me not to ask you, what was announced at re:Invent that got you the most, let's call it excited, I guess? What got you enthusiastic? What are you happy to start working with more?Aaron: I think from my perspective, there's a few different announcements. The first one that comes to mind is the stuff of AWS Amplify Studio, and that's taken this, kind of, no-code Figma designs and turn into a working front end. And it's really interesting for me to think about, okay, what is the point of cloud? Why are we moving forward in the world, especially in technology? And, you know, abstracting a lot of stuff we worry about today to simple drag-and-drop tools is probably going to be the next big thing for most of the world.You know, we've come from a privileged position in the West where we follow technology along the whole of the journey, where now we have an opportunity to open this out to many more regions, and many more AWS customers, for example. But for me, as a small business owner—I've run multiple businesses—there's a lot of effort you put into, okay, I need to set up a business, and a website, and newsletter, or whatever else. But the more you can just turn that into, “I've got an idea, and I can give it to people with one click,” you'll enable a lot more business and a lot more future customers as well.Corey: I was very excited about that one, too, just from a perspective of I want to drag and drop something together to make a fairly crappy web app, that sounds like the thing that I could use to do that. No, that feels a lot more like what Honeycode is trying to be, as opposed to the Amplify side of the world, which is still very focused on React. Which, okay, that makes sense. There's a lot of front end developers out there, and if you're trying to get into tech today and are asking what language should I learn, I would be very hard-pressed to advise you pick anything that isn't JavaScript because it is front end, it is back end, it runs slash eats the world. And I've just never understood it. It does not work the way that I think about computers because I'm old and grumpy. I have high hopes of where it might go, but so far I'm looking at it's [sigh] it's not what I want it to be, yet. And maybe that's just because I'm weird.Aaron: Well, I mean, you know, you mentioned part of the problem really is two different competing AWS services themselves, which with a business like AWS and their product strategy being the word, “Yes,” you know, you're never really going to get a lot of focus or forward direction with certain products. And hopefully, there'll be the next, no-code tool announced in re:Invent in a few years' time, which is exactly what we're looking for, and gives startup founders or small businesses drag-and-drop tools. But for now, there's going to be a lot of competing services.Corey: There's so much out there that it's almost impossible to wind up contextualizing re:Invent as a single event. It feels like it's too easy to step back and say, “Oh, okay. I'm here to build websites”—is what we're talking about now in the context of Amplify—and then they start talking about mainframes. And then they start talking about RoboRunner to control 10,000 robots at once. And I'm looking around going, “I don't have problems that feel a lot like that. What's the deal?”Aaron: I think even just, like you said in perspective of re:Invent is like, when you go to an event like this, that you can't experience everything and you probably have a very specific focus of, you know, what am I here to do. And I was really surprised—again, my first time at a big tech conference, as well as Vegas and the US is, how important it was just to meet people and how valuable that was. First time I met you, and you know, going from somebody who's probably very likely interacted with you on Twitter before the event to being on this podcast and having a great conversation now is kind of crazy to think that the value you can get out of it. I mean, in terms of over services, and areas of re:Invent that I found interesting was the announcement of the new sustainability pillar, as part of the well-architected framework. You know, I've tried to use that before in previous workplaces, and it has been useful. You know, I'm hoping it is more useful in the future, and the cynical part of me worries about whether the whole point of putting this as part of a well-architected framework review where the customer is supposed to do it is Amazon passing the buck for sustainability. But it's an interesting way forward for what we care about.Corey: An interesting quirk of re:Invent—to me—has always been that despite there being tens of thousands of people there are always a few folks that you wind up running into again and again and again throughout the week. One year for me it was Ben Kehoe; this trip it was you where we kept finding ourselves at the same events, we kept finding ourselves at the same restaurants, and we had three or four meals together as a result, and it was a blast talking to you. And I was definitely noticing that sustainability was a topic that you kept going back to a bunch of different ways. I mean previously, before starting your current consulting company, you did a lot of work in the government—specifically the UK Government, for those who are having trouble connecting the fact this is the first time in America to the other thing. Like, “Wow, you can be far away and work for the government?” It's like, we have more than one on this planet, as it turns out.Yes, it was a fun series of conversations, and I am honestly a little less cynical about the idea of the sustainability pillar, in no small part due to the conversations that we had together. I initially had the cynical perspective of here's how to make your cloud infrastructure more sustainable. It's, isn't that really a “you” problem? You're the cloud provider. I can't control how you get energy on the markets, how you wind up handling heat issues, how you address water issues from your data center outflows, et cetera. It seems to me that the only thing I can really do is use the services you give me, and then it becomes a “you” problem. You have a more nuanced take on it.Aaron: I think there's a log of different things to think about when it comes to sustainability. One of the main ones is, from my perspective, you know, I worked at the UK Home Office in the UK, and we'd been using cloud for about six or seven years. And just looking at how we use clouds as an enterprise organization, one of the things I really started to see was these different generations of cloud and you've got aspects of legacy infrastructure, almost, that we lifted-and-shifted in the early days, versus maybe stuff would run on serverless now. And you know, that's one element, from a customer is how you control your energy usage is actually the use of servers, how efficient your code is, and there's definitely a difference between stringing together EC2 and S3 buckets compared to using serverless or Lambda functions.Corey: There's also a question of scale. When I'm trying to build something out of Lambda functions, and okay, which region is the most cost effective way to run this thing? The Google search for that will have a larger climate impact than any decision I can make at the scale that I operate at. Whereas if you're a company running tens of thousands of instances at any given point in time and your massive scale, then yeah, the choices you make are going to have significant impact. I think that a problem AWS has always struggled with has been articulating who needs to care about what, when.If you go down the best practices for security and governance and follow the white papers, they put out as a one-person startup trying to build an idea this evening, just to see if it's viable, you're never going to get anywhere. If you ignore all those things, and now you're about to go public as a bank, you're going to have a bad time, but at what point do you have to start caring about these different things in different ways? And I don't think we know the answer yet, from a sustainability perspective.Aaron: I think it's interesting in some senses, that sustainability is only just enter the conversation when it comes to stuff we care about in businesses and enterprises. You know, we all know about risk registers, and security reviews, and all those things, but sustainability, while we've, kind of, maybe said nice public statements, and put things on our website, it's not really been a thing that's, okay, this is how we're going to run our business, and the thing we care about as number one. You know, Amazon always says security is job zero, but maybe one day someone will be saying sustainability is our job zero. And especially when it comes down to, sort of, you know, the ethics of running a business and how you want that to be run, whether it is going to be a capitalistic VC-funded venture to extract wealth from citizens and become a billionaire versus creating something that's a bit more circular, and gives back as sustainability might be a key element of what you care about when you make decisions.Corey: The challenge that I find as well is, I don't know how you can talk about the relative sustainability impact of various cloud services within the AWS umbrella without, effectively, AWS explaining to you what their margins are on different services, in many respects. Power usage is the primary driver of this and that determines the cost of running things. It is very clear that it is less expensive and more efficient to run more modern hardware than older hardware, so we start seeing, okay, wow, if I start seeing those breakdowns, what does that say about the margin on some of these products and services? And I don't think they want to give that level of transparency into their business, just because as soon as someone finds out just how profitable Managed NAT gateways are, my God, everything explodes.Aaron: I think it's interesting from a cloud provider or hyperscaler perspective, as well, is, you know, what is your USP? And I think Amazon is definitely not saying sustainability is their USP right now, and I think you know, there are other cloud providers, like Azure for example, who basically can provide you a Power BI plugin; if you just log in with your Cloud account details, it will show you a sustainability dashboard and give you more of this information that you might be looking for, whereas Amazon currently doesn't offer anything like that automated. And even having conversations with your account team or trying to get hold of the right person, Amazon isn't going to go anywhere at the moment, just because maybe that's the reason why we don't want to talk about it: It's too sensitive. I'm sure that'll change because of the public statements they've made at re:Invent now and previously of, you know, where they're going in terms of energy usage. They want to be carbon neutral by 2025, so maybe it'll change to next re:Invent, we'll get the AWS Sustainability Explorer add-on for [unintelligible 00:15:23] or 12—Corey: Oh no.Aaron: —tools to do the same thing [laugh].Corey: In the Google Cloud Console, you click around, and there are green leafs next to some services and some regions, and it's, on the one hand, okay, I appreciate the attention that is coming from. On the other hand, it feels like you're shaming me for putting things in a region that I've already built things out in when there weren't these green leafs here, and I don't know that I necessarily want to have that conversation with my entire team because we can't necessarily migrate at this point. And let's also be clear, here, I cannot fathom a scenario in which running your own data centers is ever going to be more climate-friendly than picking a hyperscaler.Aaron: And I think that's sort of, you know, we all might think about is, at the end of the day, if your sustainability strategy for your business is to go all-in-on cloud, and bet horse on AWS or another cloud provider, then, at the end of the day, that's going to be viable. I know, from the, sort of, hands-on stuff I've done with our own data centers, you can never get it as efficient as what some of these cloud providers are doing. And I mean, look at Microsoft. The fact that they're putting some of their data centers under the sea to use that as a cooling mechanism, and kind of all the interesting things that they're able to do because they can invest at scale, you're never going to be able to do that with the cupboard beyond the desks in your local office to make it more efficient or sustainable.Corey: There are definite parallels between Cloud economics and sustainability because as mentioned, I worship at the altar of Our Lady of Turn that Shit Off because that's important. If you don't have a workload running and it doesn't exist, it has no climate impact. Mostly. I'm sure there are corner cases. But that does lead to the question then of okay, what is the climate sustainability impact, for example, of storing a petabyte of data and EBS versus in S3?And that has architectural impact as well, and there's also questions of how often does it move because when you move it, Lord knows there is nothing more dear than the price of data transfer for data movement. And in order to answer those questions, they're going to start talking a lot more about their architecture. I believe that is why Peter DeSantis's keynote talked so much about—finally—the admission of what we sort of known for ages now that they use erasure coding to make S3 as durable yet inexpensive, as it is. That was super interesting. Without that disclosure, it would have been pretty clear as soon as they start publishing sustainability numbers around things like that.Aaron: And I think is really interesting, you know, when you look at your business and make decisions like that. I think the first thing to start with is do you need that data at all? What's a petabyte of data are going to do? Unless it's for serious compliance reasons for, you know, the sector or the business that you're doing, the rest of it is, you know, you've got to wonder how long is that relevant for. And you know, even as individuals, we could delete junk mail and take things off our internal emails, it's the same thing of businesses, what you're doing with this data.But it is interesting, when you look at some of the specific services, even just the tiering of S3, for example, put that into Glacier instead of keeping it on S3 general. And I think you've talked about this before, I think cost the same to transfer something in and out of Glacier as just to hold it for a month. So, at the end of the day, you've got to make these decisions in the right way, and you know, with the right goals in mind, and if you're not able to make these decisions or you need help, then that's where, you know, people like us come in to help you do this.Corey: There's also the idea of—when I was growing up, the thing they always told us about being responsible was, “Oh, turn out the lights when you're not in the room.” Great. Well, cloud economics starts to get in that direction, too. If you have a job that fires off once a day at two in the morning and it stops at four in the morning, you should not be running those instances the other 22 hours of the day. What's the deal here?And that becomes an interesting expiratory area just as far as starting to wonder, okay, so you're telling me that if I'm environmentally friendly, I'm also going to save money? Let's be clear people, in many cases—in a corporate sense—care about sustainability only insofar as that don't get yelled out about it. But when it comes to saving money, well, now you've got the power of self-interest working for you. And if you can dress them both up and do the exact same things and have two reasons to do it. That feels like it could in some respects, be an accelerator towards achieving both outcomes.Aaron: Definitely. I think, you know, at the end of the day, we all want to work on things that are going to hopefully make the world a better place. And if you use that as a way of motivating, not just yourself as a business, but the workforce and the people that you want to work for you, then that is a really great goal as well. And I think you just got to look at companies that are in this world and not doing very great things that maybe they end up paying more for engineers. I think I read an interesting article the other day about Facebook is basically offering almost double or 150 percent of over salaries because it feels like a black mark on the soul to work for that company. And if there is anything—maybe it's not greenwashing per se, but if you can just make your business a better place, then that could be something that you can hopefully attract other like-minded people with.Corey: This episode is sponsored by our friends at Oracle Cloud. Counting the pennies, but still dreaming of deploying apps instead of, “Hello World” demos? Allow me to introduce you to Oracle's Always Free tier. It provides over 20 free services and infrastructure, networking, databases, observability, management, and security. And let me be clear here, it's actually free. There's no surprise billing until you intentionally and proactively upgrade your account. This means you can provision a virtual machine instance or spin up an autonomous database that manages itself all while gaining the networking, load balancing, and storage resources that somehow never quite make it into most free tiers needed to support the application that you want to build. With Always Free, you can do things like run small-scale applications, or do proof-of-concept testing without spending a dime. You know that I always like to put asterisks next to the word free. This is actually free, no asterisk. Start now. Visit snark.cloud/oci-free that's snark.cloud/oci-free.Corey: One would really like to hope that the challenge, of course, is getting there in such a way that it, well, I guess makes sense, is probably the best way to frame it. These are still early days, and we don't know how things are going to wind up… I guess, it playing out. I have hopes, I have theories, but I just don't know.Aaron: I mean, even looking at Cloud as a concept, how long we've all worked with this now ranges probably from fifteen to five, and for me the last six years, but you got to think looking at the outages at the end of last year at Amazon, that [unintelligible 00:21:57], very close to re:Invent, that impacted a lot of different workloads, not just if you were hosted in us-west or east-1, but actually for a lot of the regional services that actually were [laugh]… discovered to be kind of integral to these regions. You know, one AZ going down can impact single-sign-on logins around the world. And let's see what Amazon looks like in ten years' time as well because it could be very different.Corey: Do you find that as you talk to folks, both in government and in private sector, that there is a legitimate interest in the sustainability story? Or is it the self-serving cynical perspective that I've painted?Aaron: I mean, a lot of my experience is biased towards the public sector, so I'll start with that. In terms of the public sector, over the last few years, especially in the UK, there's been a lot more focus on sustainability as part of your business cases and your project plans for when you're making new services or building new things. And one of the things they've recently asked every government department in the UK to do is come up with a sustainability strategy for their technology. And that's been something that a lot of people have been working on as part of something called the One Gov Cloud Strategy Working Groups—which in the UK, we do love an abbreviation, so [laugh] a bit of a long name—but I think there's definitely more of an interest in it.In terms of the private sector, I'm not too sure if that's something that people are prioritizing. A lot of the focus I kind of come across as either, we want to focus on enterprise customers, so we're going to offer migration professional services, or you're a new business and you're starting to go up and already spending a couple a hundred pounds, or thousands of pounds a month. And at that scale, it's probably not going to be something you need to worry about right now.Corey: I want to talk a little bit about how you got into tech in the first place because you told me elements of this story, and I generally find them to be—how do I put this?—they strain the bounds of credulity. So, how did you wind up in this ridiculous industry?Aaron: I mean, hoping as I explain them, you don't just think I'm a liar. I have got a Scouse accent, so you're probably predisposed towards it. But my journey into tech was quite weird, I guess, in the sense that when I was 16—I was, again, like I said, born in Liverpool and didn't really know what I wanted to do in the world, and had no idea what the hell to do. So, I was at college, and kind of what happened to me there is I joined, like, an entrepreneurship club and was like, “Okay, I'll start my own business and do something interesting.” And I went to a conference at college, and there was a panel with Richard Branson and other few of business leaders, and I stood up and asked the question said, you know, “I'm 16. I want to start a business. Where can I get money to start a business?”And the panel answered with kind of a couple of different things, but one of them was, “Get a job.” The other one was, “Get money off your parents.” And I was kind of like, “Oh, a bit weird. I've got a job already. You know, I would ask my parents put their own benefits.”And asked the woman with the microphone, “Can I say something back?” And she said, “No.” So, being… a young person, I guess, and just I stood back up and said, you know, “You're in Liverpool. You've kind of come to one of the poorest cities in some sense in the UK, and you kind of—I've already got a job. What can I really do?”And that's when Richard Branson turned round and said, “Well, what is it you want to do?” And I said, “I make really good cheesecakes and I want to sell them to people.” And after that sort of exchange, he said he'd give me the money. So, he gave me 200 pounds to start my own business. And that was just, kind of like, this whirlwind of what the hell's going on here?But for me, it's one of those moments in my life, which I think back on, and honestly, it's like one of these ten [left 00:25:15] moments of, you know, I didn't stand back up and say something, if I didn't join the entrepreneurship club, like, I just wouldn't be in the position I am right now. And it was also weird in the sense that I said at the start of the story, I didn't know what I wanted to do in my life. This was the first time that anyone had ever said to me, “I trust you to do something, and here's 200 pounds to do it.” And it was such a small thing, and a small moment that basically got me to where I am today. And kind of a condensed version of that is, you know, after that event, I started volunteering for a charity who—a, sort of, magazine launch, and then applied for the civil service and progressed through six to eight years of the civil service.And it was because of that moment, and that experience, and that confidence boost, where I was like, “Oh, I actually can do something with my life.” And I think tech, and I think a lot of people talk about this is, it can be a bit of a crazy whirlwind, and to go from that background into, you know, working with great people and earning great money is a bit of a crazy thing sometimes.Corey: Is there another path that you might have gone down instead and completely missed out on, for lack of a better term—and not missed out. You probably would have been far happier not working in tech; I know I would have been—but as far as trying to figure out, like, what does the road not taken look like for you?Aaron: I'm not too sure, really. And at the time, I was working in a club. I was like 16, 17 years old, working in a nightclub in Liverpool for five pounds an hour, and was doing that while I was studying, and that was almost like, what was in my mind at the time. When it came to the end of college, I was applying for universities, I got in on, like, a second backup course, and that was the only thing to do was food science. And it was like, I can't imagine coming out of university three years after that, studying something that's not really that relevant to a lot of industries, and trying to find a good job. It could have just been that I was working in a supermarket for minimum wage after I came out for uni trying to find what I wanted to do in the world. And, yeah, I'm really glad that I kind of ended up where I am now.Corey: As you take a look at what you want your career to be about in the broad sweep of things, what is it that drives you? What is it that makes you, for example, decide to spend the previous portion of career working in public service? That is a very, shall we say, atypical path—I say, as someone who lives in San Francisco and is surrounded by people who want to make the world a better place, but all those paths just coincidentally would result in them also becoming billionaires along the way.Aaron: I mean, it is interesting. You know, one of the things that worked for the civil service for so long, is the fact that I did want to do more than just make somebody else more money. And you know, there are not really a lot of ways you can do that and make a good wage for yourself. And I think early on in your career, working for somewhere like the civil service or federal government can be a little bit of that opportunity. And especially with some of the government's focus on tech these days, and investments—you know, I joined through an apprenticeship scheme and then progressed on to a digital leadership scheme, you know, they were guided schemes to help me become a better leader and improve my skills.And I think I would have probably not gone to the same position if I just got the tech job or my first engineering job somewhere else. I think, if I was to look at the future and where do I want to go, what do I care about? And, you know, you ask me, sort of, this question at re:Invent, and it took me a few days to really figure out, but one of the things when I talk about making the world a better place is thinking about how you can start businesses that give back to people in local areas, or kind of solve problems and kind of keep itself running a bit like a trust does, [laugh], if only that keeping rich people running. And a lot of the time, like, you've highlighted is coincidentally these things that we try and solve whether it's, like, a new app or a new thing that does something seems to either be making money for VCs, reinventing things that we already have, or just trying to make people billionaires rather than trying to make everyone rise up and—high tide rise all ships, is the saying. And there are a few people that do this, a few CEOs who take salaries the same as everyone else in the business. And I think that's hopefully you know, as I grow my own business and work on different things in the future, is how can I just help people live better lives?Corey: It's a big question, and it's odd in that I don't find that most people asking it tend to find themselves going toward government work so much as they do NGOs, and nonprofits, and things that are very focused on specific things.Aaron: And it can be frustrating in some sense is that, you know, you look at the landscape of NGOs, and charities, and go, “Why are they involved in solving this problem?” You know, one of the big problems we have in the UK is the use of food banks where people who don't have enough money, whether they receive benefits or not, have to go and get food which is donated just by people of the UK and people who donate to these charities. You know, at the end of the day, I'm really interested in government, and public sector work, and potentially one day, being a bit more involved in policy elements of that, is how can we solve these problems with broad brushstrokes, whether it's technology advancements, or kind of policy decisions? And one of the interesting things that I got close to a few times, but I don't think we've ever really solved is stuff like how can we use Agile to build policy?How can we iterate on what that policy might look like, get customers or citizens of countries involved in those conversations, and measure outcomes, and see whether it's successful afterwards. And a lot of the time, policies and decisions are just things that come out of politicians minds, and it'd be interesting to see how we can solve some of these problems in the world with stuff like Agile methodologies or tech practices.Corey: So, it's easy to sit and talk about these things in the grand sweep of how the world could be or how it should look, but for those of us who think in more, I guess, tactical terms, what's a good first step?Aaron: I think from my point of view, and you know, meeting so many people at re:Invent, and just have my eyes opened of these great conversations we can have a great people and get things changed, one of the things that I'm looking at starting next year is a podcast and a newsletter, around the use of public cloud for public good. And when I say that, it does cover elements of sustainability, but it is other stuff like how do we use Cloud to deliver things in the public sector and NGOs and charities? And I think having more conversations like that would be really interesting. Obviously, that's just the start of a conversation, and I'm sure when I speak to more people in the future, more opportunities and more things might come out of it. But I'd just love to speak to more people about stuff like this.Corey: I want to thank you for spending so much time to speak with me today about… well, the wide variety of things, and of course, spending as much time as you did chatting with me at re:Invent in person. If people want to learn more, where can they find you?Aaron: So yep, got a few social media handles on Twitter, I'm @AaronBoothUK. On LinkedIn is the same, forward slash aaronboothuk, and I've also got the website for my consultancy, which is embue.co.uk—E-M-B-U-E dot co dot uk. And for the newsletter, it's publicgood.cloud.Corey: And we will, of course, include links to that in the [show notes 00:32:11]. Thank you so much for taking the time to speak with me. I really do appreciate it.Aaron: Thank you so much for having me.Corey: Aaron Booth, cloud consultant with an emphasis on sustainability. I'm Cloud Economist Corey Quinn with an emphasis on optimizing bills. 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 along with an angry comment that you will then kickstart the coal-burning generator under your desk to wind up posting.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.

Risky Business
Risky Business #649 -- Java being a fiddly mess saves the day

Risky Business

Play Episode Listen Later Jan 5, 2022


On this week's show Patrick Gray and Adam Boileau discuss the week's security news, including: The log4j bug wrap The ransomware wrap The human rights and surveillance industry wrap Research and carnage wrap This week's show is brought to you by Airlock Digital. They make allowlisting software that has mostly been used in Windows environments, but as you're about to hear they've now got a very, very nice solution for the bigger Linux distros, and their Mac agent is going to be launched in a few weeks. Links to everything that we discussed are below and you can follow Patrick or Adam on Twitter if that's your thing. Show notes FTC warns companies to remediate Log4j security vulnerability | Federal Trade Commission Srsly Risky Biz: Thursday December 16 The internet runs on free open-source software. Who pays to fix it? | MIT Technology Review Propane distributor Superior Plus admits ransomware breach | The Daily Swig Ransomware attack threatens paychecks just before Christmas Cyberattack on one of Norway's largest media companies shuts down presses - The Record by Recorded Future Photography site Shutterfly is dealing with a ransomware attack - CyberScoop Lapsus$ ransomware gang hits SIC, Portugal's largest TV channel - The Record by Recorded Future US food importer Atalanta admits ransomware attack | The Daily Swig The FBI believes the HelloKitty ransomware gang operates out of Ukraine - The Record by Recorded Future Ransomware affiliate arrested in Romania - The Record by Recorded Future Iranian hackers behind Cox Media Group ransomware attack - The Record by Recorded Future Israeli newspaper Jerusalem Post is hacked, website defaced to include threats Iranian Hackers Abuse Slack For Cyber Spying Why Wall Street is worried about state and local government cybersecurity - The Record by Recorded Future North Korean hackers target Russian diplomats using New Year greetings - The Record by Recorded Future Egyptian Politician Hacked by 2 Government Hacking Groups, Researchers Say Saudi women's rights activist says phone hack by U.S. contractors led to arrest -lawsuit | Reuters UAE agency put Pegasus spyware on the phone of Hanan Elatr, Jamal Khashoggi's wife - Washington Post A new spyware-for-hire, Predator, caught hacking phones of politicians and journalists | TechCrunch Facebook says 50,000 users were targeted by cyber mercenary firms in 2021 | MIT Technology Review Encrypted Phone Company Backdoored by FBI Will Lead to 'Years' of Arrests Russian hackers bypass 2FA by annoying victims with repeated push notifications - The Record by Recorded Future More than 1,200 phishing toolkits capable of intercepting 2FA detected in the wild - The Record by Recorded Future Facebook expands bug bounty program to cover scraping attacks - The Record by Recorded Future Wireless coexistence – New attack technique exploits Bluetooth, WiFi performance features for ‘inter-chip privilege escalation' | The Daily Swig Microsoft notifies customers of Azure bug that exposed their source code - The Record by Recorded Future US charges former GRU officer with hacking and stock market trading scheme - The Record by Recorded Future Crypto exchanges keep getting hacked, and there's little anyone can do CISA tells agencies to patch recent Windows 10 zero-day abused by Emotet botnet - The Record by Recorded Future Security flaws found in a popular guest Wi-Fi system used in hundreds of hotels | TechCrunch Backdoor gives hackers complete control over federal agency network | Ars Technica Microsoft fixes harebrained Y2K22 Exchange bug that disrupted email worldwide | Ars Technica

The Tech Guy (MP3)
Leo Laporte - The Tech Guy: 1855

The Tech Guy (MP3)

Play Episode Listen Later Jan 1, 2022 69:40


Nathan calls in to ask Leo if he should switch to Linux. A caller asks for help digitizing their VHS tapes. Google Photos changes its free plan; a caller asks for an alternative. A blind listener calls in to discuss what would be required to become a HAM radio operator. Roger is approaching 70 years old and is about to buy his first computer — he asks which he should get. A perplexing puzzle: A listener's phone suddenly reboots every time they go to the grocery store. Richard calls in to recount the time an Apple Watch saved his life. The Tech Guy helps a listener set up his projector ... the listener wants to project onto the side of his unknowing neighbor's house. A beekeeper calls in to ask for advice on streaming a beekeeping demonstration. Micah from Maine asks Leo if he should pay for email service instead of using a free provider. A caller asks for help cleaning up his laptop ... the laptop keyboard is covered and coated in granulated sugar. Host: Leo Laporte Download or subscribe to this show at https://twit.tv/shows/the-tech-guy. Get episodes ad-free with Club TWiT at https://twit.tv/clubtwit Johnny JetJohnny Jet Is a travel expert and shares his tricks, tips, and advice on how to save money and get great deals.https://johnnyjet.com Dick DeBartoloDick DeBartolo is MAD's Maddest Writer and The Giz Wiz. In addition, Dick appears on ABC's "World News Now". At MAD Magazine he holds the writer's record, having something published in every issue for the past 40+ years.http://gizwiz.biz/ Scott WilkinsonScott Wilkinson, is an expert when it comes to audio-visual systems and emerging trends. He is a contributor to TechHive.com and interviews the leaders and pioneers behind today's home-theater technology.https://www.techhive.com/author/Scott-Wilkinson/ Sam AbuelsamidSam loves cars, and as a senior analyst at Navigant Research, he focuses on automated driving, mobility services, telematics, connectivity, cybersecurity, and advanced propulsion. Sam is also a senior automotive contributor at Forbes, columnist for Automotive Engineering magazine and co-hosts the "Wheel Bearings" podcast.https://wheelbearings.media/ Rod PyleRod Pyle is a space historian and author who has worked with NASA at the Jet Propulsion Laboratory and the Johnson Space Center. He's the Editor-in-Chief of Ad Astra Magazine and the author of "First on The Moon."https://www.pylebooks.com/ Chris MarquardtChris Marquardt is a photographer and host of Tips from the Top Floor, the world's longest-running photography show. He loves to explain how photography works and help people to make better pictures and videos.https://chrismarquardt.com/