A Startup Retrospective

A few weeks ago, I started to pull back work on Vine Trails, and committed to just one day a week.

My co-founder Matt and I weren’t able to keep the same schedules – I was full time, while Matt was only available for a day. At the time I thought it would be better to change my hours to suit his, and have everyone progressing on the same page at the same time. But later, I realised that by agreeing to cut down my hours, I had actually declared that my interest was fading. It just wasn’t for me.

Everyone talks about the fact that you need to be really passionate about your startup idea to succeed, because things will get hard at some point. Your passion is what will drive you through the dip to see the other side. As the weeks progressed, and we learned more things, we adjusted the idea and the focus of the product. But Vine Trails was turning into something I was getting less interested in building.  I was running into barriers, and didn’t possess the drive to break through them.

My original idea was purely travel related – a trip itinerary generator. I wanted to build something that could answer this question:

I have three weeks for a holiday, and I want to go to New Zealand.

What should I do while I’m there?

That’s an enormous problem, and difficult to know where to start. So I decided to cut it down to a really focused vertical that was easy to define: wine tourism. Vine Trails was born.

The thing is, I really like wine. I enjoy travelling to wine regions and tasting wine. I would love if a product like Vine Trails existed already, and I would use it.  But there’s a difference between wanting to use a product, and having the drive to turn an idea into something real. I have friends who like to read about new wine releases, participate in forums, research wine regions, and subscribe to winery mailing lists. For them, that’s just fun and they love reading about it. For me, it would be necessary research rather than something I’d choose to do. When we started putting more focus on Vine Trails appealing to wineries, it just got less interesting to build.

I realised that the data element of the product is what I was passionate about – taking information about their wines and making it available in a new format, or letting people search through it in unusual ways.  I find analysing and visualising data really interesting – and it doesn’t really matter whether that information is about wine, or public transport, or economic growth. Making data accessible is where my interest lies.  I am passionate about data at a completely different level than I am passionate about wine tourism.

Lesson learned.

(Along with other things I learned about startups and team composition.)

Vine Trails still exists, in the capable hands of my co-founder Matt and my husband Niall, two of the biggest wine nerds I know. They’re both working on it part time, which means it will take a little longer to mature, but it’s definitely in the pipeline. I will be pitching in occasionally, but I won’t be the principal driver any more.

In the meantime, if you know anywhere in Sydney looking for data nerds, please drop me a line.

Creating a Music Matrix with the Web Audio API

Last week I stumbled on this Tone Matrix, which uses the Web Audio API to generate and play sounds. I got really interested in the mechanics of sound generation and wondered how they did it, but unfortunately, there’s no source… so I decided to learn more about the Web Audio API, and recreate the matrix as an exercise. The source is available on github.

I’ll be running a tutorial for Women Who Code Sydney in July on how this works, and plan to cover some different filters and effects you can run sound through to get more interesting results (the matrix in its current state is pretty basic). There is more mathematics than I had bargained for, but producing a basic sound doesn’t really require a lot of code.

You’ll need to have a fairly recent version of your browser to play with the demo.

Screen Shot 2014-06-18 at 8.14.51 pm

Things I learned:

  • You can use existing sound sources (existing files, microphone) but also generate a sound wave with an Oscillator.
  • It’s a pipeline. Only one thing should output to your speakers.
  • Each audio buffer note can only be played once. You need to recreate each new note to play.
  • Sometimes there are loud ‘click’ noises as you abruptly change the notes through the speakers. You need to cater for this with some filters, or gain (aka volume control).
  • The API has been in development/experimental phase for quite a while and there’s not a lot of comprehensive documentation available. Most of the learning came from code samples.

Some interesting reading:

Heroku vs Amazon from Australia

I thought this was interesting to share.  I live in Sydney, Australia, and I was looking for relatively easy hosting setup for an Australian audience. I had two options: go with a platform-as-a-service provider like Heroku, or spend more time setting up my own infrastructure with AWS which has a datacentre in Sydney. Azure isn’t available here yet, but it’s coming real soon now(tm).

Both Heroku and AWS offer free tiers, so I didn’t need to shell out any money. I’ve used AWS before, so I figured I’d give Heroku a try.

Heroku

I won’t cover the pros/cons of Heroku as lots of people have already done it, but deploying my first app was really smooth and easy. At the time of writing you can only host in the US (EU is in beta), so I went with the default US option.

When you deploy, your app runs on a unit called a dyno, which is heroku’s equivalent of a server, and your hosting dyno will sleep after an hour of inactivity if you’re on a free tier.   I noticed a lag on page load occasionally when the dyno was waking up, so I threw it in web page test to measure*.

It takes 9 seconds for the user to see anything meaningful on the screen. Ouch.

heroku-summary

heroku-graph

 Amazon Web Services

I decided to try Amazon using their platform-as-a-service, Elastic Beanstalk. You do share underlying architecture when you’re on the free tier, but there’s no concept of your machine ‘sleeping’ like the dyno does.

Once I got the deployment working, it was noticeably faster than Heroku for a cold start.  Time to start rendering is much faster at just under 2 seconds (and reducing that time is my problem now, not the hosting). Here are the comparison graphs.
amazon-summary

amazon-graph

There is a downside, though – hosting with Amazon takes a lot more persistence because their documentation kinda sucks. It’s huge and contradicts itself in different articles, so you aren’t quite of the right thing to do. I followed these instructions to deploy a node.js app and ran into three different issues, one of which was because I’m trying to deploy region which isn’t the default US-East. If I wasn’t already familiar with AWS, I might have given up.

* Technically, I didn’t test from Australia – I used the Wellington, NZ agent in case the Sydney agents were hosted in an Amazon data centre.

The Hipster, Hacker and Hustler

The term “Hipster, Hacker and Hustler” was coined in 2012 and describes the “dream” startup team. It consists of a hipster (designer) to make your product look great, a hacker to build it, and a hustler to think about strategy and marketing. Many VCs and seed funds swear by this mix, and admit that it affects your chances of funding and acceptance into accelerator programs.  After starting Vine Trails, I think I’m a convert.

Starting with a Team of One
I’m a software developer by trade, and I assumed I’d have a “head start” on creating a startup, because I have the skills to build it myself.  Plus, I could spend more time on fun things I actually wanted to build.

Nope!

I totally busted that idea within about a week. I was researching market sizes, volumes of goods, tourism numbers, checking out other competitors in the wine space, seeing how the existing industry worked, wondering how to build two sides of a marketplace concurrently, and how to attract people to a new product. I had lots to do, and was unsure of the best use of my time at any given point. Most importantly, I didn’t write a single line of code, unless you count a landing page (I don’t.)

Wanting to Share
About two weeks in, I realised I wanted a business co-founder, aka “hustler”. Someone who had skills in analysing a market, connecting with other businesses, or getting word out to consumers.  I lacked a lot of this experience myself, and it would be great to learn from someone else who’s done it before. I could also see the advantage of splitting tasks according to areas of expertise, achieving more in a shorter time frame.

Complexities
The tricky thing is finding your co-founder. You can’t pick any random person – it should be someone you respect and trust, has a complementary working style, and shares the same passion in the product as you do. Someone I meet at a hackathon is unlikely to fill that description. Also, someone who has my exact skill set isn’t going to add much diversity to the team – although it is more fun working with people you already know.

Every person you introduce brings a communication overhead, and potential divergence of product vision. There’s a chance you’ll move slower, because there are more people you need to convince before you try something. (Of course, there will be a lot of new ideas brought to the table too, which is both positive and negative as you’ll need to weigh up new ideas for goodness and feasibility.)  A couple of really interesting articles by SNTMNT and Derek Dukes talk about this issue.

There is also an issue of balancing time and dedication to the startup – what happens if one person has more time to dedicate than another? Or feels like they have more interest in the project, or is willing to invest more effort? No situation is perfect, and people bring their own imperfections to the mix as well.

Benefits
The immediate benefit I can see of the Hipster, Hacker and Hustler is keeping your momentum when you run into problem “X” – where X can be anything from “a good strategy for cold calling someone”, “analysing user metrics” or “how to make this cross browser compatible”.  Right now when I run into something I don’t know, I hit up Google, open about 10 tabs, read a bit, think a bit, find out if there’s any meetups about it, see click bait for an unrelated topic, read the twitter page for the author… and say goodbye to another hour of productivity.

If you split your tasks up, you can reclaim mental space that used to be dedicated to marketing, or tourism research, or whatever.  Sharing gives you more time and focus on what you do best. You also get the benefit of new ideas, another person who’s vested in driving the idea forward, and two chances of having a great day for the product overall.

My Experience
Vine Trails currently has one person who’s spent a lot of time on research and data (me), and two others who are part time enthusiasts. We’re definitely further along than if it was just a single person working on the product. However, we’ve had some hurdles too – everyone has different amounts of time they can spend on the project, and it can be challenging to bring everyone on the same page when we meet up. It’ll be interesting to see where we go from here.