Skip to content
443: Rails World and Open Source with Stefanni Brasil episode artwork

Oct 8, 2024 32 min

443: Rails World and Open Source with Stefanni Brasil

from The Bike Shed Hosted by thoughtbot

Learning from other developers is an important ingredient to your success. During this episode, Joël Quenneville is joined by Stefanni Brasil, Senior Developer at Thoughtbot, and core maintainer of faker-ruby. To open our conversation, she shares the details of her experience at the Rails World conference in Toronto and the projects she enjoyed seeing most. Next, we explore the challenge of Mac versus Windows and how these programs interact with Ruby on Rails and dive into Stefanni’s involvement in Open Source for Thoughtbot and beyond; what she loves about it, and how she is working to educate others and expand the current limitations that people experience. This episode is also dedicated to the upcoming Open Source Summit that Stefanni is planning on 25 October 2024, what to expect, and how you can get involved. Thanks for listening! Key Points From This Episode: Introducing and catching up with Thoughtbot Senior Developer and maintainer of faker-ruby, Stefanni Brasil. Her experience at the Rails World conference in Toronto and the projects she found most inspiring. Why accessibility remains a key topic. How Ruby on Rails translates on Mac and Windows. Stefanni’s involvement in Open Source and why she enjoys it. Her experience as core maintainer at faker-ruby. Ideas she is exploring around Jeremy Evans’ book Polished Ruby Programming and the direction of Faker. Involvement in Thoughtbot’s Open Source and how it drew her in initially. The coaching series on Open Source that she participated in earlier this year. What motivated her to create a public Google doc on Open Source maintenance. An upcoming event: the Open Source Summit. The time commitment expected from attendees. How Stefanni intends to interact with guests and the talk that she will give at the event. Why everyone is welcome to engage at any level they are comfortable with. Links Mentioned in Today’s Episode: Stefanni Brasil Stefanni Brasil on X Thoughtbot Open Summit Open Source Issues doc Open Source at Thoughtbot Polished Ruby Programming Faker Gem Rails World The Bike Shed Joël Quenneville on LinkedIn

Episode details come from the podcast's RSS feed.

Embed this episode

Ready to play

443: Rails World and Open Source with Stefanni Brasil

0:00 32:23
of matches

Transcript Auto-generated, may contain errors

This episode is brought to you by WorkOS. If you're building a B2B SaaS app, at some point, your customers will start asking for enterprise features like single sign-on, SCIM, provisioning, role-based access control, and audit trails. That's where WorkOS comes in, with ease-to-use and flexible APIs that help you ship enterprise features on day one without slowing down your core product development. Today, some of the hottest startups in the world are already powered by WorkOS, including ones you probably know, like Perplexity, Vercel, Jasper, and Webflow. WorkOS also provides a generous free tier of up to 1 million monthly active users for its user management solution.

making it the perfect authentication and authorization solution for growing companies. It comes standard with rich features like social logins, bot protection, MFA, roles, and permissions, and more. If you're currently looking to build SSO for your first enterprise customer, you should consider using WorkOS. Integrate in minutes and start shipping enterprise plans today. Check it all out at WorkOS.com. That's WorkOS.com.

Hello and welcome to another episode of The Bike Shed, a weekly podcast from your friends at ThoughtBot about developing great software. I'm Joelle Kinville. Today I'm joined with colleague Stephanie Brazil. Hello. And together we're here to share a little bit of what we've learned along the way. So Stephanie, what's new in your world?

What's been new for me has been trying to shift my volunteer work from technology to helping out more with local initiatives and volunteering to causes that I share the values with where I live. So that has been an interesting journey for me in learning a lot and meeting excited folks who shared the same values as me. So that has been a really nice new thing in my life. What has been the motivation for you switching from sort of more technology-focused volunteer work to, I assume this is more now in-person local volunteering? Yeah, that's exactly it. Mostly because I've moved a lot throughout my life. And every time I move, I have to start again, building connections, making friends. And I started realizing how important it is to have this local connection, especially because most of us are now working remotely. I started feeling that need even more. And something that made me also think about that was there was someone from the Ruby community who was quite active. And I had noticed that...

They stopped posting, like I hadn't heard about them for a while. And a few months later, and I thought of reaching out to them to just say, hey, how's it going? But I just thought, oh, they're probably busy. And a few months later, someone else posted on Twitter that I had actually passed away in an accident. And yeah, it was a hard moment. Like we have never met in person, but it made me think as much as volunteering, meeting folks online has helped me a lot in my career. If I die today, probably nobody would notice. And I really wanted to.

have that local support and that local network. And I think that volunteering is a great way to start. That's a bit of a paradox that we have to deal with as software developers, and especially on a remote team, is that so much of the things that we care about, the communities that we're involved in, are online communities. And in Thoughtbot's case, because our company is also now fully remote, our colleagues are now online communities as well. So balancing this, like, all of my life is online versus putting roots down in our local community is sometimes a tricky thing to find that balance. Yeah, exactly. Yeah.

I think a way that we find community in tech, but also is in person, is conferences. That's where I've been seeing a lot of value in conferences post-pandemic, is not just all the things that we learn, but getting really excited about what the community is doing and connecting with other people. And you just recently got back from our pretty big conference. Yeah, it was Railsroads. This was in Toronto, if I remember correctly. That is right. Yeah, in Canada. How was that experience for you? It was really, really good.

It was also my first time in Toronto, so that was also exciting. I used to live in Sao Paulo, so it's just like Sao Paulo, but with less people, of course. But it was really, really good. The venue was different. So to compare, at least in the Ruby and RailsConf editions that I have been to, it's usually those huge convention centers, you have those rooms, and then you have one large room for the keynotes. But at this venue, it was a little bit different. The venue looked smaller.

Although there were lots and lots of people, but I think it made it easier to bump into folks and just naturally start a conversation. So I met again lots of folks from the Oversource community. I met Matt for the first time. I got just a little bit emotional because I remember when I was learning about Ruby in Brazil lots of years ago, and I never imagined that I would be in the same room as Matt and other folks that I admire. And besides all of that, which is my favorite part of the conferences, meeting folks, catching up, I really liked the keynotes a lot.

I think what's coming up in Rails 8 is definitely exciting. So yeah, it was definitely an opportunity to get really excited about being a Rails developer. I think that in general, and that's my feeling, not sure if you have also had that experience, but I noticed that Rails was kind of... not celebrated that much anymore. So I do feel that Rails is coming back to life and the Rails Foundation is doing a bunch of interesting things to bring that revival back. So you can definitely feel that when you go to the conference. So kind of that new sense of enthusiasm, despite Rails being very kind of mainstream technology now, like, oh, there are a lot of cool things that are happening and people are trying new things and pushing the boundaries of what's possible.

Yes, exactly. That's a perfect summary. And also just feeling good about saying, yes, I do use Rails. This and other hundreds of companies are making lots of money with Rails. So I think that was a good feeling. And yeah, I'm really excited. I think it's also a unique opportunity to learn about what's coming up next from folks who are working directly on these things. So Rafael Franza, Eileen, Tenderlove, and many others. Were there any particular projects that got showcased there that inspired you? Like, here's a cool thing that people are doing with Rails on their project.

Or maybe here's a fun open source project that I've made that adds this fun new feature to the framework. I think that in general, the announcement about what's coming up in Rails 8, just how different some things will be, that got me a little bit excited. I do want to just spin up on your Rails 8 app and just see how much different it is since the last time I ran Rails new. One thing that I really liked was learning about Active Search. I think that's the name, but I think it's still in beta. I would need to try it out, but it's supposed to replace Elastic Search in some situations.

So I think that was really interesting because all of those situations where I have had to use Elasticsearch, they were a bit not so great. So I would love to only use it if it is extremely necessary. I think that the changes in ActiveJob are also quite interesting. I think they are getting really up to speed with the most popular background job processor that we have, which is Cypik. So I think this is exciting. The other thing was that Rails is going to ship with built-in authentication.

I don't think it has lots of features around that yet, but depending on the case, it might be enough. But that sounds also interesting because, yeah, every app needs authentication. Not every app, but most of them. Definitely most apps that I've worked on have needed some kind of authentication. I assume all the talks were recorded, which means that probably in a month or so, the videos will come out online. Any recommendations for what the first video I should watch should be? Maybe a favorite talk that you attended. Oh, so that answer is also for me.

Because on the day that it was Eileen's keynote about how it's going in terms of using Rails as a monolith instead of microservices, I was in Toronto for the first time and I got so excited that I saw lots of folks using the bike lanes that I got a bike to go to the conference and I got lost. So I arrived at the end of Eileen's talk. But from what I talked with folks afterwards, I think that was the most interesting one in terms of the points that Eileen brought. And I'm also really, really looking forward to seeing that recording. There was one that I really enjoyed because it was so different, which makes me think that shouldn't be the case. But there was Bruno Pietro.

who was talking about accessibility in Rails applications and why it's important to use HTML to follow HTML semantics and think about folks who need accessibility support when using the applications that we build. Because I have seen lots of talks about accessibility, but this was the first time that I saw a talk being given by someone who has an accessibility need. So I found that talk really touching, and I think it was a great way to remind ourselves how we build features for everyone. Having that accessibility in mind is something important as our work as developers. Yeah, I think it's a constantly relevant topic and requires some knowledge of accessibility as a topic in general, but also just generally a good understanding of the primitives of the web as a platform that, in my opinion, every developer should get very familiar with. We should all learn some semantic HTML. We should know a little bit of HTTP and these other building blocks of the web so that we can use them. And if we use them in their sort of default way, instead of reinventing things all the time, then we get a lot of accessibility wins for free.

Yeah, exactly. That was one of the points that Bruno was bringing up. It sounds like it's a whole new thing to learn and it's really, really complex. But if you, like you said, follow HTML semantics, just get familiar with some foundational concepts, you will go a long way. And the lesson that I got was if you follow the conventions and the patterns, you are already getting accessible by default. It's only when we try to, not only, but mainly when we try to do clever things or get off the path that we will build.

apps that are not accessible. And I think really fits well with the Rails philosophy of convention over configuration and following defaults. So just like in Rails, we always pluralize our database tables in HTML. If we use links instead of trying to reinvent them using clickable divs, we get some accessibility benefits for free. Yeah, exactly. Yeah, that was one of the examples when you're using Link2 for a delete button, for example. The person who's using the screen reader, they might need to click on that button to know what it does.

But it's a delete button. You probably don't want them to click without knowing what it is. Something else that you mentioned about the convention over configuration is I really liked Rafael Francis' talk because he was talking about, for example, oh, it's great to get up to speed with Ruby and Rails if you're using Mac. Even Ubuntu. Linux is also fine. I have my Ubuntu for my personal use. But if you are out of this setup, you're going to have a hard time installing, setting up Ruby and Rails. And that really touched.

on a recent experience that we had where my colleague Justine and I were training a group of C Sharp developers to get up to speed with Rails. And that was one of the main pain points during the process because most of the folks really wanted to use Windows and command line is not that heavily used as we do. And so what Raphael was also talking about in his talk really brings more light into setting up Rails, setting up Ruby and making that experience better for everyone. So I think that was also another talk that I would recommend watching. Is this setting it up to work on Windows proper or with the Windows subsystem for Linux? I don't even think Rafael got that far as trying to set up in Windows. I think it was mostly, oh, you have this Rails app and someone is joining the code base. They will probably spend at least half a day or depending, one entire day to set up the application. So it wasn't even focusing on Windows itself. I think it was even on Linux or Mac, depending.

on where people are coming from and landing on this Rails code base, how painful it's probably going to be to set up the applications. And I think we probably feel that more than most because as consultants, we move to a new project with relative frequency. And so we're constantly setting up new Rails apps. Yeah, exactly. But what is also nice about it is that sometimes you start seeing the same error. So you kind of already remember something. Oh, wait a second. I remember doing that sometime. Or for example, when I update a dependency or something and I start seeing a C.

compilation error. I know by now that it's probably Noko Geary. Always Noko Geary. Yeah. Or I probably just need to give a bundle update on a game that has nothing to do with what I'm trying to resolve. That's troubleshooting that you have to learn the hard way just having done it a lot of times and you're like, oh yeah, no, I know this Noko Geary error or I know this Postgres error. If I'm on a Mac, do I need to update the Xcode developer tools? Oh yeah, that is always true. Or has the path to my C compiler changed?

Exactly. So I know one of the things you were excited for at Rails World was a lot of the open source related things. And you were pretty heavily involved in open source. Yeah, I think I am. Thank you for saying that. It's hard sometimes to know that when you're too in the deeps. But I do like a lot about lots of stuff at open source. And part of it is having that connection to folks that you wouldn't have because you're not working in the same team or the other company as they are. Do you maintain Faker?

which is a pretty popular Ruby gem for generating fake data. Yeah, Faker Ruby has been my first, how can I say, more maintainer. experience-like project. And it's been a really nice experience. I've been learning a lot. More recently, we want to do some changes in Faker Ruby. I finally finished reading Jeremy Evans' polished Ruby programming book, and I really liked some ideas that he brings about. For example, oh, when you're designing a library, it might not make sense for all users to load some features if they are not going to use all of those features and consider extracting some features to plugins.

I'm not yet entirely sure that's going to be the direction that we're going to go with Faker. But it has given me some ideas because Faker is great. It has lots of things. It has so much that sometimes it's hard to find things. So that's one of the things that I want to improve on Faker. But simply because I have been helping out with Faker. Since then, I have won a ticket to go to RubyGolf. I have also had the opportunity to meet Ben Curtis, who is one of the co-founders of Honey Badger. He was the original creator of Faker Rube. And it's always...

Great to meet him at conferences and talk about how the library is going. So yeah, that's been a really nice journey. And in addition to working on Faker yourself, you're also pretty involved within ThoughtBot's open source. Yeah, that was something that actually brought me to ThoughtBot because I knew how open source was part of the culture. We have lots of kind of famous libraries, so FactoryBot, Administrate, Appraisals, Climate Control. We have so many, it's hard to tell them more. But more recently, we're also having more JavaScript-related libraries, which has been really interesting. And ever since I joined...

I was starting to feel that there was something missing, that I knew some folks that were maintainers of this library or this other library, and that, for example, Shand Oil would contribute a lot to Rails. But I felt like it was missing something in terms of, oh, we don't know what everyone is working on. We have maintainers, but we are probably doing the same thing on all of those different libraries because they are all in the Ruby system. Not all of them, but they are in the Ruby ecosystem. They almost always have the same issues. And so earlier in this year,

I did a coaching, how can I say? It was a group of coaching series with my friend, Caroline Salibi. And I said, I really want you to bring open source back to the map. I don't know how to do that yet, but I have some ideas. And yeah, that's how we got started experimenting with some internal initiatives. So the most recurring one, I think, is the monthly maintainer sync, where we have this time and the space for the maintainers to catch up, share about any issues that they are having.

ask for help on any specific needs, and also brainstorm other high-level decisions for our open source strategy in general. The other initiative was we created this public doc. It's on our website, www.botbot.com slash open-source. We have this public Google doc where, after every maintainer sync, we grab the issues that the maintainers need help with, and folks can take a look at this document, grab an issue, and help out. Because I think...

when the biggest barrier for people to contributing to open source is not knowing what to do. And the biggest barrier for maintainers is I have a lot in my mind. I just don't have the time to do that project management work. And so I thought, what if we just grab a few issues that would really help out and just say, hey, if you have the time, if you use this gem, can you try fixing this and helping out? I think it's been working well. I've heard from some maintainers that they have started getting more contributions because of the public doc.

Yeah. And another thing that came out from the monthly sync is that we are going to have our first ever open source summit, which I'm really excited about. What is an open source summit like? What is the idea here? Yeah. So before we go there, I think you'll notice how excited I get about open source.

Yeah, so we had this idea a few months ago. It was mainly Sarah, Sarah Jackson. We had this idea of doing something during October because October has been now three months for contributing to open source due to Hacktoberfest. We wanted to do something about that. It was just from us, like that we were organizing and we were bringing people together. So the idea is we are going to have four project tracks with maintainers and volunteers from TalkBot where people will join those tracks and they will set up the project. The maintainer and the volunteer of the track will

help people set up the project. We go over some issues, some architecture concepts of the library, and then they will collaborate on issues with the community who's going to participate in the track. We are going to have tracks from Ruby to JavaScript. So administrate, factory bot, belt. And there is another one that we are still in the finalizing details. So that's the idea is we are going to be there to collaborate, to work together on open source, folks who will.

participate, we also have the opportunity of asking any questions directly to maintainers. And hopefully the goal is folks who participate keep coming back to contribute. So they already have that context, which is the hardest part when getting started with open source. And then by having that solved, we hope to keep seeing them coming back to contribute, help with other high level work for the library as well. And also, it's also important to know we do like to do.

events and educational materials and events like this to share with the community. So I think it's going to be really great. The registration is open. It's at thoughtbot.com slash events slash open dash summit. Registration is open and we would love to have everyone there. We'll include a link in the show notes. And it sounds like this is a synchronous event. It's not like Hacktoberfest where you just, on your own time, submit a PR to a repo. There's going to be a presentation sort of explaining the project and you show up and you do that and then...

maybe you're pair programming or connected with somebody where you might work together on a prioritized list of issues? Yeah, that's a good point. Thank you. It's going to be one day. It's going to be on October 25th. So it's going to be the last Friday of October and it's going to be a sync event. It's going to be virtual, but it's going to happen throughout all the day. I think it's going to get started at 9.30 a.m. UTC and it goes until 9 p.m. UTC. So the goal is to make it really accessible. Folks can join from any time zone that they are in and join the track that...

sounds more exciting to them. And then they will have this opportunity to be in the same virtual room as the maintainers and collaborate, ask questions and help out with the project. What is the time commitment for this? Do I have to be there for the whole time? Can I jump in and out throughout the day? What is that like? Yeah, so depending on your time zone, you have just maybe eight, six hours, I think. There's no time commitment expectations from anyone. Of course, the more that people will participate, that will be better. But there's no expectation of any sort. We will have breaks throughout the day.

and Q&A sessions as well. So it's going to be a full day of coding, but it's also going to have some breaks and people can leave and come back at any time. So you mentioned when you were at RailsConf, it was exciting to meet some of your heroes and people that inspired you. But as a prominent member of the Ruby community, as a maintainer of an open source project, I'm sure that you are an inspiration to a lot of people out there. If people join the open source summit, will they get a chance to meet you or pair with you on a project? Oh, thank you for saying that. So I will be giving one talk. At the end of the day, that will be the wrap-up talk.

I haven't decided yet. I have some ideas, but it's going to be a 30-minute talk. I will be there throughout the event, but I won't be leading any of the tracks. I will just be there to help facilitate and help out with any last-minute need for the event. So yeah, anyone who's going to participate, make sure to say hi. I think we'll also have a Slack channel or Discord channel. I'm not sure about that, but we will have a place for everyone to come together and have that connection medium, let's say. And just as a reminder, this is Friday, October 25th, 2024.

Yes, exactly. It's our first ever. The goal is to have it running annually. And I think the more we do it, the easier it gets. Yeah, but it's going to be special because it's going to be our first one. I love the energy that you bring to open source, both more broadly in the community, but also internally at ThoughtBot. And I think that this is a fun way to bridge that where people get to be involved and maybe contribute to a project for the first time. Maybe they're longtime open source contributors and they're just excited to do this in a more group setting. But I think this should be great for a pretty broad variety of levels. Yeah, I think we hope that.

Also, sometimes I go watch some talks or I go look at some projects where I have no idea how it works. It's really different. It's a different domain. But I like to look at things and be in the same spot to kind of try to absorb things by osmosis and just be around people who are doing things. So even, let's say, if someone is going to feel like, oh, I don't really follow this. I haven't used this. I don't know what it does. I do think there's also some benefit of just being around folks and seeing how do they talk? How do they think? How do they communicate?

I think that is also some value in that as well. So you're saying that it's totally fine to sign up just as a lurker. I want to see the presentation. I want to be on a call where people are working on open source and maybe I'll contribute. Maybe I'll just watch. And that can be a great way to grow with relatively low commitment on my part. Yeah, yeah. I think there is value in lurking.

So yeah, everyone listening, you don't have to go and talk to anyone if you don't need to. So you can just go and hang out and maybe get some ideas, maybe just say things differently. That's also really valuable. Yeah, so if you're looking to dip your toe in open source or just get involved in these projects with other people, October 25th, and there's a link in the show notes on how to sign up for this. Yeah, we will love to see everyone there. We're really, really excited about it. And I want to give a huge shout out to Sarah Jackson, who's helping out with...

most of the work in making this work. And yeah, I am always admired by how Sarah is great at organizing events. On that note, let's wrap up. Show notes for this episode can be found at bikeshed.thoughtbot.com. If you enjoyed listening, one really easy way to support the show is to leave us a quick rating or even a review in iTunes. It really helps other folks find the show. If you have any feedback or questions, you can reach us at hosts at bikeshed.fm via email. Thank you so much for listening to the Bike Shed and we'll see you next week. Bye!

Frequently asked questions

How long is this episode of The Bike Shed?

This episode is 32 minutes long.

When was this The Bike Shed episode published?

This episode was published on October 8, 2024.

Is there a transcript available for this episode?

Yes, a full transcript is available for this episode. You can read the complete transcript on the episode page.

Can I download this The Bike Shed episode?

Yes. Use the download control on the episode player to save the publisher-provided media file.