Tip:
Highlight text to annotate it
X
[GitHub Presents] [Passion Projects]
[Sara Chipps]
Hi Guys! Again, welcome to GitHub.
My name is Julie and I'm a designer at GitHub.
But I'm also the creator and organizer of Passion Projects, this talk series.
[Woo!] Thank you.
So, today we have all the way from New York, Sara Chipps joining us.
She's the co-founder of Girl Develop It and the CTO of Levo League.
I think I'm pronouncing it right.
Yeah, awesome.
So, please join me in welcoming Sara Chipps.
[Applause]
Hi everyone.
Alright, I'm hooking up here.
How 'bout a round of applause for Julie?
I don't think I've ever seen such a well put together series in my life.
[Appaluse]
That was only for points.
Okay, this talk is a little bit about forgiveness.
And you'll know a little more why as we go.
I promise it's related.
So, here's a little bit about myself.
I helped start an organization called Girl Develop It.
We teach low cost software development classes geared towards women.
Not only to women. We have about 15 to 20 percent guys in our classes.
We've taught 4,000 unique students so far
and San Francisco is one of our most rocking chapters.
CTO, of an organization called Levo League.
We do career elevation aimed at Gen Y women.
This is my team.
I included a picture of them because they told me not to come back
unless I had [Heisencat] and [Daft Punk Cat] stickers.
So I thought that if you could see their faces
you could know that I really wanna go back to those guys.
So if anyone has any that would be great.
Or could tell me who to talk to. [Laughs]
I'm also on team Node Bots which is -- we help -- we work together
to run events where we build robots with JavaScript. It's super fun.
On July 27th, we're doing an international day of robots
where we're hosting a whole bunch of events so check out nodebots.io
if you want to host your own or go to one in your area.
So I was looking at XKCD the other day and I saw this one
and I thought it was super applicable to this talk.
I was like, well this is kind of the essence of things that I want to talk about.
Like the things that we all think are unique to us.
Things that we just don't share with each other
but we're all constantly thinking about.
So I'm gonna introduce you to a couple products.
One of them is a three-minute video.
Please bear with me. It's going to be my face that's really big on the screen again.
So, let's just start that part.
[Vasilia]
[Introducing a new way to browse the Internet]
Hi, my name is Sara Chipps. And I'm a software developer.
I've been working for over ten years now with companies you've heard of
and some that you've haven't to bring great experiences to the web.
I'm a Java Script developer and I work with early stage start-ups
helping them design, build, and deploy their first web applications.
I also co-founded an organization called Girl Develop It.
We do low cost software development classes geared towards women.
We've taught over a thousand women how to code.
And we're in seven cities around the world.
I spend a lot of my time online.
I'm often doing things like writing emails and listing to music
or watching a movie while I'm coding or sitting on IM and
also DJing in a turntable.fm room.
I get frustrated when I have to move between tabs
every time I wanna try to do something different.
Usually I'm only interacting with a very small part of my screen.
And the rest is a bunch of ads and white space and stuff that I don't need.
During a recent love affair with building browser extensions
I learned a lot about the inner workings of the modern browser.
I learned that they were built the way they are
because windows used to need to be square.
I thought: why can't the browser take the shape of its functionality?
And so Vasilia was born.
Vasilia is a browser that is chromeless and dynamically shaped.
It allows for designers to create any interaction they can imagine online.
And it leaves navigation up to the developer.
It also leaves us the rest of our screens.
[What will this browser allow us to do online?]
Why not listen to a movie and do your taxes at the same time?
Or send emails while you're DJing in a room on turntable.fm?
Why download and install an expensive image editor?
Where I can use an online version that could be updating constantly
bringing me the best content.
The Internet has changed our lives by making everything accessible.
I believe the Internet was never meant to be square
and Vasilia let's us take browsing to the next level.
[Why Kickstarter?]
I'm bringing this project to you, the people of Kickstarter,
instead of going to pitch investors
so that Vasilia can start and stay an open source project.
The Vasilia source code will live on GitHub.
So developers around the world can learn from it and make it better.
Supporters will be able to track our progress through our blog at getvasilia.com
where we will be posting bi-weekly updates.
Thank you for your time and your support.
I'm looking forward to building a better Internet with you.
[getvasilia.com]
Ok, that was Vasilia.
I appreciate the one person that tried to clap.
That was good. [Laughs]
Ok, so next up, I wanna show you guys something else.
This is Octocat.me. It is a-- I'm a big GitHub fan
if you guys can't tell.
So Octocat.me uses facial recognition software
to recognize features on your face when you upload a picture.
So, if you're male or female, if you have a beard,
if you're wearing glasses, how long your hair is--those kind of things.
And then what it does is it makes an octocat that looks like you.
Gives you like a .png of a cute octocat that looks like your--
that looks like you.
[Concept Camp]
This is Concept Camp.
This is a fun camp for developers.
Where we all go camp outside and do chalk talk.
So it's kind of like glamping where there's outlets and things.
You bring your laptop and people that give talks talk about
more concepts than code and it's a great time for developers to get together
and just kind of hang out and learn from each other.
So, these three projects I've showed you, I promise it's for a reason.
They all have something in common.
So these are all things that I worked on
for a long time.
Things that I spent over a hundred hours on.
Things that I worked for weeks on.
And all of them failed.
None of them went anywhere. None of them even saw the light of day.
We actually did have Concept Camp one year.
It was really fun.
But besides that, these were all things that I worked on that
never went anywhere.
Things that I invested a significant amount of my time on.
Why did these projects fail?
Because they failed.
I wanted to give you guys a graphic here.
But don't search for fail on the Internet
because you'll get a million pictures.
But they failed for lots of reasons.
They failed because things got hard and I stopped caring.
They failed because I got a full time job and I no longer could focus on them.
They failed because the people that were working with me
just didn't wanna do so anymore.
Lots of different reasons.
But that's not why I'm giving this talk.
I wanted to talk about forgiveness.
And the reason why I wanna talk to guys about forgiveness is because
it's something that's really important to me.
When Julie told me the name of the series
I was really excited because passion projects are all I do.
It's--You know when you're in high school
and you read books and every character had a fatal flaw?
Well my fatal flaw is that I can't work on things that I don't care about deeply.
And everything I work on I really love.
So, when I walk away from something or
I'm not successful at something
it's difficult for me to move on to something else
because it's hard to forgive myself for failing.
And I think that's something that we all experience.
So I wanted to share some of the wisdom I've gotten from
failing a whole bunch of times and being able to move on.
So the good news is there's lots of people that do this.
And lots of people have failed at things.
In fact, people that we really admire often fail at things.
On Sunday of this week, I was putting this talk together.
And I was like, well it would be really great if I can
talk about people who have-- like famous names
like people you would recognize
about their failures.
So I put together an email and I sent it to everyone that
I consider a role model.
And funny story, I actually sent it like at 6PM-ish and then by 11PM
I hadn't got any answers so I was like oh my goodness
This is my first failure.
I just told all my role models that I'm a huge failure and
they didn't answer me.
[Laughs]
But turns out it takes at least a day
to tell people about your failures.
So the next day I got a whole bunch of answers.
And I wanted to share some of the things that I found out with you.
So Chris Williams is someone I look up to a lot.
He made JSConf and I think he's really awesome.
He has made a conference that's probably, maybe, definitely one of
the top three best conferences I've ever been to.
A great environment that's really open to families.
There's kids everywhere. There's spouses everywhere.
It's about getting together with developers and just spending time.
It was a really enjoyable experience.
He told me the story of JSConf in 2009. It was the first time they did it.
And he decided to do a conference just like out of the blue.
His wife was into it and they planned this whole thing.
They put it online. They got all the speakers.
They booked a venue. They paid-- they gave a down payment for the venue.
They knew there was no JavaScript conference.
They were gonna do one. It was gonna take off.
It was gonna be awesome.
So after doing all these things, getting the site up
They started doing publicity around it.
Asked their friends to email and tweet
and they sold no tickets.
No one wanted to go to this.
It was like a month after they opened up tickets.
And they hadn't even sold enough to cover the down payment for the venue.
So basically they had put his money out of pocket.
And they were going to cancel their conference.
So he was about--he was headed to the venue to like ask for their deposit back
be like you know like there's still a little time
can we have our money back? We're not gonna end up doing this.
And before they left he changed the invite to say it was selling out.
It was almost sold out and he tweeted it.
And then they left.
And he said that the whole way in the car
him and his wife were like arguing
like what--why'd you do this? You thought this was a great idea
your friends would come and no one's coming.
And all those things.
They're headed to the venue.
They get out of the car at the venue.
He looks on his phone and they had a waiting list.
Like they had sold all the tickets on their way to the venue.
[Laughs]
And he said that that was a real lesson.
And a lot of people shared some wisdom.
So I'm just gonna share these verbatim.
He said, "I would extend from your target point"
"and say that the greatest risk is often met with the greatest trials"
"but the combination of the risk and trials are what make the reward result"
"the sweetest."
I thought that was neat.
Neil Capel is someone else I think is pretty awesome.
He founded the company SailThru.
They have a email API for mass emailing.
So I emailed him and was like can you tell me a little about your failures?
I wanna talk to people about failures.
And he sent me a laundry list.
So in 2000, he made a real time booking software
that was for golf courses.
I don't know what it means by worked over dialup at both ends.
[Laughs] I can only imagine. But I mean
that sounds tedious.
Flash page turner for catalogs.
Dropbox application with version control.
Page flakes.
Firefox plug in that auto completed and validated for entry.
This is a lot of things.
And the wisdom that he shared was
that his main learning from all of them was
"don't try to keep a job and do a start up at the same time!"
"Very few people can manage that to sucess."
Which is pretty valid.
But I think another thing to notice is that he did all those things
and kept going and made SailThru after that--
after all those things went poorly.
Joel Spolsky. He shared a story about CityDesk.
I don't know if anyone-- I had never heard of CityDesk.
But it's a content management system
that was built on Windows.
Basically he said they sold a handful of copies of it
so they focused a lot of their resources on it.
And to quote him exactly,
"to this day my blog is still locked up in this fakakta software."
[Laughs.]
It's the first time I've heard that word in a long time.
Which I thought was neat.
So something he said that was a surprise was
"I think about 60 percent of the things we tried at Fog Creek either failed"
"or didn't work very well."
Which is really surprising because
we only see the things that only go really well.
Right? It's funny.
I also reached out to Jeff Atwood and he said too bad for you
I've never failed at anything.
[Laughs.]
So, that was that. Some people are perfect apparently.
So Mark Hedlund is someone else I really look up to a lot.
He is the SVP of Product Development at Etsy and Engineering.
He made a web app called Wasabe quite a few years ago.
And it was kind of a mit.com type competitor thing,
It was like a financial--
you import your finances and it gives you--
it's predictive and things like that.
And they shut down in 2010.
And I actually took this from a blog post that Mark pointed me to
that I thought was great. I put the link in the slides
and I'll put them up on my blog afterwards because it's a great blog post.
And it's really good self exploration of a failure afterwards.
And he said, "I don't agree with those who say you should learn from your successes"
"and mostly ignore your failures."
"Nor do I agree with those who obsess over failures for years after."
"As I have done in the past."
"I'm hoping that by writing this all out"
"I can off load it from my head and hopefully inform other people"
"who try and start companies in the future."
That's kind of--that can be cathartic.
So this is, this is his link.
So like I said, why did my projects fail?
This, this isn't so important as much as
being able to move on from your failures
and being able to forgive yourself.
One thing I think demonstrates that all these people were able to move on
is that they were okay with the fact that something failed.
And it didn't make them say
alright well, this failed
I really--I don't know that I want to do this again
or I don't want to go through this again.
They failed and they readily were like alright well then I'm gonna do something else.
That sounds super neat but how do you--
like just saying "Forgive yourself" that sounds really nice, right?
But it's not so much like a how-to.
So I spent a lot of time in thought about how I got to the point
where I felt I could forgive myself
and I have some tips that I'm just gonna share.
So I have a couple mantras that I like to live by
that I may have made up or read somewhere and forgotten
so I'm pretty sure I wrote this but I don't know.
So I think your life is about getting to know yourself, right?
We're stuck in these bodies for as long--60, 70, a hundred years.
Whatever.
We're stuck in these brains.
And the more we can take time to learn about ourselves
Learn about we're good at, what we're bad at,
what we enjoy, what we like being surrounded at,
what stimulates us, what squashes our creativity.
When you learn these things about yourself
you can just improve on the next literation.
I spend a lot time focusing on the things that I'm good at
and the things that I'm bad at.
A lot of those things are obvious, right?
You know what you're good at.
Also I found that when people--
when separate people in different environments
gave me the same feedback three, four, five times
I don't take it as fact but I say there's some truth in this.
I'm hearing this from a lot of different people.
And it must mean they're noticing the same thing.
And while that might not be the exact thing
there's something to be taken from this wisdom.
So strengths or the best part, right?
The things that we're good at.
I--just to share some of mine in case you were wondering.
[Laughs.]
I've been told that I'm good at being gregarious.
I really like rapid prototype so thinking of something and building it
really quickly just the V1.
I'm really good at V1.
Implementing big ideas.
There's not many things that can scare me.
[Twerking.]
[Laughs.]
Weaknesses.
The second best part or the worst part.
Things that I consider my-- to be some of my weaknesses are listening.
I tend to be one of those people
that talks when there's quiet.
You know people that doesn't let quiet happen.
I've learned that some other people
don't talk unless there's been quiet for a little while.
So, often I'm not listening when I'm talking to people
'cause I'm just talking the whole time.
So it's something I've been working on for a little while now.
I'm terrible at emailing.
I really--it's not that I get a lot of emails 'cause I'm super popular or something.
I'm just really bad at it.
A lot of times I'm like three weeks behind on my inbox.
It's something that's constantly a stressful situation for me.
Implementing new procedures and following new procedures.
Things like that kinda make me crazy.
I--even people that are good at this sometimes make me crazy.
I always call it like the Michael Scott and Toby relationship.
Like when I talk to accountants and things I'm like I can't even listen to you.
Like I want to stab my eye out. I can't even--
like the things that you say-- it's awful.
Also bad at spelling.
That's really how I spelled procedure the first time.
So I was like I'm just gonna keep it and say I'm bad at spelling.
[Laughs.]
So let's take a deep dive into weaknesses
and what we can do about them.
I think there are two different types of weaknesses.
The first kind are things that you are bad at that you don't want to be good at.
These are things that you're bad at that you don't care.
This is fine. I'm bad at this. I'm gonna get on with life.
I never wanna be good at this.
Here are some secrets that I've learned about these things in life in general.
So, let the people know, especially people that you work with.
Often I have a conversation when there's someone I work with that's very good procedurally
where I say, "Hey, just so you know this isn't my strength."
"I really admire you're great at this and I'd love to learn from you but"
"Just as an FYI, this isn't something I excel at."
It gives people some context when you're maybe not so great at it.
Another tip I got recently which is great was from a friend of mine
named Gary Chow and he has a lot of experience with start ups.
I was talking to him about hiring and he said "the best teams I've seen"
"hire around the weaknesses of the founding team."
So, no--there's no equation like first you hire a CEO
and then you hire a CTO and then you add an COO.
There's none of those things.
It's: you know what? Our founder is bad at this,
so we're gonna hire here in order--the company to be strong in general.
Which I thought was really neat.
Try to avoid tests that involve this particular skill.
It's not really that hard.
When everyone's like, "okay, here's our new thing, who wants to do the bookkeeping?"
I'm not like, "Oh, me!" because I know that's gonna go really badly.
So this is how I address the things that I'm bad at but I don't wanna be good at.
There is a second kind of weakness and they are the things that you want to be good at.
They're the things you're bad at that you really want to improve
in order to be good at them one day.
Identify them.
I'm really--I'm not that great at writing tests.
It's not something that I-- I really love development.
I've never had a natural talent for writing tests.
Knowing what tests to write and when.
Often I find creating action items for these things is super effective.
So lately I've been pairing with people on my team
that are really good test writers.
And I'll say upfront, "Hey, if we can focus on writing tests today,"
"that would be great. That's something I'm trying to get better at."
Track them.
Where was I six months ago?
And where am I now?
Baby steps are great. You should celebrate them.
It's something you're bad at. So if you improve a little bit
that's awesome.
Right?
You don't have to go from being bad to being great overnight.
It's gonna take a long time.
And never stop iterating on it.
Have the next step ready.
Like the next thing I wanna do once I feel better about where I am
is actual build an app that's test driven.
I've written a lot of tests. I've written a lot of apps.
I've never started with tests, so that's what I wanna do next.
Okay, so that leads really well into another mantra I have.
And it doesn't matter where you start as long as you're continuously improving.
A lot of people are intimidated by being bad at something.
It is very intimdating.
But if you can look at it as always an opportunity to be better
and not care about how good you are at it, it puts you in a great spot to improve.
As an example, I'm on the Node Bots team.
I didn't pick up an Arduino until November of last year--August?
We at a team for Node Knockout and we made a--we got the innovation award
'cause we made a Christmas sweater that talked to the Internet.
It was super fun. But I wasn't the strongest contributor on that team.
It was the first time I had ever worked with Arduino. I just knew I wanted to work with it.
Since then I've worked with it a lot and I've gotten better at it
and now I can help people at it.
But I volunteered to be on this team and I was really clear like
"Hey guys, I just picked this up. It's gonna take me a little bit to get ramped up."
But it was cool because it doesn't matter where you start as long as
you're really headed towards improvement. You're in a good spot.
As far as heading towards that improvement that you're looking for,
15 minutes a day is the commitment that I always try to make.
15 minutes a day is just small enough to not be intimidating.
I got into software in 2002 and that's where--a year where we went to
having a lot of jobs to having absolutely no jobs.
So I went through about six months that I was applying for jobs every day.
And it got really intimidating and stressful.
And I committed to myself, "I'm going to apply to five jobs every day."
It's gonna take me 15 minutes.
I'm not gonna do more, I'm not gonna do less and
if I miss a day, I'm not gonna do double the next day.
Just 15 minutes a day.
And that was a really effective way for what turned out to be
over a hundred job applications before I found something
without getting too stressed out.
Make something you want to be good at your side project.
All of my side projects are Arduino based now.
I hope that most of them don't fail.
If you can spend your free time doing something exciting that involves
what you wanna get better at, it can be really motivating.
And then again forgive yourself for being [***] at sometimes at things.
We're all human beings. We're all bad at somethings.
None of us are Superman.
Yet.
[Laughs.]
So, it's okay. You know, just like the comics said
we're all thinking about the same things. We're worried about the same things.
We're just as concerned as each other noticing those things.
It's time to be okay with being [***] at things.
So, forgiveness has some anti-patterns.
Some things you need to catch yourself doing.
That don't allow you to forgive yourself.
A big one is jealousy.
For example, I'm a huge fan of James Halliday.
I think he is amazing.
However, it's really easy to see people that you admire and make quick judgments
quick jealous judgments about how they got there.
Saying things like, "Oh you know, I bet he only does this."
"He probably doesn't have a full time job."
"He really probably just spends all his time writing modules."
"I can't do that. I have a job. So I totally get that he's better than me."
"That's fine." [Laughs.]
So something I've learned about this year is really exciting.
It's called the Hebbian Theory.
I'm not gonna read all this to you. Feel free to read it out loud.
I mean read it to yourself. [Laughs.]
Or read it to yourselves actually. That'll be disruptive.
It basically means that the [too long didn't read]
cells that fire together while wired together.
What it means is your brain changes its architecture based on
how you usually think so you can train your brain to learn new behavior.
Right? 'Cause if you think in the same-- if you have the same reaction
every time you go somewhere it becomes in your head, it becomes easier every time.
So if every time I look at someone that I think is talented, I react by being jealous.
It's gonna become easier and easier to react with jealousy.
But you can train yourself not to go there.
I did that a long time ago with this exact emotion
and it was really effective for me now my head never goes there.
I take a step back after I have that jealous thought
and I'm like wait a second.
Let me think of five amazing things about this person.
Obviously substack's amazing.
He's built probably the most node modules in NPM.
He's an amazing Javascripter, great developer, someone I really look up to
And I think is awesome.
And so thinking in that-- thinking that way, even if it means,
"Hey, I'll never be this person. I'll never be that great."
"I'll never contribute those things."
It allows you emotionally to say, "That's okay. It's fine."
"I'm not gonna do that. I'm gonna do other things."
'Cause this person is amazing and I shouldn't forget that.
Another forgiveness anti-pattern is thinking things are done.
Thinking of done as a concept even.
There's that Facebook poster that everyone steals and now has in their office.
Least that's what we did.
Done is better than perfect.
I disagree.
I don't know that there's any such thing as done.
Often the best time to get feedback is when things are half finished
or quarter finished.
I remember listening to some podcast somewhere where they were
interviewing John Resig about jQuery and they were like
"What would you have done differently if you could do anything differently?"
He's like, "I would have showed people much earlier."
"I would have gotten people involved much earlier."
"I had to learn so many things the hard way because I thought something"
"was best a certain way. And I built it that way."
"And then someone smarter than me came along and said"
'Nope, that's probably not the best way to do it.'
So I think it's really important to involve people super early on in your projects.
What do you think about this?
What's your feedback?
And it can get them excited which in turn gives you more inertia.
Keeping score.
I hear that all the time.
I hear--and I'm sure you guys do as well
"Oh, you know, I didn't go to school for computer science."
"Or oh, you know, I'm not really good at computers."
And all those things and that's just software development.
Every time I think about keeping score
I think about-- there's this group of--
There's like this demographic in our Girl Develop It classes.
Women that are 50 plus. And we've had like 70-year-old women
come take Girl Develop It classes.
And they are so into it.
And they're the most dedicated students. I will take them any time over younger students.
They always find each other and they make study groups.
It's the weirdest thing. Every class that I had women in that age bracket
I had men in that age bracket as well, they would find each other
and get together after class or during the week and study together.
I guess that's a lost concept we don't really do anymore.
But that was really neat.
But they were so motivating, right?
You're 60, why do you need to learn to build software?
They just weren't intimidated by it.
And there's no such thing as too old or not good enough
or any of those things.
Here are some facts that I found on Wikipedia.
Here's one--I was working on this last night in my hotel room and I was watching--
I think that David Letterman was on. It was just like the TV was on for noise.
I don't watch David Letterman. [Laughs.]
And this woman was on. And she was telling this story.
She was a pretty popular singer in the 60s.
And then her kind of like-- she gave up on her career and
she got irrelevant. And she said that a few years ago
she was literally cleaning a bath--
she started doing house cleaning to make money.
She was so far away from this world and this environment that she started
cleaning houses and she said it was about Christmas time
and she was literally cleaning a bathroom when she heard her song play
at the house. A song that she had sung on the record player the place that she was.
She was like "Yeah, I don't wanna do this anymore."
And so she just dedicated herself and got back into it.
Started singing again and last night she was on David Letterman so that's cool.
Okay, now you guys know everything so you can go forgive yourselves.
This is awesome.
I realize that it's not that easy to say
"Alright, I need to get over my failures and move on."
I spend a lot of time in thought about how I got to this
how I realized that that's something that I can do.
And that was something that was important.
And so I think I identified where my behavior like this started.
And it has a lot to do with the mouse over for that XKCD.
It was when I had a weird high school situation.
So the first time I took Calculus was my freshman year at school.
And it's the first time that I took a class that I was notoriously the kid that
didn't study, didn't do homework, did great on tests and just kind of floated by, right?
So I did that for every class up until Calculus.
I took Calc 1, and I just failed it fantastically.
I was like this is really hard and you know, I'm super smart so this shouldn't have happened.
And I need to--I'm gonna do it again and I'm totally gonna be fine at it.
I probably just wasn't paying enough attention.
So I wasn't able to say, "Okay, it's okay I'm not that great at this."
"I'm gonna do better."
My attitude was like, "Oh, obviously this was the wrong teacher."
"So, just do it again, and I'll be fine this time."
So I took the class again and about halfway through the class
I was failing spectacularly again and I went to see my professor
to talk to her about why things were going so poorly 'cause--
I was still mind boggling for me because what had happened?
What was she doing wrong?
And so I sat down with her and I talked to her and
she said probably the best thing she could have possibly said to me
and she said, "Sara, it's so okay."
"Some people aren't made to do the science and math careers."
"My husbands like that. It's totally fine. You can just accept it."
I was like-- [Laughs.]
So I had to do a Hail Mary for the next three weeks.
I had to get A's. I had two exams left and coming from failing five exams in a row
I had to get A's on both of those in order to not fail the class.
So I realized that I had to put my pride aside and say
"Hey, this might be something that I actually have to study and actually have to learn."
So I sat there for the next three weeks straight.
Didn't do anything but calculus and I passed that class.
And I think that was a huge lesson for me to say, to be able to forgive myself
for being bad at something in order to be good at it.
So that's my anecdotal story and that's my talk about forgiveness.
[Applause.]
[GitHub Presents] [Passion Projects]
[Sara Chipps]
Okay, so lots of questions. I think the leading one for me is always
how did you get into computers? What was your "aha" moment?
So, is this good? When I went really close it was really loud.
[Laughs.] So I'm gonna go like this.
So when I was--I get asked this question a lot
because everyone's like lady coder let's talk about it.
But I think it's great. I think it's good to talk about this stuff.
The--I was just explaining why I have a story ready.
[Laughs.]
So when I was younger I was home schooled until high school.
My parents are pretty religious so that was something that was
super important to them.
So, I'm from a generation of people that became software developers
because they were losers.
[Laughs.]
I didn't have any friends when I was little but I had a computer.
And it was a way for me to talk to people.
I had a BBS. Do you remember BBSs?
[Woo.]
Yeah?
I was the co-sysop of a BBS.
If you know how important that is it's really important.
[Laughs.]
So I just know I really enjoyed it.
My parents had this 286 that cost three thousand dollars.
I remember going to a computer place and they put it together
and it was a whole big ordeal about, "we're gonna build this computer for you."
It was so expensive.
And then I just used to tie up our phone line all day and get really mad at my mom
when she picked up the phone.
It ruined everything.
[Laughs.]
And then when I got a little older I went to high school and I took a C++ class.
And it was the first time that I found something that just made sense to me.
I was like, "Oh, this is perfect! This is how my brain works. Makes so much sense."
After that I went to Penn State and studied computer science
and now I've been doing it for 11 years so.
- It's exciting. -It's awesome.
So you talked a little bit in your talk, you have basically an emailing list
for the people who inspire you or the people you look up to.
How do you find someone to mentor you?
What was that experience like for you?
So it's one thing about the software community that I try to get the word out there
is that the men in this community are super supportive.
I've experienced people just bending over backwards trying to help me
in my career.
They do a few things. I've met a lot of male software developers
that are like, "You're a lady coder? I know another lady coder!"
"You guys should be friends!"
[Laughs.]
Which is always great.
But also another thing that they do is that they're always open for advice
and sharing and just kind of talking about giving me feedback about my career.
So that's something that I've been really fortunate to experience
is just a collective of people who have been cheering for me the whole time.
- It's awesome. - That's great.
This is actually, it's perfect segue because the next question was
how do you ask for feedback?
How do you solicit feedback from the people that you want to hear it from?
I've got to the point where I'm really frank about it.
Recently there was a conference that I applied to speak at
and I didn't get chosen so I emailed the conference orgnanizer
who's a personal friend and I was like "Hey, no bad feelings. This is totally fine."
"You've put together an amazing line up. I would just love some feedback from you"
"about why I wasn't selected. I know I gave a talk there last year."
"I know it was kind of like meh. Can we talk about what the selection process was?"
So I'm just really, I ask people all the time.
That's awesome. Cool.
So, Vasilia. Did I say it right?
Vasilia.
Vasilia. And obviously Octocat Me. And a couple other projects.
You're really well known for open source projects.
Right?
- I've done a couple. - Yeah.
They're okay. [Laughs.]
What was your first open source project?
My first open source project that I ever contributed to
was a, does everyone remember WPF?
Which was like a Microsoft thing?
[Yeah!]
[Laughs.]
So there was a Windows Twitter client that some friends of mine had worked on.
That was my first contribution to open source.
I remember I built, what feature was it?
I was something about, oh threading! That's an important--
It was like threaded tweets which was new and important at the time.
So that was exciting.
- That's pretty awesome. That's cool. - Yeah.
How much do you contribute to open source now that you have a full time job?
Yeah, that's something that's really suffered in my life.
So that's something I really wanna start working on again.
[Laughs.]
That's awesome.
So you started a few projects, you now work at Levo League.
I'm assuming you've worked for companies as just an employee.
What was the leap like from starting or from going from employee
to sort of like a leader on the founding team or being a C level executive
- Yeah. - at a start up or company?
So before I joined Levo League,
I was contracting for three years almost four years.
So I hadn't had a job in a really long time.
And I didn't want a job at all.
I slept 'til two every day. And I worked fifteen hours a week.
And that was great.
But I just kind of fell in love with the people at Levo.
They were my client.
And I just kind of fell in love with them and what they were doing.
I really believed in it.
The difficult thing for me has been being someone's boss.
A lot times when you have a lot of experience as a developer
and people appreciate you as a developer
they're like, "I know, let me put you in charge of other developers."
And those are very different talents. So it's been really humbling.
It's been really amazing having people that I respect greatly
that are super talented want to be on my team.
There's been a lot of challenges.
We really focus on--I always say that the majority of my life is spent
worrying about developer feelings.
I really, I just want them all to be happy and really enjoy what they do.
So we do a lot of things around that.
We have a monthly developer potluck where we have someone come speak
and then the 25 or so developers come bring dinner things
and we all eat together and stuff.
So yeah, so the challenge was, to answer your question,
the challenge was being someone's boss is super difficult.
Yeah. That's awesome.
How did you come up with the idea,
- you started Girl Develop It with Vanessa. - Yeah.
How did you, did you guys know each other already?
How did Girl Develop It come to life?
It was one of those situations where we both had a mutual friend
Our friend, Tom, who was like, "Lady coder. Other lady coder. Be friends!"
[Laughs.]
And it was great! It was awesome.
She's a wonderful person and we had conversations about
how we always felt super weird when we went to talks
or when we had computer science classes and it wasn't because anyone made us feel weird.
It's just weird when you're the one woman and there's a hundred guys
and you have a question and you're like "Oh my goodness."
"I'm like identifying my entire gender if this is stupid."
"I don't even want to ask this question 'cause it probably is stupid. I have no idea."
And so we were like, wouldn't it be great if someone
if there was a place where you could go just where you have to ask a stupid question.
Really encourage people to ask stupid questions.
So yeah, that's how it got started and we scheduled a class
and it sold out really quickly and so evolved from there.
So you said you welcome male students as well so it's not just, it's female focused
- but it's more like inclusive to everybody. - Right.
How does that work as far as messaging to people that everyone is welcome?
Yeah. Well it's worked out great 'cause guys need that too sometimes.
- Yeah. - A lot of times there's these things
that are characteristically female like ladies have trouble negotiating.
But guess what, guys have a lot of trouble negotiating, too.
It's hard for everyone and everyone needs an environment where they won't be judged.
Sure, we have that discussion at GitHub a lot actually as we've grown.
It tends to be sort of like a women focused conversation around not being aggressive
but there are a lot of people with quiet personalities who are also men
It's not being sensitive is not something that's specifically prescribed to women.
It can be, it can come up in a lot of other people's personalities also
and so kind of also creating that environment that it's not necessarily
the loudest person who wins the argument or you can also have different personalities
at your company or people you work with and it can be sort of a safe environment for everyone
which is kind of what it seems like you created at Girl Develop It
which is really awesome.
How many cities do you know now that have Girl Develop It classes?
- I think we're at 22. - That's awesome.
And have you gone on Sara Chipps world tour yet?
[Laughs.]
No, but that sounds awesome.
[Laughs.]
I'm so in for it.
So you mentioned a whole group of your mentors, the people you look up to.
Is there one specific person who's really helped you in the last ten years?
You don't have to say their name if you're not comfortable with it
but is there one person that you really look up to and who's helped you make decisions?
Well, in the past I was actually just having this conversation.
Mark Hedlund, the SVP at Etsy Product and Engineering.
He sat down with me about eight months ago and for an hour just gave me all this wisdom
that carried me for so long.
Things like "don't forget that you're someone's boss."
"And if you don't say hi to them in the morning they think you're mad at them."
They don't think, "hey, you're in a rush. You have to go into a meeting."
Everyone takes things super personally.
And ask team members about other team members to see how they're doing.
You can get insight about your team and also how that employee is doing
and stuff like that.
That was super effective for me. So most recently, it's been Mark.
- I've met Mark as well and he is an amazing person. - Yeah.
And awesome. Awesome guy to have in your life.
I was gonna ask this about Girl Develop It--aah! No, this is bad.
I'm not supposed to be the one that's nervous and a wreck.
[Laughs.]
- I'm gonna drink some GitHub beer. - Yes. This is not GitHub beer actually.
But I figured we shouldn't give away free branding. So there ya go.
[Laughs.]
That's that.
Oh no! I had such a good question for you.
Moving on.
What do you think--Oh! You said that you felt weird
when you would show up to drink ups or meet ups or conferences
and be the only woman there.
Do you still feel weird? Or has it changed in the last five to ten years for you?
- What's the difference? - So, it's funny.
Now I'm really weird in super diverse groups.
Like oh my God I don't know what to do.
You're not all guys.
[Laughs.]
But I mean, things started getting a lot-- like I said I was just at JSConf
and there were a ton of ladies there like really awesome. It was really great.
So I'm always excited when I see things like that.
But yeah, I've just gotten kind of used to it.
- There are a ton of ladies here actually. - That's great! I've seen that.
- Really cool. - I saw the list in the bathroom.
Oh nice. Yeah. [Laughs.]
Cool. Does anyone else have questions for Sara?
No? No questions?
Okay, Jake. Yeah.
[Audience member asks question.]
I was pretty hand held through it to tell you the truth.
It was one of those situations where I complained about the feature not existing
and they were like, "well how 'bout you build it?"
And I was like, "That seems hard."
[Laughs.]
And they were like, "Well, we'll help you." And that was awesome.
But I always tell people to find a smaller project, don't go into the deep end first.
Find something small that you can contribute to
get to know the people that are building it.
Ask them questions a bunch so they know it's you.
And don't feel weird about people criticizing what you did
'cause that's part of learning.
That's awesome.
So do you--is there a specific thing that you do to kind of deal with
maybe an overwhelming amount of feedback or criticism?
How do you manage that? Because now you've worked on so many different projects
with I'm assuming a diverse group of people, how do you manage that now?
Well, the thing I get criticized most now is that we do pool requests
in order to merge with master.
So we do a pool request and everyone knows and everyone looks and tells you
everything that you did wrong. Which is great.
[Laughs.]
Especially 'cause this is something that I'm emotionally invested in
I really appreciated it because I'm like, "Oh good. Nothings going into master that's bad."
I guess I've just learned to roll with it.
I just kind of expect it now.
Yeah. How much of your day is split between meetings
because you are the COO exec there, between meetings and actual coding?
Yeah. So that's actually been a real challenge lately.
Where I was just doing so many meetings that I wouldn't take features
'cause I would end up clogging up the timeline. Right? So I would take bugs
and even those bugs would take a while to get fixed because I didn't have time to focus on it.
So actually that's something that I've spoken to our CEO and some other people
that were working on. Because right now we have some pivots.
And the pivots are pairing with people.
And I'm like, "I wanna pair with a pivot so bad!"
[Laughs.]
But actually in the past two weeks I've been able to spend two solid days pairing
and much more time coding so that's been awesome.
- That's really awesome. - Yeah.
How important do you think that this for your happiness?
I know you talk a lot about making sure everyone on your team is happy.
How much of that do you have to kind of like reserve for yourself?
Yeah that goes--it's so energizing.
I just realized that I was just drained.
And even just the first day I was back it was so energizing.
It was really great.
And I think that if effects the entire team, too.
Everyone doesn't like seeing someone on the team that's always in meetings.
So, yeah, it was awesome.
If you were to start learning how to code now, where do you think
is the best place for someone to start?
And not just with code, if they wanted to learn more about
sort of like either the start up community or coding or designing or any of those things.
Where would you tell someone to start?
Obviously, I always say Girl Develop It.
[Laughs.]
But there's a ton of stuff like that out there.
There's a ton of meet ups. There's a ton of beginner meet ups.
I always tell people to start with HTML and CSS because it's something that's pretty low level.
And I always tell people to actually work on something.
If they want like a blog or something like that.
Get a Tumblr blog and make it your own style
and things like that because it's really, it's a great baby step.
Rather than I'm gonna build a railed app.
But I always encourage them to go to meet ups and it's funny.
It took half of my career before I realized that there was a community out there.
I always just thought I was gonna work with a bunch of people
that I only thought were okay that worked in enterprise for a long time.
I was like, "Well, this is part of it. But I really like what I do."
But then discovering that community, it was like eye opening.
Right? So I always tell people to go to meet ups.
There are a lot of people in your same position and if you can find another one
it's really validating.
That's awesome. What's next for you? For maybe Levo League and also Girl Develop It?
What do you wanna do with the next five years?
No pressure!
[Laughs.]
That's a really good question.
That's something I've been spending some time thinking about recently.
My latest project that I've been working on is jewelry that communicates with
either the Internet or other jewelry.
I'm really into that.
I don't think anyone has fixed the problem of fashion and technology.
It's always something weird where you're like,
"Yeah, that's neat but I wouldn't ever wear it."
I've seen there's this rainbow apple keyboard dress that Adidas sells.
[Laughs.]
- I don't know-- - Yeah, I don't see myself wearing that.
But yeah, that sounds like a pretty interesting problem to solve.
- Yeah, I'm excited. I mean I haven't solved it but-- - Yeah. Soon.
Well, awesome. If no one else has questions anyone else? We will continue drinking.
And I'm just gonna say cheers to Sara Chipps.
And thank you for joining us all the way from New York.
- Thank you for having me. This is so great. - And thank you everyone!
[GitHub Presents]
[Passion Projects]
[Sara Chipps]