In 2013, we took our first attempt at defining what we do and how we’re going to do it. At that point our full-time team consisted of only two people: my co-founder Antti and myself. A lot has changed since then: our product and business model have gone through many modifications, and our team has grown to nine people. We realized that it was time to revisit the subject.
In August 2014, Sharetribe offices were relocated to downtown Helsinki. One of the benefits of our new whereabouts was the huge variety of lunch joints around us. Our previous location was Startup Sauna in Otaniemi, where our options were limited to a couple of student restaurants, so it was no surprise we were excited about the change of venue. We decided to take the full advantage of our new surroundings and try out as many lunch restaurants as we could.
Sharetribe strives to be the easiest way for anyone to create their own marketplace website. Now we are ready to make that promise. Two weeks ago we launched a completely revamped sharetribe.com, where you can create your site in 60 seconds. Over 1000 people from 100 different countries have already done that. The diversity of countries underlines the importance of our other big news: the new payment system works pretty much anywhere around the world.
Rob experienced a revelation after trying out Airbnb a couple of times. “The peer-to-peer rental model was a great experience. In my previous job I was fascinated with marketplaces and matching supply & demand, so I immediately started to think of ways the Airbnb model could be applied to other things.”
It is surprisingly often that I talk to people who have this idea of a marketplace for “sharing everything”. And it does make sense intuitively: people who share their tools are probably also likely to share their cars. And when you have built a network of trust for sharing one asset, why shouldn’t you use that for other assets too?
Have you seen this?
NoMethodError: undefined method `' for nil:NilClass
I bet you have, many times, way too many. However, it doesn’t have to be so. There’s a pattern that helps you to get rid of the errors you get when handling nil-values.
Meet Option pattern! The idea is simple: Wrap the value in a wrapper and treat nil values the same way you would treat non-nil values.
There are many existing gems that use this pattern. Also, I rolled up my own version called Possibly. In this post all the examples use the Possibly gem.