Career Development

Summarized using AI

Why Is Open Source So Closed?

Ra'Shaun Stovall • November 11, 2016 • Cincinnati, OH

In the talk titled "Why Is Open Source So Closed?", Ra'Shaun Stovall addresses the challenges faced by new developers entering the job market, particularly those emerging from bootcamps. He highlights the growing divide between the 'haves' and the 'looking for jobs' in the tech community, advocating for a model of 'Cyclical Mentorship' to support new talent. Stovall uses historical references and personal anecdotes to delve into the complexities surrounding the concept of 'open source' and the term 'free', noting that the interpretation of freedom is often misconstrued. He emphasizes the psychological barriers many developers face, including feelings of inadequacy and the pressures of job supply versus demand.

Key Points Discussed:
- Misconceptions of "Free": The speaker clarifies the multiple meanings of 'free', especially within the context of open source, which can lead to misunderstandings about job opportunities.
- Under-Credentialing Issues: Many bootcamp graduates encounter challenges entering mid-level positions due to perceived lack of experience.
- Psychological Barriers: Developers can impose mental limitations on themselves, complicating their ability to succeed and navigate the job market.
- Historical Context: Stovall cites figures like Dr. Martin Luther King Jr. to highlight the importance of perspective and alternative paths in both tech and broader societal contexts.
- Cross-Technical Collaboration: Stovall urges developers to explore various technologies, underscoring that collaboration nurtures innovation rather than competition.
- Importance of Community: The talk stresses the significance of mentorship and community support through networking and sharing experiences.
- Inclusivity in Open Source: Stovall advocates for welcoming contributions from newcomers, which fosters a supportive and enriching environment for all community members.

Conclusion:
Stovall concludes by reinforcing the importance of pushing through limitations, engaging in conversations, and contributing to the community. He calls on both seasoned developers and novices to embrace opportunities for growth and support one another, encouraging a culture that celebrates learning, collaboration, and progress in the open source landscape.

Why Is Open Source So Closed?
Ra'Shaun Stovall • November 11, 2016 • Cincinnati, OH

RubyConf 2016 - Why Is Open Source So Closed? by Ra'Shaun Stovall

Why is Open Source So Closed? With the rapidly increasing amount of students coming out of bootcamp schools we have now created a gap within our communities of the "haves", and the "Looking for job"s. Being the organizer of New York City's 4,500+ member Ruby community with NYC.rb I have discovered ways we can ensure the generations of rubyists after us have a path paved before them. "Cyclical Mentorship" is the answer. Best part is we will know individually how we can immediately begin the feedback loop of not computers, but people!

RubyConf 2016

00:00:14.760 Hello, everyone! Can we all tighten in a little bit? I have a show that you're going to want to see. You'll be happy to be up here for it. My name is Snugs, and one of the things that we do when we start off our meetups is a little fun activity. Have you all seen this mannequin challenge? People standing still and posing. Well, in New York, we have handstand challenges. Usually, when I come in, there's a bunch of people in front of me who look like they just got off work. I pick them up like this, so here's what we're going to do: Count me down from one, two, three, and on three, I'll go up into a handstand and you guys clap for me like someone's doing a handstand in front of your face.
00:01:37.979 Keep clapping! My yoga teacher is going to be so happy. Thank you so much, that's a nice icebreaker. I feel good; it's great to see everyone happy here. Now, we're going to get to business. This is a talk that really touches me, and I know it's going to resonate with you as well. It's taken from some points in history, along with the sentiments of people involved in NYC.rb. We're going to delve a little into their thoughts, but I promise it won't be offensive, because they kicked me out for that! However, it will resonate with you because you're all interested, and it's mostly words. So here we go: Why is open source so closed?
00:02:20.470 The semantics of words are fascinating. When words pop up, they resonate with us and trigger certain feelings, sometimes good and sometimes bad. Let's start with this image. Can anyone tell me who this is? Augustus Caesar—why is he so awesome? Personalities often emerge from cults. Can anyone tell me what this image represents? That’s right! This was a little culture cult known as the homebrew group, and I consider it to be really the first open source group. It's important to know about your history because out of these cults often come defining personalities.
00:02:52.299 Now, going back to the homebrew group in its infancy, it was a place where a lot of exciting ideas originated. This reminds me of one of my favorite bands, 'Living Colour,' who had a song called 'Cult of Personality.' It resonated with me; one of my favorite lines is 'Neon lights, Nobel Prize, when the leader speaks, that leader dies.' There’s drama in the lyrics, but also happiness. Once people develop their personalities in these groups, we feel empowered, like we can do anything.
00:04:09.220 In our community, NYC.rb, we have a steady flow of people coming out of boot camps, and that’s exactly the feeling they experience: freedom to write code and see all their tests pass with ease. However, there's a nuance to the word 'free'—it's used in many contexts. There has been an issue with the interpretation of 'free' in relation to open source, where some people mistakenly think it means zero cost. The problem is rooted in the English language; we use the same word for multiple meanings. For example, we tell boot campers there's going to be tons of work for them, but they often find that the demand is not what they expected.
00:05:57.020 When you hear the word 'demand,' what comes to mind? Can I see a show of hands for those who view it as a positive term? Okay, about half the room. And how many view it as a negative term? Fascinating—it's almost evenly split. And what about 'command?' It raises similar thoughts. These words can carry different weight based on context. For example, in French, to 'command' something is more assertive, while in English, 'demand' can feel like an imposition.
00:07:53.680 So, when boot campers enter the job market, they hear a lot about demand but often face a harsh reality of being under-credentialed. This creates a sense of being pressed both horizontally and vertically. Vertical oppression occurs when boot campers quickly learn they are not being considered for mid to senior-level positions. Horizontal oppression happens in the workplace when colleagues favor their own methods, leading to frustration in collaboration. We can't see these forms of pressure until we squint to observe how they affect us. Unfortunately, the supply of jobs they expected diminishes, and this leaves many feeling disheartened.
00:09:54.000 What’s compelling is that, while demand might stay strong, the supply is what truly drops. Developers actually should hold more control over job opportunities, but it seems flipped, with job supply dwindling or at least perceived to be so. I hear this sentiment echoed in many meetups, where attendees express frustration after investing in boot camps, wondering what went wrong. Consequently, we must explore the true meaning of 'free.' In Latin, there are two terms: 'libra' and 'gratis.' In English, we mistakenly conflate them, thinking that being 'free' also means 'without cost.' However, they thought their version of free would yield opportunities, only to realize it meant something very different.
00:11:17.000 When we're working hard and not seeing productivity, that creates frustration. Historically, there's a physical aspect to the notion of freedom, but mentally, it can feel like we imprison ourselves. In conversations with mentors, I’ve come to understand that in this day and age, slavery is often more psychological than physical. This self-inflicted limitation stems from fear and doubt. Many of us struggle with feelings of inadequacy. This mental blockade can spiral, creating even more barriers, and therein lies the problem.
00:12:20.000 It's often about how our mental patterns translate over to both machines and ourselves. Once we begin to feel uncomfortable in our environment, we might become resistant to looking beyond our immediate situation. One day it hits you: there’s a closed sign on the door you didn't even know was there. You’ve put in the effort and skill, yet feel abandoned and unsure of how to advance. There's a certain skill set, but knowing how to market yourself can feel daunting. You’ve invested your time, and without results, it’s easy to begin feeling like a failure.
00:14:40.000 To navigate this clarity, I turned to historical figures like Dr. Martin Luther King Jr. His 'I Have a Dream' speech brings forth concepts of alternative perspectives. Collaborating with colleagues from Stanford and MIT, I found a document that could be just as valuable to us in our current struggles. In an interview with Dr. King at Bennett College, he highlighted the importance of the ballot while also emphasizing the limitations of the political landscape. He stated that neither the Republican nor Democratic parties hold the moral high ground; instead, we must wisely use our votes.
00:16:06.000 This revelation challenged my prior understanding. The thought that we can have alternatives is powerful. This resonates not only with political choices but also with tech paths we pursue. At an inspiring location like the Washington Memorial, we read: 'Out of a mountain of despair, a stone of hope.' I had to reconsider my perspective that often constrains us from seeing other paths. It exemplifies the idea that we can dip our toes into different technologies.
00:17:53.270 When traveling, we gain new lenses to see the world. Often, it's in transit that we spark insights. In my traveling experiences abroad, I encountered individuals in different systems, like the Swedish model devoid of slums, contrasting with the narratives I was taught. This opens our eyes to the fact that solutions are often outside what we know. Capitalism has its benefits, but it also prompts a sense of scarcity. I find many junior developers struggling with the jump to mid-level roles, which represents a chasm to cross.
00:20:09.860 In our development journeys, it becomes evident that we often lack guidance on how to market ourselves effectively. As developers, we are hesitant to showcase our capabilities, which results in being undervalued in job markets. Often we end up working for scraps, when instead, we could strive for a more meaningful engagement, which can be 'freedom for free.' The struggle lies in pushing ourselves to explore new opportunities while remaining grounded.
00:21:39.150 I encourage everyone to embrace exploration, whether it's in physical travel or diving into new code repositories. Idea dissemination is crucial. We must remember to stay connected to our roots while exploring the wider ecosystem. When Ruby developers experience the offerings in the JavaScript world or other technologies, it opens avenues of collaborative innovation. Sometimes we think we're 'stuck,' but in truth, it's about refreshing perspectives.
00:23:09.220 As I navigated this and shared my experiences, I became engaged with concepts like 'bubble tape.' I ventured into JavaScript for asset management and learned that good development can transcend one language or framework. Integration with various languages enhances our development capacity, not minimizing our foundational expertise in Ruby. Networking through NYC.rb, I’ve seen how these collaborations can lead to impressive environments.
00:24:35.920 Working collaboratively through pull requests and open source opportunities opens doors. I noticed the importance of joining not just for coding, but also for recognizing and welcoming all contributions, no matter how small. This inclusivity creates a welcoming environment, especially as newcomers step into our communities. Competition can stir apprehension but ultimately, collaboration fosters innovation.
00:26:17.000 I’ll leave you with an example: After diving into the Ruby community, I explored various tools for contributions. For instance, I worked on a project that could seamlessly integrate JavaScript tools and libraries, which demonstrated that exploration can lead to innovative solutions. When comparing contributors from Ruby and Node ecosystems, we saw that many developers could join forces to elevate their endeavors.
00:27:40.960 Look at how swiftly these communities adapt and integrate modern technologies. The goal isn’t to outcompete one another but to enrich one another's strengths. The appreciation for diverse technologies fosters growth for us all, allowing us to share insights and collaborate effectively.
00:29:05.920 This cycle of contributing to the community creates a culture of mentorship, promoting knowledge sharing. At NYC.rb, we actively challenge attendees to connect, share their work, and lead conversations. It's amazing the opportunities that arise from those interactions. By unboxing our experiences, we can realize our potential extends far beyond what we initially perceive.
00:30:40.920 My experiences as an educator also taught me invaluable lessons; I had a standout student in her sixties, learning programming for enjoyment. Her passionate approach exemplified how important mindset is in this world. Conversely, I had a student with a wealth of experience who allowed past limitations to hold him back. His struggle with Ruby demonstrated how mental blocks can hinder progression.
00:32:21.720 Consequently, I invite you to challenge yourself. Engage in conversations, allow your experiences to drive you, and remain open in your contributions. Each person’s journey adds richness to our collective tapestry. As we both learn and teach, we must flourish through mutual support and guidance, fostering a positive culture in the open-source community.
00:34:04.920 In conclusion, let's notice how we can contribute effectively while uplifting others. Whether you're a seasoned developer or a novice, your input is valuable, so embrace the opportunities available. Publishing early and often, building connections, and participating in discussions fosters an enriching environment for us all. Together, let’s create a culture that celebrates growth and progress, where we continuously learn from each other's strengths and experiences.
00:39:21.000 Happy Veterans Day to those who have served! If anyone is interested in collaborative opportunities, I’m here to help bridge gaps and facilitate connections. Reach out and share your experiences with NYC.rb and others in the open-source community because we're all striving for collective growth. Thank you for allowing me the time to share these insights, and hey, thanks for cheering me on during that handstand!
Explore all talks recorded at RubyConf 2016
+82