Podcasts about planetscale

Sam Lambert returns to chat about the launch of PlanetScale Metal, the importance of looking past averages, constraints of working with Amazon, how building good software is like building an airline, thoughts on the standard software dev playbooks, advice for younger developers, and reflections on killing the free tier at PlanetScale.Links:Sam LambertMetal — PlanetScalePlanetScale DesignSponsor: Terminal now offers a monthly box called Cron.Want to carry on the conversation? Join us in Discord. Or send us an email at sliceoffalittlepieceofbacon@tomorrow.fm.Topics:(00:00) - The fun of building with paranoia (00:39) - The party (03:20) - How was the launch of PlanetScale Metal? (09:34) - How is Planetscale Metal different? (14:32) - The importance of looking beyond the averages (20:46) - Constraints of working within Amazon (27:48) - How do you know that a random bug won't bring everything down? (33:08) - Building good software is like building an airline (34:47) - PlanetScale changes one year later (40:41) - Is there a standard playbook for selling software you follow? (48:29) - Hype ruins so much software (01:01:30) - I have no advice to give to younger developers (01:08:09) - How do you reflect on killing the free tier? (01:18:30) - Playing the long game instead of listening to tech Twitter ★ Support this podcast ★

Today, we have Sam Lambert back on the show! Sam is the CEO of PlanetScale, and if you follow him on X, you know he's one of the sharpest voices in the database space—cutting through the hype with deep experience and a no-nonsense approach. In this episode, we dive into PlanetScale's new Metal offering, which has been battle-tested with PlanetScale's high-scale cloud business partners and is now GA. Sam also shares why staying profitable is crucial—not just for the business but for the stability and reliability it guarantees for customers. While many cloud infrastructure companies chase the next hype cycle, Sam prefers to keep it boring—delivering rock-solid performance with no surprises Finally, we close with Sam's thoughts on other happenings in the database space -- Aurora DSQL, Aurora Limitless, MySQL benchmarks, and multi-region strong consistency. Tune in for a deep dive into databases, cloud infrastructure, and what it takes to build a sustainable, high-performance tech company. Timestamps 01:34 Start 06:42 PlanetScale Metal 11:15 The problem with separation of storage and compute 15:02 EBS Tax 17:32 How does Vitess handle durability 22:58 Metal recommended for all PlanetScale users? 27:20 The hidden expense of IOPS for cloud databases 37:41 Timeline of creating PlanetScale Metal 41:32 Focus on profitability 47:52 Removal of hobby plan 57:45 Deprecation of PlanetScale Boost 01:00:24 DSQL 01:01:51 Aurora Limitless 01:04:15 AWS as a partner 01:07:00 The spectacle of AWS re:Invent 01:12:22 Benchmarks and benchmarketing 01:15:51 AWS Databases + multi-region strong consistency

Sam Lambert stops by to talk Unifi networking, cooking meat, microplastics, disease research, the history of the world, scaling at PlanetScale, and why people love PostGres.Want to carry on the conversation? Join us in Discord.The ultimate MySQL database platform — PlanetScaleUniFi - Introduction - UbiquitiNest Wifi Pro CoverageAztec EmpireBuddhas of BamiyanModern PostgreSQL BookTopics:(00:00) - Computers will always let you down (00:27) - Falling asleep to self driving Tesla chats (02:17) - Using Unifi networking gear (12:02) - Cooking meat (18:24) - Why are microplastics everywhere? (22:55) - Ordering diseases and cells for research from a JC Penny Catalogue (30:25) - American history with Adam and Dax (34:26) - South American history with Dax (38:24) - Could all the data get wiped out and we lose everything? (54:52) - Scaling and PlanetScale (01:08:48) - Why do people love PostGres?

Databases underpin almost every user experience on the web, but scaling a database is one of the most fundamental infrastructure challenges in software development. PlanetScale offers a MySQL platform that is managed and highly scaleable. Sam Lambert is the CEO of PlanetScale and he joins the show to talk about why he started the platform, The post Hyperscaling SQL with Sam Lambert appeared first on Software Engineering Daily.

Databases underpin almost every user experience on the web, but scaling a database is one of the most fundamental infrastructure challenges in software development. PlanetScale offers a MySQL platform that is managed and highly scaleable. Sam Lambert is the CEO of PlanetScale and he joins the show to talk about why he started the platform, The post Hyperscaling SQL with Sam Lambert appeared first on Software Engineering Daily.

In this episode of the Business of Laravel podcast, host Matt Stauffer interviews Aaron Francis, co-founder of Try Hard Studios, beloved Internet personality, Laravel developer, and all-around Internet nice guy. Aaron shares his journey from his days at a property tax company to his bold leap into entrepreneurship, sharing insights into his evolution every step of the way. He discusses moving beyond the "hustle era" to what he terms the "Try Hard era," emphasizing the importance of concerted effort and determination in achieving success. Tune in to learn about Aaron's background, his passion for creating educational content, and the exciting ventures he's currently pursuing in the world of Laravel development.Matt Stauffer Twitter - Matt Stauffer (@stauffermatt) on XTighten Website - Tighten | Software Development for Web + Mobile | Laravel + Vue.jsAaron Francis Twitter - @‌aarondfrancisAaron Francis Website - aaronfrancis.comTry Hard Studios - tryhardstudios.comRadical Candor - https://www.radicalcandor.com/37 Signals - https://37signals.com/books/Brené Brown - https://brenebrown.com/-----Editing and transcription sponsored by Tighten.

A brief list of topics discussed in this brief episode: New Jersey follow up from last episode, PlanetScale layoffs and performative twitter responses, free tiers aren't going to last forever, the Devin AI demo, Astro's file format choices, Adam has no thoughts about capitalism, does online bitterness extend to real life, why aren't more of us using Cameo for shit posting, Adam needs more movies to watch, and Dax learns about Adam's LOTR obsession.Want to carry on the conversation? Join us in Discord.Aaron Francis (@aarondfrancis) / XHow About Tomorrow?Devin: AI EngineerCopilotAI Pair ProgrammerGPT Prompt PluginCursor Code EditorHomeI Am LegendI Am Legend 2007 Francis LawrenceFavorite Stars PersonalizedEx Machina Film ReviewOscar Best Picture Winners by NayanThe Wolf of Wall StreetKillers of the Flower MoonNolan's FilmsScorsese's FilmsQuentin Tarantino FilmsThere Will Be BloodNo Country for Old Men Film ReviewDune 2021 Film ReviewsDune: Part TwoGuillermo del Toro FilmsThe Fellowship of the RingIan Mckellen Hobbit BreakdownKing Kong 2005 Peter JacksonMulan TrailerMarley & Me Film ReviewsPlanetScale performs layoff and prioritizes profitabilityTopics:(00:00) - Adam leaves special messages for you on YouTube (00:37) - New Jersey slander on Twitter (06:00) - PlanetScale layoffs (14:37) - Performative Twitter and the stupidity of responses (21:14) - The free tier system (29:22) - Weird noises in the yard (31:52) - The Devin demo (41:07) - Astro choosing their own file format (45:01) - Adam doesn't think about capitalism (51:44) - Does online bitterness extend to real life? (57:58) - Is the future going to be cleaner or messier? (01:04:16) - Why is Twitter the best developer community? (01:05:20) - Cameo as an underutilized service for shitposting (01:09:10) - What movies should Adam watch? (01:17:08) - Miami plans (01:34:52) - Adam sold a domain

Look we all know there are things to talk about but we recorded this last week before any of that stuff happened!

Ian & Aaron discuss being laid off, what comes next for Aaron, why layoffs always go bad, good free tiers vs. bad free tiers, & more.Sponsored by LaraJobs & Screencasting.com.Sent questions or feedback to mostlytechnicalpodcast@gmail.com.(00:00) - We Don't Have Bosses (06:51) - Dune Part 2 Side Tangent (14:19) - The Main Character (26:13) - These Things Always Go Bad (32:44) - Free Tiers (42:50) - Have You Heard About Cloudflare? (48:32) - Thoughts on Content Marketing (56:34) - Face of the Organization (01:01:48) - The Future (01:15:18) - The Future, Continued (01:27:31) - I'm Hot & Rich Now! (01:34:14) - Aaron Francis Studio of Light & Sound (01:37:33) - Follow Up & An Interesting Idea Links:"...@ianlandsman, who is a gifted takesman" (on Twitter)Aaron got laid offAaron Francis Studio of Light and SoundAlamo DrafthouseStudio Movie GrillAaron's tweet about seeing Dune 2PlanetScale forever (blog post)PlanetScale's schema recommendationsLaracon US - tickets still available!Primeagen's breakdown of the PlanetScale layoffs (on YouTube)The Ramsey ShowCar TalkMike and the Mad DogAaron's tweet about a call in radio show 

2024 is the year of business accountability across all aspects of the software industry. This means that all variations of the free tier are going away in one way or another. SHOW: 802CLOUD NEWS OF THE WEEK - http://bit.ly/cloudcast-cnotwCHECK OUT OUR NEW PODCAST - "CLOUDCAST BASICS"SHOW SPONSORS:CloudZero provides immediate and ongoing savings with 100% visibility into your total cloud spendSHOW NOTES:Linkerd changes publishing model of imagesPlanetScale discontinues Free Tier (“Hobby”) of serviceWHY DID THE FREE TIER(S) EXIST IN THE FIRST PLACE?Why do free tiers exist? Marketing awareness, experimentation, Why is talking about making money, or profitability considered taboo?Why do we reconcile the love of employees and the hatred of paying for software?WHAT ARE THE TRADE-OFFS WHEN THE FREE TIER GOES AWAY?Are free tiers and free open source software the same thing?Are “wants” and “value” the same thing? What should be free in the software world? Should end-users want the backers of a project or company to be successful?Will VCs continue to back companies that have free tiers, or companies that spend on marketing, or is the game needing new (undefined) rules? FEEDBACK?Email: show at the cloudcast dot netTwitter: @cloudcastpodInstagram: @cloudcastpodTikTok: @cloudcastpod

The SM7B is everywhere. Adam and Dax can't wait for their AI coworkers to arrive, but should you be concerned about your job with AI? And what does E/ACC mean? Adam asks Dax about his tweets and rules for Twitter. And the US healthcare system is broken with no fix in sight.Want to carry on the conversation? Join us in Discord.SM7B - Vocal Microphone - Shure USAPerplexityDax on X: “you've all had co2 monitors for over a month now and i haven't seen an improvement”Query Insights — PlanetScale DocumentationIntroducing the Data API for Amazon Aurora Serverless v2 and Amazon Aurora provisioned clusters | AWS Database BlogAI description of this episode.(00:00) - Do it at the beginning (00:29) - Mics and mic technique (05:32) - AI developer coworkers (18:09) - What does the best programming language look like in the future? (24:39) - Are we too optimistic about AI's future? (29:28) - AI is great for cleaning up data (33:17) - You don't have to be human with AI (38:16) - What does E/ACC mean? (40:39) - The White House says we should write Rust (42:07) - Adam asks Dax about his tweets (44:00) - Dax's Twitter avatar rule (46:24) - What's PlanetScale Insights? (53:18) - The state of health care in America (01:02:13) - Interest rates going down - or up? (01:03:39) - Meta ask: leave us a rating please! (01:08:03) - Would you get Neuralink?

Michael and Nikolay are joined by Andrew Atkinson, author of High Performance PostgreSQL for Rails, to discuss how Rails and Postgres work together — where the limits are, how people use the ORM, things that are improving, and some things we can do as a Postgres community to make it even better. Here are some links to things they mentioned:Planet Argon survey https://rails-hosting.com/2022/#databasesActive Record https://guides.rubyonrails.org/active_record_basics.htmlPostgreSQL specific usage of Active Record https://guides.rubyonrails.org/active_record_postgresql.htmlMultiple Databases with Active Record https://guides.rubyonrails.org/active_record_multiple_databases.htmlschema.rb vs structure.sql https://blog.appsignal.com/2020/01/15/the-pros-and-cons-of-using-structure-sql-in-your-ruby-on-rails-application.htmlactiverecord-clean-db-structure (Ruby gem by Lukas Fittl) https://github.com/lfittl/activerecord-clean-db-structureGitLab's migration_helpers.rb https://gitlab.com/gitlab-org/gitlab/-/blob/master/lib/gitlab/database/migration_helpers.rbSQLite https://www.sqlite.orgPlanetScale's foreign key support announcement video https://twitter.com/PlanetScale/status/1732070818958500083DoorDash Engineering Blog https://doordash.engineering/blograils-pg-extras https://github.com/pawurb/rails-pg-extrasBenoit Tigeot testing Peter Geoghegan improvement for large IN lists https://gist.github.com/benoittgt/ab72dc4cfedea2a0c6a5ee809d16e04dHigh Performance PostgreSQL for Rails (Andy's book, 35% discount code “postgres.fm”) https://pragprog.com/titles/aapsql/high-performance-postgresql-for-railsAndy's blog and website https://andyatkinson.com~~~What did you like or not like? What should we discuss next time? Let us know via a YouTube comment, on social media, or by commenting on our Google doc!~~~Postgres FM is produced by:Michael Christofides, founder of pgMustardNikolay Samokhvalov, founder of Postgres.aiWith special thanks to:Jessie Draws for the elephant artwork 

Come hang with us! Like what you hear? Connect with me - Website: gun.io/taylor Email: taylordesseyn@gun.io LinkedIn: Taylor Desseyn Tweet me: @tdesseyn Pics of the life, wife, daughter & dog: @tdesseyn

Danilo Campos, Proprietor of Antigravity, joins @quinnypig on Screaming in the Cloud to discuss his philosophy behind building tools that not only enhance developer experience but also improve the future of our world. Danilo shares his thoughts on how economic factors have influenced tech companies and their strategies for product, open source, and more. He also shares what he thinks is another, better way to approach these strategies, without ignoring the economic element. About DaniloDanilo Campos wants a world where technology makes us more powerful and expressive versions of ourselves. He worked with GitHub and the White House to deliver coding platforms to public housing residents, supported Glitch.com in its last days as an independent, and developed products for multiple early-stage startups, including Hipmunk. Today Danilo offers freelance developer experience services for devtools firms through Antigravity DX.Links Referenced: Antigravity DX: https://antigravitydx.com/ Blog: https://redeem-tomorrow.com TranscriptAnnouncer: Hello, and welcome to Screaming in the Cloud with your host, Chief Cloud Economist at The Duckbill Group, Corey Quinn. This weekly show features conversations with people doing interesting work in the world of cloud, thoughtful commentary on the state of the technical world, and ridiculous titles for which Corey refuses to apologize. This is Screaming in the Cloud.Corey: Welcome to Screaming in the Cloud. I'm Corey Quinn, and periodically on this show, we like to gaze into the future and tried to predict how that's going to play out. On this episode, I want to start off by instead looking into the past, more specifically my past. Before I started this place, I wound up working at a company called FutureAdvisor, which was a great startup for all of three months before we were bought by a BlackRock. I soon learned what a BlackRock actually was.While I was there, I encountered an awful lot of oral tradition around a guy named Danilo, and he—as it turned out—was a contractor who had been brought in to do a fair bit of mobile work. Meet my guest today, Danilo Campos, who is at present, the proprietor of a company called Antigravity DX. Thank you so much for joining me, I appreciate it.Danilo: Hey, Corey, it's good to be here.Corey: It's weird talking to you, just because you were someone that I knew by reputation, and if I were to take all the things that were laid at your feet after you no longer had been there, it feels like you were there for 20 years. What did you actually do there, and how long were you embedded for?Danilo: I loved the FutureAdvisor guys. I thought they were such a blast to work with. I loved what they were working on. I learned so much about how finance and investing works from FutureAdvisor, and somehow it was only seven months of my life. I'd been introduced to the founders as a freelance iOS developer at the time—this was 2014—and a guy I had worked with at Hipmunk actually put me in touch with these guys, and we connected. And they needed to get started doing mobile. They'd never done any mobile stuff, they didn't have anyone on staff who did mobile stuff.And by that point, I'd shipped I think, must have been half a dozen iOS native apps, and so I knew this stuff pretty well. I understood the workflows, I understood the path to getting from idea to shipped product, and they just wanted occasional help. How do we wireframe this? How do we plan the product that way? How do we structure this thing? And so, it started off as this just, kind of, occasional troubleshooting consulting thing.And I think about August 2014. They call me in for a meeting, they said, “Hey, we're stuck. We don't know how to get this thing off the ground. Could you help us get this project moving so that we actually ship it?” And so, I just came and embedded for seven months, and by the end of it, I was just running the entire iOS engineering team. We had a designer working with us. We had, I think it was four folks who were building the product. We had QA. It was a whole team to get this thing out the door. And we got it out the door after seven months of really working at it. And like I said, it was a blast. I love those folks.Corey: I have to be clear, when I say that I encountered a lot of what you had done. It was not negative. This was not one of those startups where there's a glorious tradition of assassinating the character out of everyone who has left the company—or at least Git repos—because they're not there to defend themselves anymore. There were times where decisions that you had made were highlighted as, “We needed to be doing things more like this.” There were times it was, “Oh, we can't do that because of how you wound up building this other thing.”And it was weird because it felt like you were the hand of some ancient deity, just moving things back and forth in your infinite wisdom of the ancients. It was unknowable, and we had to accept it as gospel, whether we liked it or not, at different times. In practice, I now know this was honestly just the outgrowth of a rapidly expanding culture where you've got to go from a team of five people to the team of 50 and keep everyone rowing in the same direction, ideally. But it was a really interesting social dynamic that I got to observe as a result, and I'm just tickled pink to be able to talk to you now. What are you doing these days?Danilo: Thank you for the context, by the way, because you know, I move on, as you do in a contract capacity, and you hope things work out.Corey: Yeah. To be clear, it was never a context of, “There's the bastard. Get him.” Like, that is not the perspective we are coming at this from at all.Danilo: Yeah, yeah, yeah. No, and it's hard because it was a very strange, alien codebase compared to the rest of the company. I get how it ended up in that spot. These days, I am a freelance developer experience consultant, and I spent a year-and-a-half at Glitch.com. And developer experience was always something that I really cared about. I did some work at GitHub that was about getting people—specifically teenagers living in public housing—into computing and the internet, and I'd had to do a bunch of DX work to make that happen because I had an afternoon to get people from zero to writing code.And that is not a straightforward situation, especially in a low-income housing environment, for example, right? So, I cared about this stuff a lot. And then I spent a year-and-a-half at Glitch.com, and it was like getting a graduate degree on everything about the leverage for creating outcomes in developer tools. And I just, I felt like I was carrying some gift from the Gods. I just, I felt the need to get this out to the wider world, and so that's what I do with Antigravity.Corey: When I got to catch up with you in person for the first time at the excellent and highly recommended Monktoberfest conference—Danilo: Excellent.Corey: —that the folks over at RedMonk put on every year, it was interesting, in that you and I got to talking very rapidly, not about technology as such, but about culture and the industry and values and the rest. It was a wonderfully refreshing conversation that I don't normally get to have so soon after meeting someone. I think that one of the more interesting aspects of our relatively wide-ranging conversation in a surprisingly brief period of time focused, first off, among the idea of developer tools and what so many of them seem to get wrong. I know that we basically dove into discussing about our violently agreeing opinions around the state of developer experience, for example. What are the hills you're willing to die on in that space?Danilo: I think that computing generally exists to amplify and multiply our power. Computing exists to let us do things that we could not do with the simple, frail flesh that we're born with, right? Computers augment our ambitions because they can do things with infinite iteration. And so, if you can come up with something that you can bottle in the form of an algorithm that repeats infinitely, you can have incredible impact on the world. And so, I think that there's a responsibility to find ways to make that power something that is easy to hand to other people and let them pick up and run with.And so, developer tools, to me, has this almost sacred connotation because what you're doing is handing people the fire of the Gods and saying, “Whatever you can come up with, whatever your imagination allows you to do with these tools, they can repeat infinitely and make whatever change you want—for good or for ill—in the world.” And that's very special to me. I think we've gotten bored of it because it's just, you know, it's a 50-year-old business at this point. But I think there's still a lot of magic to it, and the more we see the magic, the more magical outcomes we can coax out of everyday people who become better developers.Corey: From my perspective, one of the reasons I care so much about developer experience is that the failure mode of getting it wrong means that the person trying to understand the monstrosity you've built feels like they're somehow not smart, or they're just not getting it in some key and fundamental way. And that's not true. It's that you, for whatever reason, what you have built is not easily understandable to them where they are. I go back to what I first heard in 2012, at a talk that Logstash creator, Jordan Sissel wound up saying, where his entire thesis was that if a user has a bad time, it's a bug.Danilo: Yeah.Corey: And I thought that that was just a wonderfully prescient statement that I wanted to sign onto wholeheartedly. [That was 00:09:08] my first exposure to it. I know that's not the entirety of developer experience by a long shot, but it's the one where I think you lose the most mind share when you get it wrong.Danilo: Well, and I'm glad that you bring that up because I think that kind of defines the spectrum of the emotional experience of interacting with developer tools. On one end of the spectrum, you've got, “I feel so stupid. This has made me feel worse about myself. This has given me less of a sense of confidence in myself than I had when I started.” And at the other end of the spectrum, the other extreme is, “I cannot believe I am this cool. I cannot believe that my imagination has been made manifest in this way that now exists in the world and can go out and touch other people and make their lives better.”Those are the two, kind of, extremes of the subjective emotional experience that can come from developer tools. And so, I think that there is a business imperative that really pushes us toward the extreme of making people feel awesome. I think about this in the context of Iron Man, you've seen Iron Man, yeah.Corey: Oh, yes.Danilo: All right. So, the Iron Man suit is the perfect metaphor for a developer tool that is working correctly for you, right? Because on its own, the suit is not very interesting, and on his own, Tony Stark is not all that powerful, but you combine the suit and the person, and suddenly extraordinary emergent outcomes come out. The ambition of the human is amplified, and he feels so [BLEEP] cool. And I think that's what we're looking to do with developer tools is that we want to take a person, amplify their range, give them a range of motion that lets them soar into the clouds and do whatever they need to do up there so that when they come back down, they feel transformed. They feel like more than what they started.Corey: I would agree with that. There's a sense of whimsy and wonder as I look through my career trajectory, going from a sysadmin role, where you there was a pretty constant and hard to beat ratio in most shops—and the ratio [unintelligible 00:11:29] varied—but number of admins to the number of servers. And now with the magic of cloud being what it is, it's a, “Well, how many admins does it take to run X number of servers?” Like, “Well, as an [admin done 00:11:39] right, I can manage all of them because that's how programming languages work.” And that is a mystical and powerful thing.But lately, it seems like there's been some weird changes in the world of developer tooling. Cynically, I've said a couple of times that giving a toss about the developer experience was in fact a zero interest rate phenomenon. Like, when you're basically having to fend off casual offers of 400 grand a year from big tech, how do you hire and retain people at a company that has one of those old, tiny profit-generating business models and compete with them? And a lot of times, developer experience was part of how you did that. I don't know that I necessarily believe that that is as tied to that cynical worldview as I might pretend on the internet, but I don't know—I do wonder if it's a factor because it seems like we've seen a definite change in the way that developer tools are approaching their community of users and customers.Danilo: Well, my immediate reflex is to open up the kind of systems theory box and look at what's inside of that. Because I think that what we are experiencing, if we use the interest rate lens, is a period of time where everyone is a little bit worried that the good times are over for good. And I feel the sense of this in a lot of places. I think developer experience is a pretty good avatar to try this on with because I definitely also perceive it in that sphere.During the heyday of 0% interest rates, everything was about how much totalizing growth can you achieve? And from a developer tools perspective, all right, well, we need to make it so that the tools, kind of, grow themselves, so let's invest a lot in developer experience so that people very quickly get onboarded, without us having to hold their hand, without us having to conduct a sales call, let's get them to the point where they can quickly understand—because the documentation is so good and the artifacts are so good—exactly how to use these tools to maximum effect. Let's get them to a point where it's very easy for them to share the results of their work so that other people see the party and really want to join in. And so, all kinds of effort and energy and capital was being invested in this kind of growth strategy.And now I think that people are, again, a little bit afraid that the good times are over, and so we see this really sales-driven culture of growth, where it's like, all right, well, for this company to succeed, we have to really make sure that we're going and closing these big sales, and if individual developers can't figure out how the hell this works, well, that's their problem, and we're not going to worry about it. And we've talked about this: this fear of the good times being over drives people, I think, to all kinds of bad behavior. The rug-pulling that we've seen in open-source licensing where somebody's like, “All right, I've taken a bunch from this community, and now I'm going to keep it, and I'm not going to give anything back.” This is the behavior of people who are afraid that the good times are behind them. I don't have the luxury of being that pessimistic about the future, and I don't think our industry can afford it either.[midroll 00:15:03]Corey: The rules changing late in the game is something that has always upset me. It feels inherently unfair, and it's weird because you can have these companies say that, “Look, we've never done anything like that. Why wouldn't you trust us?” Right up until the point where they do. Reddit is a great example, where for years, they had a great API—ish—that could do things that their crap-ass mobile client natively couldn't. And Apollo was how I interacted with Reddit constantly. I was a huge Reddit user. I was simultaneously, at one point, moderator of the legal advice subreddit and the personal finance subreddit. I was passionate about that stuff, and it was great.And then they wound up effectively killing all third-party clients that don't bend the knee, and well, why am I going to spend my time donating content and energy and time to a for-profit company that gets very jealous when other people find ways to leverage their platform in ways that they don't personally find themselves able to do. Screw ‘em. I haven't been back on Reddit since. It's just a, “Fool me once, shame on me story.” Twitter did the exact same thing. I built a threading Twitter client simultaneously deployed to 20 AWS regions, until they decided they didn't want people creating content through their APIs and killed the whole thing with no notice. Great. Now, they're—I got an email asking me to come back. Go to hell. I tried that once. You've eviscerated people's businesses and the rest.And you see it with licensed changes as well. But it all comes down to the same thing, from my perspective, which is an after-the-fact changing of the rules. And by moving the goalposts like that, I wonder what guarantees a startup or a project that doesn't intend to do those things can offer to its community. Because, look, HashiCorp made its decision to change the licensing for Terraform. Good for them. They're entitled to do that. I'm not suggesting, in any way shape or form, that they have violated any legal term.And I don't even know they're necessarily doing anything that doesn't make sense from their point of view. And the only people I really see that upset about it are licensing purists—which I no longer am for a variety of reasons—people who work at HashiCorp, obviously, and their direct competitors who are not sympathetic in that particular place. But as a counterpoint, if they wind up building a new open-source project, of course, I'm not going to contribute. I mean, that's a decision I get to make. And I don't know how you square that circle because otherwise, if that continues, no one will be able to have a sense of safety around contributing to anything open-source unless they're pleased to wind up doing volunteer work for a one-day unicorn.Danilo: So, I really appreciate the economical survey of the landscape that you just provided because I think that captures it really well. The Reddit case in particular breaks my heart. I will go to my grave absolutely loving Steve Huffman. Steve Huffman gave me my first break as a paid developer and product designer, and he was an enormous pain in the ass to work with, and I loved every minute of it. Like, he's just an interesting, if volatile, character.And I see that volatility playing out with Red Hat in the incredible hostility that they were conveying around being held to account for these changes. And I have a lot of sympathy for that crew because they've built all this value, they kind of missed the euphoria boat in terms of, you know, getting the best price for an IPO, for example, and they've got to figure out, all right, how do we scrape together value from what we've got within the constraints that we have? How do we build a fence around the value that we've got and put a tollbooth in front of it so that the public markets are excited about this and give us our best bang for the buck? That's Steve Hoffman's job. That's his crew's job. I understand the pressures and I respect that.And I think that the way they went about it this year was short-sighted because what it does is it undervalues everybody who isn't in the boardroom, making decisions with them. I think what we have to understand that when we build software, Metcalfe's law applies to developer tools just as much as any other network here. And so, the people who are stakeholders, who are participants, who are constituents of your community, are load-bearing members of the value chain that you are putting together, and so when you just cut them out, you might be nicking an artery that bleeds out very, very, very slowly. And the sentiment that you just expressed here about how your experience of Reddit was soured, I mean you're the enthusiast type, right? Like, who wants to sign up for the drama of flame wars and moderation except if you really just love it?And so, what they were able to do was take people who, for years, absolutely loved it, and just drain away their love and enthusiasm for it. And the thing is, over time, that harms the long-term value that you are trying to actually protect. When we live in a world where computers can do all of this stuff infinitely, when they will provide us with extraordinary scale, when information can be copied and distributed at near-zero marginal cost, what we're doing is setting up chains of incentives to get people to do stuff, essentially, for free. You were unpaid labor doing that moderation, and the reason that you did it for free was because it was fun, was because it spoke to something inside of you that really mattered, and you wanted to provide for a community of other people who also cared about these topics. And that fun was taken away from you. So, there's a bunch of this stuff that doesn't fit into a spreadsheet, and if we make decisions exclusively on what fits into a spreadsheet, we're going to turn around someday and find that we have cut off some of the most valuable parts of what makes this industry great.Corey: I agree. I feel like companies have a—they launch, and they want the benefits of having an open-source community, but as they grow and get to a point of success and becoming self-sustaining, it's harder to see those benefits because at that point, it just feels like it's all downside: you are basically giving what you built away to your direct competitors, you are seeing significant value scattered throughout the ecosystem that you are capturing a very small portion of, and it becomes frustrating—especially in historical environments—where you have the sense of—back when you built the company years ago, it's well, obviously we'd be the best place to host and run this because no one's going to run this as well as the people who built it. And then cloud companies, with their operational excellence, come in and put the lie to that, in many cases [laugh]. It's like, oh dear. Not like that.And I understand, truly, the frustration and the pain and the fear that drives companies in that position. And I don't have a better answer, which is my big problem because I'm just sitting here saying, “You're doing it wrong. Don't do it like that.” “Okay, well, what should they do instead?” “No, I just want to be angry. I'm not here to offer solutions.” And I feel for them. I do. I have a lot of empathy for everyone involved in this conversation. It just sucks, but we need a better outcome than the current state, or we're going to not see the same open innovation. Even these days, when I build things, by default, I don't build in the open, not because I'm worried about competitive threats, but because I don't want to deal with people complaining to me about things that I've built and don't want to think about this week.Danilo: I think that we're living through the hangover of—I mean, if you looked at the crypto craze as an example of this hangover, right—here we were with the sky the limit. We can sell monkey pictures for extraordinary amounts of money and there's nothing behind it. We went from euphoria to fear in the space of a handful of quarters. And so, that has put all of us, even the most optimistic, in a place where we feel our backs are against the walls. But I think the responsibility we have is, again, computing fundamentally changes the economics of so many categories of labor, and it changes the economics of information generally.And so, we can do a bunch of stuff that doesn't cost that much over the long-term, relative to the value it creates. But it only works if we have a really clear thesis of the value we're creating. If we don't value the contributions of a community, if we don't value the emergent outcomes that arise from building something that's very expressive, that then lets outsiders show up and do things that we never predicted, if we're not building strategies that look at this value as something that is precious instead of something to be cut off and captured, then I think that we just continue to spiral down the drain of paranoia, and greed, and fear instead of doing things that actually create long-term sustainable growth for our business.Corey: I really wish that there were easier, direct paths. Like on some level, too, it's—I feel like this is part of the problem, that every company views going public as its ultimate goal.Danilo: Yeah.Corey: At least that's what it feels like. Like The Duckbill Group. If we ever go public, my God, I will have been so far gone from this company long before then, just because at that point, you have given control over to people who are not aligned, in many cases, with the values that you founded the company with. Like, one of the things I love about being a small business is that I don't need to necessarily think the next quarter's earnings. I can think longer-term. “Okay, in two or three years, what do I want to be doing?” Or five or ten. I'm not forced into this narrow, short-sighted treadmill where I have to continually show infinite growth in all areas at all times. That doesn't sound healthy.Danilo: I agree, and I think that this is a place where I can give you a lot of hope because I look at a handful of economic tailwinds that are really going to make it possible to build businesses in a different way than was practical before. If we look at the last cycle, one of the absolute game changers was open-source. So, you showed up and there was already a web server written for you, and there was already a database written for you, and so you would just pull these things off the shelf instead of having to hire a team that would build your web server from scratch, that would build your database from scratch. And so, that changed the economics of how companies could be made, and that created an entire cycle of new technology growth.And if we look for an analogy of that kind of labor savings for the next technology cycle, we're going to see things like cloud-based serverless services, right? So like, now you don't need to even administer a Linux server. You don't need to know how the server works under the hood. You pay one company for an API that gives you a database, and they manage the stuff. So, I'm thinking of companies like Neon, or PlanetScale, right? You give them cash, they give you a database, they worry about it, they do all of the on-call stuff, you don't have to think about. So, this makes it even cheaper to build things of higher complexity because you are outsourcing much of the management of that complexity to other firms. And I think that that pattern is going to change the overall costs of starting and scaling and maintaining any sort of web-based product. And so, that's number one.And then number two, is that when we look at stuff like large language models, the stuff that you can do with ChatGPT in terms of figuring out how to solve a broad array of problems that maybe you don't have a lot of domain expertise in, I think that means that we're going to see smaller teams get even further than we expect. And so, the net result of these trends is going to be, you don't need to take vast amounts of venture funding in order to get to a company that serves a large number of people at a meaningful scale, with meaningful returns for the principles involved, and then they don't have to go all the way down to the IPO route. They don't have to figure out some sort of mega-scale unicorn exit; they can just build companies that work, that solve customer problems, keep it close, and then you don't have the totalizing endless need for growth. I think we're going to see a lot more of that this cycle.Corey: I sure hope you're right. I think that there's been a clear trend toward panic, or at least if not panic, then at least looking at current conditions and assuming that they'll persist forever. We just saw ten years of an unprecedented bull run, where people tended to assume that interest rates would be forever low, growth was always going to be double-digit at least, and there was no need to think about anything that would ever argue against those things. For the first few years of my consulting company, it was a devil of a problem trying to convince people to care about their AWS bills because frankly, when money is free, there is no reason for someone to. They are being irrational if they do. Now, of course, that's a very different story, but at the time, I felt for a while like I was the one who was nuts.Danilo: So, the interest rate conditions are always going to make people behave a certain way. That's why they exist, right? We have monetary policy designed to influence business behavior. And if we look at that zoom, then we say, “All right, look, this stuff is all cyclical. We know there's going to be good times, we know there's going to be lean times, but at the end of the day, we care about building stuff.” Right?I don't spend a lot of time with the sort of venture capitalist set who's really obsessed with building, but I really love building. I just, I can't stop building things. It is what I was put on this planet to do, and I think that there are so many people who feel exactly the same way. And so, regardless of the larger interest-rate phenomenon, we have to find a path where we can just build the stuff that we need to build. Build it for our reasons, for the right reasons, not because we just want to cash out. Although, you know, getting paid is great. I don't begrudge anyone that.Corey: You can't eat aspirations, as it turns out.Danilo: That's right, right? We've got to worry about the economics, and that's reasonable. But at the end of the day, making things happen through technology is its own mission and its own reward, regardless of what some sort of venture fund needs to make return happen. So, I think that we are going to get past this moment of slump and return to the fundamentals of we need to build technology because building technology makes us feel good and creates impact in the world that we absolutely need. And those are the fundamentals of this business.Corey: I agree with you wholeheartedly. I think that I've been around too many cycles—this is a polite way of saying I'm old—and you learn when that happens that everything that feels so immediate and urgent in the moment, in the broad sweep of things, so rarely is. Not everything can be life or death because you'll die lots of times.Danilo: Yeah.Corey: I really want to thank you for taking the time to speak with me. If people want to learn more, where's the best place for them to find you?Danilo: If you want to engage me for my thinking and strategy around humanist technology tools growth, you should find me at antigravitydx.com. And if you want to read more about what I think about, I maintain a blog at redeem-tomorrow.com, and you can learn all about my thinking about the last cycle, and the coming one as well.Corey: And I will absolutely include a link to that in the [show notes 00:31:52]. Thank you so much for taking the time to speak with me. I appreciate it.Danilo: It's a pleasure, Corey. Thank you for having me. Really great to chat.Corey: Danilo Campos, proprietor at Antigravity DX. I'm Cloud Economist Corey Quinn, and this is Screaming in the Cloud. If you've enjoyed this podcast, please leave a five-star review on your podcast platform of choice, whereas if you've hated this podcast, please leave a five-star review on your podcast platform of choice, along with an angry, insulting comment taking care within that comment to link to a particular section of the FutureAdvisor code repo.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.

In this episode of Syntax, Wes and Scott talk about the lessons they learned while launching the new Syntax website including launching now, transcription bugs, error monitoring, black text on black backgrounds, and more. Show Notes 00:10 Welcome to Syntax 01:41 Syntax Brought to you by Sentry 02:43 Don't wait. Launch! 04:28 Transcript bug Most Powerful Speech-to-Text API | Deepgram 09:01 Error monitoring is a must 12:36 Timestamp error 16:20 Black text on black background might hide things 17:33 WASM Vercel file system 21:18 Things have gotten easier to launch PlanetScale: The world's most advanced database platform — PlanetScale 23:36 Switching from OpenAI to Anthropic Claude and AI Responses aren't always JSON 25:34 Local dev is fast Navigation API 31:37 Mind your payloads 32:41 GitHub Milestones 33:57 Almost forgot the Robots.txt 36:17 Chron job timeout Inngest 40:06 TypeScript errors don't need to be zero to launch 42:25 GitHub Actions pipeline bug 43:23 Basic testing will do Playwright 44:56 Have a designer to work with Airbase 52:07 Sick Picks Sick Picks Scott: Dog Poop Bags With Dispenser Wes: Resistance band Shameless Plugs Scott: Sentry Wes: Wes Bos Courses Hit us up on Socials! Syntax: X Instagram Tiktok LinkedIn Threads Wes: X Instagram Tiktok LinkedIn Threads Scott: X Instagram Tiktok LinkedIn Threads

The near-cinematic trailer for the backend banter podcast. Featuring The Primeagen, Melkey, TJ Devries, Miriah Peterson, Bill Kennedy, and Brian Morrison from PlanetScale. Hope you like the pod!

PHP used to suck, but Aaron Francis, content creator and developer at PlanetScale, is on a mission to change the narrative. We talk about why PHP doesn't suck anymore and the features that have improved it. Links https://twitter.com/aarondfrancis https://www.youtube.com/@aarondfrancis https://aaronfrancis.com https://www.linkedin.com/in/aarondfrancis https://www.youtube.com/watch?v=ZRV3pBuPxEQ&ab_channel=AaronFrancis Tell us what you think of PodRocket We want to hear from you! We want to know what you love and hate about the podcast. What do you want to hear more about? Who do you want to see on the show? Our producers want to know, and if you talk with us, we'll send you a $25 gift card! If you're interested, schedule a call with us (https://podrocket.logrocket.com/contact-us) or you can email producer Kate Trahan at kate@logrocket.com (mailto:kate@logrocket.com) Follow us. Get free stickers. Follow us on Apple Podcasts, fill out this form (https://podrocket.logrocket.com/get-podrocket-stickers), and we'll send you free PodRocket stickers! What does LogRocket do? LogRocket combines frontend monitoring, product analytics, and session replay to help software teams deliver the ideal product experience. Try LogRocket for free today. (https://logrocket.com/signup/?pdr) Special Guest: Aaron Francis.

What would it look like if databases were built for developers rather than operators? Sam Lambert is the CEO of PlanetScale, a company that provides a managed MySQL database solution. PlanetScale uses Vitess, a database clustering system that allows for horizontal scaling of MySQL. MySQL powers an incredible amount of the internet, and Vitess is behind enormous MySQL installs at YouTube, Slack, GitHub, and more.  In this show, we talk about the architecture of Vitess, what it's like to manage upgrades and releases of high-scale databases, and how to maintain a high-performance culture.

In this podcast Shane Hastie, Lead Editor for Culture & Methods spoke to Nick van Wiggeren of PlanetScale about what it takes to build and nurture great teams. Read a transcript of this interview: https://bit.ly/47jLbPT Subscribe to the Software Architects' Newsletter [monthly]: www.infoq.com/software-architect…mpaign=architectnl Upcoming Events: QCon San Francisco https://qconsf.com/ Oct 2-6, 2023 QCon London https://qconlondon.com/ April 8-10, 2024 Follow InfoQ: - Mastodon: https://techhub.social/@infoq - Twitter: twitter.com/InfoQ - LinkedIn: www.linkedin.com/company/infoq - Facebook: bit.ly/2jmlyG8 - Instagram: @infoqdotcom - Youtube: www.youtube.com/infoq Write for InfoQ - Join a community of experts. - Increase your visibility. - Grow your career. www.infoq.com/write-for-infoq/?u…aign=writeforinfoq

We're delighted to welcome Lorynn Boland to our program! She is an EA who has navigated both sides of the aisle, so to speak, having spent five years at Kleiner Perkins, the legendary venture capital firm, and now the last six months supporting the CEO of PlanetScale, a database platform for developers with infinite scalability. Today we'll be learning about Lorynn's experiences of supporting in these environments which, while different, are also inextricably linked and symbiotic. We feel this is an important conversation to have, as there is definitely a compatibility and common language between these respective industries, as well as some noteworthy differences. For anyone curious to understand these difference or for someone who is perhaps preparing for a job interview or transition from one side to the other, today's conversation will be particularly valuable.

Lane and Brian talk about scaling databases, particularly MySQL, Vitess, and the PlanetScale platform. Brian is a developer educator at PlanetScale, and he breaks down how you can think about scaling databases for your own projects, or for the companies you work for. PlanetScale is used for cloud MySQL deployments in the new CI/CD course on Boot.dev that just dropped!Brian on Twitter: https://twitter.com/brianmmdevPlanetScale: https://planetscale.com/

On today's episode, Chris and Andrew have an early start and catch up on their lives. Then, they dive deep into the latest developments in the Rails community, including the release of Rails 7.0.6, bug fixes, and changes to Active Record.  They share their experiences with GitHub deployments, documentation issues, and how they navigate through its challenges. They discuss the benefits of MySQL and Postgres, as well as the ongoing advancements in Postgres, specifically Crunchy Data's contributions.  Chris and Andrew share their views on working in different company sizes, the joys of learning new things, dealing with burnout, and the slower pace of feature shipping in larger companies. There's a discussion on Reddit's recent actions, its impact on subreddit moderations, and the discontinuation of the Reddit API. We'll also hear about Chris's cooking adventures, experimenting with different flavors, and making some Texas Twinkies. Hit download to hear more! [00:02:00] Chris and Andrew talk about the release of Rails v7.0.6 with bug fixes and changes in libraries like Action Cable and Active Record, including subqueries and associations with polymorphic relationships.[00:06:10] Andrew is curious about the GitHub deployment stuff and expresses his desire to create GitHub deploys from Heroku. They talk about the complexities of setting up GitHub deployments and the lack of clear information from GitHub, and how the documentation with Checks API can be confusing to set up. [00:09:49] Chris discusses the challenges of figuring out GitHub's deployment process and the lack of documentation. He expresses frustration with the lack of clarity and support for smaller accounts. [00:14:41] PlanetScale is brought up and its association with MySQL, and they discuss the benefits of MySQL and Postgres, and the new features and advancements in Postgres, including Crunchy Data's contributions and the potential use of Postgres in web environments. [00:17:43] Chris shares a fun story about working on implementing jump server support in the new Hatchbox.  They encountered unexpected complexities with the net-ssh gem to address the problem. [00:29:51] Chris emphasizes the importance of being mindful of memory usage and performance trade-offs and how it becomes more critical when building large-scale products. [00:31:59] Andrew mentions that releasing features can be challenging and Podia is currently facing that challenge with releasing a feature while also building onto it. He emphasizes the importance of coordination, communication, and learning from code to recognize and solve problems faster. [00:33:46] Chris reflects on his experience working at a consulting agency and how it allowed him to learn quickly by facing different projects and finds joy learning new things as a programmer. [00:34:43] We hear Andrew talk about feeling stuck in a job, comparing small companies which offer more challenges, to big companies where employees get stuck doing the same tasks, and Chris tells us he's happiest when learning new things and how it accelerates burnout.[00:35:57] Chris discusses the challenges faced by big companies when it comes to feature shipping due to the need to ensure existing users are not negatively impacted, and Andrew highlights the varying levels of impact when breaking code and emphasizes the importance of being able to find and fix bugs quickly. [00:39:00] We hear about Chris's mad cooking skills with pulled pork and experimenting with smoked cream cheese which he hopes to use in some Texas Twinkies. [00:43:53] The conversation shifts to Reddit and its recent actions regarding subreddit moderation and the discontinuation of the Reddit API, and they express frustration with Reddit's handling of the situation and the negative consequences it's had on the community. [00:51:30] We end with Chris needing to attend to his cooking tasks and Andrew mentions his responsibility to lead Podia in Jason and Jamie's absence.   Panelists:Chris OliverAndrew MasonSponsor:HoneybadgerLinks:Jason Charnes TwitterChris Oliver TwitterAndrew Mason TwitterRails 7.0.6 PlanetScaleCrunchy DataReddit Won't Be the Same. Neither Will the Internet (WIRED)What the Heck is a Texas Twinkie?

Summary Data engineering is all about building workflows, pipelines, systems, and interfaces to provide stable and reliable data. Your data can be stable and wrong, but then it isn't reliable. Confidence in your data is achieved through constant validation and testing. Datafold has invested a lot of time into integrating with the workflow of dbt projects to add early verification that the changes you are making are correct. In this episode Gleb Mezhanskiy shares some valuable advice and insights into how you can build reliable and well-tested data assets with dbt and data-diff. Announcements Hello and welcome to the Data Engineering Podcast, the show about modern data management RudderStack helps you build a customer data platform on your warehouse or data lake. Instead of trapping data in a black box, they enable you to easily collect customer data from the entire stack and build an identity graph on your warehouse, giving you full visibility and control. Their SDKs make event streaming from any app or website easy, and their extensive library of integrations enable you to automatically send data to hundreds of downstream tools. Sign up free at dataengineeringpodcast.com/rudderstack (https://www.dataengineeringpodcast.com/rudderstack) Your host is Tobias Macey and today I'm interviewing Gleb Mezhanskiy about how to test your dbt projects with Datafold Interview Introduction How did you get involved in the area of data management? Can you describe what Datafold is and what's new since we last spoke? (July 2021 and July 2022 about data-diff) What are the roadblocks to data testing/validation that you see teams run into most often? How does the tooling used contribute to/help address those roadblocks? What are some of the error conditions/failure modes that data-diff can help identify in a dbt project? What are some examples of tests that need to be implemented by the engineer? In your experience working with data teams, what typically constitutes the "staging area" for a dbt project? (e.g. separate warehouse, namespaced tables, snowflake data copies, lakefs, etc.) Given a dbt project that is well tested and has data-diff as part of the validation suite, what are the challenges that teams face in managing the feedback cycle of running those tests? In application development there is the idea of the "testing pyramid", consisting of unit tests, integration tests, system tests, etc. What are the parallels to that in data projects? What are the limitations of the data ecosystem that make testing a bigger challenge than it might otherwise be? Beyond test execution, what are the other aspects of data health that need to be included in the development and deployment workflow of dbt projects? (e.g. freshness, time to delivery, etc.) What are the most interesting, innovative, or unexpected ways that you have seen Datafold and/or data-diff used for testing dbt projects? What are the most interesting, unexpected, or challenging lessons that you have learned while working on dbt testing internally or with your customers? When is Datafold/data-diff the wrong choice for dbt projects? What do you have planned for the future of Datafold? Contact Info LinkedIn (https://www.linkedin.com/in/glebmezh/) Closing Announcements Thank you for listening! Don't forget to check out our other shows. Podcast.__init__ (https://www.pythonpodcast.com) covers the Python language, its community, and the innovative ways it is being used. The Machine Learning Podcast (https://www.themachinelearningpodcast.com) helps you go from idea to production with machine learning. Visit the site (https://www.dataengineeringpodcast.com) to subscribe to the show, sign up for the mailing list, and read the show notes. If you've learned something or tried out a project from the show then tell us about it! Email hosts@dataengineeringpodcast.com (mailto:hosts@dataengineeringpodcast.com)) with your story. To help other people find the show please leave a review on Apple Podcasts (https://podcasts.apple.com/us/podcast/data-engineering-podcast/id1193040557) and tell your friends and co-workers Parting Question From your perspective, what is the biggest gap in the tooling or technology for data management today? Links Datafold (https://www.datafold.com/) Podcast Episode (https://www.dataengineeringpodcast.com/datafold-proactive-data-quality-episode-205/) data-diff (https://github.com/datafold/data-diff) Podcast Episode (https://www.dataengineeringpodcast.com/data-diff-open-source-data-integration-validation-episode-303/) dbt (https://www.getdbt.com/) Dagster (https://dagster.io/) dbt-cloud slim CI (https://docs.getdbt.com/blog/intelligent-slim-ci) GitHub Actions (https://github.com/features/actions) Jenkins (https://www.jenkins.io/) Circle CI (https://circleci.com/) Dolt (https://github.com/dolthub/dolt) Malloy (https://github.com/malloydata/malloy) LakeFS (https://lakefs.io/) Planetscale (https://planetscale.com/) Snowflake Zero Copy Cloning (https://www.youtube.com/watch?v=uGCpwoQOQzQ) The intro and outro music is from The Hug (http://freemusicarchive.org/music/The_Freak_Fandango_Orchestra/Love_death_and_a_drunken_monkey/04_-_The_Hug) by The Freak Fandango Orchestra (http://freemusicarchive.org/music/The_Freak_Fandango_Orchestra/) / CC BY-SA (http://creativecommons.org/licenses/by-sa/3.0/) Special Guest: Gleb Mezhanskiy.

On this episode of Remote Ruby, Jason, Chris, and Andrew begin by sharing their thoughts on some shows they're watching such as “White House Plumbers,” “Curb Your Enthusiasm,” and “Seinfeld.” The conversation then shifts towards the exciting release of Ruby 3.3 Preview 1, which focuses on performance improvements for YJIT and the introduction of compiler RJIT. They dive into the challenges of implementing autosaving and error display forms using Turbo and Hotwire in Rails. Then, the conversation takes a turn towards serverless function, with Andrew sharing his experiences using Vercel, and a discussion on Hatchbox and Fly for hosting applications, and the appeal of PlanetScale for databases. Go ahead and press download now to hear more! [00:00:20] The guys discuss a few shows they're watching.   [00:05:10] Chris announces the exciting release of Ruby 3.3 Preview 1, which introduces performance improvements for YJIT, and introduces the RJIT.  [00:07:11] Jason brings up an interview with Aaron Patterson that Justin Searls did at Ruby Kaigi 2023 where he talked about two people working on different parsers which could benefit alternative Ruby implementations.[00:09:38] A conversation came up somewhere about Laravel being a feature-rich framework, while Ruby is considered a better language.[00:10:59] Jason brings up the challenge of implementing autosaving and displaying errors in a form using Turbo and Hotwire in Rails. Chris mentions morphdom as a solution which can help with preserving focus during form updates.[00:16:23] Chris talks about autosaving features as a standard in modern web applications, and the need for built-in solutions within Rails is emphasized to simplify the implementation process.[00:22:00] Andrew shares his frustrations with implementing autosaving and validations.[00:25:55] Andrew explains what he was doing with functions in Vercel.[00:28:00] Jason brings up talking to Crunchy Data at RailsConf and the appeal of Planet Scale for databases. [00:30:40] Hatchbox and Fly for hosting applications is discussed and plans for upgrading Ubuntu versions and Hatchbox features.Panelists:Jason CharnesChris OliverAndrew MasonSponsor:HoneybadgerLinks:Jason Charnes TwitterChris Oliver TwitterAndrew Mason TwitterWhite House Plumbers (HBO MAX)Curb Your Enthusiasm (HBO MAX)Seinfeld (Netflix)Ruby Kaigi 2023-Aaron Patterson Interview (YouTube)morphdom-GitHubRemote Ruby Podcast-Episode 178: José Valim, creator of Elixir and former Rails core contributorVercelCrunchy DataPlanetScaleHatchboxFlyUbuntuBuild and Learn Podcast by CJ Avilla and Colin LoretzRuby Radar TwitterRuby for All Podcast

#210: If you're feeling frustrated and overwhelmed due to your current database deployment and management process not working as expected, then you are not alone! Think about how many times you've needed to maintain the schema of your database and then you give up because it's either going to break things or it's going to take too long for a migration to happen.  In this episode, we speak with Sam Lambert, CEO of PlanetScale, about how running your own database should be considered a thing of the past and that you really shouldn't be scared to make changes to your database schema when it's as simple as doing a rewind.   Sam's contact information: Twitter: https://twitter.com/isamlambert LinkedIn: https://www.linkedin.com/in/isamlambert/   YouTube channel: https://youtube.com/devopsparadox/   Books and Courses: Catalog, Patterns, And Blueprints https://www.devopstoolkitseries.com/posts/catalog/   Review the podcast on Apple Podcasts: https://www.devopsparadox.com/review-podcast/   Slack: https://www.devopsparadox.com/slack/   Connect with us at: https://www.devopsparadox.com/contact/

Sugu Sougoumarane discusses how to face the challenges of horizontally scaling MySQL databases through the Vitess distribution engine and Planetscale, a service built on top of Vitess. The journey began with the growing pains of scale at YouTube around the time of Google's acquisition of the video service. This episode explores ideas about topology management, sharding, Paxos, connection pooling, and how Vitess handles large transactions while abstracting complexity from the application layer.

Jake and Michael discuss all the latest Laravel releases, tutorials, and happenings in the community.This episode is sponsored by Honeybadger - combining error monitoring, uptime monitoring and check-in monitoring into a single, easy to use platform and making you a DevOps hero. (05:34) - Laravel 10.5 released (10:47) - Everything you can test in your Laravel application (13:38) - Replace raw query calls with Laravel Query Expressions (19:12) - Validated DTO package for Laravel (22:14) - Sponsor: Honeybadger (23:16) - PlanetScale database migrations for Laravel (28:47) - Laravel expectations plugin for Pest (32:06) - Useful Laravel date scopes for Eloquent models (35:06) - Pest architecture plugin (36:11) - Let's talk about form requests

Sam Lambert is originally from the UK, and has lived quite a few places during his life. He went to school in India, but now resides in San Francisco. He finds software to be a creative, playful process, and sees people trying to build that away from the process. He feels very lucky to building something that provides fruit and solves problems. Outside of tech, he is married with a 4 year old, and is into cooking and art. I asked about NFT's, given his tech background, but he's not super into that form of art at this time.Sam spent time working at Github as a VP of Engineering, specifically focusing on infrastructure. He and his team came across Vitess, the backend that ran YouTube, and he took this amazing framework into his current venture to remix their approach of design and scalability.This is the creation story of PlanetScale.SponsorsAirbyteDopplerHost.ioIPInfomablSupportZebraLinksWebsite: https://planetscale.com/LinkedIn: https://www.linkedin.com/in/isamlambert/Support this podcast at — https://redcircle.com/code-story/donationsAdvertising Inquiries: https://redcircle.com/brandsPrivacy & Opt-Out: https://redcircle.com/privacy

Malware infecting widely used security appliance survives firmware updates IceFire Ransomware Portends a Broader Shift From Windows to Linux Thousands scammed by AI voices mimicking loved ones in emergencies Personal details of U.S. House members exposed in health data breach Biden FCC nominee withdraws, blaming cable lobby and "unlimited dark money" Nick Van Wiggeren, VP of Engineering with PlanetScale talks about fully managed database-as-a-service. Hosts: Louis Maresca, Brian Chee, and Curtis Franklin Guest: Nick Van Wiggeren Download or subscribe to this show at https://twit.tv/shows/this-week-in-enterprise-tech. Get episodes ad-free with Club TWiT at https://twit.tv/clubtwit Sponsors: GO.ACILEARNING.COM/TWIT ZipRecruiter.com/twiet kolide.com/twiet

Malware infecting widely used security appliance survives firmware updates IceFire Ransomware Portends a Broader Shift From Windows to Linux Thousands scammed by AI voices mimicking loved ones in emergencies Personal details of U.S. House members exposed in health data breach Biden FCC nominee withdraws, blaming cable lobby and "unlimited dark money" Nick Van Wiggeren, VP of Engineering with PlanetScale talks about fully managed database-as-a-service. Hosts: Louis Maresca, Brian Chee, and Curtis Franklin Guest: Nick Van Wiggeren Download or subscribe to this show at https://twit.tv/shows/this-week-in-enterprise-tech. Get episodes ad-free with Club TWiT at https://twit.tv/clubtwit Sponsors: GO.ACILEARNING.COM/TWIT ZipRecruiter.com/twiet kolide.com/twiet

Malware infecting widely used security appliance survives firmware updates IceFire Ransomware Portends a Broader Shift From Windows to Linux Thousands scammed by AI voices mimicking loved ones in emergencies Personal details of U.S. House members exposed in health data breach Biden FCC nominee withdraws, blaming cable lobby and "unlimited dark money" Nick Van Wiggeren, VP of Engineering with PlanetScale talks about fully managed database-as-a-service. Hosts: Louis Maresca, Brian Chee, and Curtis Franklin Guest: Nick Van Wiggeren Download or subscribe to this show at https://twit.tv/shows/this-week-in-enterprise-tech. Get episodes ad-free with Club TWiT at https://twit.tv/clubtwit Sponsors: GO.ACILEARNING.COM/TWIT ZipRecruiter.com/twiet kolide.com/twiet

Malware infecting widely used security appliance survives firmware updates IceFire Ransomware Portends a Broader Shift From Windows to Linux Thousands scammed by AI voices mimicking loved ones in emergencies Personal details of U.S. House members exposed in health data breach Biden FCC nominee withdraws, blaming cable lobby and "unlimited dark money" Nick Van Wiggeren, VP of Engineering with PlanetScale talks about fully managed database-as-a-service. Hosts: Louis Maresca, Brian Chee, and Curtis Franklin Guest: Nick Van Wiggeren Download or subscribe to this show at https://twit.tv/shows/this-week-in-enterprise-tech. Get episodes ad-free with Club TWiT at https://twit.tv/clubtwit Sponsors: GO.ACILEARNING.COM/TWIT ZipRecruiter.com/twiet kolide.com/twiet

MLOps Coffee Sessions #147 with Alex DeBrie, Something About Databases co-hosted by Abi Aryan. // Abstract For databases, it feels like we're in the middle of a big shift. The first 10-15 years of the cloud were mostly about using the same core infrastructure patterns but in the cloud (SQL Server, MySQL, Postgres, Redis, Elasticsearch). In the last few years, we're finally seeing data infrastructure that is truly built for the cloud. Elastic, scalable, resilient, managed, etc. Early examples were Snowflake + DynamoDB. The most recent ones are all the 'NewSQL' contenders (Cockroach, Yugabyte, Spanner) or the 'serverless' ones (Neon, Planetscale). Also seeing improvements in caching, search, etc. Exciting times! // Bio Alex is an AWS Data Hero and self-employed AWS consultant and trainer. He is the author of The DynamoDB Book, a comprehensive guide to data modeling with DynamoDB. Previously, he worked for Stedi and for Serverless, Inc., creators of the Serverless Framework. He loves being involved in the AWS & serverless community, and he lives in Omaha, NE with his family. // MLOps Jobs board https://mlops.pallet.xyz/jobs // MLOps Swag/Merch https://mlops-community.myshopify.com/ // Related Links Key Takeaways from the DynamoDB Paper: https://www.alexdebrie.com/posts/dynamodb-paper/ Understanding Eventual Consistency in DynamoDB: https://www.alexdebrie.com/posts/dynamodb-eventual-consistency/ Two Scoops of Django 1.11: Best Practices for the Django Web Framework: https://www.amazon.com/Two-Scoops-Django-1-11-Practices/dp/0692915729CAP or no CAP? Understanding when the CAP theorem applies and what it means: https://www.alexdebrie.com/posts/when-does-cap-theorem-apply/ Stop fighting your database/ The DynamoDB book: https://dynamodbbook.com/ --------------- ✌️Connect With Us ✌️ ------------- Join our slack community: https://go.mlops.community/slack Follow us on Twitter: @mlopscommunity Sign up for the next meetup: https://go.mlops.community/register Catch all episodes, blogs, newsletters, and more: https://mlops.community/ Connect with Demetrios on LinkedIn: https://www.linkedin.com/in/dpbrinkm/ Connect with Abi on LinkedIn: https://www.linkedin.com/in/abiaryan/ Connect with Alex on LinkedIn: https://www.linkedin.com/in/alex-debrie/ Timestamps: [00:00] Alex's preferred coffee [00:27] Introduction to Alex DeBrie and DynamoDB [01:05] Takeaways [03:47] Please write down your reviews and you might have a book of Alex! [04:57] Alex's journey from being an Attorney to becoming a Data Engineer [07:31] Why engineering? [10:07] Serverless Data [12:54] Before Airflow [15:41] Batch vs streaming [17:03] Difficulties in Batch and Streaming side [19:45] Modern data infrastructure databases [24:37] Cloud Ecosystem Maturity [27:59] New generation type of Snowflake [29:47] Comparing databases [30:58] What's next on connectors from 2 perspectives? [34:25] Management services at the MLOps level [36:38] DynamoDB [39:32] Why do you like DynamoDB? [41:00] Data used in DynamoDB and size limits [43:46] Comparison of tradeoffs between DynamoDB and Redis [45:52] Preferred opinionated databases [48:43] CAP or no CAP? Understanding when the CAP theorem applies and what it means [52:10] The DynamoDB book [56:17] Chapter you want to expand on the book [57:43] Next book to write [59:25] ChatGPT iterations [1:01:59] Data modeling book wished to be written [1:03:27] Wrap up

Databases are key to almost any project, large or small.  Most database systems in the cloud are designed for heavy use and the costs can get expensive quickly, but database-as-a-service is a rapidly growing area, where many databases can share the same hardware for a much reduced rate, or even for free!  Sam Lambert, CEO of PlanetScale, joins Jason and Patrick to discuss database-as-a-service.00:01:41 Introductions00:02:34 Sam's Github learning lesson00:07:08 The day after00:10:57 Getting started with databases00:14:21 Schema change difficulties00:19:47 Database transactions00:31:15 Why data recovery matters00:38:35 Planetscale00:49:24 Greetings from the past01:02:01 How Jason discovered Planetscale01:06:53 Branching01:14:00 The vision for Planetscale01:18:12 The rationale behind Planetscale's work setup01:24:29 Careers at Planetscale01:28:06 Amp It Up01:33:10 FarewellsResources mentioned in this episode:Links: Sam Lambert:Linkedin: https://www.linkedin.com/in/isamlambert/ PlanetScale: Website: https://planetscale.com/ Twitter: https://twitter.com/planetscaledata Linkedin: https://www.linkedin.com/company/planetscale/ Github: https://github.com/planetscale Careers: https://planetscale.com/careers Amp It Up (Amazon): Paperback: https://www.amazon.com/Amp-Unlocking-Hypergrowth-Expectations-Intensity/dp/1119836115 Audiobook: https://www.amazon.com/Amp-Hypergrowth-Expectations-Increasing-Elevating/dp/B09QBRBKFB/ If you've enjoyed this episode, you can listen to more on Programming Throwdown's website: https://www.programmingthrowdown.com/Reach out to us via email: programmingthrowdown@gmail.com You can also follow Programming Throwdown on Facebook | Apple Podcasts | Spotify | Player.FM  Join the discussion on our DiscordHelp support Programming Throwdown through our Patreon ★ Support this podcast on Patreon ★

Fouad Matin, Co-founder & CEO of Indent, joins Corey on Screaming in the Cloud to discuss how to get data security right without creating unnecessary barriers for your development team. Fouad and Corey discuss how getting admin access as a developer can be time consuming and vague, when it should be efficient and come with an easily defined reason for granting access. Fouad also explains why he feels most breaches are due to not getting the basics right, and why he feels storing customer and sensitive data should be done with the same principles as dealing with hazardous waste.About FouadFouad Matin is the co-founder and CEO of Indent, a security company that enables teams to perform mission-critical operations faster and more securely. With Indent, organizations like HackerOne, Modern Treasury, Vercel, and PlanetScale are able to grant secure, time-bound user and admin permissions for cloud apps and infrastructure through Slack.Prior to Indent, Fouad worked as an engineer at Segment, a customer data platform helping companies secure their pipelines for handling customer data. He co-founded a non-partisan non-profit in 2016 to help people register and get out to vote through easy-to-use, privacy preserving tools. In 2018, while validating Indent's mission, partnered with Vote.org to build tools for users to find their polling place and preview their ballot using client-side encryption.Links Referenced: Indent: https://indent.com Nobody Should Have Production Access: https://indent.com/blog/production Fouad on Twitter: https://twitter.com/fouadmatin Indent on Twitter: https://twitter.com/indent Unplanned Maintenance: https://unplannedmaintenance.com Least Privilege in Practice Blog Post from Indent: https://indent.com/blog/least-privilege Additional Links Referenced: Email: mailto:fouad@indent.com Fouad LinkedIn: https://www.linkedin.com/company/indentinc/ Indent LinkedIn: https://www.linkedin.com/in/fouadmatin/

Iheanyi Ekechukwu and Mike Coutermarsh talk about PlanetScale, what Vitess is, if PlanetScale is for both side and big projects, what read only regions are, what schema changes are, and how PlanetScale compares to other projects.

Matt Robenolt is a part of the infrastructure team at PlanetScale. Matt joins us today to talk about his blog post titled Faster MySQL with HTTP/3. Links https://twitter.com/mattrobenolt https://www.linkedin.com/in/mattrobenolt https://mattrobenolt.com https://github.com/mattrobenolt https://planetscale.com/blog/faster-mysql-with-http3 https://www.mysql.com https://planetscale.com Tell us what you think of PodRocket We want to hear from you! We want to know what you love and hate about the podcast. What do you want to hear more about? Who do you want to see on the show? Our producers want to know, and if you talk with us, we'll send you a $25 gift card! If you're interested, schedule a call with us (https://podrocket.logrocket.com/contact-us) or you can email producer Kate Trahan at kate@logrocket.com (mailto:kate@logrocket.com) Follow us. Get free stickers. Follow us on Apple Podcasts, fill out this form (https://podrocket.logrocket.com/get-podrocket-stickers), and we'll send you free PodRocket stickers! What does LogRocket do? LogRocket combines frontend monitoring, product analytics, and session replay to help software teams deliver the ideal product experience. Try LogRocket for free today. (https://logrocket.com/signup/?pdr) Special Guest: Matt Robenolt.

The communication between backend applications and database systems always fascinated me. The protocols keep evolving and we are in constant search for an efficient protocol that best fit the workload of Backend-DB communication. In this episode of the backend engineering show I go through a blog written by @PlanetScale doing an experimentation of using HTTP/3 and HTTP/2 comparing it with MySQL Binary protocol. https://planetscale.com/blog/faster-mysql-with-http3 0:00 Intro 7:45 MySQL Binary vs HTTP 10:20 The Tests 15:00 Connection Cost + Select 1 22:00 Parallel Select 26:00 The cost of H2 and H3

About TaylorTaylor Barnett is a Staff Developer Advocate at PlanetScale. She is passionate about building great developer experiences emphasizing empathy within product, documentation, and other developer-facing projects. For the past decade, Taylor has worked at various data and API-focused startups in software development and developer relations. In her free time, as a firm believer in "touching grass," she's either gardening, taking long walks, climbing rocks with friends, trying to find the funkiest sour beers, or hanging out with her corgi, Yoda, and spouse in Austin, Texas.Links Referenced: PlanetScale: https://planetscale.com/ Twitter: https://twitter.com/taylor_atx Personal website: https://taylorbar.net 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: If you asked me to rank which cloud provider has the best developer experience, I'd be hard-pressed to choose a platform that isn't Google Cloud. Their developer experience is unparalleled and, in the early stages of building something great, that translates directly into velocity. Try it yourself with the Google for Startups Cloud Program over at cloud.google.com/startup. It'll give you up to $100k a year for each of the first two years in Google Cloud credits for companies that range from bootstrapped all the way on up to Series A. Go build something, and then tell me about it. My thanks to Google Cloud for sponsoring this ridiculous podcast.Corey: This episode is sponsored by our friends at Logicworks. Getting to the cloud is challenging enough for many places, especially maintaining security, resiliency, cost control, agility, etc, etc, etc. Things break, configurations drift, technology advances, and organizations, frankly, need to evolve. How can you get to the cloud faster and ensure you have the right team in place to maintain success over time? Day 2 matters. Work with a partner who gets it - Logicworks combines the cloud expertise and platform automation to customize solutions to meet your unique requirements. Get started by chatting with a cloud specialist today at snark.cloud/logicworks. That's snark.cloud/logicworksCorey: Welcome to Screaming in the Cloud. I'm Corey Quinn. I'm joined this week by Taylor Barnett, Staff Developer Advocate at PlanetScale. Taylor, you're one of those people that I'm ashamed I haven't had on the show before now. Thanks for joining me.Taylor: You're welcome. Yeah, I'm glad to be here.Corey: We've been traveling in similar circles for a while now. And I lost track of a lot of those areas when the pandemic hit, you know, the global plague o'er the land. And during that time, it seemed like there was a lot of question that folks had about what is developer advocacy. What does DevRel become now? And now that we're largely on the other side of it—at least business is pretending that we're behind it—do we have an answer yet?Taylor: I hope so. I mean, I have an answer. Not sure if other businesses have figured that out yet. But no, I mean, to me, advocacy is still just that glue between company and a community. But I think one of the things that the pandemic has really, like, pushed that, you know, when there were no in-person events, was that it questioned what activities that actually looks like.You know, I see advocacy as a ton of different levers and you can tweak those levers to different levels. Before, it was largely a lot of in-person stuff—I will say I was doing less in-person, actually before than most; I was doing a little bit more content—then it had to become so content-focused. And I think now we're in this awkward place where in-person events have come back and we're still, like, figuring out, like, how do we do those? What does that look like? And we've actually—I think part of it is we've over-indexed now on content.I think part of that is because it is visible and it is measurable, and that's always a big topic [laugh] in developer relations is metrics. But also, I think we've lost track of the actual advocacy part: how do we actually advocate for users internally? It's just disappeared a little bit because we were so content-focused during the pandemic.Corey: I would say that's been a recurring theme with every DevRel person that I've spoken to that metrics are the bane of their existence. And I want to be clear, I'm not just talking about developer advocates, I'm talking about people who manage and run developer advocacy teams, I'm talking about executives who are trying to bring the appropriate context to strategic-level discussions around these things. All of the metrics that I have been able to uncover are wrong. But it's like the, ‘all models are wrong, but some models are useful' type of approach, where—Taylor: Yeah.Corey: Every time you start putting a metric around it and measuring people based upon the outcome of that metric, it ends in disaster. My one and only interview for a DevRel job in my past was my question for them was how do you measure success? “Well, we want to see you have talks accepted at some of the big tier-one conferences.” And they list a few examples, and it's, yeah, “I've spoken at for the ones you just listed in the past year, so… do I get a raise?” It's one of those areas where there's no right answer, but a lot of wrong ones.Taylor: Yeah. And one of the other troubling patterns that I've started to see also more is that in these cloud startups, they have DevRel programs now that are fairly young, we're talking not even a year old. Some in the recent DevRel survey results, it was about, like, 29% of programs are less than a year old. Within those programs, 43% of those people have not even been in a DevRel role for more than a year. So, not only do we have folks that haven't done this before, the startup has not done this before.And so, the metrics conversation is basically a shit show. People with the right experiences aren't in these roles and so they're not able to craft strategies and actually look at good metrics. And so, then we then over-index on the things like, “Oh, you wrote a blog post.” Great, you know, that's, like, some kind of metric. “It got X number of page views.” Great, that's some kind of metric.And it often incentivizes some of the wrong things. And so, then it just incentivizes more and more of this content creation, to just get those pageviews up. And it's scary to me because then we're just going back to the more evangelist type of developer relations and less of the advocacy type stuff where we're actually advocating for users internally.Corey: I would agree. I'd say that there's a problem where we have a, almost across the board, lack of understanding about—let's even start at the very beginning of when DevRel is required or when it's not. I mean, take where you work now at PlanetScale. You're effectively managed Vitess-as-a-service. That's a little on the technical side and is not the sort of thing that's going to necessarily lend itself to a mass-market marketing approach.This is not something to put on billboards outside of most highways, for example, but it does require engaging with people on a technical level. I keep joking but also serious when I refer to DevRel as meaning you work in marketing, but they're scared to tell you.Taylor: Yeah. No, I mean, I actually sometimes say, “Well, like, I'm secretly probably a pretty good product marketer, but I don't want developers to know that because then I'll lose my street cred from my actual development and engineering background.” And I have a computer science degree and, like, I'm actually, like [laugh], very, very technical. But the reality is, like, you know, somebody's got to write the words, sometimes.Corey: The words are harder when they go into people then they are into computers. At least with computers—Taylor: Exactly.Corey: It's pretty—it's a bounded problem space to some extent. With people, oh no, no, there's no consistency at all.Taylor: Yeah. And like, words mean different things to different people, especially, like, my favorite one lately is, like, what does edge mean? Nobody actually has one [laugh] definition of that word.Corey: Oh, I think most of them do. Edge always means, “Oh, it's a way of describing the thing that we've been doing for 15 years, but now want to sell into a hype cycle.”Taylor: Yeah, yeah. I mean, CDNs have been around for a while. You know, and that's really—like, what PlanetScale, it is, in some ways, we're challenging what people expect from their database. We think you can actually expect more from your database platform, and so there are things you know, to teach people about some of these newer ways of working with a database. And that requires needing to think about how we present that to users, but also hearing back from users how do we work within their applications, their stacks.We're MySQL. That's, you know, a trusted standard. It's been around for a while, so it works with many, but also, we're in this whole new paradigm of how to use a database. These are all new ideas and they require both a two-way street of both putting things out there—so content, not bad; it's still needed—but also things coming in and taking that, making it actionable, and talking about it internally.Corey: When you take a look at the DevRel world, what do you think that most organizations are missing or getting wrong about it? And yes, I understand that I'm basically asking you to start beef with a whole bunch of companies out there, but that's all right. It's what we do here.Taylor: Yeah, one of the things I love, [Matty 00:07:44] Stratton had this thing where I tweeted out a few months ago that we've over-indexed on content, and matty's reply was that we've over-indexed on being able to do cool shit that isn't connected to revenue because that somehow is dirty for DevRel to somehow be connected to revenue. I think, you know, a lot of times, there are ways that we can look at how do users actually get value from our products. Like, are they actually getting value? One way they express that is by paying for it. So therefore, we are then somehow connected to revenue.I mean, I want to build things, I want to work on platforms that deliver value, that people actually want to pay for because they see this is makes my life easier, somehow. But to do that, and again, we've got to talk to our users. We've got to figure out where do they actually value. What are the things that are just fluff? There's a lot of fluff out there.Sometimes if we don't listen to them, then we don't have to find out that what we're building is fluff. So, that's probably the part that could start some beefs. But it's the reality of lots of VC money and tooling and being able to build things super easily, it's a bunch of different factors coming together in this time.Corey: One of the things that I don't pretend to understand, but I'm going to roll with it anyway, is there's been a lot of discourse on where DevRel does not belong in an org chart. I don't have a terrific answer at this, but I do know that most of the answers I get from practitioners in the space are deeply dissatisfying. It seems that—not to be unkind or cast aspersions where they don't belong, but whenever I ask the question, everyone has a whole laundry list of wrong answers and very few right ones.Taylor: I honestly will say I don't care [laugh]. I mean, that's the reality.Corey: Corporate IT. Got it.Taylor: Do I want to be on a team that makes me directly responsible for qualified leads? No. That does not necessarily say anything about the team itself. That is just a metric. That is—you know, and that team exists in a larger system that has put certain pressures on it.Like, you know, there's, like, things, like, it's more about how a team looks at just doing the DevRel stuff and doing marketing in general, or how they do sales. You know, I know lots of developers hate to hate on sales—marketing, too—and I don't necessarily think sales and marketing are a bad thing, I think is the way we incentivize those roles create bad behaviors, and so maybe we should look at how we incentivize them. And so, I don't care what team I'm honestly on most of the time. I've been on a few different ones. As long as I get to do the developer advocacy work that I actually think is impactful for developers and actually making developers' lives better, I'm cool.Corey: It's my belief, on some level, that it's very easy to internalize a bad expression of it. You can have phenomenally well-empowered DevRel teams working in marketing—Taylor: Yep.Corey: —at some companies, and in other places, it can be an absolute disaster because they start putting metrics like number of qualified leads around you. And I can't shake the feeling that people internalize, “Well, we've reported marketing once and it was terrible,” without realizing the context of yeah, but in a terrible way, and an org that didn't really understand what you do. That doesn't necessarily mean that you should throw that whole baby out with the bathwater.Taylor: Yeah, I mean, we've all had bad managers. So, we're not going to say we're just never going to have a manager.Corey: Some people try that.Taylor: Is that what you've done [laugh]?Corey: Indirectly. No, I was talking about more about the holacracy companies where oh yeah, no one reports to anyone. It's really? Because everyone makes different amounts of money, so one wonders about that.Taylor: Yeah. But by far, we just go find better managers is what we often do, you know? And there's the whole phrase that, like, people don't leave companies, they leave managers. It's very true in my experience. And we don't just say, “All marketing teams bad, so I'm never going to join a marketing team.” We should say, “Let's just go find one that fits better.”Corey: I was very frustrated in my last couple of real jobs because so much of what I was doing was DevRel-like, but this was before that was an established and accepted thing in the places that I worked, so there were questions like, “Well, what is the value of you going to give a keynote at this conference?” And the honest answer was, “Yeah, I have no idea how to quantify it, but I know that if I do it, good things come out of it.” And that was a difficult battle to fight, whereas now when I decided to go work for myself, it's, “Yeah, I'm going to go speak there. I don't know what the ROI is. I know good things and maybe some useful things will come out of it. Maybe I'll learn something, but this is how we experiment and learn.” And that looks an awful lot to most traditional management types. Like I'm trying to justify a trip somewhere.Taylor: Yeah. And I think, you know, what's been also interesting, as I noticed, some people are starting to notice a lot of more junior people wanting to get into developer relations. And we sometimes actually are wondering, some of us in developer relations, if we've not always shown like the negative parts of that. What happens when you go do that keynote? What does that mean for your week leading up to that keynote? What does travel look like? What is, like, running across an airport wearing a mask and carrying your luggage look like?I think we don't always get to see that and so it looks a little bit less glamorous when people see that. And maybe they would be slightly less interested in the role or just, like, how do you handle working with, like, five different teams across a company to try to be like that glue piece between all of them to get something done? Like, there's a lot less glamorous parts that I'm hoping more people talk about because, like you said, it just looks like you're trying to go get a trip somewhere. I think the other thing is, like, even if you are having a keynote, I think one of the things that some people—they think one keynote is going to just wreck a budget. The reality is for our business, it will not do that, so why can't we, like, have a better balance of extremes?Like, you're not going to be giving ten of those keynotes in a year, maybe experiment doing two and see what comes out of doing two of them. But the other thing is, it's a long-term game and so you're not going to see something maybe the week after. It could be six months later. I had this one experience where someone actually told me—it was probably, like, a whole year after I had given a talk—that him and his teammates—this was back when people you know, went into offices—sat in an office and watched one of my old talks together. And I was just like, what, like, y'all, like, got together and did that?Corey: Yeah, you could have invited me and I could have delivered it for you in person and answered questions, but all right.Taylor: Yeah. It was like, what I was just like, oh my gosh, that is literally never happened to me. This was a few years ago. And then, too, I was like, that just made it worth it. If you asked a CEO, would you like to have an advocate go give a talk for a whole team at a company, they'd be like, “Yes, I want you—” especially if that's a big company and the name is shiny and they would love to have that as a customer, they would be, like, a hundred percent, “Go give that talk.”And so, I think many times, leadership needs to actually kind of check in on, like, is this really that much of a cost if it's just, like, one keynote? I've seen battles over really feels like stupid things sometimes. But everything in moderation is kind of the way I approach it.[midroll 00:15:17]Corey: One problem that I tended to see and I don't know how closely your experience mirrors my own, but it seemed, especially in the before times, right before the pandemic hit, that we were almost trapped in a downward spiral at a lot of the conferences because it felt like it was mostly becoming DevRels speaking to DevRel. And that wasn't the most inclusive thing for folks who used to wind up going to a lot of local conferences to learn from their local community and see how other people were solving the problems that they were solving. Instead, it felt like a bunch of DevRel types getting up there, in most cases giving a talk that was heavily alluding to why you should buy their product, if not an outright sales pitch for it. And it just felt like we're losing something. Do you think that's something that we've avoided, that we've pressed pause on, with the pandemic and now the recession, or do you think there's something else afoot?Taylor: I think that's still happening today, especially with, like, engineers wanting sometimes to travel less, you know, some people still have personal and family reasons for not traveling, so even less of them are wanting to speak. I don't think I saw, like, a huge swath of engineers, like, really excited to speak once conferences started in person again. They thought, “Oh, my gosh, I have to go talk to people in person again?” And so, it's still happening. I've seen it from an organizer's perspective.I used to organize the API specifications conference. There's tons of DevRel submissions in there, so you know, we really tried to spend time reaching out to companies that were member companies of the OpenAPI Initiative and get them to actually have member engineers from their teams come speak. I think DevRel has a role to internally advocate for engineers who are doing the day-to-day work, go speak at conferences. You know, I think many times engineers feel like, “Oh, what I have to talk about is not very interesting.” And I have to tell them, it is very interesting, and I would love to have you speak, and I'm here to help you, and you know, need help writing a CFP? I'm there. You need help putting together slides, practicing talks? I'm there.And I think DevRel can be kind of like these coaches for folks to go speak at conferences because the reality is attendees want to hear from them. They want to hear engineers from especially major companies or companies just doing really interesting engineering challenges speaking. And I think DevRel has a part in helping that happen. I've personally backed away from speaking the last six months, partially because I'm kind of not seeing as much value for myself doing it before I was doing a lot more, so I'm using that effort to try to advocate internally to help people CFPs. Last week, I helped a bunch of people KubeCon submissions, and then next week, I have other conferences I would love to—I have engineers that I've kind of picked out that I would love to have speak. And yeah, I'm glad to play a part in trying to improve that. And I think other advocates should, too.Corey: Where do you think that we're going as an industry? Because it became pretty clear for a couple of years that so much of what we were doing and how we were discussing it, it felt like there was a brief moment in time that we could really transform what we were doing and start to have a broader awareness that DevRel was more than giving talks on stage at conferences. And it feels like we squandered that opportunity and it mostly turned into, oh, now we're going to give the same talks, we're just going to do it to webcams, either pre-recorded—which was the better approach—or we're going to do it live, even though there's no interactive component to it, just introduce a whole bunch of different failure modes. I was disappointed. I liked some of the early stuff I saw coming out, like Desert Island DevOps, where they did it inside of Animal Crossing. Like I wanted to see more stuff like that, but it just seems like we didn't.Taylor: Yeah, I mean, the reality is, I think a lot of the online events have disappeared a lot in the last three or four months. And we're also seeing events trying to be hybrid. To me, a hybrid event is, like, throwing two events. Do you have an organizing team that can actually handle two concurrent events? It's hard.And API Specifications Conference, we did two years in person. Pretty niche conference. It's like the API nerds of the API nerds. And so, we still had pretty engaged attendees because there weren't any other sources of this, but then when everyone was starting to do the same content, attendees started checking out. They got tired of sitting in front of their monitors and watching talks.You know, we're seeing things coming back in person. I think it's going to be very interesting for the Spring because the Fall for me, it was probably one of my busiest conference seasons in terms of us just also sponsoring things. And I'm unsure of the return on investment today. We will see over time how that return on investment comes out, but I think it's going to change the way we look at the Spring, it's going to change the way we look at next Fall, and I think other companies are having the same conversations, too. And so, it's going to be like, okay, what do we do instead if we don't focus on conferences? I don't know. For me, that's focusing on the actual advocacy part, the user feedback, talking to users, building a product that people find value in. But for other teams, their team might not be in the place to do that. They might be expected to still produce this content in different ways, in-person, written, online.Corey: So, one of the burning questions that I think is not asked or addressed particularly well in the space has been, how do you get users to trust you? And to be clear, I am not saying you personally. It's like, “Well, given your history of flagrant lying and misleading people and scam after scam after scam, that is honestly impressive—” No, no, no, none of that. It's how do you—the indefinite you—build user trust?Taylor: Yeah, I think this is something we've seen, lots of companies of all sizes really struggle with. You know, the obvious thing I think many times companies think of is like, oh, if I'm open and transparent and have great docs, users will trust me. You know, I think that's part of it. I think the other thing that many often forget is that you need to listen to them, you need to take their feedback that they give you when you ask questions—and there's a whole, like, asking questions; I'm learning myself, like, how to ask better questions—how do you then make that actionable internally?You know, you have to understand who makes product decisions. Who do I need to talk to about this feature versus this other feature, and there's all these internal dynamics that you're then wading into. So, you have to get good at that. And then when you finally actually get some kind of change, whether that be some small paper cut of a thing related to a feature, or a big feature that you release, you actually go back to the user and you tell them, “Hey, look, we did this.” And what blows my mind is I do this, I take notes on who told me what feedback, and when that issue gets closed out, I go back to them and they're just shocked that I replied. They are shocked that I actually followed up. And to me, it's like such a basic thing, just following up. Doesn't seem, like, that hard.But it actually is hard but also useful. And you know, I think we've seen this so many times. We see—this is one example that I think about a lot, and I think you're familiar with this one too, Corey, the Aurora Serverless Data API in V1, people loved that. Then they came out with V2. There was no data API.And if you search that people are upset everywhere. And AWS keeps on telling them, “Nope, it's not going to happen.” And it's like, it's such an easy win if they actually listened to the user base. But there's countless examples of this, you know? There's things that we do at PlanetScale that we could improve on, you know, that users are telling us.There's only so much time in the day, but I think part of an advocate's job to wade through this feedback and figure out where can we bring the biggest value and the most impact. And, you know, I think all companies could benefit just from listening more and doing something about it.Corey: I wish that were a message that would get in front of the right people to make them a little bit more receptive. It feels like that's a message that is bandied around—to be direct—in DevRel circles an awful lot, but it doesn't seem to gain traction outside of that.Taylor: This kind of goes back to what we were talking about earlier with what team you're on. Sometimes that makes a huge difference, especially in larger companies. If you were siloed away in a marketing org—nothing bad about marketing, to be clear, but internally, you're seen as marketing—engineers, developers, see you as marketing. When you come with product feedback, they're kind of, “That's not your box. Go back to your box. Go back to your silo.”And you know, I think the reality is, we can't look at advocacy like that. I have users tell me things that they would never tell salesperson, they would never tell someone on our leadership team, they might tell someone in support. They tell me things. They send me emails that are multiple paragraphs long, giving positive and negative feedback. Many times it's positive, but I'm just shocked they'll even write that much, you know, positive. Like, they actually took out the time to do it.And they trusted that it was worth their time. I've done something right there if they're willing to do that at that point. And I, you know, I make sure I respond to every single one of those emails. I had someone ask me like, “Oh, do you want us to forward you all of them?” And I'm like, “Yes. Every single one. No matter what it says, I'm going to reply to this email.”Because then if I lose that trust, it's everything for me as an advocate. It's how I can help them, you know, see the value in the product, and help them with adoption, and bring them along to eventually paying, potentially—dirty word, revenue—but otherwise, I wouldn't have a job. So, you know, I think it's really something that startups, they think they see DevRel advocacy as content farms and not enough of the part that actually helps them make money.Corey: I really want to thank you for being so generous with your time. If people want to learn more, where's the best place for them to find you?Taylor: So, for now, I'm on Twitter as @taylor_atx. But if anything happens with that, as we know right now, you can also find me at taylorbar.net is my website. I'll always try to keep links of where I am on there. Trying to write more. We'll see if I accomplish that over the holidays. But yeah, that's the two places you can find me.Corey: And we will, of course, include links to that in the [show notes 00:26:27]. Thank you so much for your time. I appreciate it.Taylor: Yeah, thanks, Corey, for letting me rant, ramble, kind of have all these thoughts about advocacy. I'm hoping we can have a good 2023 in the world of DevRel and advocacy and make progress on some of these things.Corey: I sure hope you're right.Taylor: [laugh]. I hope I'm right, too, for the happiness of my job [laugh].Corey: Taylor Barnett, Staff Developer Advocate at PlanetScale. I'm Cloud Economist Corey Quinn, and this is Screaming in the Cloud. If you've enjoyed this podcast, please leave a five-star review on your podcast platform of choice, whereas if you've hated this podcast, please leave a five-star review on your podcast platform of choice, along with an angry comment channeling a late Christmas spirit to tell us what the true meaning of DevRel was all along. Which will be wrong. Because it includes metrics.Corey: If your AWS bill keeps rising and your blood pressure is doing the same, then you need The Duckbill Group. We help companies fix their AWS bill by making it smaller and less horrifying. The Duckbill Group works for you, not AWS. We tailor recommendations to your business and we get to the point. Visit duckbillgroup.com to get started.Announcer: This has been a HumblePod production. Stay humble.

One of the most critical aspects of software projects is managing its data. Managing the operational concerns for your database can be complex and expensive, especially if you need to scale to large volumes of data, high traffic, or geographically distributed usage. Planetscale is a serverless option for your MySQL workloads that lets you focus on your applications without having to worry about managing the database or fight with differences between development and production. In this episode Nick van Wiggeren explains how the Planetscale platform is implemented, their strategies for balancing maintenance and improvements of the underlying Vitess project with their business goals, and how you can start using it today to free up the time you spend on database administration.

Daniel & Caleb talk about being snowed in, dreaming of databases, and love hating Twitter and email. It's a night record folks. Grab a turkey leg and enjoy... This episode is brought to you by PlanetScale

Sam Lambert is CEO of PlanetScale, the serverless MySQL database platform for developers. PlanetScale is powered by the open source database clustering system Vitess which was originally built at Google to scale YouTube. The company has raised over $100M from investors including KPCB, Insight, SignalFire, and a16z. In this episode, we discuss PlanetScale's positioning as a database platform rather than a database, the importance of authenticity and showing off capabilities with every launch, transparency around pricing, proving the ability to scale, looking at the quality of companies and people in the community as a measure of success, thinking about GTM very early, and much more!

In this supper club episode of Syntax, Wes and Scott talk with Nikolas Burke from Prisma about the role an ORM plays in a tech stack, how Prisma has changed over the years, ways to query data in Prisma, and how migrations work with Prisma. Hasura - Sponsor With Hasura, you can get a fully managed, production-ready GraphQL API as a service to help you build modern apps faster. You can get started for free in 30 seconds, or if you want to try out the Standard tier for zero cost, use the code “TryHasura” at this link: hasura.info. We've also got an amazing selection of GraphQL tutorials at hasura.io/learn. Storyblok - Sponsor Storyblok is a headless component-based CMS with a real-time visual editor. It offers the flexibility for developers to craft their perfect tech stack, but it also empowers content creators to make changes independently. The result is that every team has the freedom to quickly and easily create the ideal website with limitless extensibility. Other key features include robust Storyblok SDKs and APIs, powerful internationalization options, and an eCommerce-ready platform. FireHydrant - Sponsor Incidents are hard. Managing them shouldn't be. FireHydrant makes it easy for anyone in your organization to respond to incidents efficiently and consistently. Intuitive, guided workflows provide turn-by-turn navigation for incident response, while thoughtful prompts and powerful integrations capture all of your incident data to drive useful retros and actionable analytics. Did we mention that FireHydrant is free? Get started at Firehydrant.com/syntax. Show Notes 00:35 Welcome 01:30 Guest intro @NikolasBurk on Twitter 04:56 How has Prisma evolved? Prisma Keystone GraphQL 10:44 What was Prisma V1? 17:04 Is there any GraphQL specific functions in Prismic? 21:26 Sponsor: Hasura 22:26 What role does an ORM play in a tech stack? 29:54 What is Planetscale? Planetscale The T3 Stack 32:22 Where does TRPC fit? tRPC 33:46 Sponsor: Storyblok 35:28 What is an ORM? Prisma VS Code plugin 42:00 How do migrations work with Prisma? 45:58 Query your data with Prisma client 49:43 Have you looked into alternative JavaScript environments? 55:16 Sponsor: FireHydrant 57:05 Supper Club questions 58:50 SIIIIICK ××× PIIIICKS ××× ××× SIIIIICK ××× PIIIICKS ××× Lichess Shameless Plugs Prisma blog Tweet us your tasty treats Scott's Instagram LevelUpTutorials Instagram Wes' Instagram Wes' Twitter Wes' Facebook Scott's Twitter Make sure to include @SyntaxFM in your tweets

In this episode, James and Amy answer questions from the audience about Github Copilot, modern frameworks, Serverless vs Express.js, PlanetScale vs Supabase vs Firebase, and more!SponsorsZEALZEAL is a computer software agency that delivers “the world's most zealous” and custom solutions. The company plans and develops web and mobile applications that consistently help clients draw in customers, foster engagement, scale technologies, and ensure delivery.ZEAL believes that a business is “only as strong as” its team and cares about culture, values, a transparent process, leveling up, giving back, and providing excellent equipment. The company has staffers distributed throughout the United States, and as it continues to grow, ZEAL looks for collaborative, object-oriented, and organized individuals to apply for open roles.For more information visit codingzeal.comVercelVercel combines the best developer experience with an obsessive focus on end-user performance. Their platform enables frontend teams to do their best work. It is the best place to deploy any frontend app. Start by deploying with zero configuration to their global edge network. Scale dynamically to millions of pages without breaking a sweat.For more information, visit Vercel.comDatoCMSDatoCMS is a complete and performant headless CMS built to offer the best developer experience and user-friendliness in the market. It features a rich, CDN-powered GraphQL API (with realtime updates!), a super-flexible way to handle dynamic layouts and structured content, and best-in-class image/video support, with progressive/LQIP image loading out-of-the-box."For more information, visit datocms.comShow Notes00:00:00 - Intro00:02:16 - Github Copilot Controversy00:15:08 - Sponsor: DatoCMS00:16:02 - Thoughts on Next JS,Redwood, Remix, and More00:23:27 - Sponsor: ZEAL00:24:22 - Desk Cable Management 00:30:25 - Serverless vs Express.js00:34:50 - Prisma and PlanetScale00:37:17 - Sponsor:  Vercel00:38:24 - Script for YouTube Images00:39:42 - PlanetScale vs Firebase vs Supabase

Your early tech stack decisions won't ensure long term success, but they can certainly set you up for long term failure. Pragmatists rejoice! This week's episode of Dev Interrupted features Sam Lambert, CEO & President of PlanetScale, a tech leader known as the ‘Oracle of Pragmatism'. In a winding conversation that touches on Sam's time at GitHub, where he helped the then 40th most-trafficked website in the world run on just 2 servers, to his experience working at Facebook where he learned that you don't need to sacrifice quality in order to move fast, this episode has the insights you need to make straightforward, no BS decisions about your tech stack. Or as Sam says, learn how to avoid “the new hotness” in order to build a culture that reflects the often boring decisions that make or break a company. Show NotesRegister for Interact on October 25thLearn about the power of Continuous MergeCheck out PlanetScaleWant to try LinearB? Book a LinearB Demo and use the "Dev Interrupted Podcast" discount code.Join our Discord Community 

We talk to Sam Lambert, CEO of PlanetScale, the MySQL-compatible serverless database platform made for developers. Links https://planetscale.com https://twitter.com/isamlambert Follow us. Get free stickers. Follow us on Apple Podcasts, fill out this form, (https://podrocket.logrocket.com/get-podrocket-stickers) and we'll send you free PodRocket stickers! What does LogRocket do? LogRocket combines frontend monitoring, product analytics, and session replay to help software teams deliver the ideal product experience. Try LogRocket for free today. (https://logrocket.com/signup/?pdr) Special Guest: Sam Lambert.

In this supper club episode of Syntax, Wes and Scott talk edge functions and Deno with Eduardo Bouças of Netlify. Hasura - Sponsor With Hasura, you can get a fully managed, production-ready GraphQL API as a service to help you build modern apps faster. You can get started for free in 30 seconds, or if you want to try out the Standard tier for zero cost, use the code “TryHasura” at this link: hasura.info. We've also got an amazing selection of GraphQL tutorials at hasura.io/learn. Postlight Podcast - Sponsor Postlight is a strategy, design, and engineering firm that builds platforms for some of the biggest organizations in the world. The Postlight Podcast is hosted by senior leaders Rich Ziade, Paul Ford, Gina Trapani, and Chris LoSacco. If you're looking for answers to tough leadership questions, the Postlight Podcast has you covered. Listen to new episodes every Tuesday, wherever you get your podcasts. WP Mail SMTP - Sponsor Did you know that many WordPress sites are not properly configured to send emails? With WP Mail SMTP, you can easily optimize your site to send emails, avoid the spam folder, and make sure your emails land in the inbox every time. WP Mail SMTP comes with detailed email logs, email engagement tracking, visual email reports, weekly email summaries, integrations with popular email providers like SendLayer, Gmail, Outlook, and more! Try WP Mail SMTP Pro today and get 50% off or start with their free version by downloading it from the WordPress plugin directory. Show Notes 00:36 Welcome 02:31 Who is Eduardo? EduardoBoucas.com @eduardoboucas 04:29 What is a serverless function? 06:42 What is the edge and an edge function? Edge Functions Explained Deno 08:41 Sponsor: Hasura 09:18 The internet is global, and server locations matter 17:09 Chaining multiple edge functions 20:18 Sponsor: WP Mail SMTP 21:01 Why use Deno? 24:38 What are the limitations of using Deno? 27:44 Why not run NodeJS servers on the edge? 29:34 Do you see a future where people are writing packages that work anywhere? 31:32 Sponsor: Postlight Podcast 32:25 What about databases and serverless functions? Planetscale 37:46 What language does Netlify use to write apps in? Netlify Edge Handlers 43:39 Supper Club questions Warp S Town Podcast Shameless Plugs Scott: LevelUp Tutorials Wes: Wes Bos Tutorials Tweet us your tasty treats Scott's Instagram LevelUpTutorials Instagram Wes' Instagram Wes' Twitter Wes' Facebook Scott's Twitter Make sure to include @SyntaxFM in your tweets

Sam Lambert, CEO of PlanetScale, joins Doc Searls and Jonathan Bennett to talk about Vitess, his learnings as VP of Engineering at GitHub, sharding, why Rewind is a lifesaver for users needing to undo recovers during schema migrations, and much more. Hosts: Doc Searls and Jonathan Bennett Guest: Sam Lambert Download or subscribe to this show at https://twit.tv/shows/floss-weekly Think your open source project should be on FLOSS Weekly? Email floss@twit.tv. Thanks to Lullabot's Jeff Robbins, web designer and musician, for our theme music. Get episodes ad-free with Club TWiT at https://twit.tv/clubtwit Sponsors: NewRelic.com/FLOSS kolide.com/floss

This week we're joined by Deepthi Sigireddi, Vitess Maintainer and engineer at PlanetScale — of course we're talking about all things Vitess. We talk about its origin inside YouTube, how Vitess handles sharding, Deepthi's journey to Vitess maintainer, when you should begin using it, and how it fits into cloud native infra.

Running a database company requires expertise in both technical and managerial skills. There are deeply technical engineering questions around query paths, scalability, and distributed systems. And there are complex managerial questions around developer productivity and task allocation. Sam Lambert is the CEO of PlanetScale, which is building modern relational database infrastructure. Before PlanetScale he spent The post PlanetScale Management with Sam Lambert appeared first on Software Engineering Daily.