Gregory Terzian
May 17, 2018 · 2 min read

Since September 2016, I’ve been contributing to Servo.

As with most good things in life, it happened by chance. I met someone in a coffeeshop, that person was writing code and I couldn’t make out the language used. I asked, and the answer was Rust.

We ended-up sharing that coffeeshop for remote work for a while. Eventually I cloned Servo, and tried building it for the first time. It was surprisingly easy, well-documented, and supported by wonderful tools.

My first commit was a one line code change which resulted in updated test expectations for 25 test files! Wow, so much work with so little code! ;)

For my second commit, I returned to the comfort of Python, and made some changes related to the tooling of the project.

In the following winter months, I really got going with Rust with changes to the code handling incoming scroll events in the related project Webrender. That was a wonderfully ‘visual’ type of work which I could easily test on my own by scrolling the page. It was a good beginning.

In March, I went down the rabbit hole with work on my first issue labelled “hard”. It felt a little like first learning to program all over again. While in those days I had to wrap my head around new concepts like ‘variables’ and ‘functions’, this time it was about understanding parts of a large system.

Let’s just say that it’s only since then that I understood those memes about programmers not wanting to be interrupted while working. It was the first time working on a system large enough that indeed one had to make enormous efforts to just load the relevant concepts into one’s “working memory”.

It took about a month to get that PR merged, and with all that feedback, I probably learned more than I would have had otherwise in a year.

I was hooked, and have been pursuing those “hard” issues ever since. It’s fun, and while it starts slow, you end up making giant leaps.

Regarding the Servo community, well, while I often wonder how the core maintainers know so much, I am also amazed how they never make it seem like they “have all the answers”.

As someone who has received code reviews many times, I can vouch that it indeed feels like being coached, as described here(I think of it as “my free system programming bootcamp”).

So, have you been programming in something like Python, Ruby, or Javascript, and while you love reading about “programming in the large”, that stuff just hasn’t been useful for those Rails or Django projects you’ve been working on?

Or maybe the above doesn’t describe you at all?

In any case, you’re invited to pick an “easy” issue for starters, or maybe “less easy”, since they’re less quick to be picked up by others. There is also a list of “candidates for mentoring”.

And if you like it, which I have no doubt you will, take your pick at a “hard” one after a few months.

A whole new world in programming awaits you…

Programming Servo

Adventures in contributions to Servo, the parallel browser engine. https://servo.org/

Gregory Terzian

Written by

I write in Python, Javascript, Rust, and English. Always for people to read. https://github.com/gterzian/

Programming Servo

Adventures in contributions to Servo, the parallel browser engine. https://servo.org/

Welcome to a place where words matter. On Medium, smart voices and original ideas take center stage - with no ads in sight. Watch
Follow all the topics you care about, and we’ll deliver the best stories for you to your homepage and inbox. Explore
Get unlimited access to the best stories on Medium — and support writers while you’re at it. Just $5/month. Upgrade