Podcasts about Git

What's an immutable architecture, and why do you want one? Carl and Richard talk to Michael Perry about his book The Art of Immutable Architecture and the power of historical models. Michael talks about different designs for immutability, the ability to always look back through data, to avoid conflict between resources, and the advantages of eventual consistency. As Michael says, you already use immutable architecture - look at Git and how you only add new files to the system, always able to get back to a previous state! The conversation dives into implementing architecture in a way that helps to show where immutability makes sense.

Ye Haw! Git along lil doggies, Paul and Alex are talking about having respect for people in service positions and how easy it is to take negative attention as positive attention, especially if you are John Arbuckle.  Get wrapped up in this week's strip Here.  Follow the Podcast on Twitter or Instagram Follow the Paul on Instagram  Follow Alex on Twitter or Instagram Mystic Lasagna is a Member of the Missing Sock network. For other great shows like this one, check out https://www.missingsocknetwork.com/ or search Missing Sock in your favorite pod catcher.  Also we have Merch!! Follow the network on Instagram.    Lasagnaste´  

Tim Shaw is an undisputed pickup guru. He spent time at both Gibson and Heritage Guitars before joining Fender in 1996. Today, he is Fender's Chief Engineer - Guitars, in the R & D Innovations department. Tim joins us today to share about a 'once in a lifetime' project at Fender reinventing and reinvigorating Fender's Wide Range humbuckers into a stunning new range. This episode dives into the process of building your own 'unobtainium', Seth Lover's links with Fender and much more.   This episode is brought to you by Fretboard Biology    Fretboard Biology - the online guitar college created by Joe Elliott, ex Head of Guitar at GIT and McNally Smith Music College. Fretboard Biology Guitar Speak Podcast #146 - Joe Elliott - ex guitar head of GIT - launches Fretboard Biology Guitar Speak Podcast Links PayPal Tip Jar Visit us at guitarspeakpodcast.com Subscribe and find previous episodes at: Apple Podcasts Spotify Stitcher   Follow us on Instagram

The boys at Leaning Right and Turning Left With Sadler and the Senator have been busy with campaigning for office and running their small businesses here in the Commonwealth of Virginia, but they still manage to sit down together (minus Shep, he's on vacation again) to bring to you this week a great flashback to the first time the Sadler Brothers, Hermie and Elliott, got together on this podcast's second episode ever. This episode is the set-up for the incredibly awesome and great return of Elliott Sadler to the podcast next week, where he picks up where he left off, and engages in a funny and inspiring conversation about his prior life as a NASCAR® driver, and his current life as a coach, father and husband.  In the “Part Won” episode, be prepared to enjoy an absolutely hilarious conversation with the NASCAR® driver voted by the fans to be the one that they “wanted to have a beer with!” Hermie and his brother dive into family history, racing memories, and Elliott's involvement in the future of racing – iRacing. Listen and Laugh to this great episode, just like our main man, Larry the Cable Guy says that ya gotta' do!!  Git r' done!!!! For all your men's grooming needs, look no further than our sponsor www.manscaped.com, and when you place an order for their awesome products, enter promo code “Sadler” at checkout and received 20% off your order, and get free shipping anywhere in the world!! For more information about this podcast, and Hermie and Bill's open-wheel modified race team, Sadler/Stanley Racing at www.sadlerstanleyracing.com, or visit their Facebook® pages (Leaning Right and Turning Left Podcast, and Sadler/Stanley Racing). Or, you can find them on Twitter: @HermieSadler, @BillStanley, or @SadlerSenator! If you need a lawyer, and we mean a really good lawyer, contact Bill Stanley at www.vastanleylawgroup.com. You want to save big bucks on your mortgage, then go to www.savewithconrad.com. And if you like this podcast and want to listen to other great podcasts AFTER you have listened to Leaning Right and Turning Left With Sadler and the Senator, then go over to our bosses at www.podcastheat.com and tune into some other awesome shows! Learn more about your ad choices. Visit megaphone.fm/adchoices

What the challenge of building a web browser from scratch tells us about the state of the modern web, why some people are frying their AMD CPUs, more on basic password managers and regularly powercyling network gear, moving from Mercurial to Git, running old applications on modern Ubuntu, and more.   Plugs Support us on […]

Data access control is becoming increasingly important as more and more sensitive data is being stored and processed by businesses and organizations. In this episode, the VP of Developer Experience at lakeFS, Adi Polak, joins to help define data access control and give examples of sensitive data that requires access control. Adi also talks about the concept of role-based access control (RBAC), which differs from traditional access control methods and provides several advantages. The steps involved in implementing RBAC are discussed, as well as best practices and challenges. Real-world examples of RBAC implementation and success stories are provided, and lessons learned from RBAC implementation are shared. We also discuss lakeFS, an open-source platform that provides a Git-like interface for managing data lakes. In particular, we get into the data management controls, the security and privacy features, and the future of the product. Topics: What are some common types of data access controls? Why are these types of controls important? How can RBAC help organizations better manage and secure their data? What are some challenges in implementing effective data access controls? How can organizations balance data security with the need to provide employees with the information they need to do their jobs? What are some best practices for managing data access control? How do you ensure that data access controls remain effective over time as your organization grows and changes? What is lakeFS? What model of data access management does lakeFS support? What are some of the other privacy and security features of lakeFS? What's next for lakeFS? Anything you can share? Where do you see data access control going in the next 5-10 years? Resources: lakeFS Roadmap Scaling Machine Learning with Spark: Distributed ML with MLlib, TensorFlow, and PyTorch

Jim Fisk is the creator of Plenti and the founder of Causeworks, a full service creative agency for mission-driven organizations.In this episode we discuss using open source technology for social goods, whether you should be bearish or bullish on Jamstack, and the benefits of a Git-based CMS.Jim Fisk Twitter GitHub LinkedIn Jantcu Plentico Jamstack Boston CauseworksWebsite

Kubernetes is an open-source system for automating deployment, scaling, and management of containerized applications. Although it improves the management and scaling of infrastructure and applications, Kubernetes frequently has challenges managing the complexity of releasing applications. Git is the most widely used version-control system in the software industry today. GitOps is a set of procedures that uses The post GitOps for Kubernetes with Priyanka Ravi and Stefan Prodan appeared first on Software Engineering Daily.

Jūra Smiltė. „Gitė ir Leonardas Liūtas laukia pavasario“ iš knygos „Brigitos Begemotaitės ir jos draugų nuotykiai“. Išleido leidykla „homo liber“. Skaito Giedrė Vaičekauskienė.

Adam Miller is back with a fantastic new record and we hear all about it on the Guitar Speak Podcast! In Adam's words "Beyond Reason is a Guitarist / Songwriter album, if there was such a genre! I began to take note, that most of my guitar playing time was spent writing and creating, rather than practising. This led to me writing multiple albums worth of material the past few years whilst off the road for a while.” The 8 song album contains elements of blues, jazz, funk, rock, folk, and country and features Miller on electric, archtop, acoustic, resonator, and nylon string guitar. The bass & drums were recorded in Los Angeles by Miller's now long time collaborators, drummer / engineer / producer Justin Glasco, and bass player Joel Gottschalk. Miller then worked up the tracks through 2022 in his home of Newcastle Australia, between his return to performing and touring dates. https://www.adammiller.com.au/ http://www.guitarspeakpodcast.com/e/adam-miller-gsp-80/ http://www.guitarspeakpodcast.com/e/adam-miller-us-adventures-and-a-new-record-gsp-141/   This episode is brought to you by Fretboard Biology    Fretboard Biology - the online guitar college created by Joe Elliott, ex Head of Guitar at GIT and McNally Smith Music College. Fretboard Biology Guitar Speak Podcast #146 - Joe Elliott - ex guitar head of GIT - launches Fretboard Biology Guitar Speak Podcast Links PayPal Tip Jar Visit us at guitarspeakpodcast.com Subscribe and find previous episodes at: Apple Podcasts Spotify Stitcher   Follow us on Instagram  

Randall Waller returns to the podcast to discuss his much anticipated solo album, "More". Randall's guitar chops are on display from brutal drop C riffs and killer solos to beautiful acoustic moments. A star studded lineup of guests feature, including the Budapest Scoring Orchestra, Richard Fortus, Joel McDonald, Irwin Thomas and Chris Kamzelas to name but a few. And...Randall is one of Australia's finest rock vocalists by the way...   SHOW LINKS:   Check out Randall on Facebook   Listen to our earlier interviews with Randall talking about touring with Shania Twain, Kieth Urban, Dragon, Avion and more: Randall Waller GSP #23 Randall Waller GSP #24   This episode is brought to you by Fretboard Biology    Fretboard Biology - the online guitar college created by Joe Elliott, ex Head of Guitar at GIT and McNally Smith Music College. Fretboard Biology Guitar Speak Podcast #146 - Joe Elliott - ex guitar head of GIT - launches Fretboard Biology Guitar Speak Podcast Links PayPal Tip Jar Visit us at guitarspeakpodcast.com Subscribe and find previous episodes at: Apple Podcasts Spotify Stitcher   Follow us on Instagram

Welcome to the newest episode of The Cloud Pod podcast! Justin, Ryan and Matthew are your hosts this week as we discuss all the latest news and announcements in the world of the cloud and AI. Do people really love Matt's Azure know-how? Can Google make Bard fit into literally everything they make? What's the latest with Azure AI and their space collaborations? Let's find out! Titles we almost went with this week: Clouds in Space, Fictional Realms of Oracles, Oh My.  The cloudpod streams lambda to the cloud A big thanks to this week's sponsor:  Foghorn Consulting, provides top-notch cloud and DevOps engineers to the world's most innovative companies. Initiatives stalled because you have trouble hiring?  Foghorn can be burning down your DevOps and Cloud backlogs as soon as next week.

Git is a version control system that allows developers to collaborate on projects, keep track of changes, and easily revert to previous versions if necessary. It's an essential tool for any software developer, but if you're new to Git, it can seem overwhelming. Read more › The post Basics of Git appeared first on Complete Developer Podcast.

Emergency podcast!! The GSP 'Iconic' roundtable team of Matt Wakeling, Rob Rhodes & Gabor Josika assemble to discuss their favourite new stuff to emerge from NAMM 2023. Guitars, amps, pedals and crazy gadgets abound!  Rob Rhodes - www.rhodetripent.com Gabor Josika - SuperFunAwesomeHappyTime Pedal Show   This episode is brought to you by Fretboard Biology    Fretboard Biology - the online guitar college created by Joe Elliott, ex Head of Guitar at GIT and McNally Smith Music College. Fretboard Biology Guitar Speak Podcast #146 - Joe Elliott - ex guitar head of GIT - launches Fretboard Biology Guitar Speak Podcast Links PayPal Tip Jar Visit us at guitarspeakpodcast.com Subscribe and find previous episodes at: Apple Podcasts Spotify Stitcher   Follow us on Instagram

Darko Mesaroš, Senior Developer Advocate at AWS, joins Corey on Screaming in the Cloud to discuss all the weird and wonderful things that can be done with old hardware, as well as the necessary skills for being a successful Developer Advocate. Darko walks through how he managed to deploy Kubernetes on a computer from 1986, as well as the trade-offs we've made in computer technology as hardware has progressed. Corey and Darko also explore the forgotten art of optimizing when you're developing, and how it can help to cut costs. Darko also shares what he feels is the key skill every Developer Advocate needs to have, and walks through how he has structured his presentations to ensure he is captivating and delivering value to his audience.About DarkoDarko is a Senior Developer Advocate based in Seattle, WA. His goal is to share his passion and technological know-how with Engineers, Developers, Builders, and tech enthusiasts across the world. If it can be automated, Darko will definitely try to do so. Most of his focus is towards DevOps and Management Tools, where automation, pipelines, and efficient developer tools is the name of the game – click less and code more so you do not repeat yourself ! Darko also collects a lot of old technology and tries to make it do what it should not. Like deploy AWS infrastructure through a Commodore 64.Links Referenced: AWS: https://aws.amazon.com/ Blog post RE deploying Kubernetes on a TRS-80: https://www.buildon.aws/posts/i-deployed-kubernetes-with-a-1986-tandy-102-portable-computer AWS Twitch: https://twitch.tv/aws Twitter: https://twitter.com/darkosubotica Mastodon: https://hachyderm.io/@darkosubotica TranscriptAnnouncer: Hello, and welcome to Screaming in the Cloud with your host, Chief Cloud Economist at The Duckbill Group, Corey Quinn. This weekly show features conversations with people doing interesting work in the world of cloud, thoughtful commentary on the state of the technical world, and ridiculous titles for which Corey refuses to apologize. This is Screaming in the Cloud.Corey: This episode is sponsored in part by our friends at Chronosphere. When it costs more money and time to observe your environment than it does to build it, there's a problem. With Chronosphere, you can shape and transform observability data based on need, context and utility. Learn how to only store the useful data you need to see in order to reduce costs and improve performance at chronosphere.io/corey-quinn. That's chronosphere.io/corey-quinn. And my thanks to them for sponsor ing my ridiculous nonsense. Corey: Do you wish your developers had less permanent access to AWS? Has the complexity of Amazon's reference architecture for temporary elevated access caused you to sob uncontrollably? With Sym, you can protect your cloud infrastructure with customizable, just-in-time access workflows that can be setup in minutes. By automating the access request lifecycle, Sym helps you reduce the scope of default access while keeping your developers moving quickly. Say goodbye to your cloud access woes with Sym. Go to symops.com/corey to learn more. That's S-Y-M-O-P-S.com/coreyCorey: Welcome to Screaming in the Cloud. I'm Cloud Economist Corey Quinn and my guest today is almost as bizarre as I am, in a somewhat similar direction. Darko Mesaroš is a Senior Developer Advocate at AWS. And instead of following my path of inappropriately using things as databases that weren't designed to be used that way, he instead uses the latest of technology with the earliest of computers. Darko, thank you for joining me.Darko: Thank you so much, Corey. First of all, you know, you tell me, Darko is a senior developer advocate. No, Corey. I'm a system administrator by heart. I happen to be a developer advocate these days, but I was born in the cold, cold racks of a data center. I maintain systems, I've installed packages on Linux systems. I even set up Solaris Zones a long time ago. So yeah, but I happen to yell into the camera these days, [laugh] so thank you for having me here.Corey: No, no, it goes well. You started my career as a sysadmin. And honestly, my opinion, if you asked me—which no one does, but I share it anyway—is that the difference between an SRE and a sysadmin is about a 40% salary bump.Darko: Exactly.Corey: That's about it. It is effectively the same job. The tools are different, the approach we take is different, but the fundamental mandate of ‘keep the site up' has not materially changed.Darko: It has not. I don't know, like, what the modern SRS do, but like, I used to also semi-maintain AC units. Like, you have to walk around with a screwdriver nonetheless, so sometimes, besides just installing the freshest packages on your Red Hat 4 system, you have to also change the filters in the AC. So, not sure if that belongs into the SRE manifesto these days.Corey: Well, the reason that I wound up inviting you onto the show was a recent blog post you put up where you were able to deploy Kubernetes from the best computer from 1986, which is the TRS-80, or the Trash-80. For the record, the worst computer from 1986 was—and remains—IBM Cloud. But that's neither here nor there.What does it mean to deploy Kubernetes because, to be direct, the way that I tend to deploy anything these days, if you know, I'm sensible and being grown up about it, is a Git push and then the automation takes it away from there. I get the sense, you went a little bit deep.Darko: So, when it comes to deploying stuff from an old computer, like, you know, you kind of said the right thing here, like, I have the best computer from 1986. Actually, it's a portable version of the best computer from 1986; it's a TRS-80 Model 102. It's a portable, basically a little computer intended for journalists and people on the go to write stuff and send emails or whatever it was back in those days. And I deployed Kubernetes through that system. Now, of course, I cheated a bit because the way I did it is I just used it as a glorified terminal.I just hooked up the RS 232, the wonderful serial connection, to a Raspberry Pi somewhere out there and it just showed the stuff from a Raspberry Pi onto the TRS-80. So, the TRS-80 didn't actually know how to run kubectl—or ‘kube cuddle,' what they call it—it just asked somebody else to do it. But that's kind of the magic of it.Corey: You could have done a Lambda deployment then just as easily.Darko: Absolutely. Like that's the magic of, like, these old hunks of junks is that when you get down to it, they still do things with numbers and transmit electrical signals through some wires somewhere out there. So, if you're capable enough, if you are savvy, or if you just have a lot of time, you can take any old computer and have it do modern things, especially now. Like, and I will say 15 years ago, we could have not done anything like this because 15 years ago, a lot of the stuff at least that I was involved with, which was Microsoft products, were click only. I couldn't, for the love of me, deploy a bunch of stuff on an Active Directory domain by using a command line. PowerShell was not a thing back then. You could use VB Script, but sort of.Corey: Couldn't you wind up using something that would effect, like, Selenium or whatnot that winds up emulating a user session and moving the mouse to certain coordinates and clicking and then waiting some arbitrary time and clicking somewhere else?Darko: Yes.Corey: Which sounds like the absolute worst version of automation ever. That's like, “I deployed Kubernetes using a typewriter.” “Well, how the hell did you do that?” “Oh, I use the typewriter to hit the enter key. Problem solved.” But I don't think that counts.Darko: Well, yeah, so actually even back then, like, just thinking of, like, a 10, 12-year step back to my career, I automated stuff on Windows systems—like Windows 2000, and Windows 2003 systems—by a tool called AutoIt. It would literally emulate clicks of a mouse on a specific location on the screen. So, you were just really hoping that window pops up at the same place all the time. Otherwise, your automation doesn't work. So yeah, it was kind of like that.And so, if you look at it that way, I could take my Trash-80, I could write an AutoIt script with specific coordinates, and I could deploy Windows things. So actually, yeah, you can deploy anything with these days, with an old computer.Corey: I think that we've lost something in the world of computers. If I, like, throw a computer at you these days, you're going to be pretty annoyed with me. Those things are expensive, it'll probably break, et cetera. If I throw a computer from this era at you, your family is taking bereavement leave. Like, those things where—there would be no second hit.These things were beefy. They were a sense of solidity to them. The keyboards were phenomenal. We've been chasing that high ever since. And, yeah, they were obnoxiously heavy and the battery life was 20 seconds, but it was still something that—you felt like it is computer time. And now, all these things have faded into the background. I am not protesting the march of progress, particularly in this particular respect, but I do miss the sense of having keyboards didn't weren't overwhelmingly flimsy plastic.Darko: I think it's just a fact of, like, we have computers as commodities these days. Back then computers were workstations, computers were something you would buy to perform a specific tasks. Today, computer is anything from watching Twitch to going on Twitter, complaining about Twitter, to deploying Kubernetes, right? So, they have become such commodities such… I don't want to call them single-use items, but they're more becoming single-use items as time progresses because they're just not repairable anymore. Like, if you give me a computer that's five years old, I don't know what to do with it. I probably cannot fix it if it's broken. But if you give me a computer that's 35 years old, I bet you can fix it no matter what happened.Corey: And the sheer compute changes have come so fast and furious, it's easy to lose sight of them, especially with branding being more or less the same. But I saved up and took a additional loan out when I graduated high school to spend three grand on a Dell Inspiron laptop, this big beefy thing. And for fun, I checked the specs recently, and yep, that's a Raspberry Pi these days; they're $30, and it's not going to work super well to browse the web because it's underpowered. And I'm sitting here realizing wait a minute, even with a modern computer—forget the Raspberry Pi for a second—I'm sitting here and I'm pulling up web pages or opening Slack, or God forbid, Slack and Chrome simultaneously, and the fan spins up and it sounds incredibly anemic. And it's, these things are magical supercomputers from the future. Why are they churning this hard to show me a funny picture of a cat? What's going on here?Darko: So, my theory on this is… because we can. We can argue about this, but we currently—Corey: Oh, I think you're right.Darko: We have unlimited compute capacity in the world. Like, you can come up with an idea, you're probably going to find a supercomputer out there, you're probably going to find a cloud vendor out there that's going to give you all of the resources you need to perform this massive computation. So, we didn't really think about optimization as much as we used to do in the past. So, that's it: we can. Chrome doesn't care. You have 32 gigs of RAM, Corey. It doesn't care that it takes 28 gigs of that because you have—Corey: I have 128 gigs on this thing. I bought the Mac studio and maxed it out. I gave it the hostname of us-shitpost-1 and we run with it.Darko: [laugh]. There you go. But like, I did some fiddling around, like, recently with—and again, this is just the torture myself—I did some 6502 Assembly for the Atari 2600. 6502 is a CPU that's been used in many things, including the Commodore 64, the NES, and even a whole lot of Apple IIs, and whatnot. So, when you go down to the level of a computer that has 1.19 megahertz and it has only 128 bytes of RAM, you start to think about, okay, I can move these two numbers in memory in the following two ways: “Way number one will require four CPU cycles. Way number two will require seven CPU cycles. I'll go with way number one because it will save me three CPU cycles.”Corey: Oh, yeah. You take a look at some of the most advanced computer engineering out there and it's for embedded devices where—Darko: Yeah.Corey: You need to wind up building code to run in some very tight constraints, and that breeds creativity. And I remember those days. These days, it's well my computer is super-overpowered, what's it matter? In fact, when I go in and I look at customers' AWS bills, very often I'll start doing some digging, and sure enough, EC2 is always the number one expense—we accept that—but we take a look at the breakdown and invariably, there's one instance family and size that is the overwhelming majority, in most cases. You often a—I don't know—a c5.2xl or something or whatever it happens to be.Great. Why is that? And the answer—[unintelligible 00:10:17] to make sense is, “Well, we just started with that size and it seemed to work so we kept using it as our default.” When I'm building things, because I'm cheap, I take one of the smallest instances I possibly can—it used to be one of the Nanos and I'm sorry, half a gig or a gig of RAM is no longer really sufficient when I'm trying to build almost anything. Thanks, JavaScript. So okay, I've gone up a little bit.But at that point, when I need to do something that requires something beefier, well, I can provision those resources, but I don't have it as a default. That forces me to at least in the back of my mind, have a little bit of a sense of I should be parsimonious with what it is that I'm provisioning out there, which is apparently anathema to every data scientist I've ever met, but here we are.Darko: I mean, that's the thing, like, because we're so used to just having those resources, we don't really care about optimizations. Like, I'm not advocating that you all should go and just do assembly language. You should never do that, like, unless you're building embedded systems or you're working for something—Corey: If you need to use that level of programming, you know.Darko: Exactly.Corey: You already know and nothing you are going to talk about here is going to impact what people in that position are doing. Mostly you need to know assembly language because that's a weeder class and a lot of comp-sci programs and if you don't pass it, you don't graduate. That's the only reason to really know assembly language most of the time.Darko: But you know, like, it's also a thing, like, as a developer, right, think about the person using your thing, right? And they may have the 128 gig us—what is it you called it? Us-shitpost-1, right—that kind of power, kind of, the latest and greatest M2 Max Ultra Apple computer that just does all of the stuff. You may have a big ‘ol double Xeon workstation that does a thing.Or you just may have a Chromebook. Think about us with Chromebooks. Like, can I run your website properly? Did you really need all of those animations? Can you think about reducing the amount of animations depending on screen size? So, there's a lot of things that we need to kind of think about. Like, it goes back to the thing where ‘it works on my machine.' Oh, of course it works on your machine. You spent thousands of dollars on your machine. It's the best machine in the world. Of course, it runs smoothly.Corey: Wait 20 minutes and they'll release a new one, and now, “Who sold me this ancient piece of crap?” Honestly, the most depressing thing is watching an Apple Keynote because I love my computer until I watch the Apple Keynote and it's like, oh, like, “Look at this amazing keyboard,” and the keyboard I had was fine. It's like, “Who sold me this rickety piece of garbage?” And then we saw how the Apple butterfly keyboard worked out for everyone and who built that rickety piece of garbage. Let's go back again. And here we are.Darko: Exactly. So, that's kind of the thing, right? You know, like, your computer is the best. And if you develop for it, is great, but you always have to think other people who use it. Hence, containers are great to fix one part of that problem, but not all of the problems. So, there's a bunch of stuff you can do.And I think, like, for all of the developers out there, it's great what you're doing, you're building us so many tools, but always that take a step back and optimize stuff. Optimize, both for the end-user by the amount of JavaScript you're going to throw at me, and also for the back-end, think about if you have to run your web server on a Pentium III server, could you do it? And if you could, how bad would it be? And you don't have to run it on a Pentium III, but like, try to think about what's the bottom 5% of the capacity you need? So yeah, it's just—you'll save money. That's it. You'll save money, ultimately.Corey: So, I have to ask, what you do day to day is you're a senior developer advocate, which is, hmm, some words, yes. You spend a lot of your free time and public time talking about running ancient computers, but you also talk to customers who are looking forward, not back. How do you reconcile the two?Darko: So, I like to mix the two. There's a whole reason why I like old computers. Like, I grew up in Serbia. Like, when I was young in the '90s, I didn't have any of these computers. Like, I could only see, like, what was like a Macintosh from 1997 on TV and I would just drool. Like, I wouldn't even come close to thinking about getting that, let alone something better.So, I kind of missed all of that part. But now that I started collecting all of those old computers and just everything from the '80s and '90s, I've actually realized, well, these things are not that different from something else. So, I like to always make comparisons between, like, an old system. What does it actually do? How does it compare to a new system?So, I love to mix and match in my presentations. I like to mix it, mix and match in my videos. You saw my blog posts on deploying stuff. So, I think it's just a fun way to kind of create a little contrast. I do think we should still be moving forward. I do think that technology is getting better and better and it's going to help people do so much more things faster, hopefully cheaper, and hopefully better.So, I do think that we should definitely keep on moving forward. But I always have this nostalgic feeling about, like, old things and… sometimes I don't know why, but I miss the world without the internet. And I think that without the internet, I think I miss the world with dial-up internet. Because back then you would go on the internet for a purpose. You have to do a thing, you have to wait for a while, you have to make sure nobody's on the phone. And then—Corey: God forbid you dial into a long-distance call. And you have to figure out which town and which number would be long distance versus not, at least where I grew up, and your parents would lose their freaking minds because that was an $8 phone call, which you know, back in the '80s and early '90s was significant. And yeah, great. Now, I still think is a great prank opportunity to teach kids are something that it costs more to access websites that are far away, which I guess in theory, it kind of does, but not to the end-user. I digress.Darko: I have a story about this, and I'm going to take a little sidestep. But long-distance phone calls. Like in the '80s, the World Wide Web was not yet a thing. Like, the www, the websites all, just the general purpose internet was not yet a thing. We had things called BBSes, or Bulletin Board Systems. That was the extreme version of a dial-up system.You don't dial into the internet; you dial into a website. Imagine if you have a sole intent of visiting only one website and the cost of visiting such a website would depend on where that website currently is. If the website is in Germany and you're calling from Serbia, it's going to cost you a lot of money because you're calling internationally. I had a friend back then. The best software you can get were from American BBSes, but calling America from Serbia back then would have been prohibitively expensive, like, just insanely expensive.So, what this friend used to do, he figured out if he would be connected to a BBS six hours a day, it would actually reset the counter of his phone bill. It would loop through a mechanical counter from whatever number, it would loop back again to that number. So, it would take around six and some hours to complete the loop the entire phone counting metric—whatever they use back in the '80s—to kind of charge your bill, so it's effectively cost him zero money back then. So yeah, it was more expensive, kids, back then to call websites, the further away the websites were.[midroll 00:17:11]Corey: So, developer advocates do a lot of things. And I think it is unfair, but also true that people tend to shorthand those of those things do getting on stage and giving conference talks because that at least is the visible part of it. People see that and it's viscerally is understood that that takes work and a bit of courage for those who are not deep into public speaking and those who are, know it takes a lot of courage. And whereas writing a blog post, “Well, I have a keyboard and say dumb things on the internet all the time. I don't see why that's hard.” So, there's a definite perception story there. What's your take on giving technical presentations?Darko: So, yeah. Just as you said, like, I think being a DA, even in my head was always represented, like, oh, you're just on stage, you're traveling, you're doing presentations, you're doing all those things. But it's actually quite a lot more than that, right? We do a lot more. But still, we are the developer advocate. We are the front-facing thing towards you, the wonderful developers listening to this.And we tend to be on stage, we tend to do podcasts with wonderful internet personalities, we tend to do live streams, we tend to do videos. And I think one of the key skills that a DA needs to have—a Developer Advocate needs to have—is presentations, right? You need to be able to present a technical message in the best possible way. Now, being a good technical presenter doesn't mean you're funny, doesn't mean you're entertaining, that doesn't have to be a thing. You just need to take a complex technical message and deliver it in the best way possible so that everybody who has just given you their time, can get it fully.And this means—well, it means a lot of things, but it means taking this complicated topic, distilling it down so it can be digested within 30 to 45 minutes and it also needs to be… it needs to be interesting. Like, we can talk about the most interesting topic, but if I don't make it interesting, you're just going to walk out. So, I also lead, like, a coaching class within internally, like, to teach people how to speak better and I'm working with, like, really good speakers there, but a lot of the stuff I say applies to no matter if you're a top-level speaker, or if you're, like, just beginning out. And my challenge to all of you speakers out there, like, anybody who's listening to this and it has a plan to deliver a video, a keynote, a live stream or speak at a summit somewhere, is get outside of that box. Get outside of that PowerPoint box.I'm not saying PowerPoint is bad. I think PowerPoint is a wonderful tool, but I'm just saying you don't have to present in the way everybody else presents. The more memorable your presentation is, the more outside of that box it is, the more people will remember it. Again, you don't have to be funny. You don't have to be entertaining. You just have to take thing you are really passionate about and deliver it to us in the best possible way. What that best possible way is, well, it really depends. Like a lot of things, there is no concrete answer to this thing.Corey: One of the hard parts I found is that people will see a certain technical presenter that they like and want to emulate and they'll start trying to do what they do. And that works to a point. Like, “Well, I really enjoy how that presenter doesn't read their slides.” Yeah, that's a good thing to pick up. But past a certain point, other people's material starts to fit as well as other people's shoes and you've got to find your own path.My path has always been getting people's attention first via humor, but it's certainly not the only way. In many contexts, it's not even the most effective way. It works for me in the context in which I use it, but I assure you that when I'm presenting to clients, I don't start off with slapstick comedy. Usually. There are a couple of noteworthy exceptions because clients expect that for me, in some cases.Darko: I think one of the important things is that emulating somebody is okay, as you said, to an extent, like, just trying to figure out what the good things are, but good, very objectively good things. Never try to be funny if you're not funny. That's the thing where you can try comedy, but it's very difficult to—it's very difficult to do comedy if you're not that good at it. And I know that's very much a given, but a lot of people try to be funny when they're obviously not funny. And that's okay. You don't have to be funny.So, there are many of ways to get people's attentions, by again, just throwing a joke. What I did once on stage, I threw a bottle at the floor. I was just—I said, I said a thing and threw a bottle at the floor. Everybody started paying attention all of a sudden at me. I don't know why. So, it's going to be that. It can be something—it can be be a shocking statement. When I say shocking, I mean, something, well, not bad, but something that's potentially controversial. Like, for example, emacs is better than vim. I don't know, maybe—Corey: “Serverless is terrible.”Darko: Serverl—yeah.Corey: Like, it doesn't matter. It depends on the audience.Darko: It depends on the audience.Corey: “The cloud is a scam.” I gave a talk once called, “The Cloud is A Scam,” and it certainly got people's attention.Darko: Absolutely. So, breaking up the normal flow because as a participant of a show, of a presentation, you go there you expect, look, I'm going to sit down, Corey's going to come on stage and Corey says, “Hi, my name is Corey Quinn. I'm the CEO of The Duckbill Group. This is what I do. And welcome to my talk about blah.”Corey: Tactically, my business partner, Mike, is the CEO. I don't want to I don't want to step too close to that fire, let's be clear.Darko: Oh, okay [laugh]. Okay. Then, “Today's agenda is this. And slide one, slide two, slide three.” And that the expectation of the audience. And the audience comes in in this very autopilot way, like, “Okay, I'm just going to sit there and just nod my head as Corey speaks.”But then if Corey does a weird thing and Corey comes out in a bathtub. Just the bathtub and Corey. And Corey starts talking about how bathtubs are amazing, it's the best place to relax. “Oh, by the way, managing costs in the cloud is so easy, I can do it from a bathtub.” Right? All of a sudden, whoa [laugh], wait a second, this is something that's interesting. And then you can go through your rest of your conversation. But you just made a little—you ticked the box in our head, like, “Oh, this is something weird. This is different. I don't know what to expect anymore,” and people start paying more attention.Corey: “So, if you're managing AWS costs from your bathtub, what kind of computer do you use?” “In my case, a toaster.”Darko: [laugh]. Yes. But ultimately, like, some of those things are very good and they just kind of—they make you as a presenter, unpredictable, and that's a good thing. Because people will just want to sit on the edge of the seat and, like, listen to what you say because, I don't know what, maybe he throws that toaster in, right? I don't know. So, it is like that.And one of the things that you'll notice, Corey, especially if you see people who are more presenting for a longer time, like, they've been very common on events and people know them by name and their face, then that turns into, like, not just presenting but somebody comes, literally not because of the topic, but because they want to hear Corey talk about a thing. You can go there and talk about unicorns and cats, people will still come and listen to that because it's Corey Quinn. And that's where you, by getting outside of that box, getting outside of that ‘this is how we present things at company X,' this is what you get in the long run. People will know who you are people will know, what not to expect from your presentations, and they will ultimately be coming to your presentations to enjoy whatever you want to talk about.Corey: That is the dream. I really want to thank you for taking the time to talk so much about how you view the world and the state of ancient and modern technologies and the like. If people want to learn more, where's the best place for them to find you?Darko: The best way to find me is on twitch.tv/aws these days. So, you will find me live streaming twice a week there. You will find me on Twitter at @darkosubotica, which is my Twitter handle. You will find me at the same handle on Mastodon. And just search for my name Darko Mesaroš, I'm sure I'll pop up on MySpace as well or whatever. So, I'll post a lot of cloud-related things. I posted a lot of old computer-related things, so if you want to see me deploy Kubernetes through an Atari 2600, click that subscribe button or follow or whatever.Corey: And we will, of course, include a link to this in the show notes. Thank you so much for being so generous with your time. I appreciate it.Darko: Thank you so much, Corey, for having me.Corey: Darko Mesaroš, senior developer advocate at AWS, 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 and insulting comment that you compose and submit from your IBM Selectric typewriter.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.

We surprise each other with three secret topics, with one big catch.

Hard hitting news and current affairs - sort of! The Guitar Speak 'Iconic' series team assemble to talk through some recent noise in guitar-land including Bad Monkey hype, reissue pedals from Marshall and DOD, new music from Nuno, Fender's Gold Foil series, isolated Jimi tracks and much more! TheSuperFunAwesomeHappytimePedalShow Punkifriar Vs Everything! Check out PastFX! Rob Rhodes - www.rhodetripent.com Gabor Josika - SuperFunAwesomeHappyTime Pedal Show   This episode is brought to you by Fretboard Biology    Fretboard Biology - the online guitar college created by Joe Elliott, ex Head of Guitar at GIT and McNally Smith Music College. Fretboard Biology Guitar Speak Podcast #146 - Joe Elliott - ex guitar head of GIT - launches Fretboard Biology Guitar Speak Podcast Links PayPal Tip Jar Visit us at guitarspeakpodcast.com Subscribe and find previous episodes at: Apple Podcasts Spotify Stitcher   Follow us on Instagram

Tip #1 never sleep with a cloud. Tip #2 NEVER serve a centaur wine. Git up and tune in for more survival tips! Events: Full Year: https://fancons.com/events/ Tampa Bay Screams 2023 April 14-15, 2023 Holiday Inn Tampa Westshore - Airport Area Tampa, FL Chicago Steampunk Exposition 2023 April 14-16, 2023 Hyatt Regency Schaumburg, Chicago Schaumburg, IL Furcationland 2023 April 14-16, 2023 Holiday Inn Portland-by the Bay Portland, ME Grand Rapids Comic-Con 2023 April 14-16, 2023 DeltaPlex Arena & Conference Center Walker, MI Las Vegas Fur Con 2023 April 14-16, 2023 Alexis Park All Suite Resort Las Vegas, NV Monster-Mania Con 2023 April 14-16, 2023 Delta Hotels Baltimore Hunt Valley Hunt Valley, MD Motor City Legacy 2023 April 14-16, 2023 Sheraton Detroit Metro Airport Romulus, MI Neon Retrofest 2023 April 14-16, 2023 Hotel Alba Tampa Tampa, FL

Joël submitted a last-minute submission to RailsConf discreet math, which got picked up!

Ken Thompson's 75-year-project is a jukebox for the ages, Tabby is a self-hosted AI coding assistant, Codeberg is a collaboration platform and Git hosting for open source software, content and projects, TheSequence explains The LLama Effect & Paul Orlando writes about Ghosts, Guilds and Generative AI.

In this episode, Donn and Kaushik talk to long-time friend Dan Lew about his recent career switch from Android developer to TypeScript/Node.js/Progressive Web App Developer (and more).It's an interesting discussion that covers ...Why Dan decided to leave the Android worldThe challenges he faced when he moved from one tech stack to anotherHow to prepare for a big change like this (mentally, financially, etc.)How to create the life you want live vi by identifying what's important to youand much more ...LinksRheaplyDonn's Git CourseNeed to learn Git? Donn has the course for you. In this FREE course, you'll learn everything you need to know to start working with Git everyday. Watch it here.AndroidJobs.IOJob postings are FREE on AndroidJobs.IO during the early release phase (at the time of this recording).Sign up to get notified of new jobs every week as well.AndroidJobs.IOSoftware FreelancingDonn's Freelance Faction CommunityFreelance Tactics BookDonn's Freelancing Content on YouTubeContact@fragmentedcast or our Youtube channel@donnfelker and donnfelker (on Instagram)Freelancing for Mobile Developers (Donn's YouTube)kaushikgopal (on YouTube) or kau.sh/blog or @kaushikgopalDisclaimer: Many of the links we share to products are affiliate links. They help support the production of Fragmented. Thank you for your support.

'Oğlunuzun erkek arkadaşıyla evlenmesini ister misiniz?' sorusu, kendini pek zeki zanneden birinin son derece beceriksiz bir 'tuzak' sorusu aslında. O tuzağa düşecek tilkiyi elinizle de yakalayabilirdiniz zaten. Ama cevabı şu: 'Sana ne!' Daha da önemlisi 'Bana ne!' Oğlumun ya da kızımın kiminle (cinsiyeti her ne olursa olsun) evleneceğine karışmam. Ama gelip bana 'Baba, memlekette jelibon yatakları bulunmuş, yatırım yapsam mı acaba?' diye sorarsa verecek cevabım var: 'Git işine, salak mısın sen!'

Linda and Dave chat again with Jay Clifford, Developer Advocate at InfluxData. InfluxData are the makers of InfluxDB, a popular open-source platform for simplifying time series data management. Designed to handle high speed and high volume data ingest and real-time data analysis, InfluxDB's robust data collectors, common API across the entire platform, highly performant time series engine, and optimized storage lets you build once and deploy across multiple products and environments. In part two of this conversation, Jay gives us a pop quiz on time series data, offers best practices for developers on handling time series data, shares some real-world customer success stories, and covers handling visualization with time series data. If you missed part one, you can listen in with Episode 76. Follow Jay on LinkedIn: https://www.linkedin.com/in/jaymand13/ Jay on Git: https://github.com/Jayclifford345 Linda on Twitter: https://twitter.com/lindavivah Linda's Website: https://lindavivah.com/ Linda on TikTok: https://www.tiktok.com/@lindavivah Linda on Instagram: https://www.instagram.com/lindavivah/ Linda's Medium: https://medium.com/@LindaVivah [DOCS] InfluxDB Cloud Powered by IOX -https://docs.influxdata.com/influxdb/cloud-iox/get-started/ [GIT] InfluxData Telegraf Plugins & Integrations - https://github.com/influxdata/telegraf [GIT] InfluxDB OSS - https://github.com/influxdata/influxdb [PORTAL] InfluxData Website - https://www.influxdata.com [PORTAL] InfluxData Cloud Signup - https://cloud2.influxdata.com/signup [PORTAL] InfluxDB Use Cases - https://www.influxdata.com/customers/ [PORTAL] Pandas - https://pandas.pydata.org/ [SLACK] InfluxData Community Slack - https://www.influxdata.com/slack (connect with Jay @JayClifford) [TRAINING] InfluxDB University (Free InfluxDB Training) - https://university.influxdata.com Subscribe: Amazon Music: https://music.amazon.com/podcasts/f8bf7630-2521-4b40-be90-c46a9222c159/aws-developers-podcast Apple Podcasts: https://podcasts.apple.com/us/podcast/aws-developers-podcast/id1574162669 Google Podcasts: https://podcasts.google.com/feed/aHR0cHM6Ly9mZWVkcy5zb3VuZGNsb3VkLmNvbS91c2Vycy9zb3VuZGNsb3VkOnVzZXJzOjk5NDM2MzU0OS9zb3VuZHMucnNz Spotify: https://open.spotify.com/show/7rQjgnBvuyr18K03tnEHBI TuneIn: https://tunein.com/podcasts/Technology-Podcasts/AWS-Developers-Podcast-p1461814/ RSS Feed: https://feeds.soundcloud

Marlin is back and ready to throw this simmering Pot RIGHT in yalls faces! lol Git yo ass in here! --- Support this podcast: https://podcasters.spotify.com/pod/show/wryhpodcast/support

Following up the Charvel signature love shared in episode #22o with Prashant Aswani, we look back at Guthrie Govan's interview with us in this GSP classic. Guthrie Govan is - with good reason - one of the most celebrated voices of the modern guitar era. Guthrie joins us from his tour with Hans Zimmer to discuss his relationship with the legendary film composer, fresh music and tours from The Aristocrats, a look behind the latest Charvel Guthrie Govan Signature Model, listener questions and more. First published in March 2022.     This episode is brought to you by Fretboard Biology - the online guitar college created by Joe Elliott, ex head of guitar at GIT and McNally Smith Music College. Fretboard Biology Guitar Speak Podcast #146 - Joe Elliott - ex guitar head of GIT - launches Fretboard Biology Guitar Speak Podcast #40 - Joe Elliott   Guitar Speak Podcast Links PayPal Tip Jar Visit us at guitarspeakpodcast.com Subscribe and find previous episodes at: Apple Podcasts Spotify Stitcher   Follow us on Instagram   Contact us at guitarspeakpodcast@gmail.com

On this episode of Ruby for All, Andrew and Julie welcome Mike Munroe, Co-founder of OBLSK, a Rails consultancy, who's here today to discuss their Junior Developer Apprentice Program. Today, we'll learn all the details about the program, the importance of having a mentor and a framework in place to guide the Junior developer's progress, and how Mike believes with the right mentorship, a Junior developer can become independent and self-sustaining within a year. There's a conversation on how remote mentorship differs from in-person mentorship, and some strategies to help Juniors ask for help. He also talks about the importance of not stressing about time, encourages the exploration of learning, and why Mike believes for Juniors to be successful there has to be passion. Press download the hear much more! [00:01:01] Mike tells us what OBLSK is and his background in programming. [00:03:10] If you want to hear about the Apprentice Program, Mike gives us all the details and how he believes it's important to invest in Junior developers and support them.  [00:08:56] We hear how Mike thinks that a Junior developer, with the right mentorship, can become independent and self-sustaining within a year. [00:12:46] Julie tells us she is good about reaching put for help when she's stuck on something but feels like many people may have a problem with reaching out,  Mike shares some tactics to help Juniors ask for help, such as asking any questions at any time, even if you think it's a “stupid question, and put code into GitHub.[00:18:04] Andrew highlights something Mike said, and he strongly believes in, is that if a Junior has a question, invite that Junior into the room for the meeting to be a part of the team. [00:19:01] Mike stresses the importance of leaders showing vulnerability and humility to make Juniors feel more comfortable.  [00:00:00] A great piece of advice Mike shares for Juniors is not letting time be a stressor, also taking breaks and pursue tangents to keep the process fun and positive.[00:24:14] We learn why Mike believes for Juniors to be successful there has to be passion.[00:26:46] With the current Junior Apprentice who's gone through the program, Julie wonders how the program has been for him, and Mike explains some of the struggles with Git and Front-End Technologies.[00:29:43] Find out where you can follow Mike on the web. Panelists:Andrew MasonJulie J.Guest:Mike MunroeSponsors:GoRailsHoneybadgerLinks:Andrew Mason TwitterAndrew Mason WebsiteJulie J. TwitterJulie J. WebsiteMike Munroe TwitterMike Munroe LinkedInOBLSKOBLSK 30/60/90 Apprenticeship Program

How it works https://docs.gitlab.com/ee/user/project/pages/ GitLab always deploys your website from a specific folder called public in your repository. To deploy your site, GitLab uses its built-in tool called GitLab CI/CD to build your site and publish it to the GitLab Pages server. The sequence of scripts that GitLab CI/CD runs to accomplish this task is created from a file named .gitlab-ci.yml, which you can create and modify. A specific job called pages in the configuration file makes GitLab aware that you're deploying a GitLab Pages website. Overview of Steps The end state has to be a directory named public that contains the site contents Optionally, run a build process in a container to create the contents of the public directory There has to be a pages declaration in .gitlab-ci.yml Example 1 simple demo Create the Git repo and site content Go to gitlab and create new Gitlab repo Clone it to your workstation Add public folder with site files add .gitlab-ci.yml Commit and push git clone git@gitlab.com:norrist/simple_pages_demo.git cd simple_pages_demo/ mkdir public echo "Hello World" > public/index.html git add public/ vim .gitlab-ci.yml git add .gitlab-ci.yml git commit -am "new page" git push .gitlab-ci.yml pages: stage: deploy script: - echo artifacts: paths: - public Pages settings Menu on left, Settings, Pages Your pages are served under: Example 2 docs.norrist.xyz Combine my HPR show notes into a single page Custom Domain Verified with TXT record .gitlab-ci.yml image: "debian" before_script: - apt-get update - apt-get install -y pandoc stages: - build pages: stage: build script: - bash build_html.sh artifacts: paths: - public set -euo pipefail IFS=$'nt' mkdir -pv public for MD in $(ls *md) do echo # echo "---" # echo # echo "#" $MD echo echo "---" echo cat $MD done |pandoc -H markdown.header -B body.header --toc --toc-depth=1 -f gfm -t html -o public/index.html Example 3 HPR static Build the new HPR static site .gitlab-ci.yml services: - mariadb variables: MYSQL_DATABASE: hpr_hpr MYSQL_ROOT_PASSWORD: mysql connect: stage: .pre image: mysql script: - echo "SELECT 'OK';" | mysql --user=root --password="$MYSQL_ROOT_PASSWORD" --host=mariadb "$MYSQL_DATABASE" pages: image: debian before_script: - apt update - apt -y install libgetopt-complete-perl libmemory-usage-perl libconfig-std-perl libtemplate-perl libtemplate-plugin-dbi-perl libclass-dbi-perl libtie-dbi-perl libdbd-mysql-perl libdate-calc-perl - apt -y install curl mariadb-client git - curl -o hpr.sql http://hackerpublicradio.org/hpr.sql - mysql --user=root --host=mariadb "$MYSQL_DATABASE" --password="$MYSQL_ROOT_PASSWORD" < hpr.sql stage: build script: - git clone https://gitlab.com/roan.horning/hpr_generator.git - cd hpr_generator - git apply ../mysql_settings.patch - grep "database|user|driver|password" site.cfg - ./site-generator --all - mv -v public_html ../public artifacts: paths: - public site.cfg Patch diff --git a/site.cfg b/site.cfg index aefadb2..0243d27 100644 --- a/site.cfg +++ b/site.cfg @@ -8,10 +8,10 @@ #user: (not used - leave blank) #password: (not used - leave blank) # Configuration settings for MySQL -#database: mysql -#driver: dbi:mysql:database=hpr_hpr:hostname=localhost -#user: hpr-generator (Suggested user with read-only privileges) -#password: ********* (Password for user) +database: mysql +driver: dbi:mysql:database=hpr_hpr:hostname=mariadb +user: root +password: mysql # Configure the location of the templates and the generated HTML [app_paths] @@ -25,7 +25,7 @@ output_path: ./public_html [root_template] content: page.tpl.html #baseurl: OPTIONAL [i.e. file://] -baseurl: file:///home/roan/Development/hpr/website/hpr_generator/public_html/ +baseurl: https://norrist.gitlab.io/hpr_generator_build/ media_baseurl: https://archive.org/download/hpr$eps_id/ # Configure the navigation menu and the content templates for each page Other Example Projects https://gitlab.com/pages Hugo, Jekyll, Plain HTML, ... Fork or just Copy Common Frustrations Waiting on builds during debugging. Having to push to CICD instead of running local Links HPR Generator - https://repo.anhonesthost.net/rho_n/hpr_generator Gitlab Example Repo Gitlab pages URL https://gitlab.com/norrist/simple_pages_demo https://norrist.gitlab.io/simple_pages_demo/ https://gitlab.com/norrist/docs.norrist.xyz https://docs.norrist.xyz/ https://gitlab.com/norrist/hpr_generator_build https://norrist.gitlab.io/hpr_generator_build/

Lex Neva, Staff Site Reliability Engineer at Honeycomb and Curator of SRE Weekly, joins Corey on Screaming in the Cloud to discuss reliability and the life of a newsletter curator. Lex shares some interesting insights on how he keeps his hobbies and side projects separate, as well as the intrusion that open-source projects can have on your time. Lex and Corey also discuss the phenomenon of newsletter curators being much more demanding of themselves than their audience typically is. Lex also shares his views on how far reliability has come, as well as how far we have to go, and the critical implications reliability has on our day-to-day lives. About LexLex Neva is interested in all things related to running large, massively multiuser online services.  He has years of SRE,  Systems Engineering, tinkering, and troubleshooting experience and perhaps loves incident response more than he ought to.  He's previously worked for Linden Lab, DeviantArt, Heroku, and Fastly, and currently works as an SRE at Honeycomb while also curating the SRE Weekly newsletter on the side.Lex lives in Massachusetts with his family including 3 adorable children, 3 ridiculous cats, and assorted other awesome humans and animals.  In his copious spare time he likes to garden, play tournament poker, tinker with machine embroidery, and mess around with Arduinos.Links Referenced: SRE Weekly: https://sreweekly.com/ Honeycomb: https://www.honeycomb.io/ TranscriptAnnouncer: Hello, and welcome to Screaming in the Cloud with your host, Chief Cloud Economist at The Duckbill Group, Corey Quinn. This weekly show features conversations with people doing interesting work in the world of cloud, thoughtful commentary on the state of the technical world, and ridiculous titles for which Corey refuses to apologize. This is Screaming in the Cloud.Corey: This episode is sponsored in part by our friends at Chronosphere. Tired of observability costs going up every year without getting additional value? Or being locked into a vendor due to proprietary data collection, querying, and visualization? Modern-day, containerized environments require a new kind of observability technology that accounts for the massive increase in scale and attendant cost of data. With Chronosphere, choose where and how your data is routed and stored, query it easily, and get better context and control. 100% open-source compatibility means that no matter what your setup is, they can help. Learn how Chronosphere provides complete and real-time insight into ECS, EKS, and your microservices, wherever they may be at snark.cloud/chronosphere that's snark.cloud/chronosphere.Corey: Welcome to Screaming in the Cloud. I'm Corey Quinn. Once upon a time, I decided to start writing an email newsletter, and well, many things happened afterwards, some of them quite quickly. But before that, I was reading a number of email newsletters in the space. One that I'd been reading for a year at the time, was called SRE Weekly. It still comes out. I still wind up reading it most weeks.And it's written by Lex Neva, who is not only my guest today but also a staff site reliability engineer at Honeycomb. Lex, it is so good to finally talk to you, other than reading emails that we send to the entire world that pass each other like ships in the night.Lex: Yeah. I feel like we should have had some kind of meeting before now. But yeah, it's really good to [laugh] finally meet you.Corey: It was one of the inspirations that I had. And to be clear, when I signed up for your newsletter originally—I was there for issue 15, which is many, many years ago—I was also running a small-scale SRE team at the time. It was, I found as useful as a part of doing my job and keeping abreast of what was going on in the ecosystem. And I found myself, once I went independent, wishing that your newsletter and a few others had a whole bunch more AWS content. Well, why doesn't it?And the answer is because you are, you know, a reasonable person who understands that mental health is important and boundaries exist for a reason. No one sensible is going to care that much about one cloud provider all the time [sigh]. If only we were all that wise.Lex: Right? Well, [laugh] well, first of all, I love your newsletter, and also the content that you write that—I mean, I would be nowhere without content to link to. And I'm glad you took on the AWS thing because, much like how I haven't written Security Weekly, I also didn't write any kind of AWS Weekly because there's just too much. So, thanks for falling on that sword.Corey: I fell on another one about two years ago and started the Thursdays, which are Last Week in AWS Security. But I took a different bent on it because there are a whole bunch of security newsletters that litter the landscape and most of them are very good—except for the ones that seem to be entirely too vendor-captured—but the problem is, is that they lacked both a significant cloud focus, as well as an understanding that there's a universe of people out here who care about security—or at least should—but don't have the word security baked into their job title. So, it was very insular, using acronyms they assume that everyone knows, or it's totally vendor-captured and it's trying to the whole fear, uncertainty, and doubt thing, “And that's why you should buy this widget.” “Will it solve problems?” “Well, it'll solve our revenue problems at our company that sells the widgets, but other than that, not really.” And it just became such an almost incestuous ecosystem. I wanted something different.Lex: Yeah. And the snark is also very useful [laugh] in order to show us that you're not in their pocket. So yeah, nice work.Corey: Well, I'll let you in on a secret, now that we are—what, I'm somewhat like 300 and change issues in, which means I've been doing this for far too long, the snark is a byproduct of what I needed to do to write it myself. Because let's face it, this stuff is incredibly boring. I needed to keep myself interested as I started down that path. And how can I continually keep it fresh and funny and interesting, but not go too far? That's a fun game, whereas copying and pasting some announcement was never fun.Lex: Yeah, that's not—I hear you on trying to make it interesting.Corey: One regret that I've had, and I'm curious if you've ever encountered this yourself because most people don't get to see any of this. They see the finished product that lands in their inbox every Monday, and—in my case, Monday; I forget the exact day that yours comes out. I collect them and read through them for them all at once—but I find that I have often had caused a look back and regret the implicit commitment in Last Week in AWS as a name because it would be nice to skip a week here and there, just because either I don't particularly feel like it, or wow, there was not a lot of news worth talking about that came out last week. But it feels like I've forced myself onto a very particular treadmill schedule.Lex: Yeah. Yeah, it comes with, like, calling it SRE Weekly. I just followed suit for some of the other weeklies. But yeah, that can be hard. And I do give myself permission to take a week off here and there, but you know, I'll let you in on a secret.What I do is I try to target eight to ten articles a week. And if I have more than that, I save some of them. And then when it comes time to put out an issue, I'll go look at what's in that ready queue and swap some of those in and swap some of the current ones out just so I keep things fresh. And then if I need a week off, I'll just fill it from that queue, you know, if it's got enough in it. So, that lets me take vacations and whatnot. Without that, I think I would have had a lot harder of a time sticking with this, or there just would have been more gaps. So yeah.Corey: You're fortunate in that you have what appears to be a single category of content when you construct your newsletter, whereas I have three that are distinct: AWS releases and announcements and news and things to make fun of for the past week; the things from the larger community folks who do not work there, but are talking about interesting approaches or news that is germane; and then ideally a tip or a tool of the week. And I found, at least lately, that I've been able to build out the tools portion of it significantly far in advance. Because a tool that makes working with AWS easier this week is probably still going to be fairly helpful a month from now.Lex: Yeah, that's fair. Definitely.Corey: But putting some of the news out late has been something of a challenge. I've also learned—by getting it wrong—that I'm holding myself to a tighter expectation of turnaround time than any part of the audience is. The Thursday news is all written the week before, almost a full week beforehand and no one complains about that. I have put out the newsletter a couple of times an hour or two after its usual 7:30 pacific time slot that it goes out in; not a single person has complained. In one case, I moved it by a day to accommodate an announcement but didn't explain why; not a single person emailed in. So, okay. That's good to know.Lex: Yeah, I've definitely gotten to, like, Monday morning, like, a couple of times. Not much, not many times, but a couple of times, I've gotten a Monday morning be like, “Oh, hey. I didn't do that thing yesterday.” And then I just release it in the morning. And I've never had a complaint.I've cancelled last minute because life interfered. The most I've ever had was somebody emailing me and be like, you know, “Hope you feel better soon,” like when I had Covid, and stuff like that. So, [laugh] yeah, sometimes maybe we do hold ourselves to a little bit of a higher standard than is necessary. I mean, there was a point where I got—I had major eye surgery and I had to take a month off of everything and took a month off the newsletter. And yeah, I didn't lose any subscribers. I didn't have any complaints. So people, I think, appreciate it when it's there. And, you know, if it's not there, just wait till it comes out.Corey: I think that there is an additional challenge that I started feeling as soon as I started picking up sponsors for it because it's well, but at this point, I have a contractual obligation to put things out. And again, life happens, but you also don't want to have to reach out on apology tours every third week or whatnot. And I think that's in part due to the fact that I have multiple sponsors per issue and that becomes a bit of a juggling dance logistically on this end.Lex: Yeah. When I started, I really didn't think I necessarily wanted to have sponsors because, you know, it's like, I have a job. This is just for fun. It got to the point where it's like, you know, I'll probably stop this if there's not some kind of monetary advantage [laugh]. And having a sponsor has been really helpful.But I have been really careful. Like, I have always had only a single sponsor because I don't want that many people to apologize to. And that meant I took in maybe less money than I then I could have, but that's okay. And I also was very clear, you know, even from the start having a contract that I may miss a week without notice. And yes, they're paying in advance, but it's not for a specific range of time, it's for a specific number of issues, whenever those come out. That definitely helped to reduce the stress a little bit. And I think without that, you know, having that much over my head would make it hard to do this, you know? It has to stay fun, right?Corey: That's part of the things that kept me from, honestly, getting into tech for the first part of my 20s. It was the fear that I would be taking a hobby, something that I love, and turning it into something that I hated.Lex: Yeah, there is that.Corey: It's almost 20 years now and I'm still wondering whether I actually succeeded or not in avoiding hating this.Lex: Well, okay. But I mean, are you, you know, are you depressed [unintelligible 00:09:16] so there's this other thing, there's this thing that people like to say, which is like, “You should only do a job that you really love.” And I used to think that. And I don't actually think that anymore. I think that it is important to have a job that you can do and not hate day-to-day, but there's no shame in not being passionate about your work and I don't think that we should require passion from anyone when we're hiring. And I think to do so is even, like, privilege. So, you know, I think that it's totally fine to just do something because it pays the bills.Corey: Oh, absolutely. I find it annoying as hell when I'm talking to folks who are looking to hire for roles and, “Well, include a link to your GitHub profile,” is a mandatory field. It's, well, great. What about people who work in places where they're not working on open-source projects as a result, and they can't really disclose what they're doing? And the expectation that oh, well outside of work, you should be doing public stuff, too.It's, I used to do a lot of public open-source style work on GitHub, but I got yelled at all the time for random, unrelated reasons and it's, I don't want to put something out there that I have to support and people start to ask me questions about. It feels like impromptu unasked-for code review. No, thanks. So, my GitHub profile looks fairly barren.Lex: You mean like yelling at you, like, “Oh, you're not contributing enough.” Or, you know, “We need this free thing you're doing, like, immediately,” or that kind of thing?Corey: Worse than that. The worst example I've ever had for this was when I was giving a talk called “Terrible Ideas in Git,” and because I wanted to give some hilariously contrived demos that took a fair bit of work to set up, I got them ready to go inside of a Docker container because I didn't trust that my laptop would always work, I'm might have to borrow someone else's, I pushed that image called “Terrible Ideas” up to Docker Hub. And I wound up with people asking questions about it. Like, “Is this vulnerable to ShellCheck.” And it's, “You do realize that this is intentionally designed to be awful? It is only for giving a very specific version of a very specific talk. It's in public, just because I didn't bother to make it private. What are you doing? Please tell me you're not running this in production at a bank?” “No comment.” Right. I don't want that responsibility of people yelling at me for things I didn't do on purpose. I want to get yelled at for the things I did intentionally.Lex: Exactly. It's funny that sometimes people expect more out of you when you're giving them something free versus when they're paying you for it. It's an interesting quirk of psychology that I'm sure that professionals could tell me all about. Maybe there's been research on it, I don't know. But yeah, that can be difficult.Corey: Oh, absolutely. I used to work at a web hosting company and the customer spending thousands a month with us were uniformly great. But there was always the lowest tier customer of the cheapest thing that we offered that seemed to expect that that entitle them to 80 hours a month of support from engineering problems and whatnot. And it was not profitable to service some of those folks. I've also found that there's a real transitive barrier that begins as soon as you find a way to charge someone a dollar for something.There's a bit of a litmus test of can you transfer a dollar from your bank account to mine? And suddenly, the entire tenor of the conversations with people who have crossed that boundary change. I have toyed, on some level, with the idea of launching a version of this newsletter—or wondering if I retcon the whole thing—do I charge people to subscribe to this? And the answer I keep coming away with is not at all because it started in many respects is marketing for AWS bill consulting and I want the audience as fast as possible. Artificially limiting its distribution via a pay-for model just seemed a little on the strange side.Lex: Yeah. And then you're beholden to a very many people and there's that disproportionality. So, years ago, before I even started in my career in I guess, you know, things that were SRE before SRE was cool, I worked for a living in Second Life. Are you familiar with Second Life?Corey: Oh, yes. I'm very familiar with that. Linden Labs.Lex: Yep. So, I worked for Linden Lab years later, but before I worked for them, I sort of spent a lot of my time living in Second Life. And I had a product that I sold for two or three dollars. And actually, it's still in there; you could still buy it. It's interesting. I don't know if it's because the purchase price was 800 Linden dollars, which equates to, like, $2.16, or something like that, but—Corey: The original cryptocurrency.Lex: Right, exactly. Except there's no crypto involved.Corey: [laugh].Lex: But people seem to have a disproportionate amount of, like, how much of my time they expected for support. You know, I'm going to support them a little bit. You have to recognize at some point, I actually can't come give you a tutorial on using this product because you're one of 500 customers for this month. And you give me two dollars and I don't have ten hours to give you. You know, like, sorry [laugh]. Yeah, so that can be really tough.Corey: And on some level, you need to find a way to either charge more or charge for support on top of it, or ideally—it I wish more open-source projects would take this approach—“Huh. We've had 500 people asking us the exact same question. Should we improve our docs? No, of course not. They're the ones who are wrong. It's the children who are getting it wrong.”I don't find that approach [laugh] to be particularly useful, but it bothers me to no end when I keep running into the same problem onboarding with something new and I ask about it, and, “Oh, yeah, everyone runs into that problem. Here's how you get around it.” This would have been useful to mention in the documentation. I try not to ask questions without reading the manual first.Lex: Well, so there's a couple different directions. I could go with this. First of all, there's a really interesting thing that happened with the core-js project that I recommend people check out. Another thing that I think the direction I'll go at the moment—we can bookmark that other one, but I have an open-source project on the side that I kind of did for my own fun, which is a program for creating designs that can be processed by computer-controlled embroidery machines. So, this is sewing machines that can plot stitches in the x-y plane based on a program that you give it.And there really wasn't much in the way of open-source software available that could help you create these designs and so I just sort of hack something together and started hacking with Python for my own fun, and then put it out there and open-sourced. And it's kind of taken off, kind of like gotten a life of its own. But of course, I've got a newsletter, I've got three kids, I've got a family, and a day job, and I definitely hear you on the, like, you know, yeah, we should put this FAQ in the docs, but there can be so little time to even do that. And I'm finding that there's, like—you know, people talk about work-life balance, there's, like, work slash life slash open-source balance that you really—you know, you have to, like, balance all three of them.And a lot of weeks, I don't have any time to spend on the project. But you know what, it's still kicks along and people just kind of, they use my terrible little project [laugh] as best they can, even though it has a ton of rough edges. I'm sorry, everyone, I'm so sorry. I know it has a t—the UI is terrible. But yeah, it's interesting how these things sometimes take on a life of their own and you can feel dragged along by your own open-source work, you know?Corey: It always bothers me—I think this might tie back to the core-js issue you talked about a second ago—where there are people who are building and supporting open-source tools or libraries that they originally constructed to scratch an itch and now they are core dependencies of basically half the internet. And these people are still wondering on some level, how do I put food on the table this month? It's wild to me. If there were justice in the world, you'd start to think these people would wind up in never-have-to-work-again-if-they-don't-want-to positions. But in many cases, it's exactly the opposite.Lex: Well, that's the really interesting thing. So, first of all, I'm hugely privileged to have any time to get to work on open-source. There's plenty of people that don't, and yeah, so requiring people to have a GitHub link to show their open-source contributions is inherently unfair and biased and discriminatory. That aside, people have asked all along, like, “Lex, this is decent software, you could sell this. You could charge money for this thing and you could probably make a, you know, a decent living at this.”And I categorically refuse to accept money for that project because I don't want to have to support it on a commercial level like that. If I take your money, then you have an expectation that—especially if I charge what one would expect—so this software, part of the reason I decided to write my own is because it starts at two-hundred-some-off dollars for the competitors that are commercial and goes up into the five, ten-thousand dollars. For a software package. Mine is free. If I started charging money, then yeah, I'm going to have to build a support department and we're going to have a knowledge base, I'm going to have to incorporate. I don't want to do that for something I'm doing for fun, you know? So yeah, I'm going to keep it free and terrible [laugh].Corey: It becomes something you love, turns into something you hate without even noticing that it happens. Or at least something that you start to resent.Lex: Yeah. I don't think I would necessarily hate machine embroidery because I love it. It's an amazingly fun little quirky hobby, but I think it would definitely take away some of the magic for me. Where there's no stress at all, I can spend months noodling on an algorithm getting it right, whereas it'd be, you know, if I start having to have deliverables, it changes it entirely. Yeah.Corey: It's odd, it seems, on some level too, that the open-source world that I got started with has evolved in a whole bunch of different ways. Whereas it used to be write a quick fix for something and it would get merged, in many cases by the time you got back from lunch. And these days, it seems like it takes multiple weeks, especially with a corporate-controlled open-source project, and there's so much back and forth. And even getting the boilerplate, like the CLI—the Contributor License Agreement—aside and winding up getting other people to sign off on it, then there's back and forth, in some cases for weeks about, well, the right kind of test coverage and how to look at this and the right holistic framework. And I appreciate that there is validity and value to these things, but is that the bulk of the effort should be going when there's a pull request ready to go that solves a breaking customer problem?But the test coverage isn't right so we're going to delay it for two or three releases. It's what are you doing there? Someone lost the plot somewhere. And I'm sure there are reasons that makes sense, given the framework people are operating within. I just find it maddening from the side of having to [laugh] deal with this as a human.Lex: Yeah, I hear you. And it sometimes can go even beyond test coverage to something like code style, you know? It's like, “Oh, that's not really in the style of this project,” or, “You know, I would have written it this way.” And one thing I've had to really work on, on this project is to make it as inviting to developers as possible. I have to sometimes look at things and be like, yeah, I might do that a different way. But does that actually matter? Like, do I have a reason for that that really matters or is it just my style? And maybe because it's a group project I should just be like, no, that's good as it is.[midroll 00:20:23]Corey: So, you've had an interesting career. And clearly you have opinions about SRE as a result. When I started seeing that you were the author of SRE Weekly, years ago, I just assumed something that I don't believe is true. Is it possible that you have been contributing to the community around SRE, but somehow have never worked at Google?Lex: I have never worked at Google. I have never worked at Netflix. I've never worked at any of those big companies. The biggest company I've worked for is Salesforce. Although I worked for Heroku who had been bought by Salesforce a couple of years prior, and so it was kind of like working for a startup inside a big company. And here's the other thing. I created that newsletter two months after starting my first job where I had a—like, the first job in which I was titled ‘SRE.' So, that's possibly contentious right there.Corey: You know, I hadn't thought of it this way, but you're right. I did almost the exact same thing. I was no expert in AWS when I started these things. It came out of an effort that I needed to do of keeping touch with everything that came out that had potential economic impact, which it turns out are most things when you understand architecture and cost are the same thing when it comes to cloud. But I was more or less gathering what smart people were saying.And somehow there's been this osmotic effect, where people start to view me as the wise old sage of the mountain when it comes to AWS. And no, no, no, I'm just old and grumpy. That looks alike. Don't mistake it for wisdom. But people will now seek me out to get my opinion on things and I have no idea what the answer looks like for most of the stuff.But that's the old SRE model—or sysadmin model that I've followed, which is when you don't know the answer, well, how do you get to a place where you can find the answer? How do you troubleshoot this? Click the button. It doesn't work? Well, time to start taking the button apart to figure out why.Lex: Yeah, definitely. I hear you on people. So, first of all, thanks to everyone who writes the articles that I include. I would be nothing without—I mean—literally, that I could not have a newsletter without content creators. I also kind of started the newsletter as an exploration of this new career title.I mean, I've been doing things that basically fit along with SRE for a long time, but also, I think my view of SRE might be not really the same as a lot of folks, or, like, that Google passed down from the [Google Book Model 00:22:46]. I don't—I'm going to be a little heretical here—I don't necessarily a hundred percent believe in the SLI SLO SLA error budget model. I don't think that that necessarily fits everyone, I'm not sure even suits the bigger companies as well as they think it does. I think that there's a certain point to which you can't actually predict failure and just slowing down on your deploys. And it likes to cause there to be fewer incidents so that you can get—your you know, you can go back to passing in your error budget, to passing your SLO, I'm not sure that actually makes sense or is realistic and works in the real world.Corey: I've been left with the distinct impression that it's something of a framework for how to think about a lot of those things. And it's for folks on a certain point of their development along whatever maturity model or maturity curve you want to talk about, it becomes extraordinarily useful. And at some point, it feels like the path that a given company is on will deviate from that. And, on some level, if you don't wind up addressing it, it turns into what it seems like Agile did, where you wind up with the Cult of Agile around it and the entire purpose of it is to perpetuate the Cult of Agile.And I don't know that I'm necessarily willing to go so far as to say that's where SLOs are headed right now, but I'm starting to get the same sort of feeling around the early days of the formalization of frameworks like that, and the ex cathedra proclamation that this is right for everyone. So, I'm starting to wonder whether there's a reckoning, in that sense, coming down the road. I'm fortunate that I don't run anything that's production-facing, so for me, it's, I don't have to care about these things. Mostly.Lex: Yeah. I mean, we are in… we're in 2023. Things have come so much further than when I was a kid. I have a little computer in my pocket. Yeah, you know, “Hey, math teacher, turns out yeah, we do carry calculators around with us wherever we go.” We've built all these huge, complicated systems online and built our entire society around them.We're still in our infancy. We still don't know what we're doing. We're still feeling out what SRE even is, if it even makes sense, and I think there's—yeah, there's going to be more evolution. I mean, there's been the, like, what is DevOps and people coining the term DevOps and then getting, you know, almost immediately subsumed or turned into whatever other people want. Same thing for observability.I think same thing for SRE. So honestly, I'm feeling it out as I go and I think we all are. And I don't think anyone really knows what we're doing. And I think that the moment we feel like we do is probably where we're in trouble. Because this is all just so new. Look where we were even 40 years, 30, even 20 years ago. We've come really far.Corey: For me, one of the things that concerns slash scares me has been that once someone learns something and it becomes rote, it sort of crystallizes in amber within their worldview, and they don't go back and figure out, “Okay, is this still the right approach?” Or, “Has the thing that I know changed?” And I see this on a constant basis just because I'm working with AWS so often. And there are restrictions and things you cannot do and constraints that the cloud provider imposes on you. Until one day, that thing that was impossible is now possible and supported.But people don't keep up with that so they still operate under the model of what used to be. I still remember a year or so after they raised the global per-resource tag limit to 50, I was seeing references to only ten tags being allowed per resource in the AWS console because not even internal service teams are allowed to talk to each other over there, apparently. And if they can't keep it straight internally, what hope to the rest of us have? It's the same problem of once you get this knowledge solidified, it's hard to keep current and adapt to things that are progressing. Especially in tech where things are advancing so rapidly and so quickly.Lex: Yeah, I gather things are a little feudalistic over inside AWS, although I've never worked there, so I don't know. But it's also just so big. I mean, there's just—like, do you even know all of the—like, I challenge you to go through the list of services. I bet you're going to find when you don't know about. You know, the AWS services. Maybe that's a challenge I would lose, but it's so hard to keep track of all this stuff with how fast it's changing that I don't blame people for not getting that.Corey: I would agree. We've long since passed the point where I can talk incredibly convincingly about AWS services that do not exist and not get called out on it by AWS employees. Because who would just go and make something up like that? That would be psychotic. No one in the right mind would do it.“Hi, I'm Corey, we haven't met yet. But you're going to remember this, whether I want you to or not because I make an impression on people. Oops.”Lex: Yeah. Mr. AWS Snark. You're exactly who I would expect to do that. And then there was Hunter, what's his name? The guy who made the—[singing] these are the many services of AWS—song. That was pretty great, too.Corey: Oh, yeah. Forrest Brazeal. He was great. I loved having him in the AWS community. And then he took a job, head of content over at Google Cloud. It's, well, suddenly, you can't very well make fun of AWS anymore, not without it taking a very different tone. So, I feel like that's our collective loss.Lex: Yeah, definitely. But yeah, I feel like we've done amazing things as a society, but the problem is that we're still, like, at the level of, we don't know how to program the VCR as far as, like, trying to run reliable services. It's really hard to build a complex system that, by its nature of being useful for customers, it must increase in complexity. Trying to run that reliably is hugely difficult and trying to do so profitably is almost impossible.And then I look at how hard that is and then I look at people trying to make self-driving cars. And I think that I will never set foot in one of those things until I see us getting good at running reliable services. Because if we can't do this with all of these people involved, how do I expect that a little car is going to be—that they're going to be able to produce a car that can drive and understand the complexities of navigating around and all the hazards that are involved to keep me safe.Corey: It's wild to me. The more I learned about the internet, the more surprised I am that any of it works at all. It's like, “Well, at least you're only using it for ridiculous things like cat pictures, right?” “Oh, no, no, no. We do emergency services and banking and insurance on top of that, too.” “Oh, good. I'm sure that won't end horribly one day.”Lex: Right? Yeah. I mean, you look at, like—you look at how much of a concerted effort towards safety they've had to put in, in the aviation industry to go from where they were in the '70s and '80s to where we are now where it's so incredibly safe. We haven't made that kind of full industry push toward reliability and safety. And it's going to have to happen soon as more and more of the services we're building are, exactly as you say, life-critical.Corey: Yeah, the idea of having this stuff be life-critical means you have to take a very different approach to it than you do when you're running, I don't know, Twitter for Pets. Though, I probably need a new fake reference startup now that Twitter for reality is becoming more bizarre than anything I can make up. But the idea that, “Well, our ad network needs to have the same rigor and discipline applied to it as the life support system,” maybe that's the wrong framing.Lex: Or maybe it's not. I keep finding instances of situations—maybe not necessarily ad networks, although I wouldn't put it past them—but situations where a system that we're dealing with becomes life-critical when we had no idea that it could possibly do. So, for example, a couple companies back, there was this billing situation where a vendor of ours accidentally nilled our customers incorrectly and wiped bank accounts, and real people were unable to make their mortgage payments and unable to, like, their bank accounts were empty, so they couldn't buy food. Like, that's starting to become life-critical and it all came down to a single, like, this could have been any outage at any company. And that's going to happen more and more, I think.Corey: I really want to thank you for taking time to speak with me. If people want to learn more, where's the best place for them to find you?Lex: sreweekly.com. You can subscribe there. Thank you so much for having me on. It has been a real treat.Corey: It really has. You'll have to come back and we'll find other topics to talk about, I'm sure, in the very near future. Thank you so much for your time. I appreciate it.Lex: Thanks.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.

Renowned guitarist, producer and songwriter Prashant Aswani joins us to talk about his freshly released Charvel signature PA28.  Known as the “guru of groove,” Aswani has honed his technical chops across almost every imaginable genre, from mainstream hard rock, pop and soul to more eclectic international fare. In addition to recording his own acclaimed solo albums and soundtracks, Aswani's impressive repertoire includes touring and recording with artists such as Greg Howe, Christina Milian, Justin Timberlake, Jose Pasillas (Incubus), Rhonda Smith (Prince) and Ronu Majumdar.   This episode is brought to you by Fretboard Biology  Fretboard Biology - the online guitar college created by Joe Elliott, ex Head of Guitar at GIT and McNally Smith Music College. Fretboard Biology Guitar Speak Podcast #146 - Joe Elliott - ex guitar head of GIT - launches Fretboard Biology Guitar Speak Podcast Links PayPal Tip Jar Visit us at guitarspeakpodcast.com Subscribe and find previous episodes at: Apple Podcasts Spotify Stitcher   Follow us on Facebook & Instagram Contact us at guitarspeakpodcast@gmail.com

In this episode, Linda and Dave chat with Jay Clifford, Developer Advocate at InfluxData. InfluxData are the makers of InfluxDB, a popular open-source platform for simplifying time series data management. Designed to handle high speed and high volume data ingest and real-time data analysis, InfluxDB's robust data collectors, common API across the entire platform, highly performant time series engine, and optimized storage lets you build once and deploy across multiple products and environments. Jay shares his journey to the cloud, gives us a developer introduction to time series data management, how to compare it to relational data and databases, how developers should think about this kind of data, and shares some real world customer success stories. Follow Jay on LinkedIn: https://www.linkedin.com/in/jaymand13/ Jay on Git: https://github.com/Jayclifford345 Linda on Twitter: https://twitter.com/lindavivah Linda's Website: https://lindavivah.com/ Linda on TikTok: https://www.tiktok.com/@lindavivah Linda on Instagram: https://www.instagram.com/lindavivah/ Linda's Medium: https://medium.com/@LindaVivah [DAVES COLLECTION] Rick and Morty - https://awsdeveloperspodcast.s3.amazonaws.com/RickMorty.PNG [DAVES COLLECTION] World of Warcraft Collectors Editions – https://awsdeveloperspodcast.s3.amazonaws.com/WoWCollectorsEditions.PNG [DOCS] InfluxDB Cloud Powered by IOX -https://docs.influxdata.com/influxdb/cloud-iox/get-started/ [GIT] InfluxData Telegraf Plugins & Integrations - https://github.com/influxdata/telegraf [GIT] InfluxDB OSS - https://github.com/influxdata/influxdb [PORTAL] InfluxData Website - https://www.influxdata.com [PORTAL] InfluxData Cloud Signup - https://cloud2.influxdata.com/signup [PORTAL] InfluxDB Use Cases - https://www.influxdata.com/customers/ [PORTAL] Pandas - https://pandas.pydata.org/ [SLACK] InfluxData Community Slack - https://www.influxdata.com/slack (connect with Jay @JayClifford) [TRAINING] InfluxDB University (Free InfluxDB Training) - https://university.influxdata.com Subscribe: Amazon Music: https://music.amazon.com/podcasts/f8bf7630-2521-4b40-be90-c46a9222c159/aws-developers-podcast Apple Podcasts: https://podcasts.apple.com/us/podcast/aws-developers-podcast/id1574162669 Google Podcasts: https://podcasts.google.com/feed/aHR0cHM6Ly9mZWVkcy5zb3VuZGNsb3VkLmNvbS91c2Vycy9zb3VuZGNsb3VkOnVzZXJzOjk5NDM2MzU0OS9zb3VuZHMucnNz Spotify: https://open.spotify.com/show/7rQjgnBvuyr18K03tnEHBI TuneIn: https://tunein.com/podcasts/Technology-Podcasts/AWS-Developers-Podcast-p1461814/ RSS Feed: https://feeds.soundcloud

In this episode, Donn and Kaushik talk about one of the age old bike shedding topics - code formatting, and how you can solve it with automation and tools.Code formatting can turn into an endless debate amongst peers and teams, and what Kaushik and Donn have found is that this can be delegated to a tool and automated. Freeing you and your team of having to worry about proper indentation, bracket placement, etc. By relying on a well defined tool and some automation you can clean your code up, make it much more uniform and easier maintain.We talk about ktfmt, a Kotlin code formatter that was released by Facebook. We dive into ktlint, detekt and more. We also dive into spotless which can help you by integrating ktfmt into your gradle build pipeline.Linksktfmt - website, githubspotless - githubdetekt - websitektlint - websiteDonn's Git CourseNeed to learn Git? Donn has the course for you. In this FREE course you'll learn everything you need to know in order to start working with Git everyday. Watch it here.AndroidJobs.IOJob postings are FREE on AndroidJobs.IO during the early release phase (at the time of this recording).Sign up to get notified of new jobs on a weekly basis as well.AndroidJobs.IOSoftware FreelancingDonn's Freelance Faction CommunityFreelance Tactics BookDonn's Freelancing Content on YouTubeContact@fragmentedcast or our Youtube channel@donnfelker and donnfelker (on Instagram)Freelancing for Mobile Developers (Donn's YouTube)kaushikgopal (on YouTube) or kau.sh/blog or @kaushikgopalDisclaimer: Many of the links we share to products are affiliate links. They help support the production of Fragmented. Thank you for your support.

Bry is vindicated, Q celebrates his birthday week, Git ‘em reveals his perfect woman, Ming's first stand up set is reviewed.

Happy St Patrick's Day! To celebrate we re-issue our Iconic Albums roundtable discussing our favourite Irish supergroup, U2. This week we look at U2's Achtung Baby, an album where the biggest band in the world reinvented itself. Rob Rhodes  www.rhodetripent.com Gabor Josika  SuperFunAwesomeHappyTime Pedal Show This episode is brought to you by Fretboard Biology  Fretboard Biology - the online guitar college created by Joe Elliott, ex Head of Guitar at GIT and McNally Smith Music College. Fretboard Biology Guitar Speak Podcast #146 - Joe Elliott - ex guitar head of GIT - launches Fretboard Biology Guitar Speak Podcast Links PayPal Tip Jar Visit us at guitarspeakpodcast.com Subscribe and find previous episodes at: Apple Podcasts Spotify Stitcher   Follow us on Facebook & Instagram Contact us at guitarspeakpodcast@gmail.com

ScreenCastsOnline Tutorial: Create Projects with Apple Photos Keyboard Maestro Tips from Bob Cassidy All the Gear we Use for the Remote Live Show Support the Show A New Take on Web Browsers with Arc from The Browser Company – by Tom from Ontario Version Control with Git for Your Keyboard Maestro Macros Transcript of NC_2023_03_12 Join the Conversation: allison@podfeet.com podfeet.com/slack Support the Show: Patreon Donation PayPal one-time donation Podfeet Podcasts Mugs at Zazzle Podfeet 15-Year Anniversary Shirts Referral Links: Parallels Toolbox - 3 months free for you and me Learn through MacSparky Field Guides - 15% off for you and me Backblaze - One free month for me and you Setapp - One free month for me and you Eufy - $40 for me if you spend $200. Sadly nothing in it for you. PIA VPN - One month added to Paid Accounts for both of us

The multiskilled Todd Mills joins us to bring tales from the road as touring Guitar Tech, Drum Tech and Stage Manager for legendary rock band Jefferson Starship, Todd brings us unique insights of life in the wings of stages across the globe, including tours with Deep Purple, looking after Jefferson Starship's triple guitar team, a day in the life of a touring tech, dodging flying wardrobe debris, rock star encounters and his contribution to arguably the greatest collision of rock music and a galaxy far, far away.   This episode is brought to you by Fretboard Biology  Fretboard Biology - the online guitar college created by Joe Elliott, ex Head of Guitar at GIT and McNally Smith Music College. Fretboard Biology Guitar Speak Podcast #146 - Joe Elliott - ex guitar head of GIT - launches Fretboard Biology Guitar Speak Podcast Links PayPal Tip Jar Visit us at guitarspeakpodcast.com Subscribe and find previous episodes at: Apple Podcasts Spotify Stitcher   Google Podcasts

In 2022, Rails Hiring is Still Hot was our most listened to episode! By popular demand, Brian is back to give us the state of the Ruby on Rails hiring market for 2023. Brittany and Brian discuss his clients, advice for those who have a job and advice for those who are seeking a role in this weird market. Show Notes & Links: Episode 419: Rails Hiring is Still Hot (Brittany + Brian) (https://www.therubyonrailspodcast.com/419) Mirror Placement (https://www.mirrorplacement.com/) Sponsored By: Honeybadger (https://www.honeybadger.io/) Status Pages now come with incident management! Build confidence with a public status page that shows your live service status, incident history, and more—and bring your own domain! Transparency inspires trust—when your next outage happens, communication is key. Go to Honeybadger.io (https://www.honeybadger.io/) to learn more. JetBrains RubyMine (https://www.jetbrains.com/ruby/) RubyMine is an intelligent cross-platform IDE that provides all essential tools for Ruby and Ruby on Rails developers out of the box. It offers smart code completion and analysis, easy code navigation, safe automated refactorings, an interactive debugger, Git workflow support, database integration, and many other tools. All tools are integrated together in a highly customizable, productive, user-friendly environment. To get a special 20% discount for the listeners of The Ruby on Rails Podcast just enter the discount code railspodcast during purchase (https://www.jetbrains.com/ruby/). You can apply this discount to JetBrains All products pack and use IDEs of your choice.

Alex Rottier and Gabor Josika of TheSuperFunAwesomeHappyTimePedalShow join Matt to discuss their uniquely monikered YouTube channel. TSFAHTPS is one of Australia's longest running gear channels and has close to 30K subscribers worldwide. This episode brings fascinating insights into the running of a successful YouTube channel from dealing with multi-national companies to boutique one man and women operations, thoughts on influencers in the gear space, 90s vintage rack stuff, addressing the paid promotion issue, wacky KOT shootouts and much more. Guitar Speak Podcast listeners may recognise Gabor as a co-host of our Iconic series of shows. https://www.youtube.com/c/thesuperfunawesomehappytimepedalshow Matt Wakeling on TSFAHTPS podcast   This episode is brought to you by Fretboard Biology  Fretboard Biology - the online guitar college created by Joe Elliott, ex Head of Guitar at GIT and McNally Smith Music College. Fretboard Biology Guitar Speak Podcast #146 - Joe Elliott - ex guitar head of GIT - launches Fretboard Biology Guitar Speak Podcast Links PayPal Tip Jar Visit us at guitarspeakpodcast.com Subscribe and find previous episodes at: Apple Podcasts Spotify Stitcher   Google Podcasts

Dave and Chris discuss calipers, IoT devices, Git, eInk, new chip companies, and more!

Watch on YouTube About the show Sponsored by Compiler Podcast from Red Hat. Connect with the hosts Michael: @mkennedy@fosstodon.org Brian: @brianokken@fosstodon.org Show: @pythonbytes@fosstodon.org Special guest, Erin Mullaney: @erinrachel@fosstodon.org Join us on YouTube at pythonbytes.fm/live to be part of the audience. Usually Tuesdays at 11am PT. Older video versions available there too. Brian #1: Use TOML for .env files? Brett Cannon .env files are used to store default settings that can be overridden by environmental variables. Possibly brought on by twelve-factor app design. Supported by python-dotenv, which is also used by pydantic, pipenv, and others. One issue is that it's not a defined standard. from python-dotenv docs “The format is not formally specified and still improves over time. That being said, .env files should mostly look like Bash files.” Adafruit decided that an upcoming CircuitPython will use TOML as the format for settings.toml files, which are to be used mostly how .env files are being used. Brett notices this may fix things for Python for VS Code, and other people as well. So… Is this a good idea? I think so. Michael #2: Pydantic gets serious funding via Mark Little (was on episode 285) Sequoia backs open source data-validation framework Pydantic to commercialize with cloud services. Pydantic Services Inc. emerges from stealth today with $4.7 million in seed funding. Pydantic's new commercial entity will incorporate a swath of new tools and services that are both “powered-by and inspired-by the Pydantic library” Pydantic will start with an initial team of six, with the first three engineers based in Montana, Chicago and Berlin. “With $4.7 million in the bank, Colvin said that they're continuing to rewrite parts of Pydantic in Rust, with a view toward making it more efficient via a ten-fold performance improvement.” Erin #3: JSON Fields for performance (Denormalization) David Stokes Using JSON fields when you design your databases is a good way to improve database query performance. Brian #4: f-strings with pandas and Jupyter keyboard shortcuts Kevin Markham After a couple year break from blogging, friend of the show Kevin Markham has a couple great, short, useful posts. How to use Python's f-strings with pandas My favorite bit is the part about using f-strings for dictionary keys Fly through Jupyter with keyboard shortcuts