TechTalksTO Underground

Tech Talks TOAlong with the team at FreshBooks, StartupNorth is proud to support TechTalksTO. TechTalksTO previous put together a series of speakers at the Gladstone Hotel on West Queen West that feature some great talks about technology for Toronto developer community. We’re very happy to be a Sponsor and Media Sponsor of their upcoming conference event on August 13, 2011. It’s a great group of front-end, back-end and devops focused entrepreneurial technologists.

What a great way to spend a Saturday before flying out to GrowConf later in the week.

The Details

When: Saturday, August 13, 2011
Where:  Toronto Underground Cinema, Spadina Avenue.
What:  All-day conference + After-Party


Speaker Lineup

After Party

One of the best parts about our previous TechTalksTO events were the unofficial gatherings afterward. They were always a great opportunity to network and have some great conversations. We enjoy it so much, we figured for this event, we’d make it an official part of the day so your ticket will include admission, food, and drinks at the exclusive after-party Saturday evening to be held at a nearby establishment.

Tickets

Tickets are available NOW! Alas, due to the size and scope of this undertaking, we have to charge actual money for tickets for this one but we think you’ll totally get your money’s worth. Tickets will be priced at $150, including admission to the after-party, which will also get you a couple of drinks and some food. We also plan to have some food and drinks available throughout the day at the conference venue.

Teaching Software Engineering and Startups at UofT


AttributionNoncommercialNo Derivative Works Some rights reserved by SteveGarfield

About 5 years ago I was asked to teach a 4th year undergrad software engineering course at the University of Toronto. The course had been previously cancelled due to low enrollment; in an era dubbed the “Software Gold Rush” a cancelled course indicated something was wrong…

Software engineering is difficult to teach
Students are expected to learn how to avoid mistakes they never made. A great divide results from the instructor talking about concepts suitable for a mature organization when students are all about working their ass off and getting things done the night before. We borrowed several lessons from startups, having been personally involved with two startups over a dozen years. The way startups work are much closer to students ways of doing things. Since launch, course enrolment has tripled and two Y Combinator applications have been submitted based on class projects. Here is what we have learned so far:

1. Use a startup software process
Students are all about getting things done the night before; similar to how startups work. Teaching a heavyweight process feels foreign because students haven’t made the mistakes to understand reasons for the overhead!

2. Change the project every year
There is nothing more of a turnoff than a make-work project with antiquated technology. Instructors that use the same project over and over are sleepwalking. A new project each year puts the instructor and students on equal footing, solving problems together. Make the class goal to have someone apply to Y Combinator. Discuss the non-technical issues of software such has how people are going to use the product, how are you going to sell it, what is the competition like, what is the business plan. One big class project brings issues into the classroom better resembling the real world. This also allows non-trivial projects to be developed and students to test-out roles (e.g. project management) that would not otherwise exist.

3. Allow controlled crashes
Let the students make mistakes. For example, let them avoid source control. A student who looses code because of clobbered checkins will be a lesson learned for the entire class. However, when crashes occur, it is the instructor’s responsibility to manage and fix it. After the mistakes have been made, teach them about process. Keep things light and give them references for their future travels. During lectures on process, tie them into the mistakes that were made. Make process real.

4. Demo early and often
Create a culture where the principal deliverable is working software rather than documentation. Use early demos to correct mistakes and give guidance rather than having them worry about their grades.

5. Instructors should code
The instructor-student relationship changes dramatically if the instructor contributes code. Everyone becomes a peer instantly. This improve communication and follows the startup philosophy that even managers should write code.

Next steps
The course has been well received by the students at UofT. I have much more regular contract with students from this class than the other courses I have taught at UofT and UofW. I am interested in hearing from anyone who is interested in providing continuity to the students; a partner that would provide input on the project at the beginning, stay involved with it during the course, and offer a path forward for interested students ready to commit to a startup.

How to Hire Me, A Technical Co-Founder

There has been a lot of buzz the past 6-8 months about hiring great technical co-founders. The implication seems to be that being a non-technical co-founder is a handicap of sorts and that CEOs buy sandwiches before the product is finished. Apparently coding & building great products is hard, but running the business is easy. Here are some articles:

Why You Can’t Recruit a Technical Cofounder
Quora – Technical Co-Founders
Please, please, please Stop Asking How To Find a Technical Co-Founder
Thoughts On Hiring a Technical Co-Founder

I am a “technical co-founder” at Peek – I code, keep big scale systems up, hire & fire, set dev processes, and all that other technical stuff. So let me tell you about how I got recruited into Peek by Amol Sarva, @amolsarva.

Sell Vaporware

Amol had one VC committed to Peek in our A, and had a letter of intent from Target (yes – www.target.com – that Target) to sell Peeks nation-wide, in-store in the US. The status of the “product” – he had a carved out a wooden model of the Peek (ala Palm)!! And these deals were huge – a $15mm A round with half committed. Target – nation-wide for Christmas 2008!! These days I hear too much crap from “deal guy” founders about finishing product before doing deals. Lame. Be a stud – go sell vaporware. Go get real customers who pay you real money. Go find partners and distributors. I have seen countless, great sales guys in my life sell smoke and mirrors. Why can’t you?

This guy hired me

Hire Other Studs

Amol had recruited John Tantum, former President of Virgin Mobile USA, as our chairman. He had an all-star marketing & retail guru lined up. Our advisory team was the president of BlackBoard, SVP strategy at Intuit, and the former head of the FCC. No matter what, I knew I was going to learn and have an awesome experience working with some great folks.

Be Generally Awesome

Amol was an interesting guy in general. He had a PhD in Philosophy from Stanford. He was/is building a new property in Queens. He took a photo that hangs in MoMA. The blog I write on is startupnorth, the “blogs” he writes on are Salon & Business Insider. Being generally impressive is important. The important question here is the Peter Thiel question, why is employee #20 going to come work for you? The weight of the CEO’s personality and accomplishments matter here. Senior guys will want to know the accomplishments of your business as well as the accomplishments of your management team. You have to be generally awesome enough to bring people in if you aren’t one of those super red hot, Twitter-esque companies.

Be Top Amongst Your Peers

Amol, while starting Peek, was mentoring other founders. He was one of the original members of Founders Roundtable. His peers looked to him for advice on starting a company.

Now, I know this is a bit of a love-in of Amol. And it also probably feels like a pretty high bar. All you have to do is go get a PhD, raise $15mm and get a distro deal done with the second largest retailer in the US before you can hire great technical co-founders.

Not quite. The main lesson is this. Forget your technical co-founder and realize that the “product” is one aspect of your business. Potentially an important one (also potentially a complete waste of time you need to pivot off of). You need to start consistently proving that you can make this business successful without having a “heroic engineering, product only” mindset. Can you on a day-in, day-out basis creatively solve the problems of the business such as acquiring customers faster/cheaper, reducing churn, recruiting great folks, financing the company’s goals, having great customer service, delivering everything on-time, getting great advice, navigating treacherous competitive waters, and so on and so forth. Can you relentlessly out-execute with or without the crutch of great product and fabulous engineering? The way you have built the business pre-launch tells me a lot about how you will run the business post-launch.

If you can do stuff like Amol did, you’ll be fine. If you are buying sandwiches… sorry, go find someone else.

I’d love to hear from other founders (technical or not) on how they both built their company pre-launch and how they found their technical co-founder.