![#railsgirlslj (at Telekom Slovenije)](./img/5c2acea173c932d419bf93c9fd9b254e-tumblr_mf2fcpFlrG1qekjngo1_500.jpg "#railsgirlslj)
This Saturday I infiltrated an event for girls. Girls awesome enough to dip their toes into the world of web development and programming in general.
It was a bit like geek heaven.
There you are, surrounded by 75 human females, every one of them hand picked to be interested in what you do. Girls who came there to learn, with a mind completely open, everything is new. You can say almost anything and they will believe you. No questioning, no male ego. Just acceptance that you know what the hell you are doing.
Not daunting. Not daunting at all.
I volunteered to mentor at Rails Girls Ljubljana in a moment of weakness, one evening when I was very tired. Immediately regretting the decision I saw it through anyway ... the experience was amazing, I was not disappointed.
My impostor syndrome meter was through the roof. You see, before the event I had a grand total of two hours of Ruby on Rails experience. Tried to go through the Rails Girls guide the previous evening, failed miserably on my machine because all the generators and scripts did the wrong thing for some reason. Probably a version thing.
Perhaps sensing my hopelessness the girls in my group (three per mentor) did not ask too much about Ruby or Rails. They focused more on the interesting stuff one can actually teach in a day - how to make things pretty.
I could help with that!
Talked their ear off about html and css ... the other mentors relay a similar experience. But that's what beginners are like, they want something to change on the screen, something cool to happen. Perfectly happy changing templates around, they rarely care about the deep logic behind things. There's easier fruit to pick.
Although I'm sorry there wasn't enough time to explain one of the girls how to make a twitter bootstrap button with a custom colour. Would simply take too long.
The best thing about teaching girls, the absolute best thing is they don't have annoying ego problems.
Teaching guys, I would mostly sit around and observe what they're doing. They would poke around, ruin everything and only after getting hopelessly lost they would ask about some irrelevant issue. They wouldn't ask for understanding, they'd ask _"Hey, why is it complaining about this comma?" _... are you kidding me, you clearly have no idea what's going on and you ask me about a syntax error?
Girls ... they ask. If something isn't clear, if something doesn't work, if they're simply unsure of something. They ARE going to ask you. And you will be confused, you will have to pull on all your past experience with other frameworks ... and when you fuck it all up, you can always ask another mentor about that tangential syntax error.
I probably learned more about Ruby on Rails than the girls did, but I couldn't have done it without them. They taught me plenty simply by asking good questions and making sure I didn't have a single minute of down time in the three or four hours we spent coding together.
Hopefully we taught all the ladies that computers aren't some arcane mystery and that they will at least consider programming as a solution to the problems they encounter in whatever they're doing.
The fact it took 10 minutes to teach everyone where [ and ] are will forever stay a warm memory of just how utterly I underestimated the importance of initiatives like Rails Girls.
PS: Thanks to Rails Girls franchise for the awesome guides. I would be completelyeven more lost without those
PPS: https://twitter.com/RailsGirls_LJ/status/280676513215545344
Continue reading about I infiltrated #railsgirlslj, here's what it was like
Semantically similar articles hand-picked by GPT-4
- I infiltrated another Rails Girls event, #RailsGirlsMb
- The real-time WebCamp bash
- #WebcampLj was bitchin'
- Debauchery at BcLj2
- Webcamp Zagreb report
Learned something new?
Read more Software Engineering Lessons from Production
I write articles with real insight into the career and skills of a modern software engineer. "Raw and honest from the heart!" as one reader described them. Fueled by lessons learned over 20 years of building production code for side-projects, small businesses, and hyper growth startups. Both successful and not.
Subscribe below 👇
Software Engineering Lessons from Production
Join Swizec's Newsletter and get insightful emails 💌 on mindsets, tactics, and technical skills for your career. Real lessons from building production software. No bullshit.
"Man, love your simple writing! Yours is the only newsletter I open and only blog that I give a fuck to read & scroll till the end. And wow always take away lessons with me. Inspiring! And very relatable. 👌"
Have a burning question that you think I can answer? Hit me up on twitter and I'll do my best.
Who am I and who do I help? I'm Swizec Teller and I turn coders into engineers with "Raw and honest from the heart!" writing. No bullshit. Real insights into the career and skills of a modern software engineer.
Want to become a true senior engineer? Take ownership, have autonomy, and be a force multiplier on your team. The Senior Engineer Mindset ebook can help 👉 swizec.com/senior-mindset. These are the shifts in mindset that unlocked my career.
Curious about Serverless and the modern backend? Check out Serverless Handbook, for frontend engineers 👉 ServerlessHandbook.dev
Want to Stop copy pasting D3 examples and create data visualizations of your own? Learn how to build scalable dataviz React components your whole team can understand with React for Data Visualization
Want to get my best emails on JavaScript, React, Serverless, Fullstack Web, or Indie Hacking? Check out swizec.com/collections
Did someone amazing share this letter with you? Wonderful! You can sign up for my weekly letters for software engineers on their path to greatness, here: swizec.com/blog
Want to brush up on your modern JavaScript syntax? Check out my interactive cheatsheet: es6cheatsheet.com
By the way, just in case no one has told you it yet today: I love and appreciate you for who you are ❤️