Posts from November 2017

At Hootsuite, we value innovation. We believe that it is important to allocate time to step back and tackle impactful issues. That is one of the reasons why we hold regular internal hackathons. Hackathons are a great way to get people thinking out of the box, sharing ideas, and growing their skills.

Hackathon 11/17 Logo

How does a Hackathon work exactly? First, employees pitch ideas (usually based upon a problem that they are trying to solve). Everyone has the option to either pitch online (through Workplace) or live on stage. Either way, they express their idea concisely and specify what skills and resources they are looking for to help bring the idea to life. Then everyone gets to decide what they want to work on. You can sign up with someone who pitched an idea or you can always do your own thing.

Ideas don’t have to be strictly technical, and non-technical people can always ask for technical help in their pitches, if they need it. We make hackathons inclusive because processes, media, and other aspects of the business can also be hacked.

Once everyone has a team the hacking begins! This time we allocated three days of hacking. On the last day everyone gets to demo what they achieved, good or bad. After all, you learn the most when failing.


This time around we had two main themes: “Enabling the Platform” and “Automagically”. The themes are there for focus, but also to encourage participants to align their hacks with company goals. You can always stray from the main themes and #gorouge as we like to call it.

The “Enabling the Platform” theme is geared towards the Hootsuite third-party app ecosystem. We want to have a great platform in which other developers can add-on capabilities. Hacks in this category would make it easier for developers to contribute to the ecosystem or improve the overall platform experience.

The “Automagically” theme looks to make our customers’ lives easier, or to automate their tasks. From batching of tasks to advanced artificial intelligence, anything that makes repetitive tasks easier or more intuitive qualifies.

The Pitches

We hosted the live pitches on the HQ1 main stage. The pitches were also broadcasted live for our owls in other offices to watch and participate. There were 15 live pitches and 24 online pitches for a total of 39 great ideas. The atmosphere at the pitches was very lively, a great way of getting everybody excited and ready for three days of hacking.

People then got a chance to find a team. Every person that pitched an idea was standing with the name of their idea on a piece of paper. Interested participants approached the idea holder and had a chat. From there, the teams were born. Form Birds of a feather to #hoggr, teams both large and small got to hacking.

People hacking People hacking People hacking People hacking

There were a total of 43 teams of which 13 hacked on the Automagically theme, 13 hacked on Enabling the Platform, and 17 were #goingrouge. The total number of participants was 129 people, almost all of our Product and Development teams across the world (some of them in more than one team #youmaketherules).

Demo Time

On Friday, starting at 1pm, everyone got a chance to demo their hack. Every team had three minutes to demo and one minute for questions. Our Toronto and New York offices kicked off the demos via live feed. Then we demoed Automagically-themed hacks in Vancouver followed by Enabling the Platform and finished off with #goingrouge.

People demoing

At the end of each theme group everyone got a chance to vote for the best hack in that group. This also allowed for much needed breaks.

And the winner is…

After four long but exciting hours of demos the votes were cast and we had the winners. We had 2 theme categories and 3 extra categories:


Create AI can predict the performance of a tweet as a user composes it. The team created and trained a deep neural network on a dataset of 50,000 tweets with the goal of predicting likes and retweets.

Enabling the Platform

APIs and webhooks The team, created a new integration for third-party developers. We don’t want to reveal too much, but keep an eye on the Hootsuite developers blog for a follow-up announcement.

Learning Opportunity (Failure)

Scoring Social Engagement Scoring user’s social behaviour from 0 to 5 using machine learning; social behaviour being your engagement with post and engagement on your posts. The idea is to help gauge a user’s social change after going through Hootsuite Academy training or using Amplify / Amplify + Selling.

Non-Technical Hack

Goodbyes are hard David rounded out his previous set of Hackathon animated emoji with a brand new set for slack.

Mobile Hack

Drag n’ Drop Apple introduced drag ‘n drop with iOS 11, allowing to easily move content from one app to another. Until now, the Hootsuite app was left out – no more! Drag ‘n drop allows to drag text, URLs, images and GIFs from any app straight to the Composer to attach them to the message. The feature will be available in the next release of the app.


A hackathon is a great way of getting a group of people to really focus on one thing. It’s amazing what a small team can achieve in a small amount of time.

Despite most of the participants being in Vancouver, it was a global effort with participants in Toronto, New York and Bucharest. So much so that a team from the New York office won best “Automagically” hack. As a global team which is working to be #bettertogether, it was great to see a project presented through the livestream get chosen as the best hack.

This hackathon produced a lot of great working implementations but it also was a great learning opportunity. Not all hacks were technical successes, but we recognize that failing is part of the learning process. Having a “Learning Opportunity” category in the prices encourages participants to stand in front of everyone and talk about what they tried and what they learned about it.

We will definitely continue to have hackathons at Hootsuite and we will improve how we do it to maximize impact and minimize friction. One thing we want to do better next time is the demos. Some demos are great but other ones can sometimes drag on for more than three minutes. We are thinking of ways to make this process better for next time.

Last week, I had the great honour to be an attendee and a speaker at the very first KotlinConf in San Francisco. As a self-described Kotlin evangelist, it was a great opportunity to be inspired by the stories and projects of other Kotlin developers from around the world. With three session tracks, and 1200 attendees, there was no shortage of things to do!

I wanted to write a post about my experiences at the conference while it is still fresh in my mind. All the sessions were recorded and will be uploaded to Youtube sometime this month, I will post again a link to my talk when they are public.

Speakers Dinner

In addition to the two days of conference proceedings, as a speaker, I was invited on a Hornblower cruise around the bay the night before the conference began.

I admit that I had to fight the feeling of imposter syndrome on the boat with some of the great names in Kotlin. I saw Andrey Breslav, the father of Kotlin, Dmitry Jemerov and Svetlana Isakova, authors of “Kotlin in Action” that we had previously read at Hootsuite in our Kotlin Book Club. I spoke with Hadi Hariri, myself and Simon Tse had previously appeared on his “Talking Kotlin” podcast. I also got a chance to thank Alina Dolgikh, who has been instrumental in the success of our Vancouver Kotlin Meetup Group (join at

The cruise was great, we travelled out underneath the Golden Gate Bridge and braved the wind for a good view of the city. Sadly, my Pixel 2 has not yet arrived, otherwise my picture taken from above deck might have been clearer. Meeting some of the JetBrains team as well as the other speakers and connecting with them on a personal level was an experience that helped me to feel more comfortable speaking myself.

Conference Day 1

The conference began the following morning, in beautiful Pier 27, on the Embarcadero. Immediately upon entering the venue, we were greeted by all things Kotlin: banners, swag, even pillows on the couch!


In the keynote, Andrey and team introduced some amazing new things for Kotlin. Kotlin Multiplatform Projects sound very interesting! In the future, you will be able to share code between your iOS, Android, and web clients as well as your backend servers. An official Kotlin wrapper for React is out now meaning you could soon swap jsx for kotlin, exciting!

There were a lot of great things announced so check out the KotlinConf Keynote Recap that JetBrains posted on the Kotlin blog.

The Morning Sessions

There are so many new stickers, I’m running out of laptop room!

Cords and Gumballs

The first session that I attended was Mike Hearn’s talk “Cords and Gumballs”. The first part of his talk was about how Corda is using Kotlin in the banking industry. Some of his stories of the way in which they trained devs on Kotlin in house reminded me of our own adoption here at Hootsuite. We found that it was very easy to have devs fall in love with Kotlin.

The second part of Mike’s talk was about a side project that he has been working on to package Kotlin into native go-like binaries. The tool, Gumball, is open-source, and he invites people to contribute to the project.

What’s New and Cool in Kotlin Tools

Dmitry Jemerov, the aforementioned coauthor of “Kotlin in Action” spoke on new features of Kotlin and its tooling. In this talk we got a closer look at Kotlin multiplatform. This initiative is incredibly exciting. Being able to share code across Mobile, Web Backend, and Web Frontend has the potential to save vast amounts of development time and effort. Additionally, in the new serialization library, protobuf is supported out of the box!

I had made it one of the objectives of my attendance at KotlinConf to get my copy of “Kotlin in Action” signed by both of its authors, after this Dmitry was kind enough to be the first.

Over lunch I ran into Svetlana and she was happy to sign as well, now I am the proud owner of a signed copy of the book.

The Afternoon Sessions

After getting some lunch, it was time for the afternoon sessions.

Kotlin Static Analysis with Android Lint

This talk with Tor Norbye was a real eye opener. The Android lint program is incredibly extensible and powerful. I can envision how much time we could save on pull requests if we wrote a few lint checks to automatically flag and fix common errors. My big takeaway from this talk is that our Android team needs to sit down for a few hours with Android lint.

Lessons Learned Building a Build Tool

The next talk I attended was Cedric Beust on the build system that he created, “Kobalt”. There were two things that stood out to me from this talk.

The first were the problems of figuring out what nodes of a dependency graph are safe to build. Simon Tse and I created a tool called “Peon” that automatically creates Pull Requests based on changes to dependencies in a graph. I will expand on the details of this tool in an upcoming blog post but the core similarity with Cedric’s problem was that we had to figure out how to create the minimum number of pull requests and in which order to merge them, to propagate changes through the graph.

The algorithm that Cedric used in Kobalt was a similar to (though more advanced than) the algorithm that Simon and I used in Peon. Cedric’s algorithm allowed for the parallelization of builds, it could be a great extension to the peon tool.

The other piece of the talk which stood out was Cedric’s discussion of Ad-hoc Polymorphism. His solution of how to implement it in Kotlin is similar (though more structured) than some of the things that we do in our own app to decouple the way we call APIs for displaying streams of social content. Both I and Andy Fisher, an Android developer at Hootsuite, who was with me at the talk, resolved to take this lesson back to our own code base, to perform ad-hoc polymorphism in a cleaner fashion.

Kotlin Puzzlers

The final talk of the day was Anton Keks speaking about “Kotlin Puzzlers”. His talk was inspired by Java Puzzlers and it had a very interactive format. Anton showed small snippets of code and had the audience guess the output of the program, then explain why they thought it was so.

The whole talk was great fun and full of head scratching and even counting exclamation marks for:


In the end, I walked away from the talk with a smile on my face and a healthy distrust of the Kotlin compiler in certain circumstances. Check out Anton’s repo of puzzlers here:

Day 1 Evening

After the final session of the day, there was an evening full of events, a party in Pier 27 kicked off by a “Party Keynote”. I had to ask myself, “What the heck is a Party Keynote?”

Party Keynote

Thankfully our Party Keynote speaker, Michael Carducci answered that question for us. Starting with illusions on a software development theme and ending with some mentalism, including guessing that Stephanie Cuthbertson was thinking of her son Peter.

After the keynote, everyone was ready for a bite to eat. There was a lot of great food waiting for us, unfortunately everyone had the same idea and so it left to some long lines at the start.

After the lines settled down, there was still plenty for everyone and in the meantime, Andy and I were able to get a photo to commemorate the event.

Conference Day 2

After a great first day of the conference, I woke up on day 2 anxiously awaiting my presentation slot as the first after lunch. However, the first thing we had in store for the day was a talk from the always interesting, Erik Meijer.

My Life as a Tech Transfer Monad

I’m still reeling from this talk by Erik Meijer, on what exactly probabilistic programming is and how we as programmers can apply it to real world problems. However, There were two things I loved immediately from this talk. First, near the beginning, Erik had a very succinct description on the expressiveness of Kotlin.

The other is that, we as programmers need to learn to think and develop differently because machines are coming for our jobs vis-à-vis Machine Learning Algorithms.

My Talk

Now it was time for me to do some final preparation for my talk. I presented earlier this year at AnDevCon and I covered my experience here. KotlinConf was a lot larger though, with some 1200 attendees.

Kickstarting Kotlin Culture: The Journey from Java to Kotlin

I had been scheduled at the same time as Andrey Breslav and so I wasn’t sure if anyone would show up. However, I was pleasantly surprised when I had a room more than half full to present to.

As I mentioned in my talk, which I won’t go into detail until a later date when the video is published, I try to live by the principle of “working out loud”. Noel Pullen (who also wrote on Guilds at Hootsuite) gave me that advice on my first day at Hootsuite and it has really stuck with me. To me, working out loud means: Work passionately, know that what you’re doing will be valuable to someone, and strive to share what you’re working on with those around you.

This was a major motivator for me wanting to share our story of Kotlin adoption at Hootsuite. I hope that my talk helps others accelerate their adoption and to grow Kotlin culture in their own organizations and communities.

I was honoured to be able to tell our story at KotlinConf but I certainly had help doing so. I would like to thank my director, Paul Cowles, for supporting me and the team through our Kotlin journey here at Hootsuite, and for helping me tell this story. I also need to thank Simon Tse, who appeared on Talking Kotlin with me, and who wrote the first line of Kotlin at Hootsuite. Finally, my team at Hootsuite for driving Kotlin Culture with me, both within and outside Hootsuite.

When the slides and video of my talk are posted by JetBrains, I will share them here in another post!

The Cost of Kotlin Language Features

The next talk after mine was about the cost of Kotlin features relative to Java by Duncan McGregor.

The talk was very enlightening and despite there being a measurable cost to some of the features of Kotlin, null safety, let blocks, etc. Duncan’s conclusion is that “Everything is reassuringly OK”. So based on his research, keep using your fancy Kotlin language features.

Going Serverless with Kotlin

Next was a talk that I knew I had to attend from the title alone by Marcos Placona. Paul Cowles and I wrote on our experience using AWS Lambda functions for cross platform iOS and Android development earlier this year. That blog post formed the conference talk that I gave at AnDevCon in July of this year.

Marcos had experimented with a variety of cloud providers which was interesting as we have just used AWS Lambda and API Gateway here at Hootsuite. One of his points aligned with what we found, Serverless functions are very cheap to execute and the free tiers from cloud providers is generous.

I chatted with Marcos shortly after his talk about Serverless and about the open source library that we created at Hootsuite to help people set up and maintain Lambda functions with Terraform and Gradle. Our function currently uses Java, he inspired me to cut a ticket to convert it to Kotlin.

Two Stones, One Bird: Implementation Tradeoffs

In the final talk of the conference, Christina Lee talked about tradeoffs in implementation while reviewing some Kotlin language features.

She discussed some of the differences between: let, with, run, apply, and also. When I see these features discussed I think of the graphic that we created at Hootsuite last year to help us understand the symmetry of these functions. I’ve since seen a similar illustration in other places (a missed opportunity to work out loud on my part) but I will also share it here.

apply and also return the object that the functions are called on while run and let return the last expression of the lambda.

apply and run have ‘this’ as the receiver inside the lambda while also and let have the renamable ‘it’.

The symmetry of these functions makes them easier to understand and we have cases we each at Hootsuite described in our style guide.

Closing Panel

All good things…

The closing panel was very insightful and the panel answered a lot of hard questions. There were some laughs when Andrey was asked what else he might add to Kotlin. He rephrased the question as “What haven’t I stolen yet?” and gave immutable data as a possible answer.

It’s at the panel that I learned there are around 50 people working full time on the Kotlin language, no wonder they’re making such great strides with Kotlin/Native, multiplatform, and other initiatives! I’m very happy that Jetbrains has invested and continues to invest so much in the Kotlin language.

I also learned that 17% of all apps in the Google Play Store are using Kotlin! I’m sure that number will rise before the next KotlinConf. The conference app, on web, Android, and iOS was programmed in Kotlin using Kotlin/Native, Kotlin/JVM, and Kotlin/JS.

Andrey and Stephanie Cuthbertson also talked about the language foundation which was promised when Kotlin was made an official Android development language during Google I/O this year. They currently have a language committee and they are committed to developing Kotlin in a thoughtful manner. The committee so far has: William Cook, University of Texas at Austin, Andrey Breslav, JetBrains, Jeffrey van Gogh, Google.

Andrey reiterated that with Kotlin, he’s more concerned about the features that are not added than the features that are. He doesn’t want the language to become too large, if they add many new features in the future, it will likely be coupled with the gradual phasing out of other features.


After two whirlwind days the first KotlinConf is over! I can’t overstate how honored I was to be selected as a speaker and how happy I was to simply attend. I hope that I can continue to #workoutloud and share my journey with Kotlin and more!

If anyone would like to reach out to me about my talk, about growing Kotlin culture, or about the Atlas and Peon tools that we use at Hootsuite, please contact me at or on Twitter.