Subscribe to Rebecca Grenier RSS

Last week I was fortunate enough to present at Scala eXchange in London, alongside the likes of Martin Odersky, Peter Hilton, and many other people who are famous in the Scala community and have shaped my Scala path from afar. It was a great conference, put on by the Skills Matter company who for some reason do not yet operate in the US, which is a shame. They are a treasure for any programming community to have, organizing conferences on many different languages, videoing most of the presentations and making these videos available for free to all. In fact, I am not entirely sure how they make money. The conference had four tracks of talks so there was always something I was highly interested in.

I presented as part of Underscore Consulting's Diversity Program. Which refreshingly was not targeted at women, but at anyone who had not spoken at a Scala conference before. They offered financial assistance to attend the conference, which I was going to need because no company in their right mind would pay for an employee to go to a conference on another continent when there are perfectly good ones much closer. But more importantly they offered "speaker training" which was just that extra bit of support I needed to craft a proposal and the eventual presentation.

Without Underscore and my old boss Eric Smith's encouragement I would have assumed a beginner talk on Slick would not be interesting to the Scala community, who from afar seem like a group of all super high-level people who only are interested in high-level things. And there are a few members of the community who are like that, but for the most part this has not been my experience. Both Jan Christopher Vogt, the creator of Slick, and Stefan Zeiger, who is the lead developer on the project now, attended my talk and spoke with me about it afterward. I am sure you can imagine what a delight that was. Stefan had taken notes of my problem areas with the library and went down the list explaining how most of them would be fixed in the next release. Peter Hilton, an author whose book 'Play for Scala' I had purchased and read a few years ago also attended my talk and spoke to me about it and other Scala opportunities afterward. These are all examples of high-level Scala users who were interested in me and my experience.

And there has also been some feedback from lower-level users of Scala who appreciated a talk that was aimed more at "Joe Everyman" (or Jane Everywoman) programmer who is just trying to write small-to-medium size web applications. There was a panel discussion at the conference on the topic of what Scala needs to grow, which I think the consensus was to appeal more to the masses of programmers, and perhaps my talk helped with that.

Some of the things I did to prepare for this talk that really helped were
* Give the same talk to a local user group one or two weeks before the conference
* Give the same talk to some technical friends one or two weeks before that (maybe do this twice)

What didn't really help:
* Writing out everything I planned to say word-for-word, because nobody else was using paper notes so I did not feel comfortable doing so as much as I had planned on doing

Here is a link to my presentation
And just the slides are here

For the presentation From Syrup to Software: Landing a Tech Job in Vermont


Vermont Tech Job Resources: (content below)

Craigslist Jobs categories Internet Engineering, Software/QA/DBA/Etc, Web/HTML Info Design, less useful is “Gigs” section under Computer
Seven Days has an IT jobs category is a jobs-conglomerate and does a very good job. Search for the technology you know, etc HTML, CSS in Vermont Once you find a relevant search you can set up an email alert to keep getting any new jobs added to this category. (this is what the Burlington Free Press uses) UVM is not known for paying well but they have excellent benefits including free classes/tuition and a 37 hour work week.

Vermont Technical Community Resources
This meetup group has most of the events:
Although for some reason it does not have the Word Press group:
Nor the newer more “harware/maker” events such as at the Generator
And Labratory B

Online Technical News and Information
Hacker News:
Reddit has a lot of “subreddits” on all kinds of different technologies, or a useful one is cscareerquestions:

It can never hurt to look up a company you are interested in on , but take the reviews with a grain of salt

After working in development for 13 years I finally gave my first technical presentation last week, and I wanted to share my experience in the hopes that it might help someone else.

“Just write a great description for your talk, send it in, and then you’ll have no choice but to pull it together sometime before the conference.” As I gave this advice to a friend, I saw that this could be the answer to my own public speaking aversion as well.  If I waited until after I had put together a great presentation it was just never going to happen.

So, a few weeks later I sent an email to a local user group suggesting a topic I had recently learned quite a bit about and implemented for work, the Apache Solr Search Server. He was very receptive and we set a date about one month away, on which I would give the presentation.  

The panic set in two weeks from the presentation date. I thought I should learn more about Apache Solr and desperately tried to study the book I had, but kept finding myself too anxious to do anything but re-scan the same paragraph over and over (which I fruitlessly forced myself to do for way too long).  Then, when I saw the date of my talk was a little over a week away I began on the slides.  It was the first time I had used PowerPoint in over a decade.  I had no idea how to start so I just forced myself to keep making slides until I had about 15, which I thought was a good start for a 30-minute presentation.  This took quite a few hours and quite a few beers.  They were terrible slides and I knew it, basically just lists of bullet-points.  And my self-doubt kept interrupting after each one saying, “this sucks, your topic sucks and so do you.”  Which is hard to get past when the work you are doing does actually suck.  And so it was with great difficulty that I finished my first draft.

A couple saintly friends of mine were willing to sit through my first practice. Not only were they terrible slides, but it was a boring topic as well and I was not a good presenter. They stopped me shortly after I had begun and said they were having trouble following. I hadn’t defined several terms. I hadn’t really said what Apache Solr was. I hadn’t explained why someone might want to use it. It was hard for them to pay attention when they didn’t know the relevance. It was just me talking about configuration files. Instead, they said, I should tell a story. ( I thought, “Once upon a time there was this software program...”) But they were right, and I had to write the whole thing over again, which I did that very night, with a few less beers this time.  

Thus began my endless rounds of practicing, and then tearing apart my slides. I practiced in front of both technical and non-technical people. I ended up defining every technical term I used, even things I was pretty sure my audience would know, such as API.  As my sister advised, it takes 10 seconds to offer a quick definition and it is a kindness to anyone who might not know. Slowly my presentation took on a shape with an introduction, middle, and conclusion, and with all necessary pieces such as About Me and Questions? 

I allowed the rising panic I felt as the date approached to drive me to keep practicing. I got pretty good at explaining my slides. I had even put in a few that made people laugh. I practiced 6 times in all. 

On the day of my presentation, I was nervous still (maybe the panic had just become habit by then) but felt more confident due to all the time I had put in.  If I didn’t do well, at least I had given it my best shot, but I was pretty sure I had beat that presentation into something decent. Finally it was time to speak, and it went pretty good. The audience laughed at the appropriate spots. A few times I felt like my knees were trembling but the feedback I got was that I didn’t seem nervous. (Evidence that nobody can tell) At the last minute I had decided to demo an app made with that technology so they could see it in action, and that ended up not working, but I was able to skip over that pretty quickly. It was just extra anyway, not fundamental to understanding my topic. I told my audience I was a new public speaker and asked for any feedback they might have (something I read in "Lean In"), and everyone said I did great and there was nothing negative. 

Then I was so relieved to be done and have this monkey of a presentation off my back. I was proud of myself for doing something that scared me so much, and I had created a pretty good talk that I could give again. It was surprising, not only to me but to those friends who had watched my initial efforts, how much improved my final presentation was--almost unbelievable. And I have volunteered to give it again already, to a different group in a few weeks, and I'm not that nervous about it anymore.

So the moral to this story is that all you have to do to speak in public is find somewhere to start and keep going.