Podcasts about good parts

Things we are talking about in this episode: How all of Miami smells like BR540.Morning Swood.Elorea's new fragrance collection: Timeless Legacy.The polarizing (between us) Frederic Malle X Acne scent.Lube.Lube.And more Lube — with Dave Shanfield of GoodParts Find more info, episodes, and merch at Smellyalater.liveLeave us a voice message on the SYL Hotline at Speakpipe.com/smellyalater and we may respond on a future episode.Follow us on Instagram @smellyalater.mp3Leave a (nice) comment & (5-star) review wherever you stream, and if you feel so inclined, respond to our Spotify episode prompts please!

Welcome to #Millennial, the home of pretend adulting and real talk! The internet had some real talk for Watcher Entertainment in the wake of its announcement it was leaving YouTube and paywalling its previously free content. The response from their fans was swift and harsh, leading to Watcher rolling back its new model. Laura's been a fan of the Watcher team for years, and was disappointed by their approach to pivot to a 100% paid subscription model. The lack of consideration for their paid supporters on Patreon and the push to put past and future content behind a paywall showed a disconnect with where their audience is at currently. What content are we looking for from our favorite parasocial relationships? We hear it again and again - authenticity is waaaaay more important than production value.  Reddit inspired us to take a more sunny approach towards the millennial experience by asking ourselves, "what are the best things about being a millennial?" The internet just hit different back in our day - we all hid behind weird screen names and avatars. Are millennials the most adaptable generation when it comes to technology? We (especially Andrew) count our blessings that our cringiest youth moments weren't documented to be judged for all eternity. #findandrewssimsgf Tbh we were feral as kids, roaming the neighborhood and getting into mischief until the street lights came on (and sometimes after). We've got entertainment recs for y'all this week! 'Gen V' on Amazon Prime (Laura), 'Pen15' on Hulu (Pam), and 'Challengers' (Andrew). And in this week's installment of After Dark, available on Patreon and Apple Podcasts: Remember the really rude "Surprise Bitch!" segment we used to do back in the day? We're resurrecting it for After Dark. We're randomly dialing up a few Patrons to ask them random questions like what basic thing they suck at, how they handle having a bad day, and what the last thing was they disagreed with us on. "Andrew has bad taste in movies." -A loyal listener giving it to Andrew straight. Learn more about your ad choices. Visit megaphone.fm/adchoices

Today's guest is Daniel Vassallo, the creator of the Small Bets community, which counts more than 5 ,000 members and includes engineers, entrepreneurs, and creators of all kinds. Daniel is also a former software engineer at AWS, the author of The Good Parts of AWS and created a successful Twitter course. With Daniel, we will talk about his unconventional journey in tech, the Small Bets philosophy, and advice for engineers about careers, site projects, technology and skills. Here is what we talked about: (01:11) Introduction & background (05:21) Small Bets' genesis & philosophy (14:36) Understanding the market (19:36) Taking care of the downsides (24:43) Improving your lifestyle first (29:05) The dangers of labelling yourself (32:10) Allocating your time (37:13) Self-managing your own work (45:34) Transitioning to a self-employed lifestyle (52:21) The selection criteria for your ideas — You can also find this at:

A lot to share, and I still have more lol. Building my foundation, getting ready to launch "just the good parts", writing nasty stories, and preparing for blessings. Email List: (scroll to the very bottom) https://www.ohsodope.co/ Join the discord group: https://discord.gg/tmRHw3TcwH Shop my Greeting Cards and Stationery: www.ohsodope.co/greetingcards Follow on IG: www.instagram.com/ohsodope.co Read the blog: www.ohsodope.co/blog Journal Prompts: 1. Do you believe that "indecision" is worse than no decision? 2. What time of the day does you brain work best? Do you take advantage of this time? 3. Are there any areas in your life where you feel out of integrity?

“Porn performers aren't respected in our society and nothing underlines this fact better than the Stormy Daniels/Donald Trump scandal. When the world learned that President Trump had tried to buy porn performer Stormy Daniel's silence about their affair before the 2016 election, she was the one who was skewered in the court of public opinion. Trump, on the other hand, emerged unscathed. This is business as usual when it comes to the treatment of porn performers in our society. Porn actors aren't seen as worthy of respect. As model Amber Rose told Marlow Stern, Senior Entertainment Editor of The Daily Beast: “Porn stars are here for our convenience. Everyone uses them when they want to use them and then throws them away after. We don't respect them enough.” Stereotyped and stigmatized, porn performers are denied their humanity. It doesn't make a difference that the stereotypes aren't true. Feminist porn director, Erika Lust, told Dazed: “It's often assumed that to be an adult performer you're troubled, on drugs, have money problems and no self-esteem. Even though those cases certainly exist, it's not a fair judgment to pass on to everyone who chooses to do adult films, and it's not my experience at all.” When society denies that porn performers are three-dimensional beings with the same needs and desires as other people, this creates a world in which it's okay to deny them their rights.” -https://aninjusticemag.com/its-time-to-stop-the-unfair-violation-of-porn-performers-rights-3f9c9b153e87. --- Support this podcast: https://podcasters.spotify.com/pod/show/antonio-myers4/support

As a 5-member multinational girl group that debuted on May 2, 2022, it was on Billboard 200 in 6 months since its debut.It entered the charts for the shortest time in K-pop girl group history.In addition, it is the first female idol group to have three music videos with over 100 million views among its debut groups in 2022.Through collaboration with famous foreign musicians, they showed high-quality music.It also captured the hearts of global fans.It has lots of nicknames like Fim-twins, Geun-ssera-fim, LeSsera-gym, Jjangsse-ra-fim(핌둥이들, 근세라핌, 르세라짐, 짱세라핌) etc.It's recognized as one of the most popular male and female idols of all time.It's a team that's recognized as showing the strongest performance.It came back with a new album that was released in 4 months.K-pop Top Player is back with its first album of the year [EASY]!The center of the 4th generation K-pop girl group genealogy!Let's meet Le Sserafim's music~*Today's playlist1. EASY2. ANTIFRAGILE3. UNFORGIVEN (feat. Nile Rodgers)4. Perfect Night5. Good Parts (when the quality is bad but I am) - Nive's Pick6. 피어나 (Between you, me and the lamppost) - prettylittleiris's Pick

At the age of 17, Nadia Vaeh's mom completed suicide. Nadia is now 30. We discuss: Coping strategies for anxietyWhy art is not enoughHow to zoom in on the good parts of ourselfWhy it's not easy to consistently love yourselfSponsor:Is there something interfering with your happiness or is preventing you from achieving your goals? https://betterhelp.com/leo and enjoy 10% off your first month and start talking to mental health professional today!! 1-on-1 Coaching: If you want go from feeling hopeless to hopeful, lonely to connected and like a burden to a blessing, then go to 1-on-1 coaching, go to www.thrivewithleo.com. Let's get to tomorrow, together. National Suicide Prevention Lifeline988Teen Line (Los Angeles)800-852-8336The Trevor Project (LGBTQ Youth Hotline)866-488-7386National Domestic Violence Hotline800-799-SAFE [800-799-7233]Crisis Text LineText "Connect" to 741741 in the USALifeline Chathttps://suicidepreventionlifeline.org/chat/International Suicide Hotlines: http://www.suicide.org/international-suicide-hotlines.htmlhttps://www.nowmattersnow.org/skillshttps://sobermeditations.libsyn.com/ www.suicidesafetyplan.com https://scaa.club/

Debbie just wants it all out there I guess. This hour of Wisconsin's Morning News includes a round up of political headlines including George Santos' voted on expulsion, the debate debacle, and the reworking of Scott Walker's Act 10. Later the hour a Pancake Breakfast Special with a Fact & Fiction edition of the segment. Enjoy!

David was the chief software architect and director of engineering at Stitch Fix. He's also the author of a number of books including Sustainable Web Development with Ruby on Rails and most recently Ruby on Rails Background Jobs with Sidekiq. He talks about how he made decisions while working with a medium sized team (~200 developers) at Stitch Fix. The audio quality for the first 19 minutes is not great but the correct microphones turn on right after that. Recorded at RubyConf 2023 in San Diego. A few topics covered: Ruby's origins at Stitch Fix Thoughts on Go Choosing technology and cloud services Moving off heroku Building a platform team Where Ruby and Rails fit in today The role of books and how different people learn Large Language Model's effects on technical content Related Links David's Blog Mastodon Transcript You can help correct transcripts on GitHub. Intro [00:00:00] Jeremy: Today. I want to share another conversation from RubyConf San Diego. This time it's with David Copeland. He was a chief software architect and director of engineering at stitch fix. And at the start of the conversation, you're going to hear about why he decided to write the book, sustainable web development with Ruby on rails. Unfortunately, you're also going to notice the sound quality isn't too good. We had some technical difficulties. But once you hit the 20 minute mark of the recording, the mics are going to kick in. It's going to sound way better. So I hope you stick with it. Enjoy. Ruby at Stitch Fix [00:00:35] David: Stitch Fix was a Rails shop. I had done a lot of Rails and learned a lot of things that worked and didn't work, at least in that situation. And so I started writing them down and I was like, I should probably make this more than just a document that I keep, you know, privately on my computer. Uh, so that's, you know, kind of, kind of where the genesis of that came from and just tried to, write everything down that I thought what worked, what didn't work. Uh, if you're in a situation like me. Working on a product, with a medium sized, uh, team, then I think the lessons in there will be useful, at least some of them. Um, and I've been trying to keep it up over, over the years. I think the first version came out a couple years ago, so I've been trying to make sure it's always up to date with the latest stuff and, and Rails and based on my experience and all that. [00:01:20] Jeremy: So it's interesting that you mention, medium sized team because, during the, the keynote, just a few moments ago, Matz the creator of Ruby was talking about how like, Oh, Rails is really suitable for this, this one person team, right? Small, small team. And, uh, he was like, you're not Google. So like, don't worry about, right. Can you scale to that level? Yeah. Um, and, and I wonder like when you talk about medium size or medium scale, like what are, what are we talking? [00:01:49] David: I think probably under 200 developers, I would say. because when I left Stitch Fix, it was closing in on that number of developers. And so it becomes, you know, hard to... You can kind of know who everybody is, or at least the names sound familiar of everybody. But beyond that, it's just, it's just really hard. But a lot of it was like, I don't have experience at like a thousand developer company. I have no idea what that's like, but I definitely know that Rails can work for like... 200 ish people how you can make it work basically. yeah. [00:02:21] Jeremy: The decision to use Rails, I'm assuming that was made before you joined? [00:02:26] David: Yeah, the, um, the CTO of Stitch Fix, he had come in to clean up a mess made by contractors, as often happens. They had used Django, which is like the Python version of Rails. And he, the CTO, he was more familiar with Rails. So the first two developers he hired, also familiar with Rails. There wasn't a lot to maintain with the Django app, so they were like, let's just start fresh, fresh with Rails. yeah, but it's funny because a lot of the code in that Rails app was, like, transliterated from Python. So you could, it would, it looked like the strangest Ruby code in the world because it was basically, there was no test. So they were like, let's just write the Ruby version of this Python just so we know it works. but obviously that didn't, didn't last forever, so. [00:03:07] Jeremy: So, so what's an example of a, of a tell? Where you're looking at the code and you're like, oh, this is clearly, it came from Python. [00:03:15] David: You'd see like, very, very explicit, right? Like Python, there's a lot of like single line things. very like, this sounds like a dig, but it's very simple looking code. Like, like I don't know Python, but I was able to change this Django app. And I had to, I could look at it and you can figure out immediately how it works. Cause there's. Not much to it. There's nothing fancy. So, like, this, this Ruby code, there was nothing fancy. You'd be like, well, maybe they should have memoized that, or maybe they should have taken that into another class, or you could have done this with a hash or something like that. So there was, like, none of that. It was just, like, really basic, plain code like you would see in any beginning programming language kind of thing. Which is at least nice. You can understand it. but you probably wouldn't have written it that way at first in Ruby. Thoughts on Go [00:04:05] Jeremy: Yeah, that's, that's interesting because, uh, people sometimes talk about the Go programming language and how it looks, I don't know if simple is the right word, but it's something where you look at the code and even if you don't necessarily understand Go, it's relatively straightforward. Yeah. I wonder what your thoughts are on that being a strength versus that being, like, [00:04:25] David: Yeah, so at Stitch Fix at one point we had a pro, we were moving off of Heroku and we were going to, basically build a deployment platform using ECS on AWS. And so the deployment platform was a Rails app and we built a command line tool using Ruby. And it was fine, but it was a very complicated command line tool and it was very slow. And so one of the developers was like, I'm going to rewrite it in Go. I was like, ugh, you know, because I just was not a big fan. So he rewrote it in Go. It was a bazillion times faster. And then I was like, okay, I'm going to add, I'll add a feature to it. It was extremely easy. Like, it's just like what you said. I looked at it, like, I don't know anything about Go. I know what is happening here. I can copy and paste this and change things and make it work for what I want to do. And it did work. And it was, it was pretty easy. so there's that, I mean, aesthetically it's pretty ugly and it's, I, I. I can't really defend that as a real reason to not use it, but it is kind of gross. I did do Go, I did a small project in Go after Stitch Fix, and there's this vibe in Go about like, don't create abstractions. I don't know where I got that from, but every Go I look at, I'm like we should make an abstraction for this, but it's just not the vibe. They just don't like doing that. They like it all written out. And I see the value because you can look at the code and know what it does and you don't have to chase abstractions anywhere. But. I felt like I was copying and pasting a lot of, a lot of things. Um, so I don't know. I mean, the, the team at Stitch Fix that did this like command line app in go, they're the platform team. And so their job isn't to write like web apps all day, every day. There's kind of in and out of all kinds of things. They have to try to figure out something that they don't understand quickly to debug a problem. And so I can see the value of something like go if that's your job, right? You want to go in and see what the issue is. Figure it out and be done and you're not going to necessarily develop deep expertise and whatever that thing is that you're kind of jumping into. Day to day though, I don't know. I think it would make me kind of sad. (laughs) [00:06:18] Jeremy: So, so when you say it would make you kind of sad, I mean, what, what about it? Is it, I mean, you mentioned that there's a lot of copy and pasting, so maybe there's code duplication, but are there specific things where you're like, oh, I just don't? [00:06:31] David: Yeah, so I had done a lot of Java in my past life and it felt very much like that. Where like, like the Go library for making an HTTP call for like, I want to call some web service. It's got every feature you could ever want. Everything is tweakable. You can really, you can see why it's designed that way. To dial in some performance issue or solve some really esoteric thing. It's there. But the problem is if you just want to get an JSON, it's just like huge production. And I felt like that's all I really want to do and it's just not making it very easy. And it just felt very, very cumbersome. I think that having to declare types also is a little bit of a weird mindset because, I mean, I like to make types in Ruby, I like to make classes, but I also like to just use hashes and stuff to figure it out. And then maybe I'll make a class if I figure it out, but Go, you can't. You have to have a class, you have to have a type, you have to think all that ahead of time, and it just, I'm not used to working that way, so it felt, I mean, I guess I could get used to it, but I just didn't warm up to that sort of style of working, so it just felt like I was just kind of fighting with the vibe of the language, kind of. Yeah, [00:07:40] Jeremy: so it's more of the vibe or the feel where you're writing it and you're like this seems a little too... Explicit. I feel like I have to be too verbose. It just doesn't feel natural for me to write this. [00:07:53] David: Right, it's not optimized for what in my mind is the obvious case. And maybe that's not the obvious case for the people that write Go programs. But for me, like, I just want to like get this endpoint and get the JSON back as a map. Not any easier than any other case, right? Whereas like in Ruby, right? And you can, I think if you include net HTTP, you can just type get. And it will just return whatever that is. Like, that's amazing. It's optimized for what I think is a very common use case. So it makes me feel really productive. It makes me feel pretty good. And if that doesn't work out long term, I can always use something more complicated. But I'm not required to dig into the NetHttp library just to do what in my mind is something very simple. [00:08:37] Jeremy: Yeah, I think that's something I've noticed myself in working with Ruby. I mean, you have the standard library that's very... Comprehensive and the API surface is such that, like you said there, when you're trying to do common tasks, a lot of times they have a call you make and it kind of does the thing you expected or hoped for. [00:08:56] David: Yeah, yeah. It's kind of, I mean, it's that whole optimized for programmer happiness thing. Like it does. That is the vibe of Ruby and it seems like that is still the way things are. And, you know, I, I suppose if I had a different mindset, I mean, because I work with developers who did not like using Ruby or Rails. They loved using Go or Java. And I, I guess there's probably some psychological analysis we could do about their background and history and mindset that makes that make sense. But, to me, I don't know. It's, it's nice when it's pleasant. And Ruby seems pleasant. (laughs) Choosing Technology [00:09:27] Jeremy: as a... Software Architect, or as a CTO, when, when you're choosing technology, what are some of the things you look at in terms of, you know? [00:09:38] David: Yeah, I mean, I think, like, it's a weird criteria, but I think what is something that the team is capable of executing with? Because, like, most, right, most programming languages all kind of do the same thing. Like, you can kind of get most stuff done in most common popular programming languages. So, it's probably not... It's not true that if you pick the wrong language, you can't build the app. Like, that's probably not really the case. At least for like a web app or something. so it's more like, what is the team that's here to do it? What are they comfortable and capable of doing? I worked on a project with... It was a mix of like junior engineers who knew JavaScript, and then some senior engineers from Google. And for whatever reason someone had chosen a Rails app and none of them were comfortable or really yet competent with doing Ruby on Rails and they just all hated it and like it didn't work very well. Um, and so even though, yes, Rails is a good choice for doing stuff for that team at that moment. Not a good choice. Right. So I think you have to go in and like, what, what are we going to be able to execute on so that when the business wants us to do something, we just do it. And we don't complain and we don't say, Oh, well we can't because this technology that we chose, blah, blah, blah. Like you don't ever want to say that if possible. So I think that's. That's kind of the, the top thing. I think second would be how widely supported is it? Like you don't want to be the cutting edge user that's finding all the bugs in something really. Like you want to use something that's stable. Postgres, MySQL, like those work, those are fine. The bugs have been sorted out for most common use cases. Some super fancy edge database, I don't know if I'd want to be doing, doing that you know? Choosing cloud services [00:11:15] Jeremy: How do you feel about the cloud specific services and databases? Like are you comfortable saying like, oh, I'm going to use... Google Cloud, BigQuery. Yeah. [00:11:27] David: That sort of thing. I think it would kind of fall under the same criteria that I was just, just saying like, so with AWS it's interesting 'cause when we moved from Heroku to AWS by EC2 RDS, their database thing, uh, S3, those have been around for years, probably those are gonna work, but they always introduce new things. Like we, we use RabbitMQ and AWS came out with. Some, I forget what it was, it was a queuing service similar to Rabbit. We were like, Oh, maybe we should switch to that. But it was clear that they weren't really ready to support it. So. Yeah, so we didn't, we didn't switch to that. So I, you gotta try to read the tea leaves of the provider to see are they committed to, to supporting this thing or is this there to get some enterprise client to move into the cloud. And then the idea is to move off of that transitional thing into what they do support. And it's hard to get a clear answer from them too. So it takes a little bit of research to figure out, Are they going to support this or not? Because that's what you don't want. To move everything into some very proprietary cloud system and have them sunset it and say, Oh yeah, now you've got to switch again. Uh, that kind of sucks. So, it's a little trickier. [00:12:41] Jeremy: And what kind of questions or research do you do? Is it purely a function of this thing has existed for X number of years so I feel okay? [00:12:52] David: I mean, it's kind of similar to looking at like some gem you're going to add to your project, right? So you'll, you'll look at how often does it change? Is it being updated? Uh, what is the documentation? Does it look like someone really cared about the documentation? Does the documentation look updated? Are there issues with it that are being addressed or, or not? Um, so those are good signals. I think, talking to other practitioners too can be good. Like if you've got someone who's experienced. You can say, hey, do you know anybody back channeling through, like, everybody knows somebody that works at AWS, you can probably try to get something there. at Stitch Fix, we had an enterprise support contract, and so your account manager will sometimes give you good information if you ask. Again, it's a, they're not going to come out and say, don't use this product that we have, but they might communicate that in a subtle way. So you have to triangulate from all these sources to try to. to try to figure out what, what you want to do. [00:13:50] Jeremy: Yeah, it kind of makes me wish that there was a, a site like, maybe not quite like, can I use, right? Can I use, you can see like, oh, can I use this in my browser? Is there, uh, like an AWS or a Google Cloud? Can I trust this? Can I trust this? Yeah. Is this, is this solid or not? [00:14:04] David: Right, totally. It's like, there's that, that site where you, it has all the Apple products and it says whether or not you should buy it because one may or may not be coming out or they may be getting rid of it. Like, yeah, that would... For cloud services, that would be, that would be nice. [00:14:16] Jeremy: Yeah, yeah. That's like the Mac Buyer's Guide. And then we, we need the, uh, the technology. Yeah. Maybe not buyers. Cloud Provider Buyer's Guide, yeah. I guess we are buyers. [00:14:25] David: Yeah, yeah, totally, totally. [00:14:27] Jeremy: it's interesting that you, you mentioned how you want to see that, okay, this thing is mature. I think it's going to stick around because, I, interviewed, someone who worked on, I believe it was the CloudWatch team. Okay. Daniel Vassalo, yeah. so he left AWS, uh, after I think about 10 years, and then he wrote a book called, uh, The Good Parts of AWS. Oh! And, if you read his book, most of the services he says to use are the ones that are, like, old. Yeah. He's, he's basically saying, like, S3, you know you're good. Yeah. Right? but then all these, if you look at the AWS webpage, they have who knows, I don't know how many hundreds of services. Yeah. He's, he's kind of like I worked there and I would not use, you know, all these new services. 'cause I myself, I don't trust [00:15:14] David: it yet. Right. And so, and they're working there? Yeah, they're working there. Yeah. No. One of the VPs at Stitch Fix had worked on Google Cloud and so when we were doing this transition from Heroku, he was like, we are not using Google Cloud. I was like, really? He's like AWS is far ahead of the game. Do not use Google Cloud. I was like, all right, I don't need any more info. You work there. You said don't. I'm gonna believe you. So [00:15:36] Jeremy: what, what was his did he have like a core point? [00:15:39] David: Um, so he never really had anything bad to say about Google per se. Like I think he enjoyed his time there and I think he thought highly of who he worked with and what he worked on and that sort of thing. But his, where he was coming from was like AWS was so far ahead. of Google on anything that we would use, he was like, there's, there's really no advantage to, to doing it. AWS is a known quantity, right? it's probably still the case. It's like, you know, you've heard the nobody ever got fired for using IBM or using Microsoft or whatever the thing is. Like, I think that's, that was kind of the vibe. And he was like, moving all of our infrastructure right before we're going to go public. This is a serious business. We should just use something that we know will work. And he was like, I know this will work. I'm not confident about. Google, uh, for our use case. So we shouldn't, we shouldn't risk it. So I was like, okay, I trust you because I didn't know anything about any of that stuff at the time. I knew Heroku and that was it. So, yeah. [00:16:34] Jeremy: I don't know if it's good or bad, but like you said, AWS seems to be the default choice. Yeah. And I mean, there's people who use Azure. I assume it's mostly primarily Microsoft. Yeah. And then there's Google Cloud. It's not really clear why you would pick it, unless there was a specific service or something that only they had. [00:16:55] David: Yeah, yeah. Or you're invested in Google, you know, you want to keep everything there. I mean, I don't know. I haven't really been at that level to make that kind of decision, and I would probably choose AWS for the reasons discussed, but, yeah. Moving off Heroku [00:17:10] Jeremy: And then, so at Stitch Fix, you said you moved off of Heroku [00:17:16] David: yeah. Yeah, so we were heavy into Heroku. I think that we were told that at one point we had the biggest Heroku Postgres database on their platform. Not a good place to be, right? You never want to be the biggest customer person, usually. but the problem we were facing was essentially we were going to go public. And to do that, you're under all the scrutiny. about many things, including the IT systems and the security around there. So, like, by default, a Postgres, a Heroku Postgres database is, like, on the internet. It's only secured by the password. all their services are on the internet. So, not, not ideal. they were developing their private cloud service at that time. And so that would have given us, in theory, on paper, it would have solved all of our problems. And we liked Heroku and we liked the developer experience. It was great. but... Heroku private spaces, it was still early. There's a lot of limitations that when they explained why those limitations, they were reasonable. And if we had. started from scratch on Heroku Private Spaces. It probably would have worked great, but we hadn't. So we just couldn't make it work. So we were like, okay, we're going to have to move to AWS so that everything can be basically off the internet. Like our public website needs to be on the internet and that's kind of it. So we need to, so that's basically was the, was the impetus for that. but it's too bad because I love Heroku. It was great. I mean, they were, they were a great partner. They were great. I think if Stitch Fix had started life a year later, Private Spaces. Now it's, it's, it's way different than it was then. Cause it's been, it's a mature product now, so we could have easily done that, but you know, the timing didn't work out, unfortunately. [00:18:50] Jeremy: And that was a compliance thing to, [00:18:53] David: Yeah. And compliance is weird cause they don't tell you what to do, but they give you some parameters that you need to meet. And so one of them is like how you control access. So, so going public, the compliance is around the financial data and. Ensuring that the financial data is accurate. So a lot of the systems at Stichfix were storing the financial data. We, you know, the warehouse management system was custom made. Uh, all the credit card processing was all done, like it was all in some databases that we had running in Heroku. And so those needed to be subject to stricter security than we could achieve with just a single password that we just had to remember to rotate when someone like left the team. So that was, you know, the kind of, the kind of impetus for, for all of that. [00:19:35] Jeremy: when you were using Heroku, Salesforce would have already owned it then. Did you, did you get any sense that you weren't really sure about the future of the platform while you're on it or, [00:19:45] David: At that time, no, it seemed like they were still innovating. So like, Heroku has a Redis product now. They didn't at the time we wish that they did. They told us they're working on it, but it wasn't ready. We didn't like using the third parties. Kafka was not a thing. We very much were interested in that. We would have totally used it if it was there. So they were still. Like doing bigger innovations then, then it seems like they are now. I don't know. It's weird. Like they're still there. They still make money, I assume for Salesforce. So it doesn't feel like they're going away, but they're not innovating at the pace that they were kind of back in the day. [00:20:20] Jeremy: it used to feel like when somebody's asking, I want to host a Rails app. Then you would say like, well, use Heroku because it's basically the easiest to get started. It's a known quantity and it's, it's expensive, but, it seemed for, for most people, it was worth it. and then now if I talk to people, it's like. Not what people suggest anymore. [00:20:40] David: Yeah, because there's, there's actual competitors. It's crazy to me that there was no competitors for years, and now there's like, Render and Fly. io seem to be the two popular alternatives. Um, I doubt they're any cheaper, honestly, but... You get a sense, right, that they're still innovating, still building those platforms, and they can build with, you know, all of the knowledge of what has come before them, and do things differently that might, that might help. So, I still use Heroku for personal things just because I know it, and I, you know, sometimes you don't feel like learning a new thing when you just want to get something done, but, yeah, I, I don't know if we were starting again, I don't know, maybe I'd look into those things. They, they seem like they're getting pretty mature and. Heroku's resting on its laurels, still. [00:21:26] Jeremy: I guess I never quite the mindset, right? Where you You have a platform that's doing really well and people really like it and you acquire it and then it just It seems like you would want to keep it rolling, right? (laughs) [00:21:38] David: Yeah, it's, it is wild, I mean, I guess... Why did you, what was Salesforce thinking they were going to get? Uh, who knows maybe the person at Salesforce that really wanted to purchase it isn't there. And so no one at Salesforce cares about it. I mean, there's all these weird company politics that like, who knows what's going on and you could speculate. all day. What's interesting is like, there's definitely some people in the Ruby community who work there and still are working there. And that's like a little bit of a canary for me. I'm like, all right, well, if that person's still working there, that person seems like they're on the level and, and, and, and seems pretty good. They're still working there. It, it's gotta be still a cool place to be or still doing something, something good. But, yeah, I don't know. I would, I would love to know what was going on in all the Salesforce meetings about acquiring that, how to manage it. What are their plans for it? I would love to know that stuff. [00:22:29] Jeremy: maybe you had some experience with this at Stitch Fix But I've heard with Heroku some of their support staff at least in the past they would, to some extent, actually help you troubleshoot, like, what's going on with your app. Like, if your app is, like, using a whole bunch of memory, and you're out of memory, um, they would actually kind of look into that, for you, which is interesting, because it's like, that's almost like a services thing than it is just a platform. [00:22:50] David: Yeah. I mean, they, their support, you would get, you would get escalated to like an engineer sometimes, like who worked on that stuff and they would help figure out what the problem was. Like you got the sense that everybody there really wanted the platform to be good and that they were all sort of motivated to make sure that everybody. You know, did well and used the platform. And they also were good at, like a thing that trips everybody up about Heroku is that your app restarts every day. And if you don't know anything about anything, you might think that is stupid. Why, why would I want that? That's annoying. And I definitely went through that and I complained to them a lot. And I'm like, if you only could not restart. And they very patiently and politely explained to me why that it needed to do that, they weren't going to remove that, and how to think about my app given that reality, right? Which is great because like, what company does that, right? From the engineers that are working on it, like No, nobody does that. So, yeah, no, I haven't escalated anything to support at Heroku in quite some time, so I don't know if it's still like that. I hope it is, but I'm not really, not really sure. Building a platform team [00:23:55] Jeremy: Yeah, that, uh, that reminds me a little bit of, I think it's Rackspace? There's, there's, like, another hosting provider that was pretty popular before, and they... Used to be famous for that type of support, where like your, your app's having issues and somebody's actually, uh, SSHing into your box and trying to figure out like, okay, what's going on? which if, if that's happening, then I, I can totally see where the, the price is justified. But if the support is kind of like dropping off to where it's just, they don't do that kind of thing, then yeah, I can see why it's not so much of a, yeah, [00:24:27] David: We used to think of Heroku as like they were the platform team before we had our own platform team and they, they acted like it, which was great. [00:24:35] Jeremy: Yeah, I don't have, um, experience with, render, but I, I, I did, talk to someone from there, and it does seem like they're, they're trying to fill that role, um, so, yeah, hopefully, they and, and other companies, I guess like Vercel and things like that, um, they're, they're all trying to fill that space, [00:24:55] David: Yeah, cause, cause building our own internal platform, I mean it was the right thing to do, but it's, it's a, you can't just, you have to have a team on it, it's complicated, getting all the stuff in AWS to work the way you want it to work, to have it be kind of like Heroku, like it's not trivial. if I'm a one person company, I don't want to be messing around with that particularly. I want to just have it, you know, push it up and have it go and I'm willing to pay for that. So it seems logical that there would be competitors in that space. I'm glad there are. Hopefully that'll light a fire under, under everybody. [00:25:26] Jeremy: so in your case, it sounds like you moved to having your own platform team and stuff like that, uh, partly because of the compliance thing where you're like, we need our, we need to be isolated from the internet. We're going to go to AWS. If you didn't have that requirement, do you still think like that would have been the time to, to have your own platform team and manage that all yourself? [00:25:46] David: I don't know. We, we were thinking an issue that we were running into when we got bigger, um, was that, I mean, Heroku, it, It's obviously not as flexible as AWS, but it is still very flexible. And so we had a lot of internal documentation about this is how you use Heroku to do X, Y, and Z. This is how you set up a Stitch Fix app for Heroku. Like there was just the way that we wanted it to be used to sort of. Just make it all manageable. And so we were considering having a team spun up to sort of add some tooling around that to sort of make that a little bit easier for everybody. So I think there may have been something around there. I don't know if it would have been called a platform team. Maybe we call, we thought about calling it like developer happiness or because you got developer experience or something. We, we probably would have had something there, but. I do wonder how easy it would have been to fund that team with developers if we hadn't had these sort of business constraints around there. yeah, um, I don't know. You get to a certain size, you need some kind of manageability and consistency no matter what you're using underneath. So you've got to have, somebody has to own it to make sure that it's, that it's happening. [00:26:50] Jeremy: So even at your, your architect level, you still think it would have been a challenge to, to. Come to the executive team and go like, I need funding to build this team. [00:27:00] David: You know, certainly it's a challenge because everybody, you know, right? Nobody wants to put developers in anything, right? There are, there are a commodity and I mean, that is kind of the job of like, you know, the staff engineer or the architect at a company is you don't have, you don't have the power to put anybody on anything you, you have the power to Schedule a meeting with a VP or the CTO and they will listen to you. And that's basically, you've got to use that power to convince them of what you want done. And they're all reasonable people, but they're balancing 20 other priorities. So it would, I would have had to, it would have been a harder case to make that, Hey, I want to take three engineers. And have them write tooling to make Heroku easier to use. What? Heroku is not easy to use. Why aren't, you know, so you really, I would, it would be a little bit more of a stretch to walk them through it. I think a case could be made, but, definitely would take some more, more convincing than, than what was needed in our case. [00:27:53] Jeremy: Yeah. And I guess if you're able to contrast that with, you were saying, Oh, I need three people to help me make Heroku easier. Your actual platform team on AWS, I imagine was much larger, right? [00:28:03] David: Initially it was, there was, it was three people did the initial move over. And so by the time we went public, we'd been on this new system for, I don't know, six to nine months. I can't remember exactly. And so at that time the platform team was four or five people, and I, I mean, so percentage wise, right, the engineering team was maybe almost 200, 150, 200. So percentage wise, maybe a little small, I don't know. but it kind of gets back to the power of like the rails and the one person framework. Like everything we did was very much the same And so the Rails app that managed the deployment was very simple. The, the command line app, even the Go one with all of its verbosity was very, very simple. so it was pretty easy for that small team to manage. but, Yeah, so it was sort of like for redundancy, we probably needed more than three or four people because you know, somebody goes out sick or takes a vacation. That's a significant part of the team. But in terms of like just managing the complexity and building it and maintaining it, like it worked pretty well with, you know, four or five people. Where Rails fits in vs other technology [00:29:09] Jeremy: So during the Keynote today, they were talking about how companies like GitHub and Shopify and so on, they're, they're using Rails and they're, they're successful and they're fairly large. but I think the thing that was sort of unsaid was the fact that. These companies, while they use Rails, they use a lot of other, technology as well. And, and, and kind of increasing amounts as well. So, I wonder from your perspective, either from your experience at StitchFix or maybe going forward, what is the role that, that Ruby and Rails plays? Like, where does it make sense for that to be used versus like, Okay, we need to go and build something in Java or, you know, or Go, that sort of thing? [00:29:51] David: right. I mean, I think for like your standard database backed web app, it's obviously great. especially if your sort of mindset bought into server side rendering, it's going to be great at that. so like internal tools, like the customer service dashboard or... You know, something for like somebody who works at a company to use. Like, it's really great because you can go super fast. You're not going to be under a lot of performance constraints. So you kind of don't even have to think about it. Don't even have to solve it. You can, but you don't have to, where it wouldn't work, I guess, you know, if you have really strict performance. Requirements, you know, like a, a Go version of some API server is going to use like percentages of what, of what Rails would use. If that's meaningful, if what you're spending on memory or compute is, is meaningful, then, then yeah. That, that becomes worthy of consideration. I guess if you're, you know, if you're making a mobile app, you probably need to make a mobile app and use those platforms. I mean, I guess you can wrap a Rails app sort of, but you're still making, you still need to make a mobile app, that does something. yeah. And then, you know, interestingly, the data science part of Stitch Fix was not part of the engineering team. They were kind of a separate org. I think Ruby and Rails was probably the only thing they didn't use over there. Like all the ML stuff, everything is either Java or Scala or Python. They use all that stuff. And so, yeah, if you want to do AI and ML with Ruby, you, it's, it's hard cause there's just not a lot there. You really probably should use Python. It'll make your life easier. so yeah, those would be some of the considerations, I guess. [00:31:31] Jeremy: Yeah, so I guess in the case of, ML, Python, certainly, just because of the, the ecosystem, for maybe making a command line application, maybe Go, um, Go or Rust, perhaps, [00:31:44] David: Right. Cause you just get a single binary. Like the problem, I mean, I wrote this book on Ruby command line apps and the biggest problem is like, how do I get the Ruby VM to be anywhere so that it can then run my like awesome scripts? Like that's kind of a huge pain. (laughs) So [00:31:59] Jeremy: and then you said, like, if it's Very performance sensitive, which I am kind of curious in, in your experience with the companies you've worked at, when you're taking on a project like that, do you know up front where you're like, Oh, the CPU and memory usage is going to be a problem, or is it's like you build it and you're like, Oh, this isn't working. So now I know. [00:32:18] David: yeah, I mean, I, I don't have a ton of great experience there at Stitch Fix. The biggest expense the company had was the inventory. So like the, the cost of AWS was just de minimis compared to all that. So nobody ever came and said, Hey, you've got to like really save costs on, on that stuff. Cause it just didn't really matter. at the, the mental health startup I was at, it was too early. But again, the labor costs were just far, far exceeded the amount of money I was spending on, on, um, you know, compute and infrastructure and stuff like that. So, Not knowing anything, I would probably just sort of wait and see if it's a problem. But I suppose you always take into account, like, what am I actually building? And like, what does this business have to scale to, to make it worthwhile? And therefore you can kind of do a little bit of planning ahead there. But, I dunno, I think it would kind of have to depend. [00:33:07] Jeremy: There's a sort of, I guess you could call it a meme, where people say like, Oh, it's, it's not, it's not Rails that's slow, it's the, the database that's slow. And, uh, I wonder, is that, is that accurate in your experience, or, [00:33:20] David: I mean, most of the stuff that we had that was slow was the database, because like, it's really easy to write a crappy query in Rails if you're not, if you're not careful, and then it's really easy to design a database that doesn't have any indexes if you're not careful. Like, you, you kind of need to know that, But of course, those are easy to fix too, because you just add the index, especially if it's before the database gets too big where we're adding indexes is problematic. But, I think those are just easy performance mistakes to make. Uh, especially with Rails because you're not, I mean, a lot of the Rails developers at Citrix did not know SQL at all. I mean, they had to learn it eventually, but they didn't know it at all. So they're not even knowing that what they're writing could possibly be problematic. It's just, you're writing it the Rails way and it just kind of works. And at a small scale, it does. And it doesn't matter until, until one day it does. [00:34:06] Jeremy: And then in, in the context of, let's say, using ActiveRecord and instantiating the objects, or, uh, the time it takes to render templates, that kinds of things, to, at least in your experience, that wasn't such of an issue. [00:34:20] David: No, and it was always, I mean, whenever we looked at why something was slow, it was always the database and like, you know, you're iterating over some active records and then, and then, you know, you're going into there and you're just following this object graph. I've got a lot of the, a lot of the software at Stitch Fix was like internal stuff and it was visualizing complicated data out of the database. And so if you didn't think about it, you would just start dereferencing and following those relationships and you have this just massive view and like the HTML is fine. It's just that to render this div, you're. Digging into some active record super deep. and so, you know, that was usually the, the, the problems that we would see and they're usually easy enough to fix by making an index or. Sometimes you do some caching or something like that. and that solved most of the, most of the issues [00:35:09] Jeremy: The different ways people learn [00:35:09] Jeremy: so you're also the author of the book, Sustainable Web Development with Ruby on Rails. And when you talk to people about like how they learn things, a lot of them are going on YouTube, they're going on, uh, you know, looking for blogs and things like that. And so as an author, what do you think the role is of, of books now? Yeah, [00:35:29] David: I have thought about this a lot, because I, when I first got started, I'm pretty old, so books were all you had, really. Um, so they seem very normal and natural to me, but... does someone want to sit down and read a 400 page technical book? I don't know. so Dave Thomas who runs Pragmatic Bookshelf, he was on a podcast and was asked the same question and basically his answer, which is my answer, is like a long form book is where you can really lay out your thinking, really clarify what you mean, really take the time to develop sometimes nuanced, examples or nuanced takes on something that are Pretty hard to do in a short form video or in a blog post. Because the expectation is, you know, someone sends you an hour long YouTube video, you're probably not going to watch that. Two minute YouTube video is sure, but you can't, you can't get into so much, kind of nuanced detail. And so I thought that was, was right. And that was kind of my motivation for writing. I've got some thoughts. They're too detailed. It's, it's too much set up for a blog post. There's too much of a nuanced element to like, really get across. So I need to like, write more. And that means that someone's going to have to read more to kind of get to it. But hopefully it'll be, it'll be valuable. one of the sessions that we're doing later today is Ruby content creators, where it's going to be me and Noel Rappin and Dave Thomas representing the old school dudes that write books and probably a bunch of other people that do, you know, podcasts videos. It'd be interesting to see, I really want to know how do people learn stuff? Because if no one reads books to learn things, then there's not a lot of point in doing it. But if there is value, then, you know. It should be good and should be accessible to people. So, that's why I do it. But I definitely recognize maybe I'm too old and, uh, I'm not hip with the kids or, or whatever, whatever the case is. I don't know. [00:37:20] Jeremy: it's tricky because, I think it depends on where you are in the process of learning that thing. Because, let's say, you know a fair amount about the technology already. And you look at a book, in a lot of cases it's, it's sort of like taking you from nothing to something. And so you're like, well, maybe half of this isn't relevant to me, but then if I don't read it, then I'm probably missing a lot still. And so you're in this weird in be in between zone. Another thing is that a lot of times when people are trying to learn something, they have a specific problem. And, um, I guess with, with books, it's, you kind of don't know for sure if the thing you're looking for is going to be in the book. [00:38:13] David: I mean, so my, so my book, I would not say as a beginner, it's not a book to learn how to do Rails. It's like you already kind of know Rails and you want to like learn some comprehensive practices. That's what my book is for. And so sometimes people will ask me, I don't know Rails, should I get your book? And I'm like, no, you should not. but then you have the opposite thing where like the agile web development with Rails is like the beginner version. And some people are like, Oh, it's being updated for Rails 7. Should I get it? I'm like, probably not because How to go from zero to rails hasn't changed a lot in years. There's not that much that's going to be new. but, how do you know that, right? Hopefully the Table of Contents tells you. I mean, the first book I wrote with Pragmatic, they basically were like, The Table of Contents is the only thing the reader, potential reader is going to have to have any idea what's in the book. So, You need to write the table of contents with that in mind, which may not be how you'd write the subsections of a book, but since you know that it's going to serve these dual purposes of organizing the book, but also being promotional material that people can read, you've got to keep that in mind, because otherwise, how does anybody, like you said, how does anybody know what's, what's going to be in there? And they're not cheap, I mean, these books are 50 bucks sometimes, and That's a lot of money for people in the U. S. People outside the U. S. That's a ton of money. So you want to make sure that they know what they're getting and don't feel ripped off. [00:39:33] Jeremy: Yeah, I think the other challenge is, at least what I've heard, is that... When people see a video course, for whatever reason, they, they set, like, a higher value to it. They go, like, oh, this video course is, 200 dollars and it's, like, seems like a lot of money, but for some people it's, like, okay, I can do that. But then if you say, like, oh, this, this book I've been researching for five years, uh, I want to sell it for a hundred bucks, people are going to be, like no. No way., [00:40:00] David: Yeah. Right. A hundred bucks for a book. There's no way. That's a, that's a lot. Yeah. I mean, producing video, I've thought about doing video content, but it seems so labor intensive. Um, and it's kind of like, It's sort of like a performance. Like I was mentioning before we started that I used to play in bands and like, there's a lot to go into making an even mediocre performance. And so I feel like, you know, video content is the same way. So I get that it like, it does cost more to produce, but, are you getting more information out of it? I, that, I don't know, like maybe not, but who knows? I mean, people learn things in different ways. So, [00:40:35] Jeremy: It's just like this perception thing, I think. And, uh, I'm not sure why that is. Um, [00:40:40] David: Yeah, maybe it's newer, right? Maybe books feel older so they're easier to make and video seems newer. I mean, I don't know. I would love to talk to engineers who are like... young out of college, a few years into their career to see what their perception of this stuff is. Cause I mean, there was no, I mean, like I said, I read books cause that's all there was. There was no, no videos. You, you go to a conference and you read a book and that was, that was all you had. so I get it. It seems a whole video. It's fancier. It's newer. yeah, I don't know. I would love to hear a wide variety of takes on it to see what's actually the, the future, you know? [00:41:15] Jeremy: sure, yeah. I mean, I think it probably can't just be one or the other, right? Like, I think there are... Benefits of each way. Like, if you have the book, you can read it at your own pace without having to, like, scroll through the video, and you can easily copy and paste the, the code segments, [00:41:35] David: Search it. Go back and forth. [00:41:36] Jeremy: yeah, search it. So, I think there's a place for it, but yeah, I think it would be very interesting, like you said, to, to see, like, how are people learning, [00:41:45] David: Right. Right. Yeah. Well, it's the same with blogs and podcasts. Like I, a lot of podcasters I think used to be bloggers and they realized that like they can get out what they need by doing a podcast. And it's way easier because it's more conversational. You don't have to do a bunch of research. You don't have to do a bunch of editing. As long as you're semi coherent, you can just have a conversation with somebody and sort of get at some sort of thing that you want to talk about or have an opinion about. And. So you, you, you see a lot more podcasts and a lot less blogs out there because of that. So it's, that's kind of like the creators I think are kind of driving that a little bit. yeah. So I don't know. [00:42:22] Jeremy: Yeah, I mean, I can, I can say for myself, the thing about podcasts is that it's something that I can listen to while I'm doing something else. And so you sort of passively can hopefully pick something up out of that conversation, but... Like, I think it's maybe not so good at the details, right? Like, if you're talking code, you can talk about it over voice, but can you really visualize it? Yeah, yeah, yeah. I think if you sit down and you try to implement something somebody talked about, you're gonna be like, I don't know what's happening. [00:42:51] David: Yeah. [00:42:52] Jeremy: So, uh, so, so I think there's like these, these different roles I think almost for so like maybe you know the podcast is for you to Maybe get some ideas or get some familiarity with a thing and then when you're ready to go deeper You can go look at a blog post or read a book I think video kind of straddles those two where sometimes video is good if you want to just see, the general concept of a thing, and have somebody explain it to you, maybe do some visuals. that's really good. but then it can also be kind of detailed, where, especially like the people who stream their process, right, you can see them, Oh, let's, let's build this thing together. You can ask me questions, you can see how I think. I think that can be really powerful. at the same time, like you said, it can be hard to say, like, you know, I look at some of the streams and it's like, oh, this is a three hour stream and like, well, I mean, I'm interested. I'm interested, but yeah, it's hard enough for me to sit through a, uh, a three hour movie, [00:43:52] David: Well, then that, and that gets into like, I mean, we're, you know, we're at a conference and they, they're doing something a little, like, there are conference talks at this conference, but there's also like. sort of less defined activities that aren't a conference talk. And I think that could be a reaction to some of this too. It's like I could watch a conference talk on, on video. How different is that going to be than being there in person? maybe it's not that different. Maybe, maybe I don't need to like travel across the country to go. Do something that I could see on video. So there's gotta be something here that, that, that meets that need that I can't meet any other way. So it's all these different, like, I would like to think that's how it is, right? All this media all is a part to play and it's all going to kind of continue and thrive and it's not going to be like, Oh, remember books? Like maybe, but hopefully not. Hopefully it's like, like what you're saying. Like it's all kind of serving different purposes that all kind of work together. Yeah. [00:44:43] Jeremy: I hope that's the case, because, um, I don't want to have to scroll through too many videos. [00:44:48] David: Yeah. The video's not for me. Large Language Models [00:44:50] Jeremy: I, I like, I actually do find it helpful, like, like I said, for the high level thing, or just to see someone's thought process, but it's like, if you want to know a thing, and you have a short amount of time, maybe not the best, um, of course, now you have all the large language model stuff where you like, you feed the video in like, Hey, tell, tell, tell me, uh, what this video is about and give me the code snippets and all that stuff. I don't know how well it works, but it seems [00:45:14] David: It's gotta get better. Cause you go to a support site and they're like, here's how to fix your problem, and it's a video. And I'm like, can you just tell me? But I'd never thought about asking the AI to just look at the video and tell me. So yeah, it's not bad. [00:45:25] Jeremy: I think, that's probably where we're going. So it's, uh, it's a little weird to think about, but, [00:45:29] David: yeah, yeah. I was just updating, uh, you know, like I said, I try to keep the book updated when new versions of Rails come out, so I'm getting ready to update it for Rails 7. 1 and in Amazon's, Kindle Direct Publishing as their sort of backend for where you, you know, publish like a Kindle book and stuff, and so they added a new question, was AI used in the production of this thing or not? And if you answer yes, they want you to say how much, And I don't know what they're gonna do with that exactly, but I thought it was pretty interesting, cause I would be very disappointed to pay 50 for a book that the AI wrote, right? So it's good that they're asking that? Yeah. [00:46:02] Jeremy: I think the problem Amazon is facing is where people wholesale have the AI write the book, and the person either doesn't review it at all, or maybe looks at a little, a little bit. And, I mean, the, the large language model stuff is very impressive, but If you have it generate a technical book for you, it's not going to be good. [00:46:22] David: yeah. And I guess, cause cause like Amazon, I mean, think about like Amazon scale, like they're not looking at the book at all. Like I, I can go click a button and have my book available and no person's going to look at it. they might scan it or something maybe with looking for bad words. I don't know, but there's no curation process there. So I could, yeah. I could see where they could have that, that kind of problem. And like you as the, as the buyer, you don't necessarily, if you want to book on something really esoteric, there are a lot of topics I wish there was a book on that there isn't. And as someone generally want to put it on Amazon, I could see a lot of people buying it, not realizing what they're getting and feeling ripped off when it was not good. [00:47:00] Jeremy: Yeah, I mean, I, I don't know, if it's an issue with the, the technical stuff. It probably is. But I, I know they've definitely had problems where, fiction, they have people just generating hundreds, thousands of books, submitting them all, just flooding it. [00:47:13] David: Seeing what happens. [00:47:14] Jeremy: And, um, I think that's probably... That's probably the main reason why they ask you, cause they want you to say like, uh, yeah, you said it wasn't. And so now we can remove your book. [00:47:24] David: right. Right. Yeah. Yeah. [00:47:26] Jeremy: I mean, it's, it's not quite the same, but it's similar to, I don't know what Stack Overflow's policy is now, but, when the large language model stuff started getting big, they had a lot of people answering the questions that were just. Pasting the question into the model [00:47:41] David: Which because they got it from [00:47:42] Jeremy: and then [00:47:43] David: The Got model got it from Stack Overflow. [00:47:45] Jeremy: and then pasting the answer into Stack Overflow and the person is not checking it. Right. So it's like, could be right, could not be right. Um, cause, cause to me, it's like, if, if you generate it, if you generate the answer and the answer is right, and you checked it, I'm okay with that. [00:48:00] David: Yeah. Yeah. [00:48:01] Jeremy: but if you're just like, I, I need some karma, so I'm gonna, I'm gonna answer these questions with, with this bot, I mean, then maybe [00:48:08] David: I could have done that. You're not adding anything. Yeah, yeah. [00:48:11] Jeremy: it's gonna be a weird, weird world, I think. [00:48:12] David: Yeah, no kidding. No kidding. [00:48:15] Jeremy: that's a, a good place to end it on, but is there anything else you want to mention, [00:48:19] David: No, I think we covered it all just yeah, you could find me online. I'm Davetron5000 on Ruby. social Mastodon, I occasionally post on Twitter, but not that much anymore. So Mastodon's a place to go. [00:48:31] Jeremy: David, thank you so much [00:48:32] David: All right. Well, thanks for having me.

I am thrilled to share with you the latest episode of the Jaded Mechanic podcast!

People take Jason Benetti out of context, fair or unfair, in a hilarious way + Every city has good parts and bad parts

"McElroy & Cubelic In The Morning" airs 7am-10am weekdays on WJOX-94.5!! See omnystudio.com/listener for privacy information.

Here's only here to make himself look good.  Chicago's best morning radio show now has a podcast! Don't forget to rate, review, and subscribe wherever you listen to podcasts and remember that the conversation always lives on the Q101 Facebook page.  The Q101 Morning Crew is live every morning from 6a-10a on Q101.    Subscribe to our channel HERE: https://www.youtube.com/@Q101 Like Q101 on Facebook HERE: https://www.facebook.com/q101chicago Follow Q101 on Twitter HERE: https://twitter.com/Q101Chicago Follow Q101 on Instagram HERE: https://www.instagram.com/q101chicago/?hl=enSee omnystudio.com/listener for privacy information.

In this heartwarming Just Chatting episode, we dive into the GOOD PARTS of pregnancy, birth, and motherhood. Hosted by Lina Forrestal, this episode aims to discuss the joyous moments, personal growth, and profound emotions that come with becoming a mom. Mentioned in this episode:Jon and Kate + 8: Family Circus VICE DocumentaryFirst pill for postpartum depression approved: ZurzuvaeThe good parts of pregnancy:Seeing baby on ultrasounds and watching their developmentLearning how strong the woman body truly isFeeling the baby moveNice comments from strangersThe good parts of birth:Seeing baby for the first timeWhen baby latches for the first timeRealizing that yu're much stronger than you ever thought possibleInstinctual strength and power from birthing a humanThe good parts of motherhood:Watching them grow and hit milestonesWatching their personality blossomAll the nostalgic moments reminding you of your own childhoodTheir little laughs and hugsThe unconditional love Hope you enjoyed this episode! Thank you for listening.Support the showConnect with Lina on @linaforrestal on InstagramFollow the @newmamaspodcast on InstagramRead Lina's Blog: www.linaforrestal.comSupport the Show: Buy Me a Coffee (https://www.buymeacoffee.com/newmamaspodcast)

This week Craig and Alex review Grave of the Fireflies as part of their month of Summertime Sadness! Next week we are watching Marley and Me!

Michael Furr is a comedian in Baltimore and the booking manager, producer, host, busser, etc., of the Lou Costello Room. He's been doing stand-up for 10 years and has two specials – Straight Acting and I Didn't Die – on Amazon Prime and Spotify and he's working on a third. He's one of the hardest working comedians in the area and is way too busy to waste his time with guys from Washington, D.C.Follow Michael Furr: Instagram: https://www.instagram.com/michaelfurrcomedy/Twitter: https://twitter.com/MichaelCFurrFacebook: https://www.facebook.com/MichaelFurrComedyTikTok: https://www.tiktok.com/@michaelfurrcomedyWebsite: https://www.michaelfurr.com/Support the show

FIFTY FIFTY's "Cupid" is still going strong on the charts, thanks to the popularity of its English "Twin" version. But where do you from there? What other K-pop songs do you queue up on your playlist? After all, you need at least a few good songs to get the algorithm to do its thing!Lucky for you, we've got four K-pop songs for you that are in the same vein as FIFTY FIFTY's "Cupid." Tune in to hear us break down what's helping "Cupid" chart so well plus our personal song recs for you to play next.EPISODE RUNDOWN:IntroHow does TikTok factor into all this?Is "Cupid" an outlier?Other K-pop Soft Pop Hits We RecommendIU - "BBIBBI"LE SSERAFIM - "Good Parts (when the quality is bad but I am)BOL4 - "Some"Wonder Girls - "Rewind"What older K-pop hits would blow up on TikTok today?LET US KNOW: What other K-pop soft pop hits would you recommend? Tag us on Instagram or Twitter with your thoughts!It's a K-pop Thing is hosted by two journalists and longtime K-pop stans, Alexis Hodoyán-Gastélum and Theresa Avila. FOLLOW US:Twitter: @ikptpod & Instagram: @ikptpodFEEDBACK? IDEAS FOR FUTURE EPISODES?E-mail us at info@kpoppod.com

One of the amazing things that technology enables us to do is personalize services and developments. Yaron Galai, Co-founder and Co-CEO of Outbrain, is undoubtedly a pioneer in the way he has introduced this concept into the world of online content. In an inspiring conversation with Dr. Tal Patalon, head of KSM and the host of "A Matter Of Life And Death" podcast, he talks about his drive for innovation, the positive side of technology, and the personal drama that shaped his outlook on life. Production: Raz Hason, KeyPod Studio

My new book LOSERTHINK, available now on Amazon https://tinyurl.com/rqmjc2a Find my "extra" content on Locals: https://ScottAdams.Locals.com Content: Trump Plan: Cities from scratch & flying cars Media poisoning divides us by race Defending Andrew Tate Whiteboard1: How To Fix Everything Whiteboard2: Bad Schools & Systemic Racism The Grand Reframe: Rich vs. Poor ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ If you would like to enjoy this same content plus bonus content from Scott Adams, including micro-lessons on lots of useful topics to build your talent stack, please see scottadams.locals.com for full access to that secret treasure. --- Support this podcast: https://anchor.fm/scott-adams00/support

When the Super Bowl making it's way back to our TVs once again, it's time to breakdown the best part of America's biggest sporting event... The trailers! Just like the past big football games, we are breaking down the newest movies and shows that were highlighted at Super Bowl 57!

...because if something is going to be bad, let it be AWFUL.Support the show***Patreon: https://www.patreon.com/IMNerdSend listener letters to: imnerdpodcast@gmail.comLinktree: https://linktr.ee/IMNerdPodcastThanks for listening!

Robert and Garrison traveled through a portal to the future located in Las Vegas, Nevada. Now they're going to tell you what (good) things to expect from our techno overlords.See omnystudio.com/listener for privacy information.

Life is like a movie, full of suspense, thrills, and highs and lows.  As we near the close of 2022, have we taken the time to reflect on the year? If so, what parts do you see? Do we see good parts or bad parts? Our brains are naturally wired to look for problems and challenges to keep us safe and alive, but we can CHOOSE to see the good parts.  In the Book of Mormon, the family of Lehi went traveling in the wilderness and the sons each had a different version of the story.  Nephi's was full of abundance amidst the challenges, and Laman and Lemuel's was full of hardship and complaints.  Lehi said, "I choose the good part." We too can choose the good part. We can see the good in our circumstances and learn from the challenging times rather than close in and focus on them.  At this Christmas Season, let us reflect on the year and choose the good parts!

Chuck welcomes Lucas to the show as a regular host of Adventures in Angular. They begin by discussing Angular 15's most recent updates and what benefit it might have for the current Angular community. Lucas also offers his perspective on the new tools and what makes him excited to use them. About this Episode All the new features of Angular 15 Advantages of Directive composition API Pros and Cons of Image optimization How these changes can be integrated into your application Sponsors Chuck's Resume Template Developer Book Club starting with Clean Architecture by Robert C. Martin Become a Top 1% Dev with a Top End Devs Membership Links Angular v15 Mind Map + Breaking Changes Unvoid Picks Charles - Thunderbird — Make Email Easier. — Thunderbird Charles - Gmelius: Top-Rated Email and Team Collaboration Software Charles - Pipedrive™ CRM - Pipedrive Official Site Lucas - Trip to Argentina (cities: El Calafate and Buenos Aires Lucas - Brazil World Cup squad 2022

Chuck welcomes Lucas to the show as a regular host of Adventures in Angular. They begin by discussing Angular 15's most recent updates and what benefit it might have for the current Angular community. Lucas also offers his perspective on the new tools and what makes him excited to use them. About this Episode All the new features of Angular 15 Advantages of Directive composition API Pros and Cons of Image optimization How these changes can be integrated into your application Sponsors Chuck's Resume Template Developer Book Club starting with Clean Architecture by Robert C. Martin Become a Top 1% Dev with a Top End Devs Membership Links Angular v15 Mind Map + Breaking Changes Unvoid Picks Charles - Thunderbird — Make Email Easier. — Thunderbird Charles - Gmelius: Top-Rated Email and Team Collaboration Software Charles - Pipedrive™ CRM - Pipedrive Official Site Lucas - Trip to Argentina (cities: El Calafate and Buenos Aires Lucas - Brazil World Cup squad 2022

We are back for round 2 with JP Saxe! Kat has Grammy nominated singer/songwriter JP Saxe on the show to talk about relationships from a slightly different perspective for a second week in a row. This week, Kat and JP dive more into masculinity and how to embrace the parts that fit and find freedom from the types chains and expectations that toxic masculinity attempts to lock people in.  Don't forget to listen to JP's new song When You Think of Me and presave The Good Parts! Follow JP on Instagram HERE! Follow Kat on Instagram: @Kat.Defatta Follow the podcast Instagram: @YouNeedTherapyPodcast Have a question, concern, guest idea, something else? Reach Kat at: Kathryn@youneedtherapyPodcast.com Heard about Three Cords Therapy but don't know what it is? Click here!   Produced by: @HoustonTilleySee omnystudio.com/listener for privacy information.

There are so many things available in this world that can make things so confusing. However, just because they are available doe not mean we should take advantage of it. Listen as Bro. Josh Johnson teaches on choosing the right things. Be sure to subscribe/follow us on Twitter, Instagram, all podcast platforms, and watch us on https://tv.livinghopemd.com/ every Sunday at 11am EST. Also, click on the links below to learn more about us: Website: http://www.livinghopemd.com/about-us Facebook: https://www.facebook.com/LivingHopeMdlexpark/ Twitter: https://twitter.com/livinghopemd Instagram: https://www.instagram.com/livinghopemd/

This week, Kat has Grammy nominated singer/songwriter JP Saxe on the show to talk about relationships from a slightly different perspective. Can love still be meaningful after a something ends? According to JP... it most definitely can. He shares with us what he has learned about love after having two different experiences in how his own relationships have ended. And the best news . . . Kat's interview with JP is two parts so stay tuned for MORE from JP next week! Don't forget to listen to JP's new song When You Think of Me and presave The Good Parts! Follow JP on Instagram HERE! Follow Kat on Instagram: @Kat.Defatta Follow the podcast Instagram: @YouNeedTherapyPodcast Have a question, concern, guest idea, something else? Reach Kat at: Kathryn@youneedtherapyodcast.com Heard about Three Cords Therapy but don't know what it is? Click here!   Produced by: @HoustonTilleySee omnystudio.com/listener for privacy information.

The three headed monster of HYCE is back together as they try to tame the first comeback of recently debuted, LE SSERAFIM. Similar to "Fearless" this EP serves up 5 more GOOD PARTS each with their own set of spices. No IMPURITIES are to be found though as this group seemingly cannot be broken. Let's Connect: Twitter: @HallyuCanEat Instagram: @HallyuCanEat Email: HallyuCanEat@gmail.com Follow some of the Co-Leaders! Allen Mark - https://twitter.com/allenmarkca Chuck - https://twitter.com/ChuckJose [P/E #90]

Jana connects with Dr. Wendy Walsh to hear about the benefits of divorce. It's a hard process to endure, but Dr. Walsh hopes to show that you can truly grow and excel after splitting from your partner. Jana opens up about how she feels about her ex a year after finalizing the divorce. And, we hear some amazing advice on what to do when entering a new relationship to protect yourself from more heartbreak. See omnystudio.com/listener for privacy information.

Only the good parts about home improvement and DIY projects. What's your favorite store? If you were a tool ...? What project would you tackle with $100k? Does Scooter the dog need heated floors? Lysa, Natalie, and G.J. play the game, Guess the Movie or Show. Send us your biggest questions, if we answer it on the air you'll receive a fabulous prize! https://my.captivate.fm/GoodPartsPodcast@gmail.com (GoodPartsPodcast@gmail.com ) Website: https://goodparts.captivate.fm/ (https://goodparts.captivate.fm/) https://goodparts.captivate.fm (Only the Good Parts website) InstaGram: @GoodPartsPod Some of the movies discussed: The Money Pit Property Brothers Frozen Selling Sunset Queer Eye Studio Under the Stairs Copyright 2022 Studio Under the Stairs https://www.captivate.fm/signup?ref=gjclayburn (This podcast is hosted by Captivate, try it yourself for free.)

In response to an article by a writer who was confused and fearful by all the negative she heard before her son was born, the TPP Team discusses the false ideals that discouraged them as moms and then shares what is GOOD and true about this amazing calling and actually learning to enjoy our children. 

Todays episode we discussed What Lies Beyond the Veil. We both loved this book and cannot wait for the second one to come out! As always, there will be spoilers, and make sure to listen to the trigger warnings in the beginning before listening! If you want to see our book looks, go check out our tiktok: @blues.library and our instagram: @blues.librarypodcast. We appreciate you listening to us talk, and if you have any books you would love for us to read and discuss, let us know! We will catch you on Monday, May 9th! We hope you have a good and safe week!

Only the good parts about rain gardens. What exactly is a rain garden? What do rain gardens do? Should Tom Cruise have won an Oscar for Rain Man? Lysa and G.J. play the game, Rain or Garden? Send us your biggest questions, if we answer it on the air you'll receive a fabulous prize! https://my.captivate.fm/GoodPartsPodcast@gmail.com (GoodPartsPodcast@gmail.com ) Website: https://goodparts.captivate.fm/ (https://goodparts.captivate.fm/) https://goodparts.captivate.fm (Only the Good Parts website) InstaGram: @GoodPartsPod Some of the movies discussed: Rain Man Garden State Purple Rain The Secret Garden Singin' in the Rain Studio Under the Stairs Copyright 2022 Studio Under the Stairs https://www.captivate.fm/signup?ref=gjclayburn (This podcast is hosted by Captivate, try it yourself for free.)

I think that sometimes we only talk about the good parts of life as if there weren't any bad parts. Sometimes it sucks. Sometimes it just does. Your legs hurt, your lungs hurt, your heart hurts and just about everything about life sucks. You basically feels like the world is crumbling around you. You can't breathe, you feel trapped, it's seems everyone and everything is holding you back, and you can't hang out with your old friends because they don't see your future. Some days you want to cry. You want to lay on your back in the middle of the road and ask yourself, "why?"⠀ Each episode will share practical advice and stories that can help Turn Positivity Into Possibility for everyone listening--Connect with Dane....Click Here --- Send in a voice message: https://anchor.fm/dane-boyle/message

Only the good parts about returning to the office(?) Do you prefer to work from home or the office? Uniforms, business casual, or something else? Is Christopher Walken ever the most normal person in any film or show? Lysa and G.J. play the game, From the Office. Send us your biggest questions, if we answer it on the air you'll receive a fabulous prize! https://my.captivate.fm/GoodPartsPodcast@gmail.com (GoodPartsPodcast@gmail.com ) Website: https://goodparts.captivate.fm/ (https://goodparts.captivate.fm/) https://goodparts.captivate.fm (Only the Good Parts website) InstaGram: @GoodPartsPod Some of the movies discussed: The Office Office Space Severance The Newsroom Glengarry Glen Ross Studio Under the Stairs Copyright 2022 Studio Under the Stairs https://www.captivate.fm/signup?ref=gjclayburn (This podcast is hosted by Captivate, try it yourself for free.)

Recently I have been overly focused on the negative parts of relationships & so I wanted to come back with focus on the good parts.

Recently I have been overly focused on the negative parts of relationships & so I wanted to come back with focus on the good parts.

This week, your two favorite Matts discuss the 2022 Grammy Awards, Will Smith apologizing to Chris Rock and resigning from the Academy, the Real Housewives of New York City being split into two shows, and more! Watch Matt Steele's movie DIVOS! Listen to Matt Palmer's EP, The Good Parts! Become a patron! Watch us on YouTube Follow @mattpalmermusic Follow @itsmattsteele

Only the good parts about exercise. What's your favorite type of exercise? Would you ever do an Ironman Triathlon? Can exercise give you chocolate benefits? Lysa and G.J. play the game, An exercise into Lysa's mind. Send us your biggest questions, if we answer it on the air you'll receive a fabulous prize! https://my.captivate.fm/GoodPartsPodcast@gmail.com (GoodPartsPodcast@gmail.com ) Website: https://goodparts.captivate.fm/ (https://goodparts.captivate.fm/) https://goodparts.captivate.fm (Only the Good Parts website) InstaGram: @GoodPartsPod Some of the movies discussed: When Harry Met Sally Defending Your Life Babe: The Sheep Pig Lost in Translation Studio Under the Stairs Copyright 2022 Studio Under the Stairs https://www.captivate.fm/signup?ref=gjclayburn (This podcast is hosted by Captivate, try it yourself for free.)

James's personal websiteDjango in Depth talk at PyCon Montreal 2015Django the Good Parts at PyCon 2014 and slidesLet's Build a Web Framework by Jacob Kaplan Moss at PyCon 2017How I'm Testing in 2020Against service layers in DjangoSupport the ShowThis podcast does not have any ads or sponsors. To support the show, please consider purchasing a book, signing up for Button, or reading the Django News newsletter.

I wanted to talk about Autistic Pride, as I talk about each and every year. I talk about it every year, because it is so important for Autistic People to be able to feel pride in ourselves, especially when society, often, tells us that we are defective, broken, and that our ways of doing things: interacting with, engaging with, and experiencing the world, are wrong; and that we should strive to cover up the NeuroDivergent parts of ourselves. This episode is also available as a blog post: https://neurodivergentrebel.com/2022/03/30/autistic-pride-is-not-just-about-the-good-parts-of-being-neurodivergent/ --- Support this podcast: https://anchor.fm/neurodivergentrebel/support

This week, your two favorite Matts discuss the Oscars, Will Smith slapping Chris Rock at the Oscars, the Judge Kentaji Brown Jackson Supreme Court Confirmation hearing, and more! Listen to Matt Palmer's EP, The Good Parts! Watch Matt Steele's movie DIVOS! Become a patron! Watch us on YouTube Follow @itsmattsteele Follow @mattpalmermusic

This week, your two favorite Matts discuss Coda becoming the frontrunner for Best Picture after its DGA win, Jane Campion ruining her good will at the Critic's Choice Awards, Katie & Tom from Vanderpump Rules separating, and more! Watch Matt Steele's movie DIVOS! Listen to Matt Palmer's EP, The Good Parts! Become a patron! Watch us on YouTube Follow @mattpalmermusic Follow @itsmattsteele

Only the good parts about daylight saving time. Do you prefer and extra hour of morning or evening? Should the U.S. stay on daylight saving time permanently? Is AARP a trusted source to cite? Lysa, Natalie, and G.J. play the game, It's About Time ... Travel. Send us your biggest questions, if we answer it on the air you'll receive a fabulous prize! https://my.captivate.fm/GoodPartsPodcast@gmail.com (GoodPartsPodcast@gmail.com ) https://goodparts.captivate.fm (Only the Good Parts website) InstaGram: @GoodPartsPod Some of the movies discussed: Back to the Future Bill & Ted's Excellent Adventure Safety Not Guaranteed The Simpsons Meet the Robinsons Studio Under the Stairs Copyright 2022 Studio Under the Stairs https://www.captivate.fm/signup?ref=gjclayburn (This podcast is hosted by Captivate, try it yourself for free.)

Lysa & G.J. dip in for a quick programming note. Send us your biggest questions, if we answer it on the air you'll receive a fabulous prize! https://my.captivate.fm/GoodPartsPodcast@gmail.com (GoodPartsPodcast@gmail.com ) https://goodparts.captivate.fm (Only the Good Parts website) InstaGram: @GoodPartsPod Studio Under the Stairs Copyright 2022 Studio Under the Stairs https://www.captivate.fm/signup?ref=gjclayburn (This podcast is hosted by Captivate, try it yourself for free.)

Only the good parts about The Lord of the Rings. Movies or books? Which character would you be? Is Gollum just misunderstood? Lysa and G.J. play the game, The Lord of the (Molly) Ringwalds. Send us your biggest questions, if we answer it on the air you'll receive a fabulous prize! https://my.captivate.fm/GoodPartsPodcast@gmail.com (GoodPartsPodcast@gmail.com ) Website: https://goodparts.captivate.fm/ (https://goodparts.captivate.fm/) https://goodparts.captivate.fm (Only the Good Parts website) InstaGram: @GoodPartsPod Some of the movies discussed: The Breakfast Club Pretty in Pink Sixteen Candles Riverdale Studio Under the Stairs Copyright 2022 Studio Under the Stairs https://www.captivate.fm/signup?ref=gjclayburn (This podcast is hosted by Captivate, try it yourself for free.)

Today's episode is sponsored by Codiga, a smart coding assistant and automated code review platform. Try Codiga for FREE!Links:Retweet and Like for a chance to win either Daniel's Build a Twitter Audience Course or his Good Parts of AWS bookDaniel's Twitter that contains all he doesSubscribe on iTunes, Spotify, Google, Deezer, or via RSS.

Only the good parts about Shark Tank. What product do you wish you had come up with? Which Shark would you prefer to work with? Which Shark will be the first in space? Lysa, Natalie, and G.J. play the game, Shark! Send us your biggest questions, if we answer it on the air you'll receive a fabulous prize! https://my.captivate.fm/GoodPartsPodcast@gmail.com (GoodPartsPodcast@gmail.com ) https://goodparts.captivate.fm (Only the Good Parts website) InstaGram: @GoodPartsPod Some of the movies discussed: Finding Nemo Sharknado Jaws Shark Tale Impractical Jokers Copyright 2022 Studio Under the Stairs https://www.captivate.fm/signup?ref=gjclayburn (This podcast is hosted by Captivate, try it yourself for free.)

Only the good parts about board games. Which is better, a strategic or luck-based game? Do you prefer to play online or in-person? What's the best game to play in space? Lysa, Natalie, and G.J. play the game, Guess the Game. Send us your biggest questions, if we answer it on the air you'll receive a fabulous prize! https://my.captivate.fm/GoodPartsPodcast@gmail.com (GoodPartsPodcast@gmail.com ) https://goodparts.captivate.fm (Only the Good Parts website) InstaGram: @GoodPartsPod Some of the movies discussed: Battleship Scrabble (YouTube) Candyland Jumanji Ouija Searching for Bobby Fisher (Chess) Copyright 2022 Studio Under the Stairs https://www.captivate.fm/signup?ref=gjclayburn (This podcast is hosted by Captivate, try it yourself for free.)