Podcasts about rails girls

Guest Juliana Barros Lima Panelist Richard Littauer Show Notes In this episode of Sustain, Richard Littauer talks with Juliana (Jules) Barros Lima, a full-stack developer and marketing director at Associação Python Brasil. They explore Jules' involvement in organizing and supporting Python events across Brazil, including her work with PyLadies Recife and Python Brasil. The conversation dives into the challenges of fostering diversity and inclusion in open-source communities, touching on Jules' "atomic diversity" framework for engaging local, regional, and national groups. They also discuss the impact of the pandemic on the Python community, the importance of mentorship, and the role of diverse organizing teams in creating codes of conduct that are empathetic and effective. Jules emphasizes the significance of leadership development, community collaboration, and stepping out of comfort zones to strengthen open-source communities globally. Download now to hear more! [00:01:57] Jules gives an overview of the Associação Python Brasil, what they do, and the challenges of managing a large community. [00:03:39] Jules discusses recent events organized and supported by the association and mentions that Python Brasil 2024 will be held in Rio de Janeiro and expected to have at least 300-500 attendees. [00:04:49] Jules discusses the importance of recognizing different regions' unique cultural and economic situations within Brazil. [00:06:31] We learn about the importance of subgroups and identity-based communities like PyLadies, and Jules shares insights from a talk given at PyCon US about amplifying diversity within Python communities and introduces the concept of “atomic diversity.” [00:11:43] Jules highlights how the pandemic impacted Brazil's Python community and discusses efforts to rebuild the community through open source tools and events. [00:14:07] Richard asks about how Brazil's Python community fits within the larger global context and how Brazilian developers can bridge these gaps. Jules mentions that the community is still recovering and growing, the challenges with language barriers, and emphasizes the significance of maintaining open discussions and using GitHub. [00:17:12] Richard and Jules discuss the importance of having diverse organizing teams and codes of conduct (COCs). [00:23:03] Jules offers insights into the organizational challenges faced in building inclusive events and communities. One key takeaway is the importance of engaging and listening to minority groups, such as PyLadies and Rails Girls, and the need for mentorship to help build leadership within underrepresented communities. [00:26:52] Jules stresses that community work is about giving back to the people and organizations that helped individuals grow. [00:31:32] Jules shares strategies to foster new leadership by giving people manageable tasks and responsibilities to build confidence, engaging the community through social media, storytelling, and the need for cross-community collaboration. [00:36:00] Find out where you can follow Jules online. Spotlight [00:36:39] Richard's spotlight is ‘cat' Command. [00:37:08] Jules's spotlight is the project, Querido Diário (Dear Diary). Links SustainOSS (https://sustainoss.org/) podcast@sustainoss.org (mailto:podcast@sustainoss.org) richard@sustainoss.org (mailto:richard@sustainoss.org) SustainOSS Discourse (https://discourse.sustainoss.org/) SustainOSS Mastodon (https://mastodon.social/tags/sustainoss) Open Collective-SustainOSS (Contribute) (https://opencollective.com/sustainoss) Richard Littauer Socials (https://www.burntfen.com/2023-05-30/socials) Juliana (Jules) Barros Lima Website (https://bento.me/julesbrlm) Python Brasil 2024 (https://2024.pythonbrasil.org.br/) Associação Python Brasil (https://apyb.python.org.br/index.html) APyB (Python Brasil Association) (https://apyb.python.org.br/) APyB Tarefas (Tasks) (https://github.com/apyb/tarefas) APyB Comunidade (Discussions) (https://github.com/apyb/comunidade/discussions) PyLadies Recife (https://recife.pyladies.com/) PyLadies (https://pyladies.com/) Rails Girls (https://railsgirls.com/) Querido Diário (https://docs.queridodiario.ok.org.br/pt-br/latest/) Credits Produced by Richard Littauer (https://www.burntfen.com/) Edited by Paul M. Bahr at Peachtree Sound (https://www.peachtreesound.com/) Show notes by DeAnn Bahr Peachtree Sound (https://www.peachtreesound.com/) Special Guest: Juliana Barros Lima.

Over the last year, the Rails Foundation has been hard at work on several initiatives. After a successful Rails World last year, they've been working on the program for this year's Rails World in Toronto. The Rails Foundation has also been working on several other initiatives that are very important to our community. Amanda Perino, Executive Director of The Rails Foundation joins the show to talk about the Foundation's work on the Rails Guides, Rails Girls Brazil, Tropical.rb, tutorials, working with Rails Core, and Rails World Show Notes Rails Foundation Website - https://rubyonrails.org/foundation Rails Guides - https://edgeguides.rubyonrails.org/ Rails Girls - https://railsgirls.com/ Rails World - https://rubyonrails.org/world/2024 Ridhwana Khan - https://github.com/Ridhwana Bhumi Shah - https://github.com/bhumi1102 Petrik de Heus (Rails Issues team) - https://github.com/p8 Carlos Antonio da Silva (Rails Core) - https://github.com/carlosantoniodasilva Blog: https://rubyonrails.org/2024/2/6/documentation-update-work-has-begun John Athayde - https://meticulous.com/ Blog: https://rubyonrails.org/2024/3/20/rails-guides-get-a-facelift Rails Girls São Paulo - https://railsgirls.com.br/ Debora Fernandes - https://www.linkedin.com/in/debborafernandess/ Camila Campos - https://www.linkedin.com/in/camposmilaa/ Tropical.rb - https://www.tropicalrb.com/en/ Cirdes Henrique - https://www.linkedin.com/in/cirdesh/ Doximity - https://www.doximity.com/ Bruno Miranda - https://www.linkedin.com/in/brunomiranda/ Blog: https://rubyonrails.org/2024/2/27/rails-foundation-doximity-sponsor-rails-girls-sao-paolo Planet Argon - https://www.planetargon.com/ Robby Russell - https://www.linkedin.com/in/robbyrussell/ Campus Code - https://www.campuscode.com.br/ Joāo Almeida - https://www.linkedin.com/in/joaorsalmeida/ Sponsors Honeybadger (https://www.honeybadger.io/) As an Engineering Manager or an engineer, too much of your time gets sucked up with downtime issues, troubleshooting, and error tracking. How can you spend more time shipping code and less time putting out fires? Honeybadger is how. It's a suite of monitoring tools specifically for devs. Get started today in as little as 5 minutes at Honeybadger.io (https://www.honeybadger.io/) with plans starting at free! Blue Ridge Ruby (https://blueridgeruby.com/) Are you ready to break away from your routine and immerse yourself in the vibrant world of Ruby? Join us at Blue Ridge Ruby, a friendly regional conference nestled in the picturesque mountains of western North Carolina, happening on May 30th and 31st, 2024, in the heart of downtown Asheville. Blue Ridge Ruby isn't just another tech conference; It's a gathering of passionate Ruby developers and community members. Join us at a cozy venue for a single track conference with an intimate atmosphere and connect with Rubyists of all levels to share ideas. Explore downtown Asheville during the open lunch break, sampling its eclectic food scene and cozy cafes and during the post conference weekend to see our vibrant city. Visit BlueRidgeRuby.com for registration and speaker information and secure your spot today!

In dieser Episode treffen wir auf Laura - Laura ist nicht nur Informatikerin, sondern auch Sozialwissenschaftlerin. Sie hat die "Rails Girls" mitorganisiert und sich gegen die freie Wirtschaft und für die Wissenschaft entschieden. Sie promoviert zu Nachrichtenempfehlungssystemen und findet, dass der Weg in die Forschung genau das Richtige ist für Menschen, die neugierig sind und gerne Neues herausfinden wollen. Bleibt auf jeden Fall bis zum Schluss dran, denn am Ende der Folge gibt es ein tolles Extra, in dem Laura ausführlich erklärt, zu welchem spannenden Thema sie promoviert.  Und natürlich sind wir auch wieder mit einer neuen Frage am Start, die Sara und Eli schonungslos ehrlich und offen beantworten - heute wird es richtig kitschig! Shownotes: https://bloodyhealth.gitlab.io/

In this episode, the focus is on RubyConf, the upcoming conference dedicated to the Ruby programming language. They start by talking about the origin and evolution of RubyConf, highlighting its growth in attendance and its impact on the Ruby community. Chelsea details how the conference has adapted to the digital format due to the COVID-19 pandemic but points out the value of in-person connections. They are looking forward to the Community Day event, which will feature various activities to encourage community interaction and an acknowledgment of scholarships that would help more people attend. The event will offer various programming options, workshops, and talks to cater to newcomers and seasoned professionals. There will also be some level of hands-on learning through hacking activities. The conference aims to be inclusive, offering opportunities for mentorship and growth, regardless of one's career stage. Towards the end, the discussion shifts to Ruby Central, the organizing body behind RubyConf and RailsConf. Chelsea and Allison describe multiple avenues for community engagement, ranging from board membership to open-source contributions. They also encourage donations and corporate sponsorships. Don't miss your chance to register for RubyConf and engage with the fantastic Ruby community! RubyConf (https://rubyconf.org/) Follow RubyConf on LinkedIn (https://www.linkedin.com/company/ruby-central-inc/), X (https://twitter.com/rubyconf), YouTube (), or Mastodon (https://ruby.social/@rubyconf). Learn Academy (https://learnacademy.org/) Follow Learn Academy on Facebook (https://www.facebook.com/LEARNSD/), X (https://twitter.com/SDLEARN), LinkedIn (https://www.linkedin.com/school/sd-learn/), or Instagram (https://www.instagram.com/sdlearn/). Follow Chelsea Kaufman on LinkedIn (https://www.linkedin.com/in/chelskaufman/) or X (https://twitter.com/ChelsKaufman). Follow Allison McMillan on LinkedIn (https://www.linkedin.com/in/apmcmillan/) or X (https://twitter.com/allie_p). Visit her website at daydreamsinruby.com (https://daydreamsinruby.com/). Follow thoughtbot on X (https://twitter.com/thoughtbot) or LinkedIn (https://www.linkedin.com/company/150727/). Become a Sponsor (https://thoughtbot.com/sponsorship) of Giant Robots! Transcript: VICTORIA: This is the Giant Robots Smashing Into Other Giant Robots podcast, where we explore the design, development, and business of great products. I'm your host, Victoria Guido. And with me today is Allison McMillan and Chelsea Kaufman, Board Directors, and RubyConf '23 Co-chairs. Thank you for joining me. ALLISON: Hi, thanks for having us. CHELSEA: Thanks for having us. VICTORIA: Yes, I'm glad that you were able to make time to come on the show today. I understand, Allison, that you've been having very full weeks with family over the last month. Do you want to tell us a little bit more about that? ALLISON: Yeah, it's...we have just ended what I call the gauntlet of Jewish holidays. But, basically, there are four Jewish holidays starting with Rosh Hashanah, which many folks know that's the Jewish New Year. But what a lot of folks don't know is that there are actually four holidays that are all in a row, each about a week apart. And you do different celebratory things for each of them. And so, it's been really amazing and fun, and lots of, like, sharing our home with others and meals and seeing lots of people. But it is also exhausting. And they basically all fell on weekends this year, which was nice from sort of a scheduling perspective but was exhausting in the fact that I basically have not had a weekend in over a month. So, it was wonderful and tiring. And I am, I guess, both happy and sad that they're over now. VICTORIA: Yeah, that does sound like a lot of quality family time, which has its pros and cons [laughs], right? So, after going through that, do you feel more rested? Or what do you feel like you need to do in order to recuperate and return to your normal energy levels after having every weekend full after that? ALLISON: Oh, that's a great question. I've been looking at my calendar to be like, I should take a day off. I should take a break. I'm working for myself and [inaudible 02:02] entrepreneur consultant. So, I do have the flexibility to do so, but it is hard to look at my calendar and be like, yes, I will take this day off because I deserve it. But, ideally, I would take a day or multiple days off. VICTORIA: Yes. And some of us are lucky enough to have a reason to travel for work purposes and to sneak in a little vacation and be productive [laughs] in our companies. So, I'm curious, Chelsea, if you can tell me a little bit about the option for people to come to San Diego in November and take a restful vacation by the beach and learn a little bit more about Ruby. CHELSEA: Yeah, so RubyConf will be in San Diego this year. As a native San-dieagan, I am a bit biased, but November is a beautiful time to be in San Diego. And we're going to be at the Town and Country, which feels a little bit like we're going to be in a, like, Palm Springs resort. They just went through a major renovation. And there's these really awesome, like, lounge areas with fire pits and just places for people to gather, which really kind of aligns itself with some of the stuff that we're planning because we're really trying to focus in on just connecting Rubyists together. So, to me, it feels like the perfect place because I think San Diego is, one, we're a little bit more low key, a little chill. And it's a great place to just gather and connect and share with people that have, you know, similar interests. VICTORIA: Yes, I live in San Diego now, but I was from Washington, D.C., And I would come and visit my family in San Diego once a year. And they would always go on about how great it is and how beautiful, and everyone is so happy and chill. And I was like, sure, whatever. And then we [chuckles] had the opportunity to move here, and now I'm one of those people who says that [laughs]. Like, it's great, especially in November. Everywhere else is getting a little cold and fall. And San Diego has a little bit of fall, but it's still 75 degrees out. I forget what that is in Celsius. But yes, I'm also super excited. CHELSEA: We have, like, fake fall activities that you can go do. Like, Allison, when you're talking about doing all the family activities and things like that, you know, this is when we start thinking about, oh, we need to go to, like, the pumpkin patch and apple picking and do all these things, but it's not cold or, like, fall weather at all. So, you want to get all, like, bundled up in your cute fall clothes or, like, put my kids and bundle them up in cute things. But then they're, like, sweating and trying to do [laughs] all these funny activities. But I think that there's so many beautiful things to do here that we, like, try and do these, like, fall activities. But then we just end up at the beach and play in the sand [laughs]. VICTORIA: Yeah, I will go out in, like, shorts and a T-shirt because it's that kind of weather. And my neighbors will be wearing full puffy jackets and [laughs], like, long pants and a hat. And they're like, "You're not from around here, are you?" [laughs]. It's like, you guys are silly. But it's fun. Yeah, there's seasons, I think, you know, in November...I made a list of suggested activities for my team members since thoughtbot is sponsoring RubyConf this year. And we're going to have a couple of speakers at the event. And we'll have other thoughtboters available at our booth for people to come up and chat with us. So, I'm really thrilled to be hosting everyone. And I made a list of, like, activities, and most of them were about where to see cool animals [laughs]. I was like, of course, there's the zoo, which is the obvious one, but then there's baby leopard sharks, and there's a season for them. I think they will still be around in November; I'm curious if you know, Chelsea, actually. And then there's, like, the safari parks, and whale watching, and the sea lions at La Jolla and, like, just a bunch of cool animals to see that I think it makes San Diego really special. CHELSEA: I agree. The zoo, the safari park are great places to just hang out and see some really cool exhibits. Balboa Park, the museums there are amazing. Liberty Station is one of my favorite places to go; that it's an old historic naval training center that's been converted into an arts and culture area. So, they have, like, little shops. They have...there's museums. There's brew pubs. There's coffee shops. And then there's beautiful, like, grassy areas, and right by the water, it's one of my favorite places to just go and hang out. ALLISON: This is great. I've done zero research on San Diego so far. So, just, like, I'm writing notes of what things to do and see while I'm there. CHELSEA: Yeah, I know the San Diego Ruby group is trying to put together some, like, local events and things that people can gather and do together. I know that there was a talk about doing a taco crawl. I think if I say that on the podcast, it might actually push them to do it because there are some amazing tacos in San Diego to be had. VICTORIA: Yes, I love that taco crawl. I'll reach out to them because I'll help put something like that together. I'm writing a blog post right now about all of these things and about all the other kind of events that are coming up in San Diego this fall. Great location, great time of year to be here. Tell me a little bit more about RubyConf specifically. And what are you all trying to do different this year than in past events? ALLISON: There are a bunch of things that we're doing differently. Our goal this year with this RubyConf is really to sort of focus on more ways to bring the community together. I think in the last little bit so much excitement around Ruby and Ruby Central and just sort of the community in general. It's a hard time in tech. I think people need to be sort of choosier about sort of what they attend and why they're attending something. And so, we really wanted to help folks connect with each other, help folks get to know other people, help folks sort of reconnect to ways that they love Ruby and the Ruby community and being a Ruby programmer. So, one of the things that we're doing differently is we have a three-day conference. And the way that that sort of broken down is the first day is a Community Day. And the first day is comprised of the workshops, as well as sort of this Hack Day, where people can bring their own projects. We're going to have people there that folks can hack with, sort of open-source projects that folks can work on, all sorts of different stuff. So that people can really sort of get to know one another, work with one another, work with people that they might, you know, admire or have followed in the community for a while, and have that sort of really special experience that doesn't feel as conference-y, right? It feels a little bit more sort of organic in terms of the way that the day will flow and, the options that people have, and sort of what that day looks like. And then following that, we have two days of sort of RubConf with talks and speakers, et cetera. And I'll let Chelsea add anything to Community Day and then also jump into some of the sort of new and different things we're doing at RubyConf. CHELSEA: I agree with Allison in that we've really wanted to focus in on the connection side of things. But I think coming out of the last few years, out of even the last year that's been tough in the industry, just finding ways for people to connect, support, lift up each other, I think that that was something we really wanted to do. And we didn't want it to just be about going and seeing speakers. We wanted to find more ways for people to learn from each other, to connect. And so we added in quite a few of these community connection points. So, on that first day, there's a lot of community aspects to it. We have a lot of learning happening with our workshops and also working on projects, hacking together, showing off what you're working on, connecting with people in the community. It's going to be really focused in on everyone's own skills and talents and coming together and supporting each other in where we're at in our careers, in our learning. And then, the next couple of days will look a little bit familiar in the way that it is structured with some new aspects kind of woven in. We'll have our Community Room, where we're bringing different community groups together so that people can learn more about what is going on in the community, how they can support, how they can connect. And in addition to seeing and learning about some of the new things happening in the Ruby community, we'll also have our Career Pathways room again, which will be a place for people to support their own careers. And that room was really set up so that it wasn't just about early career, but also about folks in their mid and senior careers, and finding the advice, finding the resources, finding the mentorship that they might need in whatever stage of their career that they're at, and figuring out how we can together as a community grow as a whole. VICTORIA: I really appreciate the focus on community. And, for me, as managing director at thoughtbot, in deciding to invest in which conferences we want to attend and sponsor, we find more value in groups that are trying to bring people together around a common passion and purpose versus a particular product. But I'd like to hear from each of you if you can tell me, what does the community mean to you? And I'm looking for, like, a personal story on how you've benefited or how you've engaged with the Ruby community in the past. And what makes you motivated as CEOs and founders of your own companies [laughs] to spend all this time organizing a conference? ALLISON: Many, many, many years ago, I did a Rails Girls workshop. It was actually my first introduction into the tech community, into programming in general. And, for me, really, I did Rails Girls. I did not actually expect to like programming. But I was sort of launching a startup, and I wanted to learn more about tech and blah, blah, blah. And at the end of the day, I was, like, so energized and so excited about what I had built and what I had done. The Ruby community in D.C., who I always think is just a group of really special individuals, was so supportive, was so wonderful, was so, like, "Here's where we co-work on Wednesdays. Come to this coffee shop. Here's how you can keep learning," just was so encouraging. You know, I went to the local Ruby meetup sort of really not knowing anything. And they were excited about, you know, newbies being there and asking questions and, you know, really sort of getting to know folks who are just starting out in their programming journey. And really, through that, I mean, I went to my first RubyConf as a scholar. Was strongly encouraged to do a lightning talk, did a lightning talk. That's how I, you know, sort of ended up having a whole bunch of informational interviews and having conversations with folks. And really, that's how I got my first real job in tech. And so, you know, I want people that are coming into the industry now to have that same support, to have those same opportunities, to have that same encouragement. And, for me, sort of planning RubyConf, planning these conferences, being a part of Ruby Central is really me giving back to the community that has gotten me to where I am today, right? And it's amazing, also, to just...I'm still in touch with the people that were at my table, sort of guiding and mentoring at that first Rails Girls session or the people who I met at the first-ever Ruby meetup that I went to. I still talk to them. I'm still in touch with them. We still get together. I still ask them for, you know, advice and guidance sometimes. And sometimes, they ask me, at this point, for advice and guidance, which is fun. But yeah, it just means so much to me that I have really been able to get to where I'm at because of the support and encouragement of the community. CHELSEA: I have a similar story. I guess over, gosh, over a decade ago, I also went to my first RailsBridge and got introduced to the community there at RailsBridge. And, you know, at the time, I wasn't in tech. I was in the theater. I come from the performing arts. I had spent a very long time executive leadership in the theater. And I got introduced to this community that was so warm and welcoming to people wanting to learn and grow. And I was so interested in how communities are built and how people connect together that I started getting more and more involved in the Ruby community here in San Diego. And just like Allison was saying about the welcoming and warmth that she felt from the D.C. community, I felt the same way here in San Diego. Before that, you know, I had spent so many years being the only woman in a room. I had been in an industry that made me feel like my voice was not always heard. And when I walked into this room, I felt like I mattered. I felt like people wanted to hear what I had to say. And they wanted to learn from my experiences. And in 2014, San Diego hosted RubyConf here. And at that point, my business partner and I launched our business, LEARN Academy, and it's still running strong today. But it was about creating that on-ramp for people and a launchpad into this industry where they could make a difference and they could have their voice heard. And they could be a part of a conversation, even if they hadn't been a part of that community for many, many years, that their background mattered, that their growth mattered. And helping people find their voice at a table is something that is so important to me that I love being able to bring that into the planning of this conference, into a lot of the work that I've done with Ruby Central, with LEARN academy. And really just helping people understand that just because you don't have the traditional background, maybe you didn't start programming at the age of two, you can have a different background and a different path and still provide so much value. And I think that that is the thing that I wanted to continue to be a part of and to make sure was a part of the conversation, that we need so many different types of people at the table. And I want to make sure that our community is responsive to that, that it's inclusive to that, that it's equitable as best we can, and just allows people to share their own experiences. And so, you know, I feel like, for me, we're, you know, almost at our 10-year mark at LEARN academy and that we were launching the company at RubyConf in 2014. To have it here again this year is so special to me. I remember being at the conference many years ago; you know, we spend a lot of time helping companies figure out how to work with early-career developers and to create those pipelines for them so that there's career growth for them. And, you know, I remember sitting around the table and just saying, "Hey, who wants an internship? Who wants to, you know, help these early-career developers?" And everyone raised their hand, and we found some of our very first partners at that conference. And it's always been such a warm and welcoming community that has allowed me to feel like I have a voice and then allows me to help other people find theirs. VICTORIA: Wow, thank you both for sharing that. I totally relate to that feeling of a welcoming community and just getting the sense that, like, wow, everyone who does Ruby is really nice [laughs]. And I think that you know, for me, same as Allison, starting in D.C., there were quite a few people who were involved in Women Who Code who were running Ruby meetups. And that's where I met Valerie Woolard, who I think is also coming to San Diego for RubyConf. I'm excited to see her again. And it's interesting for me coming from that perspective and hearing that from both of you because I've also heard a viewpoint on Ruby community as being highly opinionated and causing certain amounts of consternation. So, I'm curious if you have any comments on that. If not, otherwise, I'm grateful that there are people working to bring that better community in the community that I'm more familiar with more to the forefront and making it more inclusive and open for everyone. So, to, like, bring the question all the way back, it's like [chuckles], do you have any comments on, like, if there's a tendency for Rubyists to be really highly opinionated? Or what else can we do to make it more open and inclusive for people to join the community? CHELSEA: I mean, I think that people are going to be opinionated about something that they care a lot about. And I think that the thing that I've noticed in the Ruby community is people love this language. They love programming in this language, and I think that there's something very powerful about that. And it does, you know, lend itself to people [laughs] having very strong opinions about what they think needs to be out there. And, to me, it's not a matter of, like, whether we have strong opinions or not. It has more to do with whether we're listening or not. But I think it's really important for those of us who are leading to be the listeners, and that we should be there to make sure that there is space for people to be heard, whether their opinion is loud or not. And I think that there are people that are going to be louder than others; that is going to be true no matter where we go. But I think that as long as there is intention around making sure that we are listening to even the quietest voices and that we are creating space for the quietest voices, that's where we're going to find more collaboration. But if we're only going out there and saying, "This is the way it needs to be," and we're not willing to listen to anything else, then I think that growth will stop happening because we need to listen to everyone. We need to be able to create some kind of place for people to come together and share ideas; you know, you don't get the perspectives of all these amazing people in the industry. So, that's why I feel like, you know, I've been on the board at Ruby Central for about a year now, and the biggest thing that I feel like I can contribute is to simply listen. If I can help in any way of filtering ideas or creating connections with people because I've been putting my ear to the ground and saying, "Okay, these people are talking about this, and we're expanding here." And we just want to make sure that we're doing the best we can at being open to all different kinds of ideas and not closing anyone off. Maybe your opinion is really strong. It doesn't mean that we should shut you down. It just means that we need to make sure that there's space for other people, too. And I think that that's the part that, you know, as someone who has always been a bit of an introvert, a bit of a wallflower, I understand how hard it is to get my voice out there. And so, I often fight for the quiet people. I think in every language and any space where it's a craft, it's something that we're creating, people get really passionate about it. And that's going to happen. And I think there's something powerful in that because there's going to be change that happens from that. But if we're not doing our part in the listening and making sure that there isn't just one voice, that there's a collective voice, that's the part that I felt so powerful when I joined the community so many years ago was that, even though I had, you know, months of experience, my questions mattered. And as long as we hold on to that, the community will continue to grow. But those of us at Ruby Central and some of the other organizations, if we're creating space to allow people to question, allow people to speak their opinions and listen, then I think that the industry, the community will just continue to thrive because of that. But we have to be open, and we have to be compassionate when we're doing our listening. ALLISON: Yeah, I agree with all of that. And I would just add in safe places, in a way that we're creating sort of safe structures and safe places for folks to communicate. MID-ROLL AD: Are your engineers spending too much time on DevOps and maintenance issues when you need them on new features? We know maintaining your own servers can be costly and that it's easy for spending creep to sneak in when your team isn't looking. By delegating server management, maintenance, and security to thoughtbot and our network of service partners, you can get 24x7 support from our team of experts, all for less than the cost of one in-house engineer. Save time and money with our DevOps and Maintenance service. Find out more at: tbot.io/devops. VICTORIA: What, if you could tell me, what does Ruby really have going for it? Like what makes Ruby a good choice for tech founders or for new companies would make someone decide they want to build with Ruby? ALLISON: First, it's a little bit about just sort of the ease of the language to jump into and to understand, right? There's a lot that you can get done very quickly with Ruby and Rails. And in addition to sort of individuals being able to work in it, there's a whole community of resources, and support, and podcasts, and tutorials, and all sorts of stuff. I know that as an engineering leader at any company, when engineers are coming to me with, like, the desire to use a new language or try something new, part of what I look at is, if I'm going to hire, like, what would hiring look like? What does it look like for engineers to have to ramp up in this area? How long does that take? What resources are available? What sort of community am I pulling from and looking at? And that's both community in terms of sort of technical experience, expertise, years, et cetera, but also non-technical skills, right? What does the community look like in terms of some of those ideals around communication, collaboration, just sort of general pieces like that? And so, I think that, given sort of the strength of open source, strength of community, community contributions, ways to contribute, etcetera, I think that's one of the reasons that it still makes Ruby a really strong choice for folks to build in and to work with. VICTORIA: What type of people, what personas do you think will be the most interested in attending RubyConf? Is it all just going to be, like, senior or super Ruby developers, or what? CHELSEA: Oh, I don't think so. I mean, this RubyConf, in particular, is great for anyone on a learning journey. We've worked really hard to make sure there's a good breadth of programming for different folks in different stages of their careers. I think that, you know, those of you that are maybe earlier on there, this is a great opportunity to meet people who are maybe even a step or two ahead of you. I think that the best mentorship that you can find is someone who is only maybe a year ahead of you because they're going to recognize where you're at and help you along the way. And I think that there's a lot of opportunities here for that. I think that with our Community Day, the hacking that's going to be involved, like, maybe, as a new developer, you wouldn't be able to come in and, like, get your hands really dirty. But you'll get to sit next to somebody who has been through all the different stages and get to watch, and explore, and learn. I think that making those connections could be really great for anyone's career. I think that our mid-level developers, folks that are our management, there's great resources for them to connect with other developers in similar stages. There's great workshops. Because of our focus on the community, I think that it's going to be a place where you can really connect with other Rubyists. And so, if you are at a stage in your career that you want to figure out what that next spring is, where that next ladder step is, this is a good place to see all the different options because you're going to be surrounded by people in all different stages of their careers. And what we've, I think, said now quite a few times is so many people there are just so excited to help people continue that growth. And so, I think that no matter what stage you're in, you're going to find people there that are excited to help you along the way. That being said, I think for our more senior, more advanced, our executive leadership, this is going to be a great place to, one, meet some really great talent, and, two, I think, learn from other folks in the industry of, like, where people are at, what we're struggling with, and how we're changing and doing things differently. So, I really do think there's going to be a little bit of everything for people. And what I love about that is really that it gets to the core and heart of the Ruby community because we're so excited about new folks coming in that that growth continues, that you have folks like Allison who started out as a scholar and want to give back. And then because we have folks at all those different stages, you can find people that are, you know, maybe a step or two ahead of you that are going to be able to help bring you up to that next level. So, I think it's an exciting opportunity for people to really meet new people, learn some new things, maybe find a little bit of encouragement, empowerment on where you're going to go next on your career. VICTORIA: Yeah, absolutely. And it reminds me of an article I read while I was at RailsConf earlier this year about why we do conferences and what's the whole point. And, you know, for me, all of those things are true, like, all those values. As an executive, I'm going to meet a lot of great talent. I'm going to connect with other companies. I'm just going to get to show up and say hi to people and ask them questions in a way that's very informal. And that's so valuable to have that. I think where I was going to go next with this was with Ruby Central, which I believe organizes both RailsConf and RubyConf. (And you can correct me if I'm wrong on that.) I'm curious if there are anything else you want to talk about with, like how the community can engage in support and how other companies could get involved with the community and show their support. CHELSEA: I think that there's quite a few different ways for folks to get involved. We are currently recruiting board members. We just finished a round just now. But I know that in our planning, that we're likely going to bring on at least one, maybe two more, in the next six months. So, I definitely...for folks in the community that want to get involved, that is a really great place to really get involved with Ruby Central. We also have a really strong open-source community. And we're working, oh gosh, with quite a few different companies now that are really helping to support our open-source efforts. And those are also good ways to get involved. You know, we do plan both RailsConf and RubyConf. RailsConf will be in the spring again. And, you know, it takes a village to put on a conference like this and that, you know, we also look for programming committee members to help us shape the program of the conferences. So, if you are interested in any of that, that's also another great way to get involved in the community. We have an amazing programming committee that's helped us with RubyConf. And I'm excited to see what we do next with RailsConf. And I think that you know if you're one that's going to the conference and are saying, "Man, I wish that they would do this," or "I wish I could see that," come and talk to us because that's the best way for us to learn, that we want to hear all of those pieces. But don't be surprised if we then send you an email and say, "Hey, you want to be on our programming committee with us?" ALLISON: I'll add that we also, through our website, we take donations. So, if you want to help monetarily, there's the option to do that on the website. And if you're a company, I mean, we're always looking for conference sponsorships. But if your company also is interested in getting involved in sort of more of a corporate sense of sponsoring or supporting Ruby Central, we are always open to those conversations. You can send an email to contact@rubycentral.org. VICTORIA: That's great. I have a fun question about the conference because I'm leading the event with thoughtbot since I live here. And I'm thinking about some fun swag to give away. Rank your preferences on what kind of swag you'd like to see at the thoughtbot sponsor booth: a thoughtbot-branded surfboard or, a boogie board, a bucket hat, or a pickleball paddle. Any of those interesting for you? ALLISON: Wait, when you say surfboard, like, how am I going to get a surfboard back to D.C.? [laughter] VICTORIA: Okay. I think it's, like, kind of funny because if you win it, it's like, well, what do you do? [laughter] You got to shake it back. That sounds like maybe a boogie board. CHELSEA: Yeah, I'm down for a boogie board. VICTORIA: Thank you so [laughs] much for entertaining me on that one. Is there anything else that you would like to promote today? ALLISON: We would love to see everybody at RubyConf. You can register. Check out the program speakers, et cetera, at rubyconf.org. You can learn more about Ruby Central at rubycentral.org. Those are, I think, the two things that we'd love to make sure everybody knows about. CHELSEA: And if you're here in San Diego, come say hello. VICTORIA: Yes, I have met up with a few random people from the internet [laughs] who have said like, "I'm in San Diego. Who should I say hi [inaudible 34:02]?" I was like, "Me, me, me," [laughter]. So, yes, I'm very happy to meet up for drinks. Chelsea, you and I will have to get together sometime soon before the conference. And I'm super excited for RubyConf. And thank you both so much for being here today. ALLISON: Thanks for having us. CHELSEA: Thank you. VICTORIA: You can subscribe to the show and find notes along with a complete transcript for this episode at giantrobots.fm. If you have questions or comments, email us at hosts@giantsrobots.fm. And you can find me on Twitter @victori_ousg. This podcast is brought to you by thoughtbot and produced and edited by Mandy Moore. Thanks for listening. See you next time. AD: Did you know thoughtbot has a referral program? If you introduce us to someone looking for a design or development partner, we will compensate you if they decide to work with us. More info on our website at tbot.io/referral. Or you can email us at referrals@thoughtbot.com with any questions. Special Guests: Allison McMillan and Chelsea Kaufman.

Nadia Odunayo is the Founder and CEO of The StoryGraph, a new website and app for avid book readers because life's too short for a book you're not in the mood for. The StoryGraph helps you track your reading and choose your next book based on your mood, favorite topics, and themes. Victoria talks to Nadia about coming up with a product based on the concept of mood, what you're in the mood for to read, i.e., this book made me feel this way. How do I find a book that makes me feel similar? They also talk about keeping yourself open to feedback, the ability to flow and change direction, and developing a reviewing system that keeps biases in check. StoryGraph (https://thestorygraph.com/) Follow StoryGraph on LinkedIn (https://www.linkedin.com/company/the-storygraph-limited/), Instagram (https://www.instagram.com/the.storygraph/), or Twitter (https://twitter.com/thestorygraph). Follow Nadia Odunayo on LinkedIn (https://www.linkedin.com/in/nodunayo/) or Twitter (https://twitter.com/nodunayo). Follow thoughtbot on Twitter (https://twitter.com/thoughtbot) or LinkedIn (https://www.linkedin.com/company/150727/). Become a Sponsor (https://thoughtbot.com/sponsorship) of Giant Robots! Transcript: VICTORIA: This is The Giant Robots Smashing Into Other Giant Robots Podcast, where we explore the design, development, and business of great products. I'm your host, Victoria Guido. And with me today is Nadia Odunayo, Founder and CEO of StoryGraph, a new website and app for avid book readers because life's too short for a book you're not in the mood for. StoryGraph helps you track your reading and choose your next book based on your mood and your favorite topics and themes. Nadia, thank you for joining me. NADIA: Thank you for having me. VICTORIA: And you are a repeat guest at Giant Robots. But for those who missed that episode, tell me a little bit about your journey. And how did this all get started? NADIA: Okay. Yeah, so that first time was in 2015, and that was not too long after I had just got into tech. I did a bootcamp in London in 2014, Makers Academy, and that's where I learned to code. My degree was in philosophy, politics, and economics, so rather different. I worked at Pivotal for about a year and a half after I graduated from Makers Academy. And during my time at Pivotal, I got into conference speaking, and my first talk was around game theory. So I took my favorite topic in economics, game theory, and I combined that with distributed systems because that's what I was working on at the time in Pivotal on their Cloud Foundry PaaS. I think I gave it at RailsConf, and I think someone there recommended me to Giant Robots. And so Ben Orenstein interviewed me, and it was all about different types of conference talks and that kind of thing. So after Pivotal, I left and started a hybrid kind of consultancy/product company with a colleague, did that for about a year, left that, worked for about a year with my friend, Saron Yitbarek, on her company CodeNewbie. And then, when that partnership ended, I essentially had five years of runway from money that I got from the company that I started after Pivotal because we did some consulting with a bank. I'd always been entrepreneurial. I'd been doing various entrepreneurial things since secondary school, actually, high school. It was time for me to just have time on my side projects. And so I started hacking away on one of my side projects at the beginning of 2019 in January, and I haven't stopped since. That's what the StoryGraph has developed into. VICTORIA: Wonderful. And yes, I saw that the very early stages of StoryGraph started as a creative writing e-publication. Is that right? NADIA: So what happened was when I was at university, I started a creative writing e-publication, came up with the name The StoryGraph. Because we had won or we were going for some grant funding or something like that, I set up a corporate entity. And when I stopped working on that e-publication, I remember my mom saying to me, "Don't shut down the entity. I really like the name. I feel like you'll use it for something," that was in 2012. And so fast forward to 2019, and the side project that I was working on was called Read Lists. And it was very specifically focused on tracking and sharing progress through reading lists on a dashboard. But when I was doing customer research, and the scope of the project grew, Read Lists didn't fit anymore. And that's when I realized, oh, I can use The StoryGraph thing again. And so it's basically had two different lives or two different forms, the StoryGraph company. VICTORIA: That's wonderful. And I'm reading about StoryGraph and how it's an Amazon-free alternative to Goodreads. Can you talk a little bit more about the product and why people would want to use it? NADIA: So, as I said, it started life as a very specific focused side project. And I just had so much fun working on it and working in the book space. I'd always been a reader since I was a kid such that I said to myself, I need to find a way to make me building a books product a full-time thing. And so that's when customer research came in because the only way that you're going to make sure that you don't build something that people don't want is by talking to people. As I was doing customer research and figuring out, are there pain points amongst readers, people who track their reading? What would happen was the pain points that came up drove me towards building a more fully fledged reading, tracking, and recommendations product. It actually started as a very focused recommendations product. And then, we got to the point where we needed to build more around it for it to be a compelling product. And as it was growing, we never advertised ourselves as a Goodreads alternative or as an Amazon-free alternative to what was out there. But that was clearly a pain point in the market. There were tweets about us saying, "Finally a Goodreads alternative. It's small; it's independent; it's Amazon-free. And so thousands and thousands, hundreds of thousands of people have come to us because of that. VICTORIA: Wow. NADIA: And so it got to the point...mainly when we launched our payment plan, and we were trying to figure out the reasons why people were pre-ordering the plan, it was at that point where we decided to lean into the Amazon-free Goodreads alternative because that was what the market wanted. VICTORIA: Was that surprising for you? Or were there other things that came out of your research on your marketplace that kind of were different than what you thought it would be going in? NADIA: I think the most interesting thing about the product development journey was that I at least originally felt like I was building a product that wasn't for me. So what I mean by that is in my earliest rounds of research, what I was finding was that people still didn't think that they had one place to get consistently good book recommendations. And so then I started to explore, well, how do you even give somebody consistently good book recommendations? And one of the factors that kept on coming up was this concept of mood, what you're in the mood for. This book made me feel this way. How do I find a book that makes me feel similar? And so it got to the point where I said to myself, oh wow, I'm building a product for mood readers right now; that seems to be the gap, that seems to be the thing that nothing out there yet had properly attacked. And I had never considered myself a mood reader. I just thought I'm a planner. I'm an organized person. I typically decide what book I want to read, and then I read it. And so there was a point where I was concerned, and I thought, wait, am I now building something that is not for me? But then, as I started to work and do more research and talk to more and more people and thinking about my reading experiences, I developed the hypothesis or the viewpoint rather that I think everybody's a mood reader; it's just the scale. Because there are probably some books that I may have rated lowly in the past that if I had read it in a different frame of mind, or at a different time in my life, different circumstance, it probably would have resonated with me a lot more. Now, that's not to say that's true for every single book. There are some books that are just not going to work for you, no matter what. But I do think we're all on the scale of mood reading. And sometimes we say a book is a bad book, but we just read it at not the right time. And so I think the most surprising thing for me is going on that journey of realizing that, oh, I am a mood reader too. VICTORIA: [laughs] NADIA: And I ended up building an app that's a lot less focused on just the pure ratings. I was someone who, on Goodreads, if it had less than four stars, I'm not interested. And the ethos of the product is more about, well, hang on; these ratings are very subjective. And someone else's two, three-star could be your next five-star. What are the factors that really matter? Do you want something dark, adventurous? Are you looking for something funny, light? And then what kind of topics do you want to discover? And then it doesn't matter if the five people before you thought it was average; you might think it's excellent. VICTORIA: Yeah, it reminds me thinking about how bias can come in with authors and writing as well. So a simple five-star system might be more susceptible to bias against different genders or different types of names. Whereas if you have more complex numbers or complex rating systems, it might be easier to have different types of authors stand out in a different way. NADIA: That actually relates to what was going through my mind when I was developing the reviewing system on StoryGraph. You can just, if you want, leave your star rating and say no more, but the star rating is lower down on the page. And up front, we say this book would be great for someone who's in the mood for something...and then you've got checkboxes. And how would you rate the pace of the book? And if it's a fiction book, we ask you, "Are the characters lovable?" Is there a flawed narrator? Is it plot-driven or character-driven?" Questions like that because the thinking is it doesn't matter whether you are going to give the book two stars in your own personal star rating. You can still help someone else find a book that's good for them because they will be looking at the summary on the StoryGraph book page, and they'll go, "Oh wow, 80% of people said it's lovable. There's a diverse range of characters, and it's funny. So the topics fit things I'm interested in, so I care less about the average rating being like 3.5 because everything else seems perfect. Let me see for myself." And actually, we've also had a lot of feedback from people saying that "Oh, normally, I never know how to review a book or what to say. And this system has really helped me, almost give me prompts to get started about explaining the book, reviewing it for other people to help them decide if it's for them. So that's great." VICTORIA: That makes sense to me because I read a lot of books, maybe not as much as I would like to recently. But not all books that I love I can easily recommend to friends, but it's hard for me to say why. [laughs] You know, like, "This is a very complicated book." So I love it. I'll have to check it out later. It's been four years since you've been full-time or since 2019, almost five then. NADIA: Yes. VICTORIA: If you could travel back in time to when you first started to make this a full-time role, what advice would you give yourself now, having all of this foresight? NADIA: Have patience, trust the process because I can sometimes be impatient with, ah, I want this to happen now. I want this to pick up now. I want these features done now. I'm a solo dev on the project. I started it solo. I have a co-founder now, but I'm still the solo dev. And there were so many things, especially now that we've got a much larger user base, that people complained about or say is not quite right. And that can be really tough to just have to keep hearing when you're like, I know, but I don't have the resource to fix it right now or to improve it. But I think one of the things is, yeah, having faith in the process. Keep going through the cycles of listening to the customers, prioritizing the work, getting the work done, getting the feedback, and just keep going through that loop. And the product will keep getting better. Because sometimes it can feel, particularly in the first year when I was so low, you sometimes have moments of doubt. Or if a customer research round doesn't go super well, you start to wonder, is this only a nice-to-have? And is this going to go anywhere? And so that's one piece of advice. And I think the other one is knowing that there are several right paths because I think sometimes I would agonize over I want to do the right thing. I want to make sure I make the right choice right now. And, I mean, there are some things that are not good to do. You want to make sure that you're setting up your customer interviews in a non-leading way. You want to make sure that there are certain standards in the product in terms of the technical side and all that kind of stuff, so there's that. But I think it's understanding that you kind of just have to make a decision. And if you set yourself up to be able to be adaptive and responsive to change, then you'll be fine. Because you can always change course if the response you're getting back or the data you're getting back is going in the wrong direction. VICTORIA: I love that. And I want to pull on that thread about being open to changing your mind. I think that many founders start the company because they're so excited about this idea and this problem that they found. But how do you keep yourself open to feedback and keeping that ability to flow and to change direction? NADIA: I mean, I didn't set out to build a Goodreads alternative, and here I am. VICTORIA: [laughs] NADIA: I just wanted to build this specific side project or this specific...it was a companion app, in fact. Like, the first version of the thing I built, the first thing you had to do was sign in and connect your Goodreads account so that we could pull in your shelves and start creating the dashboards. So as a solo bootstrapping founder, building a Goodreads alternative was not something that I thought was going to lead to success. But through years of experience, and just hearing other people's stories, and research, I just learned that it's such a hard space just running a startup in general, and 90% of startups fail. And I just said to myself that, okay, the only way I can kind of survive for longer is if I am open to feedback, I'm open to change course, I'm patient, and I trust the process. These are the things I can do to just increase my chances of success. And so that's why I kind of feel it's imperative if you want to go down this route and you want to be successful, it's vital that you're open to completely changing the product, completely changing your direction, completely going back on a decision. You'll either lose customers or you'll run out of money, whatever it is. And so yeah, you've got to just basically be quite ruthless in the things that are just going to minimize your chances of failing. VICTORIA: That makes sense. And now, I have a two-part question for you. What's the wind in your sails? Like, the thing that keeps you going and keeps you motivated to keep working on this? And then, conversely, what's kind of holding you back? What are the obstacles and challenges that you're facing? NADIA: I think this kind of role...so I'm like founder, CEO, and developer. In general, I think I thrive under pressure and pushing myself, and trying to always be better and improve. So I'm always trying to be like, how can I improve my productivity? Or how can I run the company better? All these kinds of things. So I feel like I'm getting to explore maximizing my full potential as someone in the world of work through doing this. So that just intrinsically is motivating to me. I love books, and I love reading. I think it's such an amazing hobby. And the fact that I get to make other readers happy is awesome. So even just as the product has grown, the messages that we get about if someone got a perfect recommendation from StoryGraph, or they hadn't read for years, and now an easy form of, you know, what are you in the mood for? Check a few boxes, and we'll show you some books that fit, whatever it is. That's just so...it's so awesome just to be able to enhance readers' lives that way in terms of the things they're reading and getting them excited about reading again or keeping them excited. So those are the things that keep me going, both the personal nature of enjoying my work and enjoying trying to be the best founder and CEO that I can and building a great product. It's always great when you build something, and people just enjoy using it and like using it. So I'm always incentivized to keep making the product better, the experience better. I'm currently mid a redesign. And I'm just so excited to get it out because it's going to touch on a lot of repeated pain points that we've been having for years. And I just can't wait for everyone to see it and see that we've listened to them. And we're making progress still like three and a bit years on since we launched out of beta. What's tough? Previously, what's been tough is navigating, remaining independent, and bootstrapped with just personally trying to make money to just live my life. So I had five years of runway. And it was this tricky situation about when I had a couple of years left, I'm thinking, wow, I really like doing this, but I'm going to need to start earning money soon. But I also don't want to get investment. I don't want to stop doing this. I can't stop doing this. We've got hundreds of thousands of customers. And so kind of trying to balance my personal needs and life situations with the work I've been doing because I've been working so hard on it for so long that in the last couple of years, it's gotten to a point where it's like, how do I craft the life I want out of a product that is very not set up to be an indie bootstrapped product? [laughs] Typically, you want to do a B2B. You want to start earning money from your product as early as possible. And I feel like I've landed in a product that's typically funded, VC-backed, that kind of thing. So kind of navigating that has been a fun challenge. There's not been anything that's kind of demoralized me or held me back, or made me think I shouldn't do it. And it's just kind of been a fun challenge trying to...yeah, just navigate that. And we've been doing things like we're currently in the process of transitioning our...we have a Plus Plan. And when we launched it, it was essentially a grab bag of features. We're completely changing the feature set. And we right now have six and a half thousand people who are on that plan. But we don't have product market fit on that plan, and I can tell from when I do certain surveys the responses I get back. And so we're completely transitioning that to focus in on our most popular feature, which is the stats that we offer. And so that's kind of scary, but it's part of making that Plus Plan more sticky and easier to sell because it's going to be for your power users who love data. So they want all the data when they are reading. And then the other thing is, okay, what kind of business avenue can we start which fits in with the ethos of the product but brings in more revenue for StoryGraph? And so, we launched a giveaway segment in our app where publishers and authors can pay to list competitions for users to win copies of their books. And it's essentially a win-win-win because publishers and authors get another channel to market their books. Users get to win free books, and readers love winning free books. And StoryGraph has another revenue source that helps us stay independent and profitable, and sustainable in the long run. VICTORIA: That's wonderful. And there are two tracks I want to follow up on there; one is your decision not to seek funding; if you could just tell me a little more about the reasoning and your thought process behind that. And you've already touched on a little bit of the other ways you're looking at monetizing the app. NADIA: Since I was a teenager, I've always been interested in business, economics, entrepreneurship. I've always felt very entrepreneurial. I've read so many founder stories and startup stories over the years. And you hear about venture capitalists who come in, and even if it's fine for the first year or two, ultimately, they want a return. And at some point, that could come at odds with your mission or your goals for your company. And when I think about two things, the kind of life I want and also the nature of the product I'm building as well, VC just doesn't fit. And I know there are so many different funding programs and styles right now, a lot more friendlier [laughs] than VC. But I'm just focusing on VC because when I was younger, I used to think that was a marker of success. VC funding that was the track I thought I was going to go down, and that was what I kind of idolized as, oh my gosh, yes, getting a funding round of millions and millions and then building this huge company. That was how I used to be, so it's so interesting how I've completely gone to the other side. That idea that you could have mismatched goals and how it's ruined companies, once you take the first round of funding and you grow and expand, then you've got to keep taking more to just stay alive until some liquidation event. That just doesn't appeal to me. And I just think there's something ultimately very powerful and valuable about building a product without giving up any ownership to anybody else and being able to make it into something that people love, and that's profitable, and can give the people who run it great lifestyles. I just think that's a mark of an excellent product, and I just want to build one of those. And then I think also the nature of the product itself being a book tracking app. I think the product has done well because it is run and built so closely by myself and Rob. And so it's like, people talk about how, oh, you can tell it's built for readers by readers by people who care. And I run the company's Instagram, and it's not just me talking about the product. I'm talking with a bunch of our users about books and what we're reading. And it really feels like it's just got such a great community feel. And I worry that that can get lost with certain types of investment that I've previously thought that I wanted in my life. And so, yeah, that's the reason why I've kind of strayed away from the investment world. And then it's gotten to the point, like, now we're at the point where we don't need funding because we've been able to get to profitability by ourselves. So we don't need any type of funding. And we're just going to try and keep doing things to keep making the product better, to convert more people to the Plus Plan. And, hopefully, our giveaways platform grows in the way we want such that our goal is to just stay profitable and independent forever for as long as possible. And we think that way, we're going to have the most fun running the company, and the product is going to be the best it can be because there's not going to be competing incentives or goals for the product. VICTORIA: That makes sense. And it sounds like, in reality, in the real case, you had a team, and you had the skills yourself to be able to move the product forward without having to take on funding or take on additional support, which is awesome. And I actually really like your background. I also have a degree in economics. So I'm curious if the economics and philosophy, all of that, really lends itself to your skills as a founder. Is that accurate? NADIA: I don't think so. VICTORIA: [laughs] NADIA: I love my degree. I get sad when I meet econ grads or econ majors, and they're like, "Oh, I hated it. Oh, it was so boring," or whatever. I'm like, "No, it was so great." I'm a big microeconomics fan, so I was all about...I didn't like macro that much. I was all about the game theory and the microeconomic theory, that kind of stuff. I don't think there's anything that really ties into my skills as a founder. I feel like that's more to do with my upbringing and personality than what I studied. But, I mean, one of the reasons I did love my degree is because there are elements that do crop up. It's such a widely applicable...the subjects I did are so widely applicable, philosophy, different ways of seeing the world and thinking and approaching different people. And then, obviously, economics that's essentially behavior, and how markets work, and incentives, and all that kind of stuff. And when you get to pricing and all those sorts of things, and business, and then politics as well, I mean, everything is politics, right? People interacting. So there are definitely things and conversations I had at university, which I see things crop up day to day that I can tie back to it. But yeah, I think it doesn't really...my specific degree, I don't think it's made me a better founder than I would have been if I'd studied, I don't know, English or Math or something. VICTORIA: Right, yeah. I think economics is one of those where it's kind of so broadly applicable. You're kind of using it, but you don't even realize it sometimes. [laughs] NADIA: Yeah. MID-ROLL AD: thoughtbot is thrilled to announce our own incubator launching this year. If you are a non-technical founding team with a business idea that involves a web or mobile app, we encourage you to apply for our eight-week program. We'll help you move forward with confidence in your team, your product vision, and a roadmap for getting you there. Learn more and apply at tbot.io/incubator. VICTORIA: So what made you decide to go to a bootcamp right after finishing school? NADIA: So I'd always been entrepreneurial. I remember...I don't know where exactly it started from, whether I got it from my mom. I know she's always been very entrepreneurial and into business. The earliest memory I have of doing something that was very specifically business-oriented was in what we call sixth form in the UK, which is essentially the last two years of high school before you go to university or college; we had this scheme called Young Enterprise. And essentially, you got into teams of people, small teams, or they could be quite big, actually. It could be up to 20 people. And you started a business, and there were trade shows, and pitch meetings, and all that kind of stuff, so I remember getting involved in all that sort of stuff at school. But I'd always been on the investment banking track because when I was young...so my parents...we come from a poor background. And so my parents were very much like, you know, try and find high-paying careers to go into so that you can pay for whatever you want and you have a much better lifestyle. So I had gotten onto the investment banking track from the age of 14 when I went with a friend...at the school, I went to, there was a Take Your Daughter to Work Day. My dad said, "Oh, you want to go to try and find someone whose parent works in an investment bank or something like that. That's like a great career to go into." And so I went with a friend's dad to UBS. And I remember being blown away, like, wow, this is so fascinating. Because I think everything seems so impressive when you're 14, and you're walking into a space like that, and everything seems very lively. And everyone's walking around dressed sharp. They've got their BlackBerries. So from the age of 14 until 20, it would have been, I was very much I am going to work in an investment bank. And I did all the things that you would do, like all the schemes, the spring programs. And it got to my final internship. And I just remember at the internship being rather disillusioned and disappointed by the experience. I remember thinking, is this it? I was studying at Oxford, and I put so much into my studies. And I remember thinking; I'm working so hard. And this is what I come to? Is this it? And so around the time as well, I was also meeting a lot of people in the entrepreneurship space, social enterprises, people doing their own ventures. And I just remember thinking, oh, I feel like I've got to go down that track. And I ended up winning a place on a coding course. It was set up specifically to help more women get into tech. And it was called Code First Girls. I won a place that started...it was just part-time. What I did was I actually...I got the banking job from Deutsche Bank, it was, but I decided to turn it down. It was a very risky decision. I turned it down, and I stayed in Oxford after graduating and worked in the academic office for a while. And then, twice a week, I would go to London and do this coding course. And during it, on Twitter, I remember seeing a competition for a full-paid place at this bootcamp called Makers Academy. And I just thought to myself, having tech skills, I'd heard the feedback that it's a very powerful thing to have. And I remember thinking I should go for this competition. And I went for the competition, and I won a free place at the bootcamp. If I didn't win a free place at the bootcamp, I'm not sure what would have happened because I'm not sure whether at that point I would have thought, oh, paying £8,000 to go to a software bootcamp is what I should do. I'm not sure I would have got there. So that's how I got there, essentially. I won a competition for a bootcamp after having a taste of what coding was like and seeing how freeing it was to just be able to have a computer and an internet connection and build something. VICTORIA: Oh, that's wonderful. I love that story. And I've spent a lot of time with Women Who Code and trying to get women excited about coding. And that's exactly the story is that once you have it, it's a tool in your toolset. And if you want to build something, you can make it happen. And that's why it's important to continue the education and get access for people who might not normally have it. And you continue to do some of that work as well, right? You're involved in organizations like this? NADIA: Like Code First Girls? No. I did some years ago. I would go and attend Rails Girls workshops and be a mentor at them, at those. And while I was at Pivotal, I helped with events like codebar, which were essentially evenings where people who were learning to code or more junior could come and pair with someone more senior on whatever project they wanted to. So I did a bunch of that stuff in the years after leaving Makers Academy. And I was even a TA for a short time for a couple of weeks at Makers Academy as well after I graduated. But in more recent years, I haven't done much in that space, but I would love to do more at some point. I don't have the bandwidth to right now. [laughs] VICTORIA: And you're still a major speaker going and keynoting events all around the world. Have you done any recently, or have any coming up that you're excited about? NADIA: So before the pandemic, my last talk, I keynoted RubyWorld in Japan. That was in November 2019. And then the pandemic hit, and 2020 June, July was when StoryGraph had some viral tweets, and so we kicked off. And amongst all of that, I was being invited to speak at remote events, but it just didn't make sense for me. Not only was I so busy with work, but I put a lot of hours into my talks. And part of the fun is being there, hallway track, meeting people, being on stage. And so it just didn't appeal to me to spend so much time developing the talk to just deliver it at home. And so, I just spent all the time on StoryGraph. And I remember when events started happening again; I wondered whether I would even be invited to speak because I felt more detached from the Ruby community. Most of the conferences that I did were in the Ruby community. StoryGraph is built on Rails. Yeah, I just thought maybe I'll get back to that later. But all of a sudden, I had a series of amazing invitations. Andrew Culver started up The Rails SaaS Conference in LA in October, and I was invited to speak at that. And then, I was invited to keynote RubyConf, that was recently held in Houston, Texas, and also invited to keynote the satellite conference, RubyConf Mini in Providence, that happened a couple of weeks earlier. And so I had a very busy October and November, a lot of travel. I developed two new talks, a Ruby talk and a StoryGraph talk. It was my first ever time giving a talk on StoryGraph. It was a lot of work and amongst a lot of StoryGraph work that I needed to do. All of the talks went well, and it was so much fun to be back on the circuit again. And I'm looking forward to whatever speaking things crop up this year. VICTORIA: That's wonderful. I'm excited. I'll have to see if I can find a recording and get caught up myself. Going back to an earlier question, you mentioned quite a few times about market research and talking to the customers. And I'm just curious if you have a method or a set of tools that you use to run those experiments and collect that feedback and information. NADIA: Yes. So I remember one of the first things I did years ago was I read "The Mom Test" by Rob Fitzpatrick. And that's great for just getting the foundation of when you talk to customers; you don't want to lead them on in any shape or form. You just want to get the raw truth and go from there. So that's the underpinning of everything I do. And then, I learned from friends I made through Pivotal about how you put together a script for a customer research. You can't just have bullet points or whatever. You should have a script. And the foundation of that script is a hypothesis about what you're trying to find out in that round of research. And once you figure out your hypothesis, then you can put together the questions you want to ask and understand how you're going to measure the output. So the first ever thing I was trying to find out when I first started interviewing people was just very general. It was just like, are there any pain points? I was just trying to figure out are there any pain points among the avid reader group of people? And then I remember the results from that were, "No place for consistent, high-quality recommendations." And so then I said, okay, how are people finding recommendations now, or what are the factors that lead to people thinking a book was great for them? And that's how I ended up getting to the moods and pace. But when I do my interviews, I record them all. I watch them back. And I condense everything on sticky notes. And I use a virtual tool. And I try to take word for word. When I summarize, I still just try and use their specific words as much as possible. So I'm not adding my own editing over what they say. Every single interviewee has a different color. And I essentially group them into themes, and that's how I unlock whatever the answers are for that round. And then I use that...I might have been trying to find out what to build next or whether we should go down a certain product direction or not. And so, depending on the outcome, that helps me make up my mind about what to do. So that's the high-level process that I follow. VICTORIA: Well, that sounds very methodical, and interesting for me to hear your perspective on that. And you mentioned that you do have a redesign coming out soon for StoryGraph. Are there any other particular products or features that you're really excited to talk about coming up soon? NADIA: Yeah, I'm so excited about the redesign because we're bringing out...it's not just a UI improvement; it's a user experience improvement as well. So there are a lot of little features that have been asked for over the years. And actually, it was trying to deliver one of them that sparked the whole redesign. So people really want a marked as finished button. There's no way to mark as finished. You just toggle a book back to read. And some people find this quite counterintuitive, or it doesn't quite explain what they're doing. And so when I came to deliver the mark as finished button, this was months and months ago now, I realized that the book pane was just becoming so cluttered, and I was trying to fight with it to squeeze in this link. And I remember thinking; this is not the only thing people want to see on the book pane. They also want to see when they read the book without having to go into the book page. They also want to be able to add it to their next queue. And I just said, you know what? I need to redesign this whole thing. And so I was able to luckily work with Saron Yitbarek, who is married to my co-founder, Rob. There's a funny story about all of that. And she helped me do this redesign based on all my customer research. And so I'm just so excited to get it out because the other thing that we're bringing with it is dark mode, which is our most requested feature in history. And it's funny because I've always felt like, ah, that's a nice-to-have. But obviously, for some people, it's not a nice-to-have; it's an accessibility issue. And even me, I'm quite strict with my bedtime. I try and be offline an hour before bed. In bed by 11, up at 6, and even me if I want to track my pages, I'm like, ooh, this is a bit bright. And my phone itself is set on adaptive, so it's light mode during the day and dark mode during the night. And even me, I can see why people really want this and why it would just improve their experience, especially if everything else on your phone is dark. So I'm really excited to get that out, mainly for the UX improvements. And the other thing I'm really excited to do is transition the Plus Plan to being the advanced stats package rather than the random selection of features right now. Because not only will the people who pay us get more complex stats functionalities such that they feel like, wow, the subscription fee that I pay not only does it still make me feel like I'm supporting an alternative to Goodreads, an independent alternative to Goodreads I also get such value from these extra features. But the other thing is what I found from my customer research is that if you're a Plus customer, there's often one or two of the Plus features that you love and that you don't really use the others. But they're all really great features. And so what I'm really excited about is that we're going to make all the non-stats features free for everybody. And so I'm so excited for, like, we have a feature where if you put in a group of usernames, we look at all of your to-read lists and suggest great books for you to buddy-read together. Now, there's a bunch of Plus users who aren't social and don't care about it. But there's going to be a bunch of our free users who are so excited about that feature, probably will use it with their book clubs, things like that. We have up-next suggestions where we suggest what you should pick up next from your to-read pile based on a range of factors. It could be, oh, you're behind on your reading goal; here's a fast-paced book. Or this book is very similar to the one that you just finished, so if you want something the same, pick up this one. And, again, that's behind a paywall right now, and I'm just so excited for everybody to be able to use that. When I remember starting out with StoryGraph, I remember thinking, wow, the way this is going, wouldn't it be so cool if we could just suggest books that would be the next perfect read for you? Because a lot of people have a pile of books by their bedside table or on their shelves, and they're just like, well, which one should I start with? And this tool literally helps you to do that. And so I can't wait for everyone to be able to try it. And so that's why I'm excited about that transition because the Plus Plan will be better, and the free product will be better. VICTORIA: That sounds amazing. And I'm thinking in my head like, oh, I should start a book club with thoughtbot. Because there are some engineering management and other types of books we want to read, so maybe we could use StoryGraph to manage that and keep ourselves motivated to actually finish them. [laughs] NADIA: Cool. VICTORIA: No, this is wonderful. And what books are on your reading list coming up? NADIA: Yes. I am excited to read...I'm not sure...I'm blanking on the series' name. But the first book is called "The Poppy War." I don't know whether it's called "The Burning God" or if that's the third book in the series. But it's this very popular trilogy, and I'm excited to read that soon. I'm doing a slow chronological read of Toni Morrison's fiction. I recently read "Song of Solomon," which was great, really, really good. And so I'm excited to read more of her novels this year. I'm also on a kind of narrative nonfiction kick right now. I love narrative nonfiction. So I just finished reading "American Kingpin," which is about Silk Road. And I've picked up "Black Edge," which is about SAC Capital and Steve Cohen and that whole hedge fund insider trading situation. So I'm probably going to look for more of the same afterwards. VICTORIA: Well, that's very exciting. And it's inspiring that as a founder, you also still have time to read [laughs] and probably because StoryGraph makes it easy and motivating for you to do so. NADIA: Yeah, everyone thought that my reading would tank once I started the company, but, in fact, it's multiplied severalfold. And a couple of reasons; one is it's very important in general for me to make time for me because I'm in a situation that could easily become very stressful and could lead to burnout. So I make sure that I make time for me to read and to go to dance class regularly, which is my other main hobby. But then, secondly, I feel like I can justify it as work. Because I say, wow, me being a reader and being able to communicate with people on Instagram and on Twitter about books, not just the product, adds legitimacy to me as the founder and developer of this product. And so it's important that I keep reading. And it also helps the product be better because I understand what features are needed. So, for example, I never used to listen to audiobooks. I'm a big podcast person; I love music. So between those two, when does audio fit in? And also, I didn't like the idea that I could just be absent-minded sometimes with some podcasts, but with a book, you don't want spoilers. It could get confusing. But I started listening to audiobooks because we had a large audiobook user base. And they would ask for certain features, and it was really hard for me to relate and to understand their needs. And now that I have started listening to audiobooks as well, we made some great audiobook listeners-focused additions to the app last year, including you can track your minutes. So you can literally get you read this many pages in a day, but you also listened to this many minutes. You can set an hours goal for the year, so not just a reading goal or a pages goal. You can set an hours goal. Or maybe you're someone like me, where audiobooks are the smaller proportion of your reading, and you just want it all calculated as pages. And so I've got it on the setting where it's like, even when I track an audiobook in StoryGraph, convert it to pages for me, and I just have my nice, all-round page number at the end of the year. VICTORIA: That's so cool. Really interesting. And I've had such a nice time chatting with you today. Is there anything else that you'd like to share as a final takeaway for our listeners? NADIA: If you are someone who wants to start a company, maybe you want to bootstrap, you've got a product idea, I think it's honestly just trust the process. It will take time. But if you trust the process, you listen to customers and really listen to them...research ways to talk to customers, and don't cut corners with the process. There have been so many times when I've done a whole round of research, and then I say, oh, do I have to go through all these now and actually do a synthesis? I think anecdotally; I can figure out what the gist was; no, do the research. You don't know what insights you're going to find. And I think if you just trust that process...and I think the other thing is before you get to that stage, start building up a runway. Having a runway is so powerful. And so whether it's saving a bit more or diverting funds from something else if you have a runway and you can give yourself a couple of years, a few years without worrying about your next paycheck, that is incredibly valuable to getting started on your bootstrapping journey. VICTORIA: Thank you. That's so wonderful. And I appreciate you coming on today to be with us. You can subscribe to the show and find notes along with a complete transcript for this episode at giantrobots.fm. If you have questions or comments, email us at hosts@giantrobots.fm. And you can find me on Mastodon at Victoria Guido. This podcast is brought to by thoughtbot and produced and edited by Mandy Moore. Thank you for listening. See you next time. ANNOUNCER: This podcast is brought to you by thoughtbot, your expert strategy, design, development, and product management partner. We bring digital products from idea to success and teach you how because we care. Learn more at thoughtbot.com. Special Guest: Nadia Odunayo.

Guest Mike McQuaid | Nina Breznik Panelists Richard Littauer Show Notes Hello and welcome to a special episode of Sustain, where we interview Maintainers as part of GitHub Maintainer Month! On this episode, Richard is interviewing a few open source maintainers to talk about what it's like to be a maintainer, how awesome they are, and what issues they may have being a maintainer. My first guest is Mike McQuaid, who works for GitHub and is one of the maintainers of Homebrew. Mike tells us all about Homebrew, how you can contribute, and the most fun thing about being a maintainer there. Also joining me is Nina Breznik, another awesome maintainer, Founder of RefugeesWork, Partner and Open Source Developer at Playproject, Community Organizer at Wizard Amigos, and she works on a DatDot project with serapath. Nina shares how it is for her being a maintainer, how she helps other people see it as art, not just science and math, but a more creative thing, and she tells us the project she had the most fun working on. Go ahead and download this episode now to learn more! Mike: [00:00:48] Mike explains what Homebrew is, the size of the community, and the usage. [00:01:46] How did Mike come to maintain Homebrew and the other twenty people and how did he pivot and make the switch elegantly? [00:04:08] Richard asks if Mike has any resources he can suggest to other maintainers. [00:05:04] Mike talks about burnout and when he works on Homebrew. [00:07:19] Mike shares advice to a first time open source person, and he tells us what advice he wishes someone had given him back in the day. [00:09:00] We learn from Mike the most fun thing about being a maintainer at Homebrew. [00:09:47] Find out how you can contribute to Mike's project and where you can follow him on the web. Nina: [00:11:48] We have Nina joining us now and Richard shares her bio with us. We also hear what Nina is maintaining these days and what her code looks like. [00:14:41] Nina tells us about the number of projects she maintains in the sense of commit access and the size of the community that she's working with. [00:17:30] Find out the hardest part for Nina when it comes to maintaining code. [00:18:47] Nina shares more about the RefugeesWork project she started which was the most magical experience for her. [00:21:36] What is Nina most looking forward to over the next five to ten years as a maintainer and what does she want to see happen with her work? [00:22:57] Nina shares what she wishes people had told her to make it easier for her when she first started coding. [00:24:27] We learn what Nina does in her community to ensure that designers or tech writers, etc., feel involved in the projects she works on. [00:27:15] Find out where you can follow Nina and her projects on the web. Quotes [00:01:59] “The best way to get involved with open source was solving a problem I had for myself.” [00:04:23] “Everything we do breaks down to human relationships and managing those and trying to have an environment where people are happy with each other.” [00:07:19] “What advice would you give to a first-time open source person? I think just strict boundaries.” [00:20:34] “I transitioned from social sciences and arts into coding because I wanted to get a skill. I wanted to be able to build something on my own and this was the first time I felt the power that I built something.” [00:21:45] “I would love to see more people learning to code, which is one of the reasons why I started Wizards Amigos Project because I feel that this really is literacy of the future.” [00:23:06] “They should have told me this is not all about math, but more like art.” Links SustainOSS (https://sustainoss.org/) SustainOSS Twitter (https://twitter.com/SustainOSS?ref_src=twsrc%5Egoogle%7Ctwcamp%5Eserp%7Ctwgr%5Eauthor) SustainOSS Discourse (https://discourse.sustainoss.org/) podcast@sustainoss.org (mailto:podcast@sustainoss.org) Richard Littauer Twitter (https://twitter.com/richlitt?ref_src=twsrc%5Egoogle%7Ctwcamp%5Eserp%7Ctwgr%5Eauthor) Mike McQuaid Twitter (https://twitter.com/mikemcquaid?lang=en) Mike McQuaid Website (https://mikemcquaid.com/) Homebrew (https://brew.sh/) Sustain Podcast-Episode 117: Mike McQuaid of Homebrew on Sustainability Working on OSS Projects (https://podcast.sustainoss.org/117) Nina Breznik Twitter (https://twitter.com/ninabreznik?lang=en) serapath Twitter (https://twitter.com/serapath) Google Summer of Code 2022 Program Announced (https://summerofcode.withgoogle.com/) Rails Girls (http://railsgirls.com/) Wizard Amigos (https://wizardamigos.com/) DatDot (https://datdot.org/) Dat Ecosystem (https://dat-ecosystem.org/) Mathias Buus (https://github.com/mafintosh) Ok Distribute Blog (https://okdistribute.xyz/) Dat Foundation Governance (https://dat.foundation/about/people/) Credits Produced by Richard Littauer (https://www.burntfen.com/) Edited by Paul M. Bahr at Peachtree Sound (https://www.peachtreesound.com/) Show notes by DeAnn Bahr Peachtree Sound (https://www.peachtreesound.com/) Special Guests: Mike McQuaid and Nina Breznik.

Linda Liukas is a programmer, storyteller and illustrator from Helsinki, Finland. Her book series Hello Ruby introduces the whimsical world of technology to kids and has now been translated into over 25 languages. Her fabulous TED talk about ‘A delightful way to teach kids about computers' has been viewed over 2 million times. Linda is a key figure in the world of programming and worked in edutech before it was called that. She's the founder of Rails Girls, a global phenomenon teaching the basics of programming to young women all over the world. She believes that code is the 21st-century literacy and the need for people to speak the ABC of Programming is here. She also believes our world is increasingly run by software and we need more diversity in the people who are building it. Linda has studied business, design and engineering at Aalto University and product engineering at Stanford University. She is the recipient of many awards including Ruby Hero, Digital Champion of Finland and the State Award for Children's Culture. In today's talk we listen to Linda's sharp intellect, and melodic voice, reflect about:

Futucastin Instagram Kanava: https://www.instagram.com/futucast Sanotaan ihan kärkeen, että Linda Liukas on hyvä nimi. Sitä nimeä kantaa nuori suomalainen, joka tunnetaan mm. suositusta Hello Ruby kirjastaan, joilla voi opettaa koodaamisen perusteita lapsille. Linda perusti myös Rails Girls järjestön, joka pyrkii opettamaan naisille koodausta ympäri maailman. Tämä on jännää aikaa, kun maailman lapsille avautuu jo kasvaessaan kokonaan uudenlainen maailma oppimalla ja ymmärtämällä niitä älykkäitä koneita, jotka ovat tulleet meidän elämään. Keskustelemme Lindan kanssa mm. tästä, ja siitä, miten näiden koneiden tulevaisuus on meidän käsissämme. ▶️ Tilaa Youtube Kanava: http://www.youtube.com/c/Futucastpodcast?sub_confirmation=1

Background.radioは、エンジニアやTech業界ではたらく方をお呼びして、 生い立ちやバックグラウンドをお伺いすることで、 未来のエンジニアを目指す方や、近い立場の方へのヒントになればいいな、 というトークプログラムです。 第25回のゲストは、江森真由美 emorima さんです。 -------------------- 00:01:40 自己紹介 00:02:36 Rails Girlsオーガナイザー 00:10:30 Rails Girlsとは 00:15:20 EMORI HOUSE 00:21:10 女子校に比べれば社会はすべて男性比率が多い 00:25:50 専業主婦になりたかった中学生 00:29:25 アメリカ横断の代わりにパソコンを手に入れた 00:33:30 ファミコンだと思ったらMSX 00:39:45 実家の手伝いからプログラマーへ 00:52:20 初めてのテックイベント参加 00:56:30 ブラッディ・マンデイ ミステリと言う勿れ はみだしっ子 ロードバイク 01:04:30 Rails Girls Gathering Japan -------------------- ゲスト : emorima @emorima https://twitter.com/emorima ◆おすすめエンタテイメント ブラッディ・マンデイ https://www.tbs.co.jp/tbs-ch/item/d1618/ ミステリと言う勿れ https://flowers.shogakukan.co.jp/work/300/ はみだしっ子 https://www.hakusensha.co.jp/comicslist/41826/ ロードバイク https://www.letour.fr/ Background.radio ▼Twitterフォローよろしくお願いします▼ twitter : https://twitter.com/backgroundradi0 Anchor : https://anchor.fm/background-radio Spotify : https://open.spotify.com/show/2brpuj9ykx91Mq7jj6CtDD Apple Podcasts : https://podcasts.apple.com/jp/podcast/background-radio/id1551634977 Google Podcast : https://podcasts.google.com/feed/aHR0cHM6Ly9hbmNob3IuZm0vcy80YTA1Zjg5NC9wb2RjYXN0L3Jzcw==

Welcome back to another episode of Enjoy the Vue. This concludes our three-part interview with Babel maintainer, Henry Zhu. Last time, we closed our discussion with what work maintainers of open source projects do that is not straight coding. In this episode, we continue talking with Henry about what do people count as maintenance work versus other tasks that definitely need to get done, but are perhaps less visible to the public eye. Henry also shares his approaches to taking care of himself and the pursuit of serendipity, and we discuss the inclusivity of the open source community, the relationship between in-person communities and open source culture, and we get into our picks of the week, so make sure not to miss this episode! Key Points From This Episode: Henry opens with the dichotomy between freedom and obligation for maintainers. Maintainers don’t see certain tasks as maintenance, such as answering user queries. What Henry does to take care of himself, like sport or playing music, and his musings on what serendipity looks like in an online setting. Spaces that promote serendipity, and why actively pursuing serendipity is not a paradox. There are communities like Google Summer of Code that promote open source involvement. Preferences are shaped through experiences of the communities, so it is important that they be inclusive, particularly for women. The relationship between in-person communities and open source culture. Ben’s picks this week include a ukulele, Azul, and Nadia Eghbal’s book, Working in Public. Veekas recommends Kim’s Convenience and Race After Technology by Ruha Benjamin. Henry’s picks include Tools for Conviviality by Ivan Illich, and a card game called The Mind. Tessa suggests Journey, the Reply series, and Conquer Your Critical Inner Voice. Tweetables: “How do we get people to have a higher sense of ownership so that we can lessen the burden on maintainers?” — @left_pad [0:02:37] “There's an aspect of serendipity involves risk, and involves trust and faith in something, in the future. Me putting myself out there is going to lead to something good.” — @left_pad [0:05:50] “I feel being more intentional, specifically reaching out to people, or getting involved in certain communities is probably better. There are formal versions of this, like Google Summer of Code. We've done that and Rails Girls, Summer of Code, stuff like that. Yeah, maybe we need more of that, instead of this blanket like, ‘Hey, anyone can get involved.’” — @left_pad [0:07:48] “For a tool, we want self-expression from the people that use it and I think coding is – or anything, [Illich] mentions education, and school, and medicine, and coding could be another thing where it's increasingly harder to learn how to code, even though now we have boot camps and stuff.” — @left_pad [0:17:46] Links Mentioned in Today’s Episode: - Henry Zhu on Twitter (https://twitter.com/left_pad?lang=en) - Henry Zhu on GitHub (https://github.com/hzoo)  - Henry Zhu (https://www.henryzoo.com/) - Hope in Source Podcast (https://hopeinsource.com/) - Maintainers Anonymous Podcast (https://maintainersanonymous.com/) - Babel (https://babeljs.io/) - Google Summer of Code (https://summerofcode.withgoogle.com/archive/) - Rails Girls (http://railsgirls.com/) - Vue Vixens (https://www.vuevixens.org/) - Working in Public (https://www.amazon.com/Working-Public-Making-Maintenance-Software/dp/0578675862) - Kim’s Convenience on Netflix (https://www.netflix.com/title/80199128)  - Race After Technology (https://www.amazon.com/Race-After-Technology-Abolitionist-Tools/dp/1509526404) - Tools for Conviviality (https://www.amazon.com/Tools-Conviviality-Ivan-Illich/dp/1842300113/ref=sr_1_1?dchild=1&keywords=Tools+for+Conviviality&qid=1601903637&s=books&sr=1-1) - Journey (https://thatgamecompany.com/journey/) - Conquer Your Critical Inner Voice (https://www.amazon.com/Conquer-Your-Critical-Inner-Voice/dp/1572242876/ref=sr_1_1?dchild=1&keywords=Conquer+Your+Critical+Inner+Voice&qid=1601904786&sr=8-1) - Enjoy the Vue on Twitter (https://twitter.com/enjoythevuecast?lang=en) - Enjoy the Vue (https://enjoythevue.io/) Special Guest: Henry Zhu.

Flora Saramago tem 10 anos de experiência na área. Formada em Sistemas de Informação pela PUC-Rio, começou sua trajetória trabalhando em startups, onde descobriu sua paixão por Ruby on Rails. Ela participou múltiplas vezes da do hackathon internacional Rails Rumble, onde venceu na categoria Best Solo em 2014, com seu app Pack Pal, e novamente em 2016, com o app Build a Bot. Participou também de muitas edições do workshop Rails Girls, com o objetivo de aumentar a participação feminina na área de tecnologia usando Rails. Nos últimos 3 anos, trabalhou remotamente no Basecamp, fazendo parte da equipe que desenvolveu o novo sistema de email HEY. Hoje mora em Chicago, nos EUA, e se prepara para iniciar um novo capítulo da sua trajetória trabalhando no Shopify. Links: Flora Saramago Practical Object-Oriented Design OsProgramadores: OsProgramadores Grupo no Telegram Twitter do Marcelo Pinheiro

Wir haben mit Susanne einen neuen, tollen, interessanten Gast. Vor einem halben Jahr kam sie auf uns zu, um in einem halben Jahr mal über das Thema "Sprachen lernen" zu sprechen. Sie hat eine längere berufliche Auszeit unter anderem dazu genutzt, einen Python-Kurs zu machen. Der Codestammtisch war zusätzliche Motivation am Ball zu bleiben. Lange vor dem Python-Kurs hat sie mal Sprach- und Kommunikationswissenschaften studiert und in PR und Marketing gearbeitet, bevor sie die Internationalisierung eines Fintech-Unternehmens verantwortete. Zum Coden kam sie, weil ihre vielen Änderungswünsche auf der Homepage, ihren CTO so sehr nervten, dass sie die Views der Rails-Anwendung selbst bearbeiten durfte und dann hat sie ihre Kenntnisse bei einem Coding-Wochenende bei den Railsgirls Berlin weiter vertieft. Außerdem wollen wir ein bisschen die Werbetrommel für Women in Tech, besagte Rails-Girls oder die Geekettes rühren. Wenn ihr irgendwas könnt, programmieren, zum Beispiel: Geht doch da mal hin und erklärt das anderen Menschen, also nach COVID-19. Für den Codestammtisch hat sie sich ein Thistly Cider Whisky Cask, ein Cider aus einem Whiskyfass aus dem Getränkefeinkost geholt. Was man so hört, scheint das ein großartiges Getränk zu sein. Max trinkt ein kanadische Molson Canadian Lager aus Montreal, das ist in Kanada. Außerdem sollte man das sehr kalt trinken. Nathan trinkt mit dem Überquell vielleicht sein neues Lieblings Imperial Lager. Wir reden über natürliche Sprachen und Programmiersprachen und darüber, dass man kein Genie in Mathematik sein muss, um zu programmieren. Ein:e Programmierer:in ist jemand, der:die programmiert. Du musst nicht studieren oder eine Ausbildung in der IT absolviert haben. Ein Elfenbeinturm der Softwareentwickler:innen hilft niemandem und bitte lass dir nichts anderes einreden: Wenn du HTML und CSS schreibst, bist du ein:e Programmierer:in. Ganz einfach :-) Außerdem quatschen wir mal wieder darüber, dass es ganz normal ist, auch mit vielen Jahren Erfahrung vermeintlich billige Sachen zu googlen und nicht alles zu wissen. Max googlet beispielsweise jedes Mal, wie man einen Git-Tag auf ein Remote-Repo pusht. Und Nathan merkt sich nicht, wie man einen Git-Tag auf dem Remote-Repo löscht. Außerdem kann er 98 und 89 nicht auseinanderhalten. Was sind eure Sachen, die ihr regelmässig googlet und über die ihr immer wieder stolpert? Wir bedanken uns wie immer für's Zuhören. Verbesserungsvorschläge, Getränkeempfehlungen, Liebesbekundungen und Kritik bitte wie immer via Twitter an @codestammtisch oder diskret per Mail an hallo-at-codestammtis.ch. Kommentare könnt ihr uns auch gerne auf unser Band quatschen!

In this episode, we’re talking to Linda Liukas - Linda is the author and illustrator of Hello Ruby, a children’s picture book series about the whimsical world of computers, as well as the founder of Rails Girls, a global movement to teach young women programming in over 300 cities.Linda is a totally exceptional person. She’s originally from Helsinki, Finland. She’s created Kickstarter campaign for her book Hello Ruby in 2015 and this project totally went through the roof - by end she gathered more than $380.000 and of course her book Hello Ruby was a big hit. https://kidslab.dev/2019/12/23/hello-ruby-with-linda-liukas/

Linda Liukas is a Finnish programmer, author, illustrator and founder of Hello Ruby, an interactive and fun children’s book series about technology and computing. Launched on Kickstarter in 2014, the series is now published in 25 languages. Liukas also founded Rails Girls, teaching programming to young women in more than 300 cities, and here discusses why our view of life with computers isn’t more hopeful.

We are joined this week by author Linda Liukas, who created a wonderful series of children’s books called Hello Ruby. Linda got the idea for her books while learning computer programming herself and describes her books as “the world’s most whimsical way to learn about technology, computing and coding.” Linda also founded Rails Girls http://railsgirls.com, which organizes workshops to teach the basics of programming to girls and women. She joined us to talk about Ruby, her books and a brand-new YouTube series, Love Letters for Computers, that goes hand-in-hand with the Hello Ruby books. In this episode we talk about: 1. Whimsicality! Linda and her Ruby books are proof that computer science and whimsical things are not mutually exclusive! 2. A universal desire to expose our kids to the technological world- her books have been translated into 28 different languages and are used by parents and teachers all over the world. 3. How Ruby came to be. While studying some “dull” (Linda’s words!) programming textbooks at Stanford University, Linda began doodling a young girl in her books, thinking about how a six-year-old girl would explain the concepts to her. Thus Ruby was “born!” 4. Exploring the idea that programming could be taught through stories rather than concepts. “I do feel that there is value in having these strong characters that...the children will memorize and remember as they grow older. Maybe they don’t actually make the connection of how they relate to the world of technology...but they have this strong emotional feeling that, ‘oh techonology is something that I can feel fearless and curious about; that I feel welcome to. I think that is what books can do far better than apps and other ways to teach.” 5. Ruby is joined by a whole cast of characters that were inspired by different aspects of computers, like Ruby herself (Ruby is a Japanese programming language). While you don’t need to know the inspiration behind each character to enjoy the story, there are plenty of easter eggs for parents and teachers familiar with the tech world to find on each page! 6. Even though our kids are growing up surrounded by technology and start using it proficiently at a very young age, there is great value in teaching them (and ourselves if we are not familiar with it) about what goes into creating these things. “Kids who know how to play games are consumers of technology, not creators. The fact that they can use apps does not mean that they have some magical understanding of...computer science.” 7. We as parents do not need to be an expert on the subject when introducing our kids to new information, we can be more of a “curator.” 8. Studies are showing that kids, especially girls as young as 5 and 6 are already developing self-limiting ideas about who can or can’t be a computer scientist. 9. Coding may be touted as a useful skill, but it can also be beautiful and interesting and “intensely creative.” Linda believes that we need more materials that show the “practicality of engineering meeting...the beauty of [the] arts…” 10. While it wasn’t their intended purpose, the Ruby books are being used more and more as a teaching tool in classrooms, so Linda has created a YouTube series, Love Letters for the Computer, intended as a resource for primary school teachers, with plans of a book to go along with it in the future. Linda left us with a great idea of how to get started on putting these great ideas into practice this week. She invited us to check out the computer building activity https://www.helloruby.com/play/2  on the Hello Ruby website. We have done this with our own kids and we agree with Linda- it is a hit with kids of all ages and is a great activity to go along with the Hello Ruby books! We are so grateful to Linda for taking the time to talk with us! More information about her, her books, and more can be found in the following places: Instagram: @lindaliukas

In this week’s episode of Sustain Our Software the panel interviews Laura Gaetano. Laura is a developer and designer, whose main job was running was running Rails Girls Summer of Code. The panel considers how great Rails Girls is and all that they are doing. The panel also expresses their love for the Rails framework.  Laura explains the difference between Rails Girls and Rails Girls Summer of Code. The panel asks about the challenges that the Rails Girls Summer of code experience. Laura tells the panel how open source and the Ruby community has changed since they started. When they first started Rails Girls Summer of Code there was a lot less support for open source and diversity in programming. Now their main challenges are lack of resources, such as money and people who are invested in Rails Girls Summer of Code for the long term.  Other challenges in the organization stem from the nature of the organization. They are just trying to get everything done, that things like documentation and long term management solutions get forgotten. They want to get all their experience for the last six years documented so that knowledge can help in the future of Rails Girls Summer of Code.  The panel considers what a great feeling it is when people use or contribute to their open source and ask Laura what it’s like to actually help someone become a developer through her open source efforts. Laura explains how amazing it is to see women from past Rails Girls Summer of Code and their success. Laura shares her love of open source and the collaboration that happens in the community. Doing Rails Girls Summer of Code she gets a lot more human contact than in typical open source projects, she explains how that has made a difference in the way that she sees open source.  The panel asks Laura about the state of diversity in open source. Laura explains that there are initiatives out there to support diversity in opensource. She invites everyone to visit opensourcediversity.org. They provide resources to learn about diversity. They even have an open forum where people have a safe space to learn about diversity. She explains that diversity is now a common talking point at conferences to help improve diversity by educating developers about it. The panel discusses making projects more inclusive and explains how Github added s social impact feature that helps make your project more inclusive.  The topic turns to a talk Laura gave in 2017. Her talk explains that open source needs more than code. She explains that she would like to see more crowdsourcing of knowledge and design in open source. Programming is a major part of open source and she is so impressed the how willing programmers are to volunteer their time. However, she would love to see that desire from other people in the technology industry. Open source would be more maintainable if they had people marketing, networking, documenting. Having open source maintainers who focus on these things would help generate more funding and make it more sustainable.  The panel considers why there is such an emphasis on the code contributions, even more so than managing or other roles in open source. Code is a very visible contribution, easy to hold up and say look what they did. Other roles aren’t so easy to hold up, how can someone hold up the hours they spent finding sponsors or perfecting documentation. The discussion turns to mental health in open source. Laura talks about her own state of mind and how hard it can be to get herself to do anything when she is feeling burnt out. She explains that she needs to change the way she approaches work.  The panel discusses ways that we can help those experiencing mental health problems in open source. They suggest talking to each other more about their experiences, about what depression, anxiety, and burn out look like and how they affect different people. The panel discusses what processes can be put in place to help developers to avoid burn out.  The panel wonders if developers are susceptible to mental health problems. Do the large workloads and high amounts of stress contribute to these issues. Laura explains that in her opinion, we as humans tend to think that our experience is unique, so other industries probably feel the same way. The reality is that this is a worldwide problem, especially for those that Laura calls knowledge workers.   The panel considers other ways we can help open source maintainers not get burnt out. The power of gratitude is one way they think might help. Laura thinks that getting a thank you from supports is very important. She relates how she feels when she talks with participants of Rails Girls Summer of Code and how it makes all her hard work worth it. The panel discusses the power of money in open source, explaining why they started codefund. They explain the benefits of open source getting some money for their contributions. They consider the effect it plays on burn out. While Laura agrees to receive funds for open source contributions can be helpful, she warns that it could be a double-edged sword. She warns that the receiving fund could be adding more stress to open source because of the responsibility it adds. Laura explains that she has already started to see entitlement from open source users, getting upset when the maintainer doesn't fix something right away. The panel considers how these benefits and costs when the funding is anonymous compared to when it is a direct sponsorship.   Panelists Eric Berry Nate Hopkins Guest Laura Gaetano Sponsors   DevEd Podcast The Freelancers Show My Ruby Story CacheFly Links AlterConf Berlin 2017: Making your voice heard: Open Source Needs You by Laura Gaetano Laura Gaetano - Building inclusive Open Source communities | ReasonConf 2018 https://devchat.tv/ruby-rogues/ https://railsgirlssummerofcode.org/  https://opensourcediversity.org/  https://www.codenewbie.org/podcast/rails-girls-summer-of-code  https://github.com/about/diversity  https://twitter.com/natfriedman/status/1157379019878232064  https://m.signalvnoise.com/to-smile-again/  https://twitter.com/alicetragedy https://github.com/alicetragedy https://www.facebook.com/Sustain-Our-Software-SOS-857471391289849/ https://twitter.com/sos_opensource Picks Eric Berry: https://webflow.com/  Nate Hopkins: https://www.metabase.com  Willow Hybrid Tree  Laura Gaetano: Jocelyn K. Glei  The Bulletin Design for Real Life Special Guest: Laura Gaetano.

In this week’s episode of Sustain Our Software the panel interviews Laura Gaetano. Laura is a developer and designer, whose main job was running was running Rails Girls Summer of Code. The panel considers how great Rails Girls is and all that they are doing. The panel also expresses their love for the Rails framework.    Laura explains the difference between Rails Girls and Rails Girls Summer of Code. The panel asks about the challenges that the Rails Girls Summer of code experience. Laura tells the panel how open source and the Ruby community has changed since they started. When they first started Rails Girls Summer of Code there was a lot less support for open source and diversity in programming. Now their main challenges are lack of resources, such as money and people who are invested in Rails Girls Summer of Code for the long term.    Other challenges in the organization stem from the nature of the organization. They are just trying to get everything done, that things like documentation and long term management solutions get forgotten. They want to get all their experience for the last six years documented so that knowledge can help in the future of Rails Girls Summer of Code.    The panel considers what a great feeling it is when people use or contribute to their open source and ask Laura what it’s like to actually help someone become a developer through her open source efforts. Laura explains how amazing it is to see women from past Rails Girls Summer of Code and their success. Laura shares her love of open source and the collaboration that happens in the community. Doing Rails Girls Summer of Code she gets a lot more human contact than in typical open source projects, she explains how that has made a difference in the way that she sees open source.    The panel asks Laura about the state of diversity in open source. Laura explains that there are initiatives out there to support diversity in opensource. She invites everyone to visit opensourcediversity.org. They provide resources to learn about diversity. They even have an open forum where people have a safe space to learn about diversity. She explains that diversity is now a common talking point at conferences to help improve diversity by educating developers about it. The panel discusses making projects more inclusive and explains how Github added s social impact feature that helps make your project more inclusive.    The topic turns to a talk Laura gave in 2017. Her talk explains that open source needs more than code. She explains that she would like to see more crowdsourcing of knowledge and design in open source. Programming is a major part of open source and she is so impressed the how willing programmers are to volunteer their time. However, she would love to see that desire from other people in the technology industry. Open source would be more maintainable if they had people marketing, networking, documenting. Having open source maintainers who focus on these things would help generate more funding and make it more sustainable.    The panel considers why there is such an emphasis on the code contributions, even more so than managing or other roles in open source. Code is a very visible contribution, easy to hold up and say look what they did. Other roles aren’t so easy to hold up, how can someone hold up the hours they spent finding sponsors or perfecting documentation.   The discussion turns to mental health in open source. Laura talks about her own state of mind and how hard it can be to get herself to do anything when she is feeling burnt out. She explains that she needs to change the way she approaches work.  The panel discusses ways that we can help those experiencing mental health problems in open source. They suggest talking to each other more about their experiences, about what depression, anxiety, and burn out look like and how they affect different people. The panel discusses what processes can be put in place to help developers to avoid burn out.    The panel wonders if developers are susceptible to mental health problems. Do the large workloads and high amounts of stress contribute to these issues. Laura explains that in her opinion, we as humans tend to think that our experience is unique, so other industries probably feel the same way. The reality is that this is a worldwide problem, especially for those that Laura calls knowledge workers.     The panel considers other ways we can help open source maintainers not get burnt out. The power of gratitude is one way they think might help. Laura thinks that getting a thank you from supports is very important. She relates how she feels when she talks with participants of Rails Girls Summer of Code and how it makes all her hard work worth it.   The panel discusses the power of money in open source, explaining why they started codefund. They explain the benefits of open source getting some money for their contributions. They consider the effect it plays on burn out. While Laura agrees to receive funds for open source contributions can be helpful, she warns that it could be a double-edged sword.   She warns that the receiving fund could be adding more stress to open source because of the responsibility it adds. Laura explains that she has already started to see entitlement from open source users, getting upset when the maintainer doesn't fix something right away. The panel considers how these benefits and costs when the funding is anonymous compared to when it is a direct sponsorship.   Panelists Eric Berry Nate Hopkins Guest Laura Gaetano Sponsors   DevEd Podcast The Freelancers Show My Ruby Story CacheFly Links AlterConf Berlin 2017: Making your voice heard: Open Source Needs You by Laura Gaetano Laura Gaetano - Building inclusive Open Source communities | ReasonConf 2018 https://devchat.tv/ruby-rogues/ https://railsgirlssummerofcode.org/  https://opensourcediversity.org/  https://www.codenewbie.org/podcast/rails-girls-summer-of-code  https://github.com/about/diversity  https://twitter.com/natfriedman/status/1157379019878232064  https://m.signalvnoise.com/to-smile-again/  https://twitter.com/alicetragedy https://github.com/alicetragedy https://www.facebook.com/Sustain-Our-Software-SOS-857471391289849/ https://twitter.com/sos_opensource Picks Eric Berry: https://webflow.com/  Nate Hopkins: https://www.metabase.com  Willow Hybrid Tree  Laura Gaetano: Jocelyn K. Glei  The Bulletin Design for Real Life

In this week’s episode of Sustain Our Software the panel interviews Laura Gaetano. Laura is a developer and designer, whose main job was running was running Rails Girls Summer of Code. The panel considers how great Rails Girls is and all that they are doing. The panel also expresses their love for the Rails framework.    Laura explains the difference between Rails Girls and Rails Girls Summer of Code. The panel asks about the challenges that the Rails Girls Summer of code experience. Laura tells the panel how open source and the Ruby community has changed since they started. When they first started Rails Girls Summer of Code there was a lot less support for open source and diversity in programming. Now their main challenges are lack of resources, such as money and people who are invested in Rails Girls Summer of Code for the long term.    Other challenges in the organization stem from the nature of the organization. They are just trying to get everything done, that things like documentation and long term management solutions get forgotten. They want to get all their experience for the last six years documented so that knowledge can help in the future of Rails Girls Summer of Code.    The panel considers what a great feeling it is when people use or contribute to their open source and ask Laura what it’s like to actually help someone become a developer through her open source efforts. Laura explains how amazing it is to see women from past Rails Girls Summer of Code and their success. Laura shares her love of open source and the collaboration that happens in the community. Doing Rails Girls Summer of Code she gets a lot more human contact than in typical open source projects, she explains how that has made a difference in the way that she sees open source.    The panel asks Laura about the state of diversity in open source. Laura explains that there are initiatives out there to support diversity in opensource. She invites everyone to visit opensourcediversity.org. They provide resources to learn about diversity. They even have an open forum where people have a safe space to learn about diversity. She explains that diversity is now a common talking point at conferences to help improve diversity by educating developers about it. The panel discusses making projects more inclusive and explains how Github added s social impact feature that helps make your project more inclusive.    The topic turns to a talk Laura gave in 2017. Her talk explains that open source needs more than code. She explains that she would like to see more crowdsourcing of knowledge and design in open source. Programming is a major part of open source and she is so impressed the how willing programmers are to volunteer their time. However, she would love to see that desire from other people in the technology industry. Open source would be more maintainable if they had people marketing, networking, documenting. Having open source maintainers who focus on these things would help generate more funding and make it more sustainable.    The panel considers why there is such an emphasis on the code contributions, even more so than managing or other roles in open source. Code is a very visible contribution, easy to hold up and say look what they did. Other roles aren’t so easy to hold up, how can someone hold up the hours they spent finding sponsors or perfecting documentation.   The discussion turns to mental health in open source. Laura talks about her own state of mind and how hard it can be to get herself to do anything when she is feeling burnt out. She explains that she needs to change the way she approaches work.  The panel discusses ways that we can help those experiencing mental health problems in open source. They suggest talking to each other more about their experiences, about what depression, anxiety, and burn out look like and how they affect different people. The panel discusses what processes can be put in place to help developers to avoid burn out.    The panel wonders if developers are susceptible to mental health problems. Do the large workloads and high amounts of stress contribute to these issues. Laura explains that in her opinion, we as humans tend to think that our experience is unique, so other industries probably feel the same way. The reality is that this is a worldwide problem, especially for those that Laura calls knowledge workers.     The panel considers other ways we can help open source maintainers not get burnt out. The power of gratitude is one way they think might help. Laura thinks that getting a thank you from supports is very important. She relates how she feels when she talks with participants of Rails Girls Summer of Code and how it makes all her hard work worth it.   The panel discusses the power of money in open source, explaining why they started codefund. They explain the benefits of open source getting some money for their contributions. They consider the effect it plays on burn out. While Laura agrees to receive funds for open source contributions can be helpful, she warns that it could be a double-edged sword.   She warns that the receiving fund could be adding more stress to open source because of the responsibility it adds. Laura explains that she has already started to see entitlement from open source users, getting upset when the maintainer doesn't fix something right away. The panel considers how these benefits and costs when the funding is anonymous compared to when it is a direct sponsorship.   Panelists Eric Berry Nate Hopkins Guest Laura Gaetano Sponsors   DevEd Podcast The Freelancers Show My Ruby Story CacheFly Links AlterConf Berlin 2017: Making your voice heard: Open Source Needs You by Laura Gaetano Laura Gaetano - Building inclusive Open Source communities | ReasonConf 2018 https://devchat.tv/ruby-rogues/ https://railsgirlssummerofcode.org/  https://opensourcediversity.org/  https://www.codenewbie.org/podcast/rails-girls-summer-of-code  https://github.com/about/diversity  https://twitter.com/natfriedman/status/1157379019878232064  https://m.signalvnoise.com/to-smile-again/  https://twitter.com/alicetragedy https://github.com/alicetragedy https://www.facebook.com/Sustain-Our-Software-SOS-857471391289849/ https://twitter.com/sos_opensource Picks Eric Berry: https://webflow.com/  Nate Hopkins: https://www.metabase.com  Willow Hybrid Tree  Laura Gaetano: Jocelyn K. Glei  The Bulletin Design for Real Life

Developer Avocado, serial conference organizer, Rails Girls veteran. Show Notes Rails Girls (http://railsgirls.com/) ROSS Conf (https://www.rossconf.io/) vienna.rb (https://www.meetup.com/vienna-rb/) Rayta van Rijswijk (https://www.parallelpassion.com/9) Amsterdam.rb (https://amsrb.org/) EuRuKo 2019 (https://euruko2019.org/) EuRuKo 2019 has been shipped, sealed, delivered (https://medium.com/@euruko/euruko-2019-has-been-shipped-sealed-delivered-74f7c72baa08) White Coat Captioning (https://whitecoatcaptioning.com/) Stenotype keyboard (https://en.wikipedia.org/wiki/Stenotype) Rails Girls Summer of Code (https://railsgirlssummerofcode.org/) Recommendations Having a family Rails Girls Floor Drees Twitter (https://twitter.com/floordrees) Personal Page (https://floor.dev/) Parallel Passion Patreon (https://www.patreon.com/parpaspod) Twitter (https://www.twitter.com/parpaspod) Instagram (https://www.instagram.com/parpaspod) Facebook (https://www.facebook.com/parpaspod) Credits Edwin Andrade (https://unsplash.com/@theunsteady5) for the header photo Tina Tavčar (https://twitter.com/tinatavcar) for Parallel Passion logo Jan Jenko (https://twitter.com/JanJenko) for intro/outro music

MEMO 2019 年 4 月 4 日に収録しました

Show Notes Springfestival (https://springfestival.at/) Rails Girls (http://railsgirls.com) Dom im Berg (https://www.telegraph.co.uk/travel/galleries/worlds-coolest-underground-attractions/dom-im-berg--graz--austria/) Moderat (https://moderat.fm/) Deadmau5 Studio Tour (https://www.youtube.com/watch?v=dBiqFNNfudA) Kraftwerk (https://en.wikipedia.org/wiki/Kraftwerk) Floor Drees (https://twitter.com/FloorDrees) ROSS conf (https://www.rossconf.io/) Rayta van Rijswijk (https://www.parallelpassion.com/9) Piotr Szotkowski (https://www.parallelpassion.com/14) EuRuKo 2019 (https://euruko2019.org/) Rails Girls Summer of Code (https://railsgirlssummerofcode.org/) Facebook pays teens to install VPN that spies on them (https://techcrunch.com/2019/01/29/facebook-project-atlas/) Zuckerberg Plans to Integrate WhatsApp, Instagram and Facebook Messenger (https://www.nytimes.com/2019/01/25/technology/facebook-instagram-whatsapp-messenger.html) Spotify to acquire Gimlet and Anchor (https://investors.spotify.com/financials/press-release-details/2019/Spotify-Announces-Strategic-Acquisitions-to-Accelerate-Growth-in-Podcasting/default.aspx) Signal (https://signal.org/) Solid (https://solid.mit.edu/) diaspora* (https://diasporafoundation.org/) Mastodon (https://joinmastodon.org/) Your Apps Know Where You Were Last Night, and They’re Not Keeping It Secret (https://www.nytimes.com/interactive/2018/12/10/business/location-data-privacy-apps.html) You (https://www.netflix.com/si/title/80211991) Recommendations The Subtle Art of Not Giving a F*ck (https://www.amazon.com/o/ASIN/0062457713/parpaspod-20) Time Well Spent (https://www.youtube.com/watch?v=tf9ZhU7zF8s) The National (https://en.wikipedia.org/wiki/The_National_(band)) Sebastian Gräßl Twitter (https://twitter.com/bastilian) Instagram (https://instagram.com/bastilian) SoundCloud (https://soundcloud.com/bastilian) Personal Page (https://bastilian.me/) Parallel Passion Patreon (https://www.patreon.com/parpaspod) Twitter (https://www.twitter.com/parpaspod) Instagram (https://www.instagram.com/parpaspod) Facebook (https://www.facebook.com/parpaspod) Credits James Owen (https://unsplash.com/@jhjowen) for the header photo Tina Tavčar (https://twitter.com/tinatavcar) for Parallel Passion logo Jan Jenko (https://twitter.com/JanJenko) for intro/outro music

Samstagmorgen in der Münchner Innenstadt, hoch oben über der Bummelmeile, in einer großen, offenen Büroetage. Hier treffen sich 20 Frauen, die programmieren lernen wollen, mit fast ebenso vielen Coaches, die ihnen das beibringen. Es findet ein Rails Girls-Workshop statt. Einmal im Jahr stellt der Verein diese Frauen-Coding-Seminare auf die Beine, sucht Sponsoren, Coaches, Räume. Die Frauen können den Kurs kostenlos besuchen und bekommen an nur einem Tag die Grundlagen der Programmiersprache Ruby on Rails beigebracht. Wir sprechen mit Teilnehmerinnen, Coaches und mit einer der Organisatorinnen, Larissa Schappach, über die Idee der Rails Girls und warum es mehr Frauen in IT-Berufen braucht.

Show Notes Hello Ruby (https://www.helloruby.com/) Rails Girls (http://railsgirls.com/) Karri Saarinen (https://karrisaarinen.com/) Ruby Heroes 2013 (https://rubyheroes.com/heroes/2013) Rails Girls Summer of Code (https://railsgirlssummerofcode.org/) Codecademy (https://www.codecademy.com/) Hello Ruby Kickstarter (https://www.kickstarter.com/projects/lindaliukas/hello-ruby) Hello Ruby: Expedition to the Internet (https://www.amazon.com/o/ASIN/1250195993/parpaspod-20) Bubble Sort Zines (https://shop.bubblesort.io/) TED Talk: A delightful way to teach kids about computers (https://www.ted.com/talks/linda_liukas_a_delightful_way_to_teach_kids_about_computers) Eat and Run: My Unlikely Journey to Ultramarathon Greatness (https://www.amazon.com/o/ASIN/0544002318/parpaspod-20) Footnotes: How Running Makes Us Human (https://www.amazon.com/o/ASIN/1250127246/parpaspod-20) What I Talk About When I Talk About Running (https://www.amazon.com/o/ASIN/0099526158/parpaspod-20) Recommendations Follow your curiosity Seeing Is Forgetting the Name of the Thing One Sees (https://www.amazon.com/o/ASIN/0520256093/parpaspod-20) Björk (https://en.wikipedia.org/wiki/Bj%C3%B6rk) Linda Liukas Personal Page (http://lindaliukas.com/) Twitter (https://twitter.com/lindaliukas) Instagram (https://www.instagram.com/lindaliukas) Parallel Passion Patreon (https://www.patreon.com/parpaspod) Twitter (https://www.twitter.com/parpaspod) Instagram (https://www.instagram.com/parpaspod) Facebook (https://www.facebook.com/parpaspod) Credits Tina Tavčar (https://twitter.com/tinatavcar) for the logo Jan Jenko (https://twitter.com/JanJenko) for the music

Saudações Bughunters! Nesse episódio falamos um pouco sobre um assunto bastante importante: Mulheres no mercado de TI! Contamos neste cast com duas convidadas incríveis e com bastante experiência para dar os seus pontos de vista, expor informações, e muito mais sobre o tema! Links relacionados: Rails Girls: http://railsgirls.com/ QA Ladies: http://www.qaladies.com/ PYLadies: http://brasil.pyladies.com/ Girls in Tech: https://brazil.girlsintech.org/ Linkedin: Mari: https://www.linkedin.com/in/mariana-elisa-moises/ Iná: https://www.linkedin.com/in/inaray-santos/ João (D. Pedro): https://www.linkedin.com/in/joaolfc/ Lucas: https://www.linkedin.com/in/lucas-santos-ctfl-ctfl-at-ctal-ta-5630578a/

Show Notes Kickboxing (https://en.wikipedia.org/wiki/Kickboxing) Raspberry Pi (https://www.raspberrypi.org/) Homebridge (https://github.com/nfarina/homebridge) Coding bootcamp (https://en.wikipedia.org/wiki/Coding_bootcamp) Rubber duck programming (https://en.wikipedia.org/wiki/Rubber_duck_debugging) Rails Girls (http://railsgirls.com/) Amsterdam.rb (http://amsrb.org/) ROSS Conf (https://www.rossconf.io/) exercism (http://exercism.io/) Homebrew (https://brew.sh/) Slovenia Ruby User Group (http://www.rug.si/) TEDxAmsterdamWomen (http://www.tedxamsterdamwomen.nl/) Social credit ranking system in China (http://www.businessinsider.com/china-social-credit-system-punishments-and-rewards-explained-2018-4) Recommendations The Cost of Sugar (https://www.amazon.com/o/ASIN/1908446277/parpaspod-20) Alex Cross by James Patterson (http://www.jamespatterson.com/alex-cross) Black Mirror (https://www.netflix.com/title/70264888) Rayta van Rijswijk Twitter (https://twitter.com/raytalks) Instagram (https://www.instagram.com/raytalks/) Personal Page (https://raytalks.github.io/) Parallel Passion Patreon (https://www.patreon.com/parpaspod) Twitter (https://www.twitter.com/parpaspod) Instagram (https://www.instagram.com/parpaspod) Facebook (https://www.facebook.com/parpaspod) Credits Tina Tavčar (https://twitter.com/tinatavcar) for the logo Jan Jenko (https://twitter.com/JanJenko) for the music

Rails Girls и въведението в програмирането; CoderDojo и обучението по програмиране с Мартина Колева. Ресурси: https://www.facebook.com/RailsGirlsSofia/ https://www.facebook.com/railsgirlsvratsa/ https://www.coderdojo.bg/ Можете да ни намерите като Sonar Cast във всички социални мрежи или да ни оставите гласово съобщение в https://anchor.fm/sonar-cast Сонар Каст е подкаст на български за бизнес, технологии и влиянието им. Още подкасти на български от мрежата на ПроКастърс: https://www.procasters.co Абонирайте се за подкаста и споделете с приятели!

Panel: Charles Max Wood Guest: Aysegul Yonet This week on My Angular Story, Charles speaks with Aysegul Yonet. Aysegul is a Google developer expert for the Angular team and she works for Narwhal (Nrwl), which is a consulting company that helps big teams build their Angular applications. She first got into programming because she was interested in animation and coding made some aspects of this easier to create. They talk about how she found Angular, the importance of teaching and finding the right resources, and what she is working on now. In particular, We dive pretty deep on: Episode 58 Adventures in Angular Episode 151 Adventures in Angular Aysegul intro How did you first get into programming? Studied graphic design Interested in animation Started writing scripts and websites Python for scripting Hack Reactor Coding to enhance what she already loved Had a goal in mind from the beginning How did you find Angular? First project as a developer with Angular Teaching for Women Who Code Rails Girls at Google I/O What did you do to advance your skills? Teaching to learn yourself The importance of conferences Finding the right resources How to become a GDE? What are you most proud of in your career? Augmented reality What are you working on now? Continuous integration And much, much more! Links: Nrwl Angular Nx Episode 58 Adventures in Angular Episode 151 Adventures in Angular Python Hack Reactor Women Who Code Rails Girls Google I/O GDE @AysSomething Aysegul’s GitHub Nrwl’s GitHub Picks: Charles Don’t lose sight of the important things in life Get your loved ones to talk about themselves on video Aysegul 3JS-AR AngularDoc.io

Panel: Charles Max Wood Guest: Aysegul Yonet This week on My Angular Story, Charles speaks with Aysegul Yonet. Aysegul is a Google developer expert for the Angular team and she works for Narwhal (Nrwl), which is a consulting company that helps big teams build their Angular applications. She first got into programming because she was interested in animation and coding made some aspects of this easier to create. They talk about how she found Angular, the importance of teaching and finding the right resources, and what she is working on now. In particular, We dive pretty deep on: Episode 58 Adventures in Angular Episode 151 Adventures in Angular Aysegul intro How did you first get into programming? Studied graphic design Interested in animation Started writing scripts and websites Python for scripting Hack Reactor Coding to enhance what she already loved Had a goal in mind from the beginning How did you find Angular? First project as a developer with Angular Teaching for Women Who Code Rails Girls at Google I/O What did you do to advance your skills? Teaching to learn yourself The importance of conferences Finding the right resources How to become a GDE? What are you most proud of in your career? Augmented reality What are you working on now? Continuous integration And much, much more! Links: Nrwl Angular Nx Episode 58 Adventures in Angular Episode 151 Adventures in Angular Python Hack Reactor Women Who Code Rails Girls Google I/O GDE @AysSomething Aysegul’s GitHub Nrwl’s GitHub Picks: Charles Don’t lose sight of the important things in life Get your loved ones to talk about themselves on video Aysegul 3JS-AR AngularDoc.io

Panel: Charles Max Wood Guest: Aysegul Yonet This week on My Angular Story, Charles speaks with Aysegul Yonet. Aysegul is a Google developer expert for the Angular team and she works for Narwhal (Nrwl), which is a consulting company that helps big teams build their Angular applications. She first got into programming because she was interested in animation and coding made some aspects of this easier to create. They talk about how she found Angular, the importance of teaching and finding the right resources, and what she is working on now. In particular, We dive pretty deep on: Episode 58 Adventures in Angular Episode 151 Adventures in Angular Aysegul intro How did you first get into programming? Studied graphic design Interested in animation Started writing scripts and websites Python for scripting Hack Reactor Coding to enhance what she already loved Had a goal in mind from the beginning How did you find Angular? First project as a developer with Angular Teaching for Women Who Code Rails Girls at Google I/O What did you do to advance your skills? Teaching to learn yourself The importance of conferences Finding the right resources How to become a GDE? What are you most proud of in your career? Augmented reality What are you working on now? Continuous integration And much, much more! Links: Nrwl Angular Nx Episode 58 Adventures in Angular Episode 151 Adventures in Angular Python Hack Reactor Women Who Code Rails Girls Google I/O GDE @AysSomething Aysegul’s GitHub Nrwl’s GitHub Picks: Charles Don’t lose sight of the important things in life Get your loved ones to talk about themselves on video Aysegul 3JS-AR AngularDoc.io

Lucas (Twitter) ist Senior Consultant bei INNOQ. Podcasts sind ihm nicht fremd: so ist er Host beim CaSE Podcast, dem INNOQ Podcast und der Nerdkunde. Lucas arbeitet mit Ruby und weiß auch davon zu überzeugen. Wir sehen uns erstmal an, worum es sich bei Ruby eigentlich handelt. Im Anschluss gibt Lucas mir einen Überblick über Buildtooling und Dependencymanagement in Ruby mit Bundler, Rake und Capistrano. Wenn ihr libraries oder Frameworks für Ruby sucht, schaut Euch mal https://www.ruby-toolbox.com an. Testen ist im Ruby Umfeld ein wichtiges Thema: Hier habt ihr die Wahl zwischen minitest und RSpec. Wenn ihr oft mit APIs arbeitet, lohnt vielleicht ein Blick auf VCR und webmock. Ein ganz populärer Teil aus der Ruby Welt ist Ruby on Rails und Lucas erklärt mir, was die Idee hinter dem Framework ist und wie man es ideal einsetzt. Das populäre "How to build a blog in 15 minutes with Rails" Video findet ihr bei YouTube unter https://www.youtube.com/watch?v=Gzj723LkRJY. Eine Nummer kleiner als Ruby on Rails ist übrigens Sinatra, gerade, wenn ihr nur eine API aufbauen wollt. Am Ende kommen wir noch auf die Rails Girls, das CoderDojo Cologne und Jugend hackt zu sprechen: alle drei Projekte freuen sich über jede helfende Hand. Also wenn ihr Zeit habt, schaut Euch die drei Projekte doch mal genauer an. Wenn ihr mit Ruby starten wollt empfiehlt Lucas Euch http://tryruby.org/. Für den Einstieg in Ruby on Rails könnt ihr Euch http://www.railstutorial.org/ (auch kostenlos) ansehen.

Linda Liukas is a children's book author and the creator of Hello Ruby, a book that teaches children about the whimsical world of computers, technology and coding. Hello Ruby was the first children's book that raised $380,000 on Kickstarter and is published in over 24 languages today. In our conversation, we talk about how Linda's early adventures on the Internet have shaped her creativity, how she built Rails Girls into a global movement that teaches women how to code, the process of funding a book through Kickstarter and her thoughts on dealing with criticism, maximizing freedom and living a fulfilled life.

Iniciamos el directo del 3 de diciembre con Rail Girls venezuela de la mano de Betsabeth Torres. Esta omunidad de chicas que brinda espacio para experimentar con tecnologías libres. Ayudando a reducir la brecha de mujeres en el área tecnológica.

This week on My Ruby Story, Charles speaks with Allison McMillan. Allison is a software developer at Collective Idea, a software consulting company that solves real-world software problems. Allison is very excited about working on a number of projects and learning new things in the development world. Allison was a recent guest on Ruby Rogues and will be a speaker at Ruby Dev Summit coming up on October 16-21, 2017. In this episode we learn more about Allison’s journey as a startup founder, to make a career change to a developer, all while and making a name in the dev community and gaining a dev job. Allison talks about her involvement and contributions to the Ruby community. In particular, we dive pretty deep on: Allison got into programming working as a non-profit executive and dealing with change in the organization. Getting in involve  in the DC Tech Community  Joining the Rails Girls Workshop Got her first job by attending the Ruby Conf. at the Scholar Guide Program Working Remotely as a junior developer Doing light talks at Ruby Conf. to gain authority Allison mentions doing conference speaking and organizing as apart of contributing to the Ruby community Allison’s favorite thing to speak about at conferences involves writing interactive workshops. Links: DC Tech Community  Rails Girls http://rubyconf.org/scholarships Blog site - DayDreams In Ruby @allie_p Ruby Dev Summit  - Free Picks:  Allison Hello Ruby by Linda Liukas Baking - SmittenKitchen Charles GitLab Server MatterMost

This week on My Ruby Story, Charles speaks with Allison McMillan. Allison is a software developer at Collective Idea, a software consulting company that solves real-world software problems. Allison is very excited about working on a number of projects and learning new things in the development world. Allison was a recent guest on Ruby Rogues and will be a speaker at Ruby Dev Summit coming up on October 16-21, 2017. In this episode we learn more about Allison’s journey as a startup founder, to make a career change to a developer, all while and making a name in the dev community and gaining a dev job. Allison talks about her involvement and contributions to the Ruby community. In particular, we dive pretty deep on: Allison got into programming working as a non-profit executive and dealing with change in the organization. Getting in involve  in the DC Tech Community  Joining the Rails Girls Workshop Got her first job by attending the Ruby Conf. at the Scholar Guide Program Working Remotely as a junior developer Doing light talks at Ruby Conf. to gain authority Allison mentions doing conference speaking and organizing as apart of contributing to the Ruby community Allison’s favorite thing to speak about at conferences involves writing interactive workshops. Links: DC Tech Community  Rails Girls http://rubyconf.org/scholarships Blog site - DayDreams In Ruby @allie_p Ruby Dev Summit  - Free Picks:  Allison Hello Ruby by Linda Liukas Baking - SmittenKitchen Charles GitLab Server MatterMost

This week on My Ruby Story, Charles speaks with Allison McMillan. Allison is a software developer at Collective Idea, a software consulting company that solves real-world software problems. Allison is very excited about working on a number of projects and learning new things in the development world. Allison was a recent guest on Ruby Rogues and will be a speaker at Ruby Dev Summit coming up on October 16-21, 2017. In this episode we learn more about Allison’s journey as a startup founder, to make a career change to a developer, all while and making a name in the dev community and gaining a dev job. Allison talks about her involvement and contributions to the Ruby community. In particular, we dive pretty deep on: Allison got into programming working as a non-profit executive and dealing with change in the organization. Getting in involve  in the DC Tech Community  Joining the Rails Girls Workshop Got her first job by attending the Ruby Conf. at the Scholar Guide Program Working Remotely as a junior developer Doing light talks at Ruby Conf. to gain authority Allison mentions doing conference speaking and organizing as apart of contributing to the Ruby community Allison’s favorite thing to speak about at conferences involves writing interactive workshops. Links: DC Tech Community  Rails Girls http://rubyconf.org/scholarships Blog site - DayDreams In Ruby @allie_p Ruby Dev Summit  - Free Picks:  Allison Hello Ruby by Linda Liukas Baking - SmittenKitchen Charles GitLab Server MatterMost

Tweet this Episode Allison is a developer in the Washington DC area. She is a non-profit executive turned developer. She helps organize the RubyConf and RailsConf Scholar Program. She organizes a local meetup call Silver Spring Ruby. She works at Collective Idea. The Rogues talk to Allison about being a mom in coding and work-life balance.  They also talk about transitioning from non-profits to coding.  This episode goes into depth on: Prioritizing your family and still having a great career Goal setting, focus, and growth Team collaboration Contributing to open source and much, much more... Links: Delayed Job Allison's Blog Baby Driven Development talk Rails Girls Ruby Dev Summit RSpec Minitest RailsCasts Interactor Gem Leah Silber from Tilde tweet Tilde article on Baby at Work Mother Coders RailsBridge Allison on Twitter Picks: Eric: Gallup Strengths Test Metabase Allison: Sticky Note Game by TableXI WriteSpeakCode Ruby Jewel Crystal DISC Assessment Dave Rails Guides

Tweet this Episode Allison is a developer in the Washington DC area. She is a non-profit executive turned developer. She helps organize the RubyConf and RailsConf Scholar Program. She organizes a local meetup call Silver Spring Ruby. She works at Collective Idea. The Rogues talk to Allison about being a mom in coding and work-life balance.  They also talk about transitioning from non-profits to coding.  This episode goes into depth on: Prioritizing your family and still having a great career Goal setting, focus, and growth Team collaboration Contributing to open source and much, much more... Links: Delayed Job Allison's Blog Baby Driven Development talk Rails Girls Ruby Dev Summit RSpec Minitest RailsCasts Interactor Gem Leah Silber from Tilde tweet Tilde article on Baby at Work Mother Coders RailsBridge Allison on Twitter Picks: Eric: Gallup Strengths Test Metabase Allison: Sticky Note Game by TableXI WriteSpeakCode Ruby Jewel Crystal DISC Assessment Dave Rails Guides

Tweet this Episode Allison is a developer in the Washington DC area. She is a non-profit executive turned developer. She helps organize the RubyConf and RailsConf Scholar Program. She organizes a local meetup call Silver Spring Ruby. She works at Collective Idea. The Rogues talk to Allison about being a mom in coding and work-life balance.  They also talk about transitioning from non-profits to coding.  This episode goes into depth on: Prioritizing your family and still having a great career Goal setting, focus, and growth Team collaboration Contributing to open source and much, much more... Links: Delayed Job Allison's Blog Baby Driven Development talk Rails Girls Ruby Dev Summit RSpec Minitest RailsCasts Interactor Gem Leah Silber from Tilde tweet Tilde article on Baby at Work Mother Coders RailsBridge Allison on Twitter Picks: Eric: Gallup Strengths Test Metabase Allison: Sticky Note Game by TableXI WriteSpeakCode Ruby Jewel Crystal DISC Assessment Dave Rails Guides

Linda Liukas is a programmer, programming instructor, a children’s book author and an entrepreneur. She’s the founder of the international Rails Girls community for girls and women who want to learn coding. She’s also the author of best-selling children’s book Hello Ruby, which she financed through a super successful Kickstarter campaign in 2014. Since then she has published two more Ruby books. Last spring she attended the TED conference Residency program in New York City and also won the largest design prize in China, the DIA Gold award. Linda’s task is to increase the number of creators in the world by democratizing programming. In this episode we discuss why learning coding is so important, and what is the role of programming in designing the future. Why does Linda think programmers need to get smarter - and fast? She also tells us the story behind Rails Girls community and how it spread rapidly all around the world, why is open-air karaoke cool and about her enormous crush on Al Gore.

Juuso saa vieraakseen palkitun ohjelmoijan ja lastenkirjailijan Linda Liukkaan. Linda Liukas on ohjelmoija, kirjailija, kuvittaja ja puhuja. Hänet tunnetaan muun muassa Rails Girls -järjestön yhtenä perustajana. Rails Girls se järjestää tytöille ja naisille työpajoja joissa opetellaan koodaamaan. Linda itse alkoi opetella koodaamista 13-vuotiaana. Lindan palkittu Hello Ruby -lastenkirjasarja kertoo teknologiasta, tietokoneista ja koodaamisesta. Kirja on ollut suosittu, ei vain Suomessa, vaan myös esimerkiksi Japanissa. Viime vuonna Hello Ruby voitti Kiinan suurimman muotoilupalkinnon. Nyt julkaistaan kirjasarjan uusin osa jonka keskiössä on netti. Kohtaamisia syvässä päässä. Juuso Pekkinen etsii suurempaa ymmärrystä ympäröivästä todellisuudesta. Hydraatiota intohimoiseen tiedonjanoon maanantaista keskiviikkoon kello kymmenestä yhteentoista.

Eberhard Wolff talks with Ute Mayer about Rails Girls. Topics include how Rails Girls increase diversity in IT and thereby influence the live of the attendees. Rails Girls is a global movement and does workshops to introduce women to programming. Attendees can then join project groups to work on specific projects and apply for the Rails Girls Summer of Code to develop open source projects. The training material is free and open source - and includes information how to start a Rails Girls group. There are many way to support: Rails Girls is looking for coaches and sponsors.

Merrin Macleoad from Rails Girls to talk about Kiwi Ruby about the upcoming conference she is organising.We go into what Ruby (est 1993) is and how it fits into the Dev world.Mike and Merrin also geek out on a few languages they learnt back in the day.Kiwi Ruby is about a mixture of local and international speakers, a day of workshops and one single-track day of talks. The will cover topics that interest, excite, and delight Rubyists and the Ruby-curious of all levels.It's being held on Thursday 2 November (workshops) and Friday 3 November (conference) at Te Papa on the Wellington waterfront.------------------------------------------------------We share New Zealand tech, social media, startup people's stories. If you have a story or know someone that does - get in touch!Mike’s (@MiramarMike) background is explaining stuff, connecting people and getting things done. Raj’s (@nzRaj) background is in video, design, media and making things happen.www.accessgranted.nzhttps://twitter.com/AccessGrantedNZhttps://www.facebook.com/AccessGrantedNZ

This week on Byte Into IT we have Warren, Jo and Cade in the studio talking about recent news in technology, the internet, gaming, computing and art.We had two guests in the studio this week,Linda Liukas, the founder of Rails Girls & part of the fusion of art and technology talk at NGV comes in to discuss those projects with the crew.Alex Yabsley, stage name Dot.AY, chiptune producer and musician, talks with us about the upcoming Square Sounds festival in Melbourne and the process of writing chiptune music.

Summary Allison McMillan (@allie_p) and Bradley Schaefer (@soulcutter) talk about remote work in the age of Slack. What makes a good remote worker, or a good remote working team? How can you support more junior team members who want to work remotely? How do you email cake to remote workers on launch celebration day? How can you improve code review for remote workers? Guests Allison McMillan: Software Developer at Collective Idea (http://collectiveidea.com/) and Rails Girls (http://railsgirls.com/) Bradley Schaefer: Senior Developer at Table XI (http://www.tablexi.com/) and the RSpec (https://github.com/rspec) Core Team Show Notes 01:07 - Working Remotely: Getting Started, Setups, etc. Allison McMillan: Even the Justice League Works Remotely @ RubyConf 2016 (https://www.youtube.com/watch?v=d7Z0uS2x_cY) 03:19 - Coworking Spaces STARTMART (http://startmart.us/) 04:34 - What makes an individual successful to be able to work remotely? 07:30 - Gains and Challenges of Working Remotely 10:18 - Transitioning From Onsite to Offsite Work 11:48 - Being the Only Remote Person: How can companies help remote workers feel included? Slack (https://slack.com/) Know Your Company (http://www.knowyourcompany.com) 21:10 - Building Trust Between Companies and Remote Workers 24:30 - Working Remotely in Other Fields First 25:42 - Working Remotely as a Newbie 30:08 - Cultivating Teams and Positivity - rubocop (https://github.com/bbatsov/rubocop) Tips & Resources: Allison: Schedule weekly pairing sessions and make it a goal to ask questions. Zach Holman: Remote-First vs. Remote-Friendly (https://zachholman.com/posts/remote-first/) SheNomads (http://www.shenomads.com/) Bradley: Try to find pairing tools that work well for you. Remote: Office Not Required (https://www.amazon.com/Remote-Office-Required-Jason-Fried/dp/0804137501) Special Guests: Allison McMillan and Bradley Schaefer.

Before becoming a developer, Laura had a number of job titles, including music blogger, DJ, and maid. But it was a Rails Girls workshop that brought her back to the world of web that she fell in love with many years ago. Now, as a manger at the Travis Foundation, she gets to help introduce other women to tech through the Rails Girls Summer of Code, one of the many initiatives she runs. She tells us more about what it’s like to be a scholar in the program, the power of doing meaningful work on open source projects, and how she reconnected with the web and became a developer. Show Links Digital Ocean (sponsor) MongoDB (sponsor) Heroku (sponsor) TwilioQuest (sponsor) Girl Develop It Your First PR Katrina Owen Sinatra Google Summer of Code Women Who Code Exercism.io Discourse Fund Club Travis CI Travis Foundation Codeland Conf Codeland 2019

Lydia Guarino @lydiaguarino | data.world | GitHub Shannon Byrne @s_byrne | Blog | GitHub | shannon@emberitas.com Stephanie Riera @stefriera | The Frontside | GitHub Show Notes: 01:23 - Emberitas 02:50 - Developing Curriculum For Women By Women 10:16 - Pairing People Together 12:14 - The Volunteers and Support 18:42 - Getting Women to Attend Meetups 23:20 - Icebreaking Exercises 27:42 - Takeaways From the Event 33:35 - The Future of Emberitas 36:10 - Favorite Parts of the Event Resources: @iheartemberitas Ember ATX Women Who Code The Iron Yard Tilde Women Who Code Austin Slack Community We Speak Too ember-women Transcript: CHARLES: Hello everybody and welcome to The Frontside Podcast Episode 52. We're coming to you live from Frontside HQ where we can help you zero in on that precise experience that you want for your users. So, if that's something that you're interested in, go ahead and reach out to us at Frontside.io. Today, actually we got a pretty large panel today. It's a hardcore Austin posse - Lydia Guarino, Shannon Byrne, and Stephanie Riera. And we're going to be talking about kind of a passion project of theirs called Emberitas. We're going to be digging deep into it. But before we get into that, I want to introduce everybody. Lydia is a product engineer at Data.World which is a social network for your data. It's actually a really cool startup where you can go and you can upload your data and you can see other public data sets and slice and dice them. It's really cool. Shannon, who has been a developer since 2013, is kind of in the startup scene and been ubiquitous certainly in the circles that we've run in here in Austin. And so, her latest gig has been as a code school instructor teaching JavaScript and Ruby on the full stack. And of course, you've heard Stephanie on the podcast many times. She's a developer here at the Frontside. Without further ado, let's talk about Emberitas. What exactly is Emberitas and how did it get started? SHANNON: Emberitas is a 1-day 2-track workshop for teaching Ember to women. Last year, what was it? Like April maybe of last year, or maybe March, we were at an Ember ATX meetup. Brandon and Charles were talking about how to get more diversity into the Ember meetup. And then, of course, Lydia and Stephanie and I, as sort of the token ladies of Ember ATX, kind of huddled in a circle and we talked about how other communities in Austin were doing things. And of course, there's Rails Girls which is a 1-day workshop to teach girls programming through a little bit of Rails. We were like, "Why not do the same thing with Ember?" And so, after that, we just kind of picked up on everything, split up a lot of the work, decided we were going to do it, and made it happen. And we hosted our own 1-day workshop for teaching women who had no knowledge of coding some of the basics of HTML, CSS, and JavaScript through Ember. And then taught other women in town who maybe were using Angular or had some experience with Rails or whatever, but didn't know what Ember was, the basics of Ember, so that they could then take that back to their companies and make more Ember jobs for all of us. CHARLES: For someone who's worked on trainings before and tried to develop them, how challenging was it to develop a curriculum for women -- literally, all spectra of experience with development. It sounds like a difficult task. And I'm curious what considerations did you take in when you were developing this curriculum and what did it encompass? LYDIA: One of the things that we did to make that a little easier on ourselves is we split the workshop into two tracks. We had a beginner track and then we also had an intermediate track. Shannon ran with the intermediate track and I ran with the beginner track with an understanding that for beginners, there's a lot more discussion about some of the basics of web development in general or how you think of a project and how you start with the basic building blocks of HTML and CSS, and then grow into building an application. For the beginner course, what I wanted to focus on was taking those basic building blocks and showing how they can be converted into an application. We actually started with making static web pages and then converted those gradually in pieces into an Ember application. Ember actually makes that pretty straightforward to do because there's such strong conventions that there's obvious places to put all of that information. So, we built everything in HTML and CSS, and then we came back and layered on Ember on top of that but the project was the same in both scenarios. And I'll let Shannon talk a little bit about how she approached the more advance course. SHANNON: For the intermediate course, one of the challenges was that it was very open as to what that would mean. It wasn't intermediate Ember; it was an introduction to Ember for anyone who considered themselves a developer. So we had some people who came in and they had a little bit of JavaScript experience and then we had some people who were already full stack JavaScript developers and then some people who had experience with like an NPC framework. People were kind of coming from all over the place, was my expectation. And so, it was kind of difficult to approach that, to be honest. I wasn't really sure what to do and I had a lot of false starts as, I'm sure, most people do who kind of create tutorials. Now that I'm working on curriculum for a code school, the same thing happens. There's definitely a lot of after the fact, being like 'duh'. Now I know I should have done it this way. But the way that I approached it was really just a result of conversations that Lydia and I had been having for years, which is how there's sort of some unique differences on what we've seen for how women kind of communicate and learn a little bit differently especially when they're in our classes and the experiences cater just to them. So, I just kind of went off of that and said, "Okay, how do I like to learn?" And then kind of applied that to how I developed the curriculum. It was a lot of, "Well, you might think we could do this, but actually that doesn't work. Let's try this." And so you go through it and it's kind of like a lot of false starts, a lot of learning together, a lot of like having these tiny little frustrations that you normally have when you're coding, and then achieving something together. And so the ultimate goal of both the beginner curriculum and the intermediate curriculum was not to teach everybody everything about Ember in one day, but to give them the confidence that they could go out and do whatever they wanted with Ember or just explore more about development in general, after that workshop. CHARLES: That makes me curious, Shannon, if you can unpack that a little bit more. You said that there were challenges and things that you took into account in developing this curriculum that was specifically for an all-woman studentship. Can you elaborate on that? What were some of the concrete things that you made that you custom-tailored? SHANNON: To be completely honest, there weren't a whole lot of things that I could really custom-tailor. It was more just thinking about the things that I had witnessed in terms of working with women specifically, and seriously as a result of the conversations that I've had with Lydia, trying to be much more conversational, trying to allow the questions that generally arose sort of drive what we did instead of being very rigid about how we did it, and the approach that I thought was going to work. And generally, just kind of being like quick on my feet and allowing the course to go at the pace that it should go and not trying to force anything, and really mostly trying to read the room and understand that we might not get to everything in one day. LYDIA: From the very beginning, from the very conception of this idea, we wanted to build something by women for women. And so, it was really important that we chose female instructors which is one of the reasons that Shannon and I volunteered to be the instructors ourselves when maybe we would have wanted to seek someone else to take that piece of it. But this is something that we were personally passionate about and we knew how we learned Ember and how we could translate that into something that would be accessible to the broader community of women in Austin. So, we did some targeting with specific groups in Austin that were women-driven. So, Women Who Code has a big following in Austin and we reached out to that community and we made sure that all of the sessions were, like Shannon mentioned, collaborative. For instance, in the beginner course, everyone worked as partners. You weren't just sitting there by yourself isolated with your own level of knowledge, you have somebody to bounce ideas off of you, you have somebody right next to you to ask your little secretive questions where you're a little embarrassed to raise your hand but you need someone to quick correct you. I also made sure that when I was teaching the course itself, it was less lecture and more tutorial which allowed me to walk around the room and actually speak to each individual pair about where they were in the process. So, instead of losing people throughout the course because they had slipped behind, I knew where everybody was for the entire day. While that slows down the overall speed for some of the faster people, it meant that we didn't have anybody take off at lunchtime which is a problem for a lot of workshops as somebody gets so far behind that they just give up. That was something that we wanted to try really hard to avoid with this particular workshop. SHANNON: Another thing that I want to say, if I can go back and fix my sort of bumbling before about what I specifically did. I thought about something I actually specifically did. In a lot of online tutorials, what I found is that it will tell you to do something but it doesn't quite tell you why. And answering that 'why' question is something that's always really important to me when I'm learning something new, so I added a lot of that into the tutorials that we did. Either out loud I would explain it or I would say, "For anyone who's interested, there's a link in the curriculum that will tell you exactly what that is," a much longer explanation of what a computed property is, why that works, and sort of even some of the internals in JavaScript if people were curious in learning that, to answer that why question for attendees. CHARLES: The 'why' is a question that unfortunately gets such short shrift in almost everything that we do. It's like shocking unless you see the absence of why. The other thing I wanted to ask too, Lydia, was you talked about making sure that everybody was paired up so that nobody got behind. Were you deliberate in kind of making sure? I know you had something like 40 students in the first one, so it can be difficult to kind of assess the skill level of each one. But were you able to be deliberate in those pairings and to kind of match people with a productive set of skills? LYDIA: I think that it's actually a little bit dangerous to have people label themselves before they get into a project. So instead of saying 'hey, if you've had some experience here, maybe work with somebody that's never seen this before', I tried to avoid that. So I actually let them choose their partners -- rather I just assigned them based on where they were sitting in the room. And for any kind of gaps we had there, if I had one pair where those people had way less experience than another group, we had an army of volunteers that were available to come and kind of sit down next to one of the pairs and help them work through the pieces. And I think that that's one of the major things that helped the day running smoothly because instead of having to have me come over and help them over and over again, we had somebody that could kind of more quietly come over and sit down and work through the tougher pieces or if someone got stuck on a bug, help them untangle it. CHARLES: I think that's fantastic because having participated in running trainings before, I know that's one of the biggest challenges of keeping everybody together and moving forward in unison is making sure that everyone can do things like do an npm-install. I had an entire training derailed because one person just could not figure out how do it. It was basically just Brandon and I and it was terrible. I guess the question is how many volunteers did it take to make that go smoothly? And I guess the follow on question is do you think that's indicative of kind of the Ember community at large when you guys proposed this event that you were able to really draw on this large pool of ready volunteers to show up? LYDIA: The volunteers were actually a strategic move that Shannon and I spoke about early on which was that part of what we wanted to do is show how welcoming and how supportive the Ember community in Austin is. And so, most of the volunteers that we had on hand were actually members of Ember ATX that were interested in increasing diversity as well. So these were people that they could meet in events and people that would encourage them to come back to a meetup next month or whatever. And you could see these are like really approachable, fantastic people and they're ready to help and they're excited about having you join our community. To keep it running smoothly, to answer that question, we were kind of split. Shannon's had a little bit more people in it than mine but I ended up having close to 20 people. So I had 10 pairs. I actually had almost as many volunteers as I had pairs. So we had some drifters floating between the two classes. But at any given time, I had at least five people running around the room in addition to myself. So, that's a lot of volunteers to coordinate, but we actually had a lot of support from Ember ATX and from people that really wanted to help out. SHANNON: That's a huge ask to ask 10/15 people to come out for the whole day on a Saturday. Even for attendees, that's a lot to ask people to do. And to have so many people from the Ember community in Austin come out and do that, I don't think -- maybe there was one volunteer, Lydia's husband, who didn't know any Ember. But everyone else was from the Ember community and either did Ember professionally or as a hobby, so it worked out really well like that. I was really glad to see that because the whole reason that I do Ember is because of the people that I met at the Ember meetup and I keep going back. And that warmth that I feel about the Ember community is kind of why I feel so great about doing Ember and why I choose to do Ember professionally is because that feeling that I have kind of follows me around while I code in Ember which is kind of silly. CHARLES: I don't think it's really silly at all. I think that's so much of the pervading narrative is that technology is about technology when in fact it's about people in the community. And I think it's great that kind of almost as just by virtue of holding the event and having those volunteers, what you're giving them is not just a set of tools but also you're kind of giving them a small part, that being the benefit of it is giving them this community. SHANNON: What was really excellent too and I think what made us be able to kind of coordinate with the volunteers really well is that Lydia and I were running the classes but Steph was really in charge of coordinating the day and making sure that things run smoothly and making sure the volunteers knew where they needed to be and where they could be most helpful because our challenge was that we actually were in two different spaces. We were able to get space donated to us by The Iron Yard but the Iron Yard campus in Austin is actually like there's kind of a field between their two locations where the classrooms are and where their main space was. And so, what kind of happened was that without Steph kind of like wrangling the volunteers into the right place, the volunteers were kind of forgetting that there was this kind of second intermediate location to come to. And so, I'm so thankful that she was able to be there and just be focused on coordinating the day of type stuff to make sure that everything ran smoothly. STEPHANIE: Thank you, Shannon. That's so sweet. I did want to make a quick mention about the volunteers. I feel like, especially in our industry, we hear a lot about the "brogrammer" and we give a lot of slack to men, particularly white men in the tech industry. I think it's very important to highlight most of the volunteers that we had were all men. And it's these men that are spending their Saturday there to coach and teach women. I think it's a very beautiful thing to see because a lot of these women, I think, they are intimated by going to meetups and going to hackathons because they feel like it's not an inclusive environment and they can't ask questions in a room full of guys. I think that's indicative of 'that's not always the case'. Yes, there might be a problem in the tech industry but there are also people that care and you can see that through the volunteers. SHANNON: It's no lie that the three of us were really the only girls at Ember ATX until we put Emberitas on. We didn't have a large pool of experienced -- not even experienced Ember developers, but even people who had just sat down to try out Ember in Austin who were female to pull from. And so that was always the go-to was to make this so that we could have this be able to diversify Ember ATX in one way by bringing more women in, but also just to make the community stronger overall. I'll say again the Ember community is far and above the best programming community in Austin and I wanted to make sure that every other girl at least had the opportunity to know why I rave about Ember meetups and the Ember community and everything about Ember. And that doesn't just go for Austin, obviously. To shout out as well to Leah, who already does so much with Women Helping Women in Austin, Tilde actually donated a bunch of extra swag to us from the Ember Conf from last year, Ember Conf 2016. So, that saved us a ton of money that we got to use towards other stuff. And then saving money on that, then we got to do a happy hour after that we also invited sponsors and the rest of the community, too. We had a bunch of Ember community members who weren't able to spend the day with us volunteering but they still came out and had a couple of free drinks and got to chat with all the attendees as well. So overall, the whole day was really fun and full of Ember community members. CHARLES: Personally, I'm so sad that I missed it. I was out of the country although it was on my birthday. So, it was like a good birthday present to know that that was like going on in my community back home. Having not been to so many Ember meetups since, have you all noticed and I guess this is really just kind of a question for the four, have you noticed real traction like an uptick in the number of women in attendance and kind of an increase in that level of interest from women in the community at large? LYDIA: The meetup right afterwards had a pretty major uptick because a lot of the people that had come in through Women Who Code and are already kind of avid meetup goers took a chance and came to the meetup. And I've seen several of them come to a couple of the other ones throughout the year. There's at least two people that I've seen repeat show up a bunch of times. When you've got a meetup of about 40 people and even if you just increase it by two more, that's like actually moving the needle pretty significantly. The trick about increasing diversity, that's a little bit above chicken and the egg problem, is that the best way to get women to attend is to have women attend. And so, you want to have some women in the room when other women come for the first time because then it becomes a welcoming environment and you can start kind of the snowball effect of, "Okay, I'm welcome here. I see that this person is comfortable in this setting. That means that I'm going to have an easy time integrating here as well." SHANNON: The timing in terms of -- if we were to do this again actually, one thing I'd improve is to make sure that all three of us could be at the upcoming Ember meetup and that we plan to do it the week before the Ember meetup, so that energy is high and all that kind of stuff. But I think there was something that prevented each of the three of us from maybe even being at that next Ember meetup which really was not a good idea. Maybe one of the three of us was there. So, that's something that I'd like to improve upon is being more strategic about fulfilling on that goal. And then another thing that I'd like to do as well like we have Women Who Code slack channel here in Austin and we have an Emberitas room now and we do actually chat on there. And I'd like to incorporate that into what we do as well, is having a community for the women who met there to continue speaking online, so that we can develop that community and I can post in there and say, "Ooh, there's an Ember meetup tonight. Let's all go." But I know a lot of them. I think a lot of them went to an event together that I didn't know about. When Yehuda was in town, I think a handful of people talked about going to that and they met up through the Women Who Code Ember room. So, that's cool. CHARLES: That's fantastic. I actually think this is a good opportunity to plug something that I learned about through [Emily], who is Alex's girlfriend, is the WeSpeakToo which I think is another good way. You talked about that Catch 22, the chicken and the egg of the best way to have women to attend is to have women attend. I also think the best way to have women attend is to have women speak. And to see that in terms of leadership, there's representation there. And so, there's a tool that I just found out about that I think is really cool that helps kind of solve that Catch 22 or lower the friction if you were a meetup organizer. You can go and you can find there's a list of women in Austin, it's only in DC and Austin, but it's coupled with an analysis of the ratios of female, male, and non-binary speakers in Austin. There's a signup sheet where you can go if you're a woman or you're non-binary and you can sign up and you can enlist your levels of expertise. And if you're a meetup organizer -- you hear a lot of people say, "Where do I find someone who can speak at my meetup?" And so, that tool exists now. Everything's for Austin. If you go to wespeaktoo.org/austin, there it is. I certainly hope the three of you guys are on that list if you're not already because I've seen each one of you speak and there's a lot to share there with the community. And so, if you're listening too, I think it's also a good resource if you're in the DC area or in Austin area or if you want to bring it to your own city. Anyway, I just wanted to share that as what I thought is a cool tool. SHANNON: And to plug another list too. I have to get the URL, I don't know it off the top of my head. But Leah for Women Helping Women put together a list of female Ember speakers to make that available to all the Ember meetups. But even if you're a non-Ember person, these are a list of really great speakers. Some of them spoke at Ember Conf last year, other people who put in their proposals and then other people who were just like interested in speaking locally. She has that list somewhere and I'll try and find the link to it. CHARLES: I will definitely look for that. The other thing that I wanted to talk about before we moved on was we've talked about how you paired people up, you talked about kind of a tight-knit community you created and they were going not just Ember meetups kind of user group but also the bonds that were formed were maintained as they went to other meetups. When we were talking about this part of the podcast, you mentioned some of the icebreaking exercises that you did but you didn't give any specifics. You didn't give any details. I want to hear about this and I want to hear what the best ones were because I'm so curious. Again, I'll just throw this question up. What was it that you did to kind of break that ice and what were the best results that you saw? SHANNON: The icebreaker was actually a little bit of a happy accident. We had budgeted time for an icebreaker at the beginning and it was something that kept slipping down the priority list until the morning off. And on the morning off, we had discussed different brainstorming ideas beforehand but we hadn't settled on anything. And in the morning off, we were like, "You know what we should do is we should have them as a group act out programming terms or programming concepts." As a group, they had to decide on a way to explain some programming concepts like a wow loop or http or something like that. They had to describe that physically. STEPHANIE: Also, we use HTML too which is a hard one. CHARLES: Did you just write them on cards and hand them out to people? LYDIA: Yes. I literally was scribbling a list as people were walking in of terms that we thought would probably possibly work. And then we've split them up into groups and passed them out. I have to say people came up with the most creative things. It went so much better than I would have ever dreamed. CHARLES: Is any of this on video? What was the best one? SHANNON: I have the wow loop dance. I think it's posted on the Emberitas instagram page that you can all go check out. It was so funny. They all went up there and while one of them was clapping, all the rest of them had a dance. And then when she stopped clapping, they'd stopped dancing. And so, it's really straightforward but it was just hilarious and sort of the big personalities of some of the extroverts in the room were given their chance to shine there in the morning and I was laughing so hard. It went a lot better than I think we expected it to since we had done zero preparation. LYDIA: That said, Shannon put together a fantastic survey at the end so that we can kind of gather feedback on how to make this better in the future. And we had several comments about the icebreakers themselves. And one of the things that we might want to tweak in the future is exactly how we let different people participate in that activity because some people that were a little bit more reserved, a little bit shier like starting out the day with basically public speaking or a performance was a little bit rough. Now, I'm going to argue that when you push somebody out of the comfort zone as soon as they show up for the day, everything else is going to be great because they've already stepped outside of their comfort zone and they've already done the thing that's going to pull them out of their shell and be able to talk to other people in the room. CHARLES: Right. The point of those things is vulnerability and to make it safe to be vulnerable. And so, someone who is definitely in, someone who walks around into these groups as a shell, I definitely see the value in that. SHANNON: The other thing too is one of the positive things about an icebreaker like this is you could kind of take a backseat or kind of [inaudible] off to the side, so we didn't require everyone to say something out loud either. So, there are positives and negatives. I think that was like an overall learning thing about doing this is for me, I definitely am a perfectionist and I want everything to go perfectly and I want everything to be exactly my way. It was learning that no matter how well something goes, you can't please everyone 100%. And getting the feedback on the surveys and just seeing how, for some people, the icebreaker was their favorite part of the day. For other people, it was their least favorite part. Some people wanted more workshop time, other people wanted way less workshop time and to focus more on community building and this and that. And so, we can't please everyone but we've really pulled off something really cool that I think made a lot of the stakeholders very happy. CHARLES: Yeah, definitely, which kind of goes right into my next question which I'm going to ask to all of you is what do you feel are kind of like the key things that you learned from this based on the survey, based on your experience, based on conversations with the participants and observations later on? What was it that you feel like was kind of your biggest takeaway? Why don't we start with you, Lydia? LYDIA: For me, the biggest takeaway was that it really makes such an enormous impact for women to see other women speaking and women putting these types of workshops and things on for other women. That was the one thing that stood out to me the most in the feedback was that people were just so excited to see someone relatable up in front of them giving these presentations. And that having the opportunity to see a room full of women that were interested in the same things that they were interested in was incredibly inspiring and encouraged them to kind of go out on a limb and try something that they hadn't tried before and follow up in the future with more meetups and things like that, which was precisely the goal. I feel like our primary goal was to get women to feel like this was an accessible community and I feel like that was where we excelled the most. CHARLES: How about you, Stephanie? STEPHANIE: I wanted to piggy back off of what she just talked about because I, myself, we just touched on something earlier and it was about the feeling of being uncomfortable. It's no secret that and I said it there, I hate public speaking. Absolutely hate it, it terrifies me. I hate doing podcasts, I hate doing all kinds of speaking. But I realized how important it is. And then as Shannon was saying like you can plan and you want to try as hard as you can to make everything go as smoothly and perfect as possible, but sometimes things will happen. And I remember at one point of the day, she came up to me and asked me a favor and was like, "Hey…" She had been emceeing all day and asked, "Do you mind doing the middle part?" And I think it was talking about Ember ATX and why it was important to do this workshop and all of that. So I was caught completely unprepared and I was very hesitant. But in that moment, I thought to myself, "Well, we are choosing to be leaders in the community. We are choosing to put ourselves out there and do something for the greater good. I'm just going to do it. I'm just going to force myself to do it." I think it went well. The first bit of it, I was very nervous and I just admitted it to everyone. But someone else came up to me afterwards and told me, "I think it meant a lot to people to see someone just take something on and speak from their heart, and you can see that they're so nervous but they're still doing it." And so, that's the point I wanted to make was yes, I'm uncomfortable with it but it's the only way you can grow as an individual. I also want to send a message through that which is yes, we're all women, we're all bad ass, we all have this purpose that we want to achieve and we're doing it. So, that was my biggest takeaway. So, thank you, Shannon, for that unexpected request. SHANNON: Yeah. That kind of came as a result of like I was trying to emcee and teach and I went up to Steph and she was like, "I'm nervous!" And I was like, "Look, I need to lay down. I've been talking all day. My brain is mushed." And she did such a great job and I was so happy that you did that. For me, I would say Lydia definitely covered all of the philanthropic reasons that this is important and why it went so well and everything that was great. For me, I think that I had been going through some stuff. Like sometimes I question - am I really good at what I'm doing? Am I doing the right thing? Can I accomplish this? The sort of questions that everybody has. Taking this on and sort of planning it from start to finish on our own, doing all the marketing, getting all the sponsorships, getting all the attendees, communicating with all the attendees, trying to pretend that we were kind of more official than we were. I was individually texting people to their numbers and it would be like, "Reply with STOP if you no longer want these texts." Just to make it look like we were something official when really like I'm copying and pasting from one person to the next. And we're trying to get literally everything done, just the handful of us that were working on this. It made me start thinking about what do I really want to do. I had never truly considered teaching other people to code until this. And now, I'm trying that out. Since then, through Emberitas, we've done another lecture series for high schoolers. We did a weekend workshop for high school girls and honestly, it opened up something in me and I was like, "We need to be teaching high school-aged kids to code." I know that's something that a lot of organizations are trying to do but I now have a very specific idea of how I want to approach that. It really gave me a lot of confidence that I really needed at the time. I think that I threw myself so hard into doing Emberitas was because I needed something to really be passionate about it at the time. And then it gave back to me everything that we put into it and I was so fortunate for that. Just to watch everyone having such a good time and everyone learning something and just the look on someone's face when they get something and then the look of someone's face when they make something is so cool. And that's just what I loved about this whole experience. CHARLES: Yeah. It sounds wonderful. Here we are in 2017, what's next? Are there any further events that we can look forward to? Are there any grand plans? I mean, you kind of alluded to some of that, doing more education for targeting a younger age group? What can we look forward to? Why don't we start with, Shannon? What can we look forward to in 2017?
SHANNON: What you can look forward to in 2017 is me updating the website a little bit. It's still the typo-ed place it was at the very last day before the workshop. So, I need to update that so that people can get more information and contact us if they're interested because I have had a lot of people reach out to me over Twitter, through our Facebook page, all that kind of stuff, asking when we're going to do this again, and if we're going to do it in other cities than Austin. What was really cool was all of our curriculum is open source, so we put that out there and we told on our Twitter that people could check out our curriculum. And one morning, we just started getting ding…ding….ding…ding…ding…all of these GitHub pull requests from people in Seattle. And it turned out that a code school in Seattle was using it as part of their curriculum. And so, a couple of those girls reached out and we're like, "Oh, we might be interested in posting one of these in Seattle." And so, hopefully doing something like that would be really fun. Additionally, just kind of improving the curriculum. We need to sit down and kind of click out the best things about how we approach doing the beginner curriculum, the best things about how we approach doing the intermediate curriculum, and sort of entwine those together. So, a lot of kind of behind the scenes work to get things in place and then a lot of planning to put on the next one. And so, the biggest thing that limits us from putting on more is money. We need sponsors and we kind of already hit up everybody who does Ember here in Austin. So, we're going to have to expand our reach if we want to put on another one of these at the same quality that we did before. CHARLES: So, you heard it here. If you're interested in seeing this happen, by all means, reach out and send money. SHANNON: Yeah. CHARLES: Lots of money. SHANNON: You can email me: Shannon@emberitas.com, if you want to talk about any of those things. Or hit up our Twitter or our Instagram. Yeah, there's place to contact us if you're interested in helping us out in any way. STEPHANIE: And it's also important to point out that a lot of those sponsors gave lightning talks. SHANNON: Yup. STEPHANIE: So, you can have your plugs in there. SHANNON: Yeah. You can show up and have a captive audience for five minutes. CHARLES: Alrighty. In closing, again, I want to kind of go around and ask what was the number one -- we talked about kind of mistakes that were made, things that were learned. In terms of the number one impactful thing that you feel like this event had and this kind of process had either for the external world or even for the internal world, like affecting the way that you work day to day. What has that been? What has that been for you, Lydia? LYDIA: My favorite part of the entire thing was that some of my best friends and I decided to build a thing that we cared about. And then we watched it grow into something amazing, and then we got to see the people that got to enjoy the beautiful thing that we built. It was just one of those moments where you feel really proud about deciding to take a risk and deciding to kind of put yourself out there and do something that is outside of your comfort zone that makes it totally worthwhile and makes it so that you want to do it again, and again, and again. And I'm just really grateful that Shannon and Steph thought this was a cool idea and just had to make it a real thing. SHANNON: I was just thinking, as usual Lydia says it best. That's exactly what was so great about it was we did it together, it was great, we want to do it again, we want other people to do it. There's something so inherently rewarding about this experience and it was just so much fun. And I'm so glad that I got to do it with the two of these guys. CHARLES: Yeah. I think just kind of watching from the sidelines, just the energy that it generated. I think it touched everybody who participated, who volunteered, and even people like me who just kind of watched it from the sidelines as part of the general community. And so, I am really looking forward to what you guys are going to bring in the future. And I really hope that you don't allow it to just fall by the wayside and that there is some continuance of it. And I promise I will participate this time. But thank you, thank you, thank you so much for doing that. It really was wonderful. Thank you all for coming by and sharing the story of Emberitas. You can find them on Emberitas.com or if you want to reach out directly over Twitter, it's @iheartemberitas. Hopefully, we get to hear from you and we'll continue the discussion. And thank again. Thanks everybody for listening and thanks to you guys for coming. SHANNON: Thanks for having us.

Olá pessoal e sejam bem-vindos à mais um episódio do Castálio Podcast! Nossa convidada de hoje atualmente trabalha como programadora na Stone Pagamentos, é voluntária das PyLadies Brasil, Django Girls e Rails Girls. Além disso tudo, ela também palestrou nos eventos CaiPyRa, Python Brasil, ganhou o Prêmio Dorneles Tremea, é …

Mlade producentkinje, sa dugogodišnjim iskustvom – Bojana Milašinović i Sandra Tomić, inicijatorke su Rails Girls Beograd zajednice i osnivačice organizacije Spacevent. Međusobnu saradnju započinju još tokom studija produkcije na FDU, učestvujući u organizaciji bojnih kulturno-umetničkih događaja, da bi 2013. godine sa Rails Girls zajednicom ušle u svet IT-a. Kako je tekao njihov razvojni put, o prednostima i manama njihove profesije, šta sve obuhvata rad na jednom dugoročnom projektu, koji su im dalji planovi, ali i zašto nakon brojnih IT radionica koje su organizovale, još uvek nisu postale programerke, saznaćete u opuštenom prolećnom razgovoru, koji se odigrao ovih dana u studiju KCCK.

The Travis Foundation. Interview with Laura Gaetano Links and things we talked about: Travis Foundation (http://foundation.travis-ci.org) Open Source Grants (http://foundation.travis-ci.org/grants/) The Foundation's support of Katrina Owen from exercism.io (http://foundation.travis-ci.org/2016/01/25/exercism/) Exercism.io (http://Exercism.io) Rails Girls summer of code (http://railsgirlssummerofcode.org/campaign/) Diversity Tickets (http://diversitytickets.org) Conference support Speakerinnen (http://speakerinnen.org) Prompt (http://mhprompt.org/)

Een speciale gast uit Finland in de podcast deze keer: Linda Liukas, oprichter van Rails Girls en maker van het kinderboek Hello Ruby. Dat boek vertelt een sprookje over programmeren voor jongens en meisjes vanaf 5 jaar. Duizenden euro's verdienen met gamen, dat dat kan is niet nieuw, maar hoe ziet het leven van zo'n gamer eruit? Bas Tooms volgde een Nederlandse gamer voor NRC en moest er zelfs voor naar Berlijn. En een Nederlands drone-raceteam staat in de finale van de eerste grote drone-prix in Dubai. Prijzengeld: 230.000 euro. Lars Dellemann sprak met ze voor NOS op 3.

Linda Liukas identifies more with being a children’s author than a developer. That might be because she’s spent a good amount of time helping others learn to code than actually coding herself. She used to work for Codecademy, started Rails Girls, and most recently launched a Kickstarter campaign for a book introducing programming to children. The campaign blew past it’s $10K goal, and reached over $380K. Linda talks to us about drawing and writing the book, Hello Ruby, and what she’s learned about the coding journey as she helps kids start their own. Show Links Digital Ocean (sponsor) MongoDB (sponsor) Heroku (sponsor) TwilioQuest (sponsor) Rails Girls Codecademy Hello Ruby Hello Ruby Kickstarter Codeland Conf Codeland 2019

02:26 - Aimee Knight Introduction Twitter GitHub Blog Message Systems 02:48 - Figure Skating => Programming Persistence Balance Between Mind and Body 05:03 - Blogging (Aimee’s Blog) 06:02 - Becoming Interested in Programming Treehouse @treehouse Code School @codeschool Rails Girls @railsgirls RailsBridge @railsbridge 08:43 - Why Boot Camps? 10:04 - Mentors Identifying a Mentor Continuing a Mentorship 13:33 - Picking a Boot Camp 16:23 - Self-Teaching Prior to Attending Boot Camps 20:33 - Finding Employment After the Boot Camp Baltimore NodeSchool Passion Interview Prep 26:27 - Being a “Woman in Tech” 30:57 - Better Preparing for Getting Started in Programming Be Patient with Yourself 32:07 - Interviews Getting to Know Candidates Coding Projects and Tests 41:05 - Should you get a four-year degree to be a programmer? Eliza Brock Picks Aarti Shahani: What Cockroaches With Backpacks Can Do. Ah-mazing (Jamison) Event Driven: How to Run Memorable Tech Conferences by Leah Silber (Jamison) The Hiring Post (Jamison) Kate Heddleston: Argument Cultures and Unregulated Aggression (Jamison) Axios AJAX Library (Dave) Unbroken: A World War II Story of Survival, Resilience, and Redemption by Laura Hillenbrand (Dave) [YouTube] Good Mythical Morning: Our Official Apocalypse (AJ) Majora's Mask Live Action: The Skull Kid (AJ) The Westin at Lake Las Vegas Resort & Spa (Joe) Alchemists (Joe) Valerie Kittel (Joe) The Earthsea Trilogy: A Wizard of Earthsea; The Tombs of Atuan; The Farthest Shore by Ursula K. Le Guin (Chuck) Traction: Get a Grip on Your Business by Gino Wickman (Chuck) Freelancers’ Answers (Chuck) Drip (Chuck) Brandon Hays: Letter to an aspiring developer (Aimee) SparkPost (Aimee) Exercise and Physical Activity (Aimee)

02:26 - Aimee Knight Introduction Twitter GitHub Blog Message Systems 02:48 - Figure Skating => Programming Persistence Balance Between Mind and Body 05:03 - Blogging (Aimee’s Blog) 06:02 - Becoming Interested in Programming Treehouse @treehouse Code School @codeschool Rails Girls @railsgirls RailsBridge @railsbridge 08:43 - Why Boot Camps? 10:04 - Mentors Identifying a Mentor Continuing a Mentorship 13:33 - Picking a Boot Camp 16:23 - Self-Teaching Prior to Attending Boot Camps 20:33 - Finding Employment After the Boot Camp Baltimore NodeSchool Passion Interview Prep 26:27 - Being a “Woman in Tech” 30:57 - Better Preparing for Getting Started in Programming Be Patient with Yourself 32:07 - Interviews Getting to Know Candidates Coding Projects and Tests 41:05 - Should you get a four-year degree to be a programmer? Eliza Brock Picks Aarti Shahani: What Cockroaches With Backpacks Can Do. Ah-mazing (Jamison) Event Driven: How to Run Memorable Tech Conferences by Leah Silber (Jamison) The Hiring Post (Jamison) Kate Heddleston: Argument Cultures and Unregulated Aggression (Jamison) Axios AJAX Library (Dave) Unbroken: A World War II Story of Survival, Resilience, and Redemption by Laura Hillenbrand (Dave) [YouTube] Good Mythical Morning: Our Official Apocalypse (AJ) Majora's Mask Live Action: The Skull Kid (AJ) The Westin at Lake Las Vegas Resort & Spa (Joe) Alchemists (Joe) Valerie Kittel (Joe) The Earthsea Trilogy: A Wizard of Earthsea; The Tombs of Atuan; The Farthest Shore by Ursula K. Le Guin (Chuck) Traction: Get a Grip on Your Business by Gino Wickman (Chuck) Freelancers’ Answers (Chuck) Drip (Chuck) Brandon Hays: Letter to an aspiring developer (Aimee) SparkPost (Aimee) Exercise and Physical Activity (Aimee)

02:26 - Aimee Knight Introduction Twitter GitHub Blog Message Systems 02:48 - Figure Skating => Programming Persistence Balance Between Mind and Body 05:03 - Blogging (Aimee’s Blog) 06:02 - Becoming Interested in Programming Treehouse @treehouse Code School @codeschool Rails Girls @railsgirls RailsBridge @railsbridge 08:43 - Why Boot Camps? 10:04 - Mentors Identifying a Mentor Continuing a Mentorship 13:33 - Picking a Boot Camp 16:23 - Self-Teaching Prior to Attending Boot Camps 20:33 - Finding Employment After the Boot Camp Baltimore NodeSchool Passion Interview Prep 26:27 - Being a “Woman in Tech” 30:57 - Better Preparing for Getting Started in Programming Be Patient with Yourself 32:07 - Interviews Getting to Know Candidates Coding Projects and Tests 41:05 - Should you get a four-year degree to be a programmer? Eliza Brock Picks Aarti Shahani: What Cockroaches With Backpacks Can Do. Ah-mazing (Jamison) Event Driven: How to Run Memorable Tech Conferences by Leah Silber (Jamison) The Hiring Post (Jamison) Kate Heddleston: Argument Cultures and Unregulated Aggression (Jamison) Axios AJAX Library (Dave) Unbroken: A World War II Story of Survival, Resilience, and Redemption by Laura Hillenbrand (Dave) [YouTube] Good Mythical Morning: Our Official Apocalypse (AJ) Majora's Mask Live Action: The Skull Kid (AJ) The Westin at Lake Las Vegas Resort & Spa (Joe) Alchemists (Joe) Valerie Kittel (Joe) The Earthsea Trilogy: A Wizard of Earthsea; The Tombs of Atuan; The Farthest Shore by Ursula K. Le Guin (Chuck) Traction: Get a Grip on Your Business by Gino Wickman (Chuck) Freelancers’ Answers (Chuck) Drip (Chuck) Brandon Hays: Letter to an aspiring developer (Aimee) SparkPost (Aimee) Exercise and Physical Activity (Aimee)

02:32 - Mark Bates Introduction Twitter GitHub Blog Boston Ruby Users Group @bostonrb MetaCasts: HD Screencasts for GO Enthusiasts @metacasts   03:14 - Scott Feinberg Introduction Twitter GitHub Blog WePay @WePay @wepaystatus 03:46 - Community Values 2014 Videos - WindyCityRails Lightning Talks (Scott’s is first) Scott Feinberg: Where does Ruby go from here? (The Happiness Manifesto) [GitHub] the-happiness-manifesto   05:32 - Ruby Community Standards and Values Testing Programming Should Be Fun and Enjoyable Pairing Large Regional Conferences and Meetups     07:33 - User Groups Lambda Lounge @LambdaLounge Netflix Open Source Group 10:18 - Polyglot Conferences Midwest.io 2014 - MythBashers: Adventures in Overlooked Technologies - Avdi Grimm [GitHub] A web server written in Bash Great Wide Open @AllThingsOpen CodeMash @codemash 13:07 - Including and Getting Newbies Involved in Conference and Community Culture Generations Boot Camps Launch Academy @LaunchAcademy_ Hugs 20:41 - Diversity and Codes of Conduct PyLadies PyLadies Chapters (Twitter) RailsBridge @railsbridge Rails Girls @railsgirls 23:08 - AlterConf @AlterConf Ashe Dryden @ashedryden 24:22 - PyCon @pycon 25:31 - HappinessConf @Happiness_Conf   Diversity Black Girls Code @blackgirlscode Women Who Code @WomenWhoCode 28:30 - Developer Happiness and Invoking Community Values Within Corporate Company Culture Ruby Rogues Episode #191: The Developer Happiness Team with Kerri Miller PluralSight PluralSight Author Summit Trust Roles of Influence Navigating Office Politics 38:03 - Agile Software Development and Productivity The 4 Disciplines of Execution: Achieving Your Wildly Important Goals [TED Talk] Bruce Feiler: Agile programming — for your family   40:41 - “The Ruby Diaspora” Mark Bates - Panel: The Future of Ruby - Burlington Ruby Conference 2014 Elixir Programming Elixir: Functional |> Concurrent |> Pragmatic |> Fun by Dave Thomas The Go Programming Language Gophercon @GopherCon 47:47 - Acceptance Accepting Acceptance / Tolerating Intolerance 50:55 - Mentoring Boston Ruby’s “Project Night” Mentor Someone Who Doesn’t Look Like You Picks Love Letter (Coraline) RescueTime (Coraline) Hacking Happy by Dusty Phillips (Jessica) Happiness Conf Coupon Code (Scott) HappinessConf Speakers Page (Scott) The Flight Deal (Scott) iStat Menus (Scott) HappinessConf (Mark) The Go Programming Language (Mark) Use the Coupon Code: ROGUES to get your first month free: MetaCasts.tv: HD Screencasts for GO Enthusiasts (Mark)

02:32 - Mark Bates Introduction Twitter GitHub Blog Boston Ruby Users Group @bostonrb MetaCasts: HD Screencasts for GO Enthusiasts @metacasts   03:14 - Scott Feinberg Introduction Twitter GitHub Blog WePay @WePay @wepaystatus 03:46 - Community Values 2014 Videos - WindyCityRails Lightning Talks (Scott’s is first) Scott Feinberg: Where does Ruby go from here? (The Happiness Manifesto) [GitHub] the-happiness-manifesto   05:32 - Ruby Community Standards and Values Testing Programming Should Be Fun and Enjoyable Pairing Large Regional Conferences and Meetups     07:33 - User Groups Lambda Lounge @LambdaLounge Netflix Open Source Group 10:18 - Polyglot Conferences Midwest.io 2014 - MythBashers: Adventures in Overlooked Technologies - Avdi Grimm [GitHub] A web server written in Bash Great Wide Open @AllThingsOpen CodeMash @codemash 13:07 - Including and Getting Newbies Involved in Conference and Community Culture Generations Boot Camps Launch Academy @LaunchAcademy_ Hugs 20:41 - Diversity and Codes of Conduct PyLadies PyLadies Chapters (Twitter) RailsBridge @railsbridge Rails Girls @railsgirls 23:08 - AlterConf @AlterConf Ashe Dryden @ashedryden 24:22 - PyCon @pycon 25:31 - HappinessConf @Happiness_Conf   Diversity Black Girls Code @blackgirlscode Women Who Code @WomenWhoCode 28:30 - Developer Happiness and Invoking Community Values Within Corporate Company Culture Ruby Rogues Episode #191: The Developer Happiness Team with Kerri Miller PluralSight PluralSight Author Summit Trust Roles of Influence Navigating Office Politics 38:03 - Agile Software Development and Productivity The 4 Disciplines of Execution: Achieving Your Wildly Important Goals [TED Talk] Bruce Feiler: Agile programming — for your family   40:41 - “The Ruby Diaspora” Mark Bates - Panel: The Future of Ruby - Burlington Ruby Conference 2014 Elixir Programming Elixir: Functional |> Concurrent |> Pragmatic |> Fun by Dave Thomas The Go Programming Language Gophercon @GopherCon 47:47 - Acceptance Accepting Acceptance / Tolerating Intolerance 50:55 - Mentoring Boston Ruby’s “Project Night” Mentor Someone Who Doesn’t Look Like You Picks Love Letter (Coraline) RescueTime (Coraline) Hacking Happy by Dusty Phillips (Jessica) Happiness Conf Coupon Code (Scott) HappinessConf Speakers Page (Scott) The Flight Deal (Scott) iStat Menus (Scott) HappinessConf (Mark) The Go Programming Language (Mark) Use the Coupon Code: ROGUES to get your first month free: MetaCasts.tv: HD Screencasts for GO Enthusiasts (Mark)

02:32 - Mark Bates Introduction Twitter GitHub Blog Boston Ruby Users Group @bostonrb MetaCasts: HD Screencasts for GO Enthusiasts @metacasts   03:14 - Scott Feinberg Introduction Twitter GitHub Blog WePay @WePay @wepaystatus 03:46 - Community Values 2014 Videos - WindyCityRails Lightning Talks (Scott’s is first) Scott Feinberg: Where does Ruby go from here? (The Happiness Manifesto) [GitHub] the-happiness-manifesto   05:32 - Ruby Community Standards and Values Testing Programming Should Be Fun and Enjoyable Pairing Large Regional Conferences and Meetups     07:33 - User Groups Lambda Lounge @LambdaLounge Netflix Open Source Group 10:18 - Polyglot Conferences Midwest.io 2014 - MythBashers: Adventures in Overlooked Technologies - Avdi Grimm [GitHub] A web server written in Bash Great Wide Open @AllThingsOpen CodeMash @codemash 13:07 - Including and Getting Newbies Involved in Conference and Community Culture Generations Boot Camps Launch Academy @LaunchAcademy_ Hugs 20:41 - Diversity and Codes of Conduct PyLadies PyLadies Chapters (Twitter) RailsBridge @railsbridge Rails Girls @railsgirls 23:08 - AlterConf @AlterConf Ashe Dryden @ashedryden 24:22 - PyCon @pycon 25:31 - HappinessConf @Happiness_Conf   Diversity Black Girls Code @blackgirlscode Women Who Code @WomenWhoCode 28:30 - Developer Happiness and Invoking Community Values Within Corporate Company Culture Ruby Rogues Episode #191: The Developer Happiness Team with Kerri Miller PluralSight PluralSight Author Summit Trust Roles of Influence Navigating Office Politics 38:03 - Agile Software Development and Productivity The 4 Disciplines of Execution: Achieving Your Wildly Important Goals [TED Talk] Bruce Feiler: Agile programming — for your family   40:41 - “The Ruby Diaspora” Mark Bates - Panel: The Future of Ruby - Burlington Ruby Conference 2014 Elixir Programming Elixir: Functional |> Concurrent |> Pragmatic |> Fun by Dave Thomas The Go Programming Language Gophercon @GopherCon 47:47 - Acceptance Accepting Acceptance / Tolerating Intolerance 50:55 - Mentoring Boston Ruby’s “Project Night” Mentor Someone Who Doesn’t Look Like You Picks Love Letter (Coraline) RescueTime (Coraline) Hacking Happy by Dusty Phillips (Jessica) Happiness Conf Coupon Code (Scott) HappinessConf Speakers Page (Scott) The Flight Deal (Scott) iStat Menus (Scott) HappinessConf (Mark) The Go Programming Language (Mark) Use the Coupon Code: ROGUES to get your first month free: MetaCasts.tv: HD Screencasts for GO Enthusiasts (Mark)

We, as developers, consume so much information. We read blogs, use our social media to get the latest happenings, follow startup & corporate companies in the news, and we pull in so many libraries and frameworks that power our applications and reduce the amount of work we need to do. Many of us take it for granted that the libraries, frameworks, gists, codepens, blog posts, screencasts, podcasts, & books we consume are all someone elses hard work. That work probably required a lot of time & energy but more importantly, those community contributors took the mindset that others could benefit from their work. Why would they make it a priority to spend the extra time and effort doing this when they have their own deadlines & their own struggles? Surely these people must be crazy, right? Perhaps this is true...but what if it's not?   Who are the people that create for us? Why do they do it? What can we gain in our own work by delivering our own content to others? How can we help contribute? These are only a few of the questions that tend to surface when we discuss the topic of contributing to the community. Episode 30 takes a strong & hard look at the reasons why we produce content and why we consume it. More importantly, we talk to the benefits developers can gain by both producing & consuming code and content in their own work.   Levent Gurses (@gursesl), mobile developer and founder of Movel, talks with us about his experiences running meetups, building software in the open, and sharing with the community. Movel is a mobile product & services company that specializes in building scalable corporate Resources Github - https://github.com Anvil Connect Id Server - http://anvil.io CodePen -  http://codepen.io Assembly - https://assembly.com/ Gist - https://gist.github.com/ The Web Animation Newsletter -  http://webanimationweekly.com Movel - http://movel.co Mobile DC - http://www.meetup.com/mobile-dc/ Code For DC - http://codefordc.org/ Code School - https://www.codeschool.com Code Academy - http://www.codecademy.com/ Khan Academy - https://www.khanacademy.org/ Rails Girls - http://railsgirls.com/ Hack Reactor - http://www.hackreactor.com/ Girl Develop It - http://www.girldevelopit.com/ egghead.io - http://egghead.io Lets Code Javascript - http://www.letscodejavascript.com/ Panelists   Erik Isaksen - UX Engineer at3Pillar Global Christian Smith - Open Source Developer & Startup Enthusiast Danny Blue - Front End Engineer at Deloitte Digital Rachel Nabors - Web Animation Developer Advocate & Founder of TinMagpie

Спонсор выпуска — Vexor CI – облачный continuous integration сервис для ruby разработчиков с поминутной оплатой. С учетом поминутной оплаты, Vexor очень выгоден для маленьких проектов и эффективен для больших. Каждому новому пользователю предоставляется $10 на счет для экспериментов. Попробовать Vexor CI Расшифровки Коллекция рецептов для быстрого руби от Эрика. Интервью с Эриком Кир Первый раз в Москве? Эрик Ага, да. Кир И как тебе Москва, что думаешь о городе? Эрик Очень красивый город. Первый раз тут, и мне все очень нравится. Погода хорошая; вчера гуляли, были в музее космонавтики и в музее холодной войны — было здорово. Кир Круто. Эрик Ага. Кир Так вот. Ты работаешь в SoundCloud, в Берлине? Эрик Да! Кир Можешь рассказать об архитектуре SoundCloud? Эрик Так, в SoundCloud мы используем архитектуру микросервисов. Я работаю в команде, которая занимается платформой, проще говоря — серверным API. Публичный API — который используется, если использовать SoundCloud API — там запросы обрабатываются Rails приложением. Но вот как мы работаем.. Как только у нас появляются новые сервисы, и есть смысл их как-то отделить от основного, сделать их отдельным сервисом — мы так и делаем. В общем, мы используем Ruby, Rails, еще довольно много используем Scala, Clojure; все наши утилиты командной строки написаны на Go. Да, у нас даже сервисы на Julia есть. Все зависит от того, что лучше подойдет для задачи, которую мы пытаемся решить. Кир Интересно. То есть, как я понимаю, вы мигрировали с монолитного Rails приложения, да? Эрик Да! Думаю, многие компании, когда они развиваются и начинают масштабироваться, переходят с такой монолитной архитектуры приложения на архитектуру микросервисов. И да, мы довольно далеко в этом деле продвинулись. Кир Ясно. Давай поговорим про open source, над которым ты работал — какой проект твой любимый? Эрик Ох, их много — сложно выбрать. Не знаю, некоторые обертки над API, над которыми я работал — таких было несколько.. Я сделал octokit, обертку над API GitHub; еще обертку над API RubyGems.org, чтобы можно было доставать метаданные о gem'ах. Ну и, наверное, самая популярная обертка, которую я сделал — gem twitter. Да и gem soundcloud, я его сейчас поддерживаю, но автором был не я. Да, думаю, решать проблемы такого рода, причем несколько раз для разных сервисов, стало таким неплохим шаблоном, так что я горжусь теми gem'ами. Думаю, приемы работы над кодом, которые я использовал там, приводят к коду довольно чистому, хорошо покрытому тестами, и все такое. И, знаешь, наверное самый популярный мой gem — это rails_admin, там код и близко не такой чистый, так что для меня над ним не так приятно работать по этой причине. Каждый раз, когда с ним работаю, всегда нахожу какие-то вещи, которые стоит зарефакторить; но раз уж столько людей его используют, просто приятно было сделать что-то такое — люди постоянно ко мне подходят, благодарят. Так что им приятно заниматься по другой причине — не из-за красоты кода, а из-за пользы, которую он дает. Кир Понятно. А что вообще помогает тебе работать над новыми open source проектами? Эрик Ну, думаю, как и у всех — главная причина, наверное, в том, что когда я использую какой-то проект и нахожу баг, я вкладываюсь в проект просто чтобы пофиксить этот самый баг, или просто в какой-то степени этот проект улучшить. Иногда я начинаю проекты только затем, чтобы чему-то научиться — попробовать в деле новый фреймворк или новый язык; да, в общем, получается такое игрушечное приложение или игрушечная библиотека, и тогда нет причин не выпустить этот код как open source, чтобы другие люди могли учиться так же, как учился я, или научиться чему-то на моих ошибках. Да я и сам учусь на своих ошибках, потому что когда ты выпускаешь что-то как open source, другие люди видят твою работу, присылают пулл-реквесты, чтобы ее улучшить, и каждый раз, когда это происходит — это возможность мне чему-то научиться; другие же люди это увидят и тоже сделают какие-то выводы для себя. Кир Точняк. Ты упомянул, что в SoundCloud используется много разных языков, так вот, есть у тебя какой-то open source не на Ruby? Эрик Да, у нас есть. Кир Scala, Clojure? Эрик Да-да. Посмотри на https://github.com/soundcloud, думаю, у нас там больше сотни публичных репозиториев. И да, там есть проекты на Ruby, наш самый популярный — Large Hadron Migrator, LAM (https://github.com/soundcloud/lhm). Там идея в том, что если у тебя есть действительно здоровенная база данных (MySQL — прим. пер.), и тебе нужно сделать миграцию, с помощью этого проекта можно это сделать без даунтайма. Если на пальцах, он работает вот так: копирует таблицу, прогоняет миграцию на копии, потом на копию переносит все данные, которые скопились с момента начала миграции. Довольно эффективный способ делать миграции в БД. Нам этот проект был реально нужен, у нас были очень большие таблицы в MySQL, на которых нужно было делать миграции, а если мы делали обычные миграции, мы могли попасть на несколько часов даунтайма. Так что мы сделали такой вот инструмент. Другие компании, у которых тоже было много строк в таблицах их баз данных, большие таблицы, и нужно было делать миграции над ними, тоже оценили наше решение. Кир На каком это языке? Эрик На Ruby. Так что да, это в основном для миграций с Rails. Но у нас.. Если посмотреть на https://github.com/soundcloud, у нас есть репозитории почти на всех языках, что можно представить — Ruby, Clojure, Scala, Go.. Как я уже говорил, у нас есть код на Julia, думаю, мы его тоже выложили. Да, ну и на других языках. В SoundCloud мы гордимся тем, что всегда используем лучший инструмент для каждой конкретной задачи, а инженеры принимают решения основываясь на том, что по их мнению лучше всего использовать. Так что если давать инженерам автономию для принятия решений, последуют лучшие решения, чем если в компании просто есть правила — «использовать один язык для всего», или «использовать этот фреймворк для всего». И даже внутри нашей организации, мы иногда используем Rails, иногда Sinatra или другие фреймворки. Это действительно зависит только от характера проблемы, которую мы пытаемся решить. Кир Какое будущее у Ruby, по твоему мнению? Эрик Хм. Хороший вопрос. Надеюсь, что будущее будет таким же, как и прошлое — за последнее время каждый год выходит новая версия Ruby, и каждый раз она быстрее и лучше предыдущей. Так что да, надеюсь, такое продолжится в будущих версиях. Что я действительно хотел бы видеть (я упомянул об этом в своем докладе), так это JIT компилятор в MRI (CRuby). Кажется, над этим уже работают, так что я настроен оптимистично — думаю, скоро мы это увидим. Так же, как и AOT компилятор. Я еще работаю над парой интерфейсов для командной строки; Ruby не очень хорош для работы с командной строкой, потому что время запуска может быть большим, а вот если был бы компилятор, который бы предварительно парсил весь Ruby код в бинарник, было бы круто — особенно для штук вроде CLI (Command-Line Interface — прим. пер.). Так что вот, JIT и AOT компиляторы. И еще получше примитивы для параллелизма. Матц говорил, что он сожалеет о решении использовать Thread как главный примитив для параллелизма в Ruby, так что он вместе с Core Team думает над использованием actors, и может каких-то еще примитивов. Чтобы они появились в core библиотеках языка. Так что я этого очень жду, думаю, будет круто. Кир Да, я заметил тренд с переписыванием инструментов командной строки на Go. Эрик Да, точно. Кир Вот Heroku так делает. Эрик Да, это хороший пример. Их CLI для выполнения разных команд, раньше был на Ruby, но, вообще, думаю, он намного лучше стал на Go, по ряду причин. Во-первых, у Go весь runtime включен в бинарник, так что нет такой зависимости, как Ruby — не надо сначала устанавливать Ruby, а потом уже CLI. Можно просто установить бинарник, в котором все уже есть. Ну и то еще, что можно кросс-компилировать сразу на несколько разных платформ, делает разработку инструментов для командной строки намного проще. И вообще тот факт, что Go — язык компилируемый, означает, что никакой подготовки кода во время запуска нет, как в Ruby. Так что если есть, скажем, 30 библиотек, от которых зависит инструмент, то в Ruby даже для самой простой операции сначала нужно пропарсить все эти библиотеки, а это может занять много времени, особенно если нужно выполнить какую-то простую команду — такую, как help, version или что-то такое, и во многих CLI на Ruby это работает куда медленнее, чем должно бы. Так что AOT компилятор существенно этому поможет, Ruby сможет составить конкуренцию языкам вроде Go в борьбе за CLI. Кир Давай поговорим о Берлине. Эрик Ага. Кир Что ты думаешь о стартап-культуре, об атмосфере? Эрик Очень хорошая. Я переехал в Берлин из Сан-Франциско, где я до этого прожил 8 лет. И в Сан-Франциско чувствуется такое отношение, словно это единственное место в мире, где можно сделать стартап, и что если тебе нужно сделать стартап, то нужно переехать в Сан-Франциско, если хочешь добиться успеха. Это сработало для многих компаний, но в SoundCloud нам этого делать не пришлось. Есть много преимуществ работы в Берлине. Главное преимущество — мы можем нанимать талантливых людей со всей Европы, да и со всего мира, вообще говоря. У нас отличный офис, где есть разработчики из.. кажется, 35 разных стран, или вроде того. Думаю, эмиграционные законы США делают такое куда более сложным. У меня был такой скепсис, когда я переезжал из Сан-Франциско, но.. Мои коллеги — невероятно талантливые люди, я каждый день у них чему-то учусь. Да, Берлин — отличное место для работы. И стартап сцена — не только SoundCloud, у нас куча других стартапов! От самых маленьких, где пара человек работают над какой-то идеей, до людей, которые уже подняли венчурный капитал и теперь быстро растут. Да и просто классное сообщество и отношение. Митапы каждую неделю, наверное, даже каждый день — можно ходить на разные технарские митапы в Берлине. И вот что еще круто в Берлине: классное сообщество для тех, кто хочет учиться. То есть, если вы хотите научиться программированию, или если вы пока юниор, и вы ищете возможность подкачаться, Берлин — отличное для этого место. Вот Rails Girls начинались не в Берлине, но благодаря Travis CI, да, там много классных людей — Свен (Sven Fuchs — прим. пер.), Аника (Anika Lindtner — прим. пер.), да и вся команда — Джош (Josh Kalderimis — прим. пер.), Константин (Konstantin Haase — прим. пер.)… Такое комьюнити они создали! Меня пригласили выступить на Eurucamp пару лет назад — тогда я в первый раз оказался в Берлине, еще до того, как я туда переехал. Перед конференцией я побыл коучем на Rails Girls, и это был первый раз, когда я помогал на Rails Girls, и было круто. Но, думаю, Rails Girls проводятся в Берлине уже очень давно, теперь и Summer of Code проводится оттуда. Есть целые четыре разные команды Summer of Code, которые расположены в Берлине. Так что вот, это отличное место для того, чтобы научиться программированию и прокачаться. Кир Все, спасибо большое! Эрик Да, конечно. Спасибо за вопросы! Интервью с Божидаром Ярослав Привет, Божидар! Как тебе Москва? Божидар Все здорово. Фантастический город, счастлив, что я здесь и что меня пригласили. Это мой первый визит в Россию, для меня все в новинку и очень увлекательно. У вас прекрасный город, прекрасная страна. Ярослав Первый вопрос будет про Rubocop. Многие из наших ребят знают о gem parser нашей местной знаменитости, Петра (Зотова — прим. пер), который, кстати, выступал в прошлом году на этой самой конференции. Можешь рассказать немного о том, как parser и Rubocop работают вместе? Божидар Да, конечно. Когда я начал работать над Rubocop, я использовал Ripper, внутренний парсер MRI, у которого есть две фундаментальные проблемы: во-первых, он работает только с MRI, что сделало бы Rubocop несовместимым с JRuby и Rubinius. Во-вторых, он генерит ужасный AST. Я пытался отправить несколько багфиксов в Ripper, но стало понятно, что это ни к чему не приведет. В одном из сообщений об ошибке, которое я открыл на официальном багтрекере Ruby, кто-то упомянул, что мне лучше бы не использовать Ripper вообще, потому что есть новая библиотека под названием parser от Петра. Я ее посмотрел, она работала замечательно, выдавала отличный формат AST, в общем, делала ровно то, что нужно. Была переносимой, правда очень глючной, но я намеревался работать с ней, несмотря на это. В основном из-за Петра, отличного мейнтейнера. Я зарепортил, наверное, около 50 багов, или вроде того. И он обычно отвечал в течение пары часов. После того, как вышла первая версия Rubycop с использованием parser, обнаружилось еще больше багов — пользователи умудрялись писать такой Ruby код, что мы даже не знали о том, что так можно написать. Но в течение следующих релизов Петр все исправил, и я уверен, что это лучшая библиотека из тех, что существуют. Производительность отличная, почти так же быстро, как и с Ripper, но выдаются структуры данных намного проще, с этим намного приятнее работать. Если мне бы пришлось работать с Ripper, я бы, наверное, забросил Rubocop. Ярослав Мы говорим о Ripper, но ведь еще есть gem.. как его.. Божидар ruby_parser? Ярослав Да, ruby_parser. Божидар Да, проблема с ruby_parser была в том, что его не мейнтейнили особенно. Думаю, Петр изначально хотел улучшить ruby_parser (так и было — прим. пер.); он был совместим с Ruby 1.8, но не обновлялся для 1.9. Я видел от него несколько пулл-реквестов, но ребята, которые мейнтейнили ruby_parser, сказали, что изменения слишком сложные, или что-то в этом духе, и что они не будут их применять. Думаю, это и было мотивацией для Петра сделать новый gem. И еще дело было в том, что ruby_parser не был так производителен, как parser, так что при работе с огромными проектами это могло стать проблемой — можно было ждать целый час, пока идет анализ кода. Ярослав Ага. Следующий вопрос про твою самую известную работу — Ruby Guide. Можешь рассказать о процессе, о том как ты работаешь над ним? У тебя просто появился набор каких-то правил, ты сделал первый коммит и потом ты начал их обновлять? Как ты итерируешь, как обновляешь эти правила? Думаешь ли ты, что многие из них обязательные, или какие-то нет? В общем, твой Ruby Style Guide и Rails Style Guide не высечены в камне, они обновляются, так что хочется послушать про процесс. Например, как ты их валидируешь. Божидар Ну, обычно я делаю что-то, что называю проверкой толпой (Crowd Validation). Я добавляю правила иногда, когда натыкаюсь на хорошие идиомы в книгах, докладах; встречаю что-то, чего я раньше не замечал. Если я делаю правки и они не вызывают существенной негативной реакции в сообществе, значит, это и правда хорошая рекомендация. Если я что-то добавляю и все начинают на это жаловаться, значит, я сделал ошибку. Если мнения разделяются, мы начинаем вдаваться в детали. Например, мы делаем поиск по ruby-исходникам на GitHub, и если мы видим, что недавно добавленное или предложенное правило имеет смысл, если большинство отобранных проектов используют это правило, иначе мы его убираем, или правим существующее правило. Это уже много раз случалось. Но, в конце концов, кто-то должен проталкивать эти правила — обычно это не только я; можно видеть, что довольно много людей предлагают новые правила. Но я всегда стараюсь делать проверку, чтобы быть уверенным, что мы не предлагаем что-то, что нарушает сложившиеся практики. Так что если что-то звучит как хорошая идея, но никто ее не придерживается, мы не будем ее рекомендовать. Мы не хотим заставлять кого-то следовать стилю, который не принимается, не является естественным для Ruby сообщества. Ярослав Ясно. А ты начал с своего собственного набора правил, или ты использовал другие источники для вдохновления? Божидар Я начал с правил, которые я собрал из моих любимых книг по Ruby. В основном.. Моя любимая книга по Ruby — это, наверное, “The Ruby Programming Language”.. Ярослав Pickaxe? Божидар Не-не. Это “Programming Ruby”. Ярослав А, другая. Божидар Да. Так вот, я начал с советов из «Библии», то есть, единственной книжки, написанной самим Матцем, по крайней мере, частично. Я детально сверил стиль, который он использует, со стилем, который используется в Pickaxe. Были некоторые различия в верстке кода, например, Матц не использовал столько пустого места, отбивок, как использовал Дейв Томас, а я люблю читаемый код. Так что я взял у Дейва стиль для таких случаев. После этого, я начал добавлять вещи из “Eloquent Ruby”, “The Ruby Way” — книг, которые я считаю каноническими для сообщества. Так что начинал я оттуда, а после первого публичного релиза гайда, я получил массу отзывов — часто с приложенным анализом использования из поиска по GitHub, о котором я уже говорил. Например, все книги утверждали, что стоит избегать использования тернарного оператора, а использовать вместо него if/then/else в одну строку, но оказалось, что ни в одном Ruby проекте такого нет, наоборот, все используют тернарный оператор. Да, так что если люди хотят писать код так, кто я такой, чтобы им запрещать. Так что мы изменили это правило, да и другие правила тоже подверглись изменениям с изначальной версии. Мы обновляем правила все время. Например, когда все начиналось, еще не было Ruby 2.0 и 2.1, так что не было правил о аргументах-ключсловах (keyword arguments), использованию private на той же строке, что и определение метода, потому что это не имело смысла. Но гайд постоянно развивается, и, думаю, чем больше проходит времени, тем больше мы приближаемся к настоящей душе Ruby-стиля. Ярослав Я спрашивал, потому что еще до того, как я увидел твой гайд, был гайд от Кристиана, автора Rack (https://github.com/chneukirchen/styleguide — прим. пер.). Видел его? Божидар Да, видел. Ярослав Я его использовал неоднократно для обучения внутри команды, и только потом увидел твой гайд, который намного больше и подробнее. Божидар Да, я проводил поиски по гайдам. Я видел этот, видел веб-страницу, не помню URL, что-то от zenspider, наверное. Я видел три ресурса, но во всех отсутствовали примеры. Были правила, но без объяснений о том, почему это вообще хорошая идея. Некоторые правила были явно в противоречии с устоявшимися практиками. Это все были попытки, предпринятые одним человеком, больше похожие на личный набор правил. Вместо чего-то, что могло бы использоваться всеми, что и было моей целью. Потому что изначально я занимался документом по заказу компании. И мой проект случайно стал популярным. Ярослав Еще что хочу спросить о твоих гайдах. В каком-то смысле использование гайда по стилю — это как принятие методологии разработки ПО, методологии гибкой разработки ПО, например. Это много как можно сделать — кто-то делает все в точности по правилам, по книге, кто-то начинает использовать некоторые вещи и модифицирует их потом, и получается его собственная методология, и все такое. То есть, одни люди пишут книги, а другие люди просто используют их, как им заблагорассудится. Так как ты думаешь, как лучше всего применять твой гайд, или, может быть, как ты сам его применяешь на своих проектах, когда работаешь консультантом? Ты заставляешь людей ему следовать, или это процесс, шаг за шагом? Божидар Ну, обычно на моих проектах, Ruby Style Guide в его чистой форме дается как правило. Но это правило лишь до какой-то степени; некоторые правила абсолютны — например, не нужно мешать метод и его алиас в проекте, нужно выбрать одно название и использовать его везде. Правила про отступы тоже абсолютны, но, с другой стороны, у нас есть вещи вроде правил по метрикам: короткие методы, короткие классы, и вот они иногда довольно субъективны, нужно идти на нарушение правил: как ни старайся, иногда нельзя раздробить какую-то задачу на больше частей, чем ты уже сделал. Есть точка, после которой попытки упростить что-то просто вредны: больше это не оптимизация, ты уже делаешь код сложнее. Так что.. Есть другие такие правила, которые не следует применять вслепую.. Нужно думать. Я всегда говорю людям: это не десять заповедей, ниспосланные нам свыше. Многие из них — крайне разумные практики, и ничего плохого от их применения не случится, но нужно знать, когда их нарушать, и нужно знать, почему они были хорошей идеей изначально. Не нужно их нарушать, если нет четкой причины это делать. Ярослав Еще вопрос. Посмотрел на твой профиль на GitHub, и оказывается, что ты интересуешься Clojure. Божидар Да-а-а. Ярослав И у тебя даже гайд по стилю для Clojure есть. Не знал раньше. Так вот, в Ruby сообществе много разговоров идет.. В общем, на каждой Ruby конференции по крайней мере в России есть много людей, которым вообще не интересно разговаривать про Ruby, они хотят говорить про Clojure, Scala, функциональные языки, Elixir тоже популярная тема. Так вот, почему именно Clojure? Божидар Ну.. По той же причине, по которой я изначально выбрал Ruby. Я был очарован простотой и мощью языков из семейства Lisp. Когда я был начинающим программистом, я немного писал на Common Lisp. И потом я наткнулся на Ruby, и, хотя он не был Lisp'ом, очевидно, но в нем было много наследия Lisp. И это был язык, для работы на котором я хотя бы нашел людей, готовых мне заплатить. Rails был на волне, все хотели разрабатывать на Rails, веб. Это был хороший компромисс. Но сейчас есть Clojure, настоящий Lisp, со всей мощью, без ограничений Ruby. Все говорят о проблемах с производительностью Ruby, но, думаю, что есть ряд проблем, для которых объектно-ориентированный подход становится «бутылочным горлышком» в архитектуре. Ты сказал об Elixir, еще одном не-ООП языке, который недавно стал набирать популярность. Люди делают на нем классные вещи. Haskell становится популярным после того, как существовал уже 20 лет. Ярослав Да, но есть много людей, которые называют его академическим языком — в противовес Erlang и Clojure. Божидар Ну да, но нельзя отрицать и то, что количество open source проектов, использующих Haskell, выросло в 4 раза за последние пару лет. Не думаю, что люди занимаются на Haskell только исследованиями. Люди используют его для реальной, полезной работы. Есть известные веб-фреймворки для Haskell, его точно используют для решения реальных проблем, а не вычисления чисел Фибоначчи. Так что думаю, что с тем, как мультиядерность становятся нормой, языки, которые могут масштабироваться, языки, на которых можно строить распределенные системы, будут становиться все более и более популярными. А Ruby придется развиваться быстрее, или он потеряет в популярности. То, о чем ты говоришь — что люди на Ruby-конференциях здесь не хотят говорить о Ruby — это не случайность. Если посмотреть на Ruby-конференции в Штатах, например — всегда есть доклады об альтернативных языках. На последней конференции был доклад по Elixir, перед этим Рич Хики собственной персоной докладывался по Clojure на RubyConf (думаю, речь идет о RailsConf'2012 — прим. пер.), а это что-нибудь да значит. И еще нам нужно иметь в виду, что многие известные рубисты забросили Ruby и стали работать на других языках. Например, Аарон говорил о Хосе Валиме.. Ярослав С которого и начался Elixir, ага. Божидар Да. Я почти уверен, что ему Ruby уже не интересен — да, его компания известна среди рубистов, он все еще мейнтейнер Rails и сопутствующих проектов, что нужно для клиентов, но его настоящая страсть — Elixir. Он об этом сам несколько раз говорил. Был еще известный рубист, Фил Хагельберг (@technomancy — прим. пер.), сейчас он один из самых известных кложуристов. Ярослав Да, но он всегда был поклонником Emacs, и поклонником Lisp. Он был главным источником всего, что в Emacs было связано с Ruby. Все люди, которые начинали с Lisp в университете или школе, которые хакали на Emacs долгое время.. У них теперь время возмездия. Божидар Да, но думаю, что Ruby-программистов привлекает мощь всех этих новых альтернативных языков. Думаю, некоторые из хороших идей этих функциональных языков рано или поздно окажутся в Ruby. Я говорил об идее сделать строки иммутабельными, не уверен, как это можно сделать, учитывая что весь код, который зависит от строк, мутабелен, но люди говорят о персистентных структурах данных в Ruby. Матц говорил, что главная фича в Ruby 3.0 — фреймворк для параллелизма, видимо, похожий на actors. Весь мир ПО движется в этом направлении; нельзя отрицать и то, что нельзя бесконечно делать веб-приложения. Ландшафт рынка веб-приложений существенно изменился. Rails стал популярным, когда все веб-сайты были довольно стандартными. Была довольно статичная прослойка для представления, довольно простые модели. И сейчас все дошло до клиентских приложений, когда весь твой фронтенд — это отдельное приложение, а твое Rails-приложение — просто JSON-сервер. И ты начинаешь спрашивать себя — а нужен ли мне Rails только для JSON сервера? Почему бы мне не сделать приложение на чем-то высокопроизводительном — Java, Erlang? Потому что если избавиться от тесной интеграции представлений-моделей в Rails, его ценность резко уменьшается. Думаю, что мир ПО изменяется очень быстро, и сообщество Ruby и Rails должно реагировать мгновенно, или сгинет в геенне огненной. Как и много других классных технологий. Ярослав Депрессивно, но справедливо. Еще вопрос, чтобы не очень долго тебя задерживать. Очевидно, написание правильного Ruby — очень важная тема в эти дни. Ruby вырос, люди должны перестать делать отстойные приложения, чтобы их было проще поддерживать. Один из докладчиков на этой конференции — удаленный докладчик, правда — Сэнди Метц, она тоже рассказывает о способе писать на Ruby правильно, но она делает это с помощью книги. Вот. А у тебя есть гайд, с пятью тысячами вотчеров, кажется, на GitHub, огромное число, я точно не помню, но это все-таки open source проект, у него есть URL, надо ему поставить звездочку. Так вот, есть планы написать книгу? Божидар Да, я об этом говорил на докладе. Я запланировал написать книгу, но потом я стал мейнтейнером Cider, это IDE для Clojure, очень популярная. Пришлось много с этим работать, и это выкачало из меня все силы, которые я откладывал на Rubocop, Ruby Style Guide, Rails Style Guide, и вообще на все связанные с Ruby проекты, потому что очень уж я вдохновлен Clojure. Но моя работа с Cider сейчас в таком состоянии, что я ей более или менее доволен, так что я думаю, что продолжу там, где я остановился. И сделаю маленькую книгу, очень маленькую книгу. Но, думаю, будет здорово, если у всех правил будут описания побольше, примеры подлиннее. В Styleguide я этого сделать не могу — это как README длиной в 50 страниц, это было бы странно. Но, думаю, небольшая книга будет полезна многим. Ярослав Ну что же, удачи в написании книги. Спасибо, что зашел! Божидар Вам спасибо. Мы выражаем огромную благодарность Стасу Спиридонову за помощь с мастерингом этого выпуска.

Highlights of my conversation with Peta Ellis Benefits of working in a co-working space Brisbane tech Start-ups successes Various events held at River City Labs   Mentions River City Labs http://www.rivercitylabs.net/ River City Labs Events / Start-up weekend http://www.rivercitylabs.net/events/ Rails Girls http://railsgirls.com/ Uber https://www.Uber.com/cities/brisbane Ollo Mobile http://ollowearables.com/ Mothers Groupie https://mothersgroupie.com/ Right Pedal Studios http://rightpedalstudios.com/ SydStart http://sydstart.com/                                      Today I am speaking with Peta Ellis the General Manager at River City Labs: Brisbane's premiere Startup Community and Co-working space. Peta has been described as the “hub of the Brisbane start-up community" and was ranked 6 in the Top 50 Global Lean Evangelists, and StartUp Daily listed Peta as a Brisbane mentor all start-ups should get to know. Questions asked: Who is your favourite super hero and why? What is the purpose of River City Labs? What is the catalyst that started River City Labs ? What sort of business does it suit? How will a business benefit from being in a co-working space? When does a business know it is ready to join a co-working space? And where are they coming from? How does the rent a desk concept work, and if we have people listening in from overseas is the rent a desk option open to them too? You run a lot of events at River City Labs: what events have worked really well? And what events unexpectedly bombed? How can someone get in touch with you if they are interested in running an event at River City Labs? What have been some key successes for River City Labs? What have been some obstacles’ the co-working space has faced along the road? How strong is the start-up community in Brisbane? What have you learnt from managing River City Labs?   To get in touch with Peta Ellis http://www.rivercitylabs.net/ Events http://www.rivercitylabs.net/events/   To get in touch with the host of Cloud Stories Heather Smith http://www.heathersmithsmallbusiness.com http://www.twitter.com/heathersmithau http://www.FaceBook.com/heathersmithau   http://www.LinkedIN.com/in/heathersmithau

Sean has a conversation with Terence Lee. Terence is known for his work at Heroku and his open source contributions to Ruby Core, Bundler and Resque.

Sean has a conversation with Terence Lee. Terence is known for his work at Heroku and his open source contributions to Ruby Core, Bundler and Resque.

本期由Terry Tai和Dingding共同主持，邀请了 neo 的美女软件工程师鲁葳，和她一起聊聊软件咨询公司是如何工作的。让大家了解更多的优秀软件咨询公司的细节和内幕。 关于鲁葳： Twitter Blog 访谈笔记 neo Pivotal Labs thoughtbot PivotalTracker University of Waterloo rocketfuel Jim Weirich Pair programming TDD Continuous integration Sublime Text RubyMine Vim Emacs tmux Travis CI Jenkins CI Yehuda Katz Eric Ries Lean UX Rails Girls Remote Pair Programing Blog Customer.io Effective JavaScript Special Guest: 鲁葳.

This week Ben Orenstein is joined by Jeremy McAnally, employee at GitHub, author of Ruby in Practice, Rails 3 Upgrade Handbook, MacRuby in Action, and more. Jeremy and Ben discuss teaching and organizing conferences, remote working for GitHub, the and the company summits, GitHub workflows, their internal tools team. They also talk about standing out from the pack in work, life, and getting accepted to conferences, selecting people to speak at conferences, self-publishing, Jeremy's writing process and future writing plans, work-life balance, how to get a job at GitHub, and much more. MagicRuby Ruby Hoedown La Conf Hubot CodeConf Rails Girls Ruby in Practice MacRuby in Action Rails 3 Upgrade Handbook RedCarpet Markdown parser PrinceXML Securing Rails Seasonal Affective Disorder Follow @thoughtbot, @r00k, and @jm on twitter.