#nescala

[makingmeetup]

NE Scala 2016

Towards the end of the first week of March, on March 4th and March 5th, Meetup put together a small team of engineers who volunteered to attend the 6th annual Northeast Scala Symposium in Philadelphia.

I am an engineer on Meetup’s Member Engagement team, building a system that delivers smart and personalized notifications to members on our platform. I am also a part of Meetup’s Core Engineering team, where we are using Scala a lot in order to build out our platform. Given my work and interest in Scala, I was one of the engineers who participated in the trip, and I’d love to share some of the things I learned during Day 2 of the event!

This was the first language conference I have ever attended and it was even more exciting to me, given that I only started working in Scala since I joined Meetup, almost 2 years ago, straight out of college!

Day 2

Day 2 was the unconference day and it started with a casual meeting, in which every participant who had something to present would take a timeslot on a spreadsheet, such that at the end of the meeting we had a relative schedule for the day. After this, everyone was free to go to whichever presentation was most appealing to them.

And off I went!

Early Morning Category Theory with (Rúnar Bjarnason)

Eager to learn more about Scala and the theoretical background behind it (and being a math nerd), I picked Category Theory as my first presentation to attend. I did not know much about what Categories are in Scala and what kind of rules govern these entities, but I went in excited to learn something new.

The talk started with an abstract definition of Categories as collections of objects and arrows (or maps/morphisms) that define relationships between the objects. These concepts seemed very familiar to me from those of Set Theory.

Rúnar went on into describing Functors (maps between Categories, that preserve their structure) and then explained what Monads, Monoids and Comonads were, while also doing some whiteboard Scala examples of all of this. These topics were necessary background needed in order to answer a question posed by someone in the audience:

Prove that List is a comonad in the monoid category of List

Using the information absorbed up to that point, we were able to follow a simple proof of the statement.

This was my first ever exposure to Category Theory and I loved it! Rúnar's explanations made me dig more into it after the conference!

Scalaz-Stream Workshop with (Rúnar Bjarnason)

The second presentation I went to was also led by Rúnar Bjarnason, but this time it was very hands-on. He introduced us to a small IRC client & server built using scalaz-stream and everyone in the room had to implement a feature of their preference to add to it.

I went on trying to implement the ability to change nicknames while in a chatroom. The process of working with scalaz-stream and, implicitly, with scalaz was relatively new to me since I haven't written pure functional code using scalaz before, but it was a really good experience to be exposed to both of these Scala libraries.

By the end of the workshop, my implementation ended up being somewhat functional :)

Living with SI-2712 with Daniel Spiewak

After a couple of other presentations, I got to my last presentation of the day. It was about a known Scala compiler bug and it involved a lot of live coding, type-level programming, category theory (d'oh) and just pure amazement.

The gist of the presentation was a proof of concept of the compiler bug and ways to get around it. It was very well explained and, even though the material got pretty intense towards the end, I enjoyed the deep dive!

Conclusions

I really enjoyed my time at NE Scala and learned a lot of new things, from theoretical aspects of Category Theory, to more applied concepts using pure functional scalaz. I am very excited for the next conference I'm going to attend (or even unconference, since Scala Days 2016 is approaching and will be in NYC :) )!

[coderspiel]

Participatory Conferencing

We're less than a week from the [Northeast Scala Symposium][nescala], and the few remaining RSVPs spots (out of *three hundred* this year) [are dwindling][rsvp]. The symposium was born as a gathering of the Scala meetups of New York, Boston, and Philadelphia. We simply took the planning and budgeting processes of our meetups and scaled them up. Which is to say, we didn't do much planning or budgeting at all. We held the first nescala in one of our usual meetup space and we selected speakers with a voting process open to everyone who RSVP'd. This not only seemed fair, it saved us the task of trying to anticipate everyone else's preferences. This shooting-from-the-hip style of organizing has worked well for us organizers and, as far as I tell, for the attendees. Or rather, *participants*. Everyone at the gathering--not just the esteemed speakers--must contribute for it to be special. Otherwise we could all stay at home and watch the same dudes talking on youtube. Each year nescala has grown in size more or less on its own. We haven't made growth a priority, but it is gratifying and it's got to be good for the Scala community that a regional conference is growing. The greater the number of participants in nescala, the more people who have to be registered, fed, cleaned up after, and--well--taken care of. I would love it if we could do this as a group, but you have to remember that this is a conference by and for programmers. Nobody is going to cut short a conversation about the pros and cons of iteratees for something as mundane as disposing of paper plates with pizza crusts on them. Meetup organizers excel at throwing away paper plates, but as the conference grows there just aren't enough of us to keep up. So we've done the only rational thing and hired people to do this for us. And it works out: as the conference grows we get $50 from more people and we also get more offers of sponsorship. But there is one side effect of growth I'm constantly on guard against: **commoditization of the experience**. The more paid staff there are helping make the day a success, the more people will confuse the organizers with paid staff. The more they will see a customer-service relationship where there is none. The less they will be active participants in the symposium, and the more they may taint the experience of others--including, if I may be selfish, the organizers. We don't make money off of nescala and have no reason to. For a living we write software, like you. For a hobby we bring people together, and the payback is in seeing others participate actively in the conference. Watching people help each other. It's as simple as that. See you on Friday. [rsvp]: http://www.meetup.com/nescala/events/97192402/ [nescala]: http://nescala.org/

[coderspiel]

Recently, Marakana headed east for The Northeast Scala Symposium in Boston which featured 16 talks, one keynote, and one panel discussion on a broad range of topics surrounding Scala and functional programming. Marakana recorded all of the talks and will be posting them below as fast as we can edit them.

[coderspiel]

Northeast Scala Symposium Agenda

Go to the full post if you don't see an agenda above

Note to speakers: it's up to you to allow time for questions. We'll be starting talks and announcing breaks at the designated times.