Who You Calling A Jesse?

We are just a week away from the third StartupCampWaterloo at the Accelerator Centre on North Campus in Waterloo. If you work for, own, or are thinking about having anything to do with a startup in the Waterloo region you should come out and meet other like minded folks. All are welcome.

StartupCampWaterloo is a community run event that gives startups a chance to test their ideas on their peers. Everyone who wants to present is given 60 seconds to get the audience interested in hearing more. The audience then votes and we try to give at least the top five a chance to present and get some feedback from everyone.

If you just want to see what this all about and get some free pizza and chocolate bars, you are welcome to that too ;) Please sign up on either the wiki or the facebook event.

Illya posted some thoughts on Agile Release & Testing Procedures and instead of writing a big long comment I figured it was worth a blog post. At the University of Waterloo I have had experience deploying a number of different applications for a variety of audiences… it is next to impossible to get all the details in a post but here is the general truth: there are no enforced institutional wide procedures for web applications. You might think the lack of procedures is bad but it is a result of the relatively low risk environment (even though the campus community has a low tolerance for bugs and changes). There are rarely formal teams of developers, it is mostly the loan coder building a specialty application – enforced procedures would frustrate them.

When you are dealing with a simple web page, say the uni home page, I have essentially covered the typical user acceptance, performance, and stress tests when the page goes live. I go through the gamut of web browser testing, try some OS variations out, and then get it out there. There is a relatively low risk here as the users don’t interact with a database or a whole heck of a lot client side. Once rendering issues are dealt with, it is pretty much unlikely to have other issues. This is with 30 000 or more people seeing it within a short period of time too. I had relative success but I think it was more luck and the fact we kept web pages simple.

Stepping up the development a bit, throw in a Ruby on Rails or PHP application. My testing procedures involved pretty much the same as the web page testing: poke away at it, fix bugs as they appear, and get it ready to go off of the development server to production. We (co-op student and I) never really sat on changes very long. The thinking was that if it went bad on the production end we just roll back the version, fast. When I made the jump to Ruby on Rails development with Capistrano and SVN that became so easy it was scary. On many occasions we had new versions going up two or three times a day. Minor changes, but they add up. This meant a lot of bugs made it out to the community version but as a whole the community appreciated seeing the progress. Our harshest critics were few and usually the type of people that would sit on things until they are perfect, the web is never perfect.

Now I find myself in the .NET/C# development world. I am happily hacking away at the JavaScript on the front end but I still live in the development environment. Here we have a solid team, a lot of developers, some serious tools, and totally different requirements from the client relationship/expectations end. At the moment we are doing limited testing that makes sure it works and then pushing it to an environment that a group has a ‘sanity check’ and gives us feedback. Releases are going out on a weekly build routine with a daily routine for an internal release. The whole process is evolving as we go but in a very general sense we are aiming to maintain a weekly build schedule for one set of users, daily internally. Our goal is to not leave the application in a non-working state and at any time the build could go live. This habit takes time to develop though… I don’t expect us to be in the groove until over the summer.

That is the nutshell version of what I have had experience with, I suppose it is Agile without the buzz terms. Personally I don’t see a reason why any web application couldn’t work on a daily build process. If you break the big change down to a lot of little changes you reduce the risk of breaking it and you ensure stability (so the theory goes). The problem is that in order to break a big thing down to a bunch of little things you need to take the time to talk it out, plan it out, and scope out what goes into a big thing. It is a way of thinking and it doesn’t happen overnight, most people need experience thinking that way.

I am interested to know what other higher education folks are doing with release and testing procedures.

This Saturday is BarCampWaterloo (number 6!) from 1pm to around 7pm (we may retire to the pub before that) at the Accelerator Centre. A much more toned down event compared to StartupCampWaterloo, BarCampWaterloo is where people come to explore ideas and maybe get themselves ready for a DemoCampGuelph (which happens to be April 9th at the Albion in Guelph). I might show some of the stuff I have been working on this weekend ;)

DesignCampWaterloo is March 26th (Wednesday)27th (Thursday) starting at 4:30pm in the Tathum Centre on the University of Waterloo campus. The first one was a bit difficult to follow being in the SLC and all so I am really looking forward to it in the TC. Plus I just have to go up two floors from my office to attend!

There is also a RailsNite next week on Monday at Ceaser Martini’s. Not sure of the start time but I think 7ish might work.

Update: RailsNite does start at 7pm and there is a Facebook event created for it.

Another update: Rick Segal is not coming to Waterloo for his VC roundtable, but he is coming to Guelph on April 28th… Perhaps Ali is influencing people now.

Yet another update: DesignCampWaterloo is Thursday not Wednesday.

With our second StartupCampWaterloo behind us here in Waterloo we hit a milestone. Over 100 people were in the main area of the Waterloo Accelerator Centre to talk with Startups and help each other with ideas (quick estimate based on 88 chairs in the room plus Ali’s colourful chairs). I am pretty sure all those that demo’d got some useful information and experience out of the evening.

A big thanks to Stefanus De Toit for opening up the evening and breaking-in the crowed by sharing insights like: Turning academic research into a product is hard if you don’t keep your paperwork in order; hire your friends; wow people with lots of 3D chickens to get investment (actually prove your concept with a solid demo). Another big thanks to Austin Hill for closing off the evening with a great presentation which included: don’t be afraid of sharing your ideas because someone already tried it – it is your execution that is important; Canada needs more of its successful entrepreneurs re-investing in the startup scene; beware the vulture investors; do a startup while you are a student; it helps to work for a startup if you are thinking about a startup as startup culture is infectious.

What was learned from this one is that 60 second intros with voting works out really well. Keeping things short and keeping the slides out of it kept the conversation interesting and focused. The big buzzer also helped. Only took one person being caught by it—no one else dared challenge their time limits. Plus it kept us on time, mostly.

I had a lot of good feedback and now can relax—until the next one. What are we going to do next? BarCampWaterloo is on March 29th, a DemoCampGuelph will be in April, and StartupCampWaterloo3 will be sometime in May. If you can’t figure out if you want to go, I have a post coming up tomorrow that will cover that ;)

Other folks to thank for making the trip from places afar and/or helping out last night… The Toronto folks venturing outside of the GTA in their large 4×4: David Crow – thanks for the books and disruption, Jevon McDonald,  Jonas Brandon.   Ali Asaria brought some chairs and name tags and Simon Law for came down from Montreal. The other organizers Simon Woodside and Mic Berman ensured that we appeared as unconference as possible ;)

Most importantly, the night was good because of the folks that were there. Waterloo has a great community.

It is interview time here at Waterloo. It happens once every four months, thousands of students and employers enter a dating game for talent and experience. Waterloo is a bit unique having a building dedicated to the process (just happens to be where my office is) and a frequency of three times a year for the process to run. Large companies like Google, RIM and Microsoft are hear hiring large numbers of students but so are local startups like AideRSS and Semacode along with all sorts of companies from different fields and different sizes. Posters on the walls with all the different information sessions show all the opportunities for students.

Why do the companies come here? Waterloo has the talent and I would argue there is far more and better talent than Stanford (update: Larry disagrees or does he?). Our students go to the Valley or Seattle or Boston or Ottawa and all points in-between to work for big names and get started on their carriers while they are working on their undergrad (or grad) degrees. A lot them stay local (Google and RIM are in Waterloo, along with a lot of other interesting employers) and even more would like to stay local for a term or two if a great job can be found.

For local web/tech startups this is a great opportunity. If you developing an idea and you need someone that can code and wants to contribute, for around 10K you can get a junior student for four months to do that. Senior students are more but you get higher quality and more experience. Just to prove a startup concept though, a junior co-op student is inexpensive and hugely beneficial.

The project I am working on depends on the quality of Waterloo Co-ops. We are building a new system to run the job/dating game and have a great bunch of students to do that. They code, they ask questions, they learn, they are excited, and they build really cool things from your ideas. Over the years I have worked with a number of different students and all of them made me look good—which is what you want when you hire someone, right? ;)

There is a side benefit to local startups hiring students I think as well. If you keep the students here, keep them engaged, and get them excited about trying out their ideas you help the local community build resources. I think it’s one part of the puzzle that may help Waterloo’s stealthy startup scene become even more open and exciting.

If you are wondering how to hire a co-op, contact CECS and they will have you set up in no time.

If you are in the Greater Waterloo Area (roughly Milton to Woodstock in highway 401 terms) and have a thing for startups you should come out to the second StartupCampWaterloo on February 26th. Our first one attracted a great group of participants and inspired similar events in Toronto and Montreal. The event is free, the refreshments are provided thanks to sponsors, and there is working wifi. All you need to bring is your expertise, ideas, and an open mind. We have undergrads, grads, alumni, startup inclined people, technologists, and other various characters in-between that make up a large group of people all eager to share and develop ideas.

This event is informal and fun. We aren’t expecting polished presentations. The audience would prefer that you use little to no slides if you present. What you should have is a passion for your idea/technology/etc and the ability to receive open and honest feedback. The schedule is set at the event by those at the event by the participants so be sure to get there on time (starts at 6pm, wiki has details).

Please sign up on the wiki, look forward to seeing you there!

The recent buzz online between WaSP members over IE 8 is approaching lunacy. With the respected Zeldman suggesting WaSP co-lead Drew was not doing his co-lead job of signing an NDA with Microsoft. Lets step back and think about the lay of the land for the moment.

WaSP has a Microsoft Task Force and an Adobe focused Task Force both with NDA requirements, both companies are now seriously competing for the web developer market. The lead of WaSP shouldn’t be NDA’d by either but they should be informed when an announcement is coming and that is the Task Force leads job.

WaSP needs to refocus and those in all the task forces need to shake their heads at recent events and figure out their next steps. Rachel asks what happens now? Well I am inclined to say re-state the goals of the organization, re-evaluate what each task force is doing and how that fits in the goals, and ensure process are developed to maintain a professional presence.

I also commented on Rachel’s blog that I believe SXSW is partly to blame for some of the recent mess. Why? People feel cut out of contributing if they don’t go to Austin. I know I do and what is worse I know that isn’t totally true. WaSP needs to distance itself from all events unless it runs them, at least for now. Let the participation focus around online venues and crank up the advocacy once things are figured out.

The next big challenge is in front of us. IT departments now have massive, poorly developed, monsters of web applications to maintain… or Sharepoint. They don’t want the browser to change, not now, not ever. WaSP, there is your new enemy.

For the record I don’t much care for the meta targeting but I won’t hate it… just think it is a quick fix, not well thought out, but isn’t that what ‘beta’ is for?

In my relative short career I have not had the pleasure of surviving a unionised environment except as a summer student doing landscaping work for the City of Sault Ste Marie. IT related work environments just don’t seem all that interested in a union, I would argue most knowledge workers have little interest in such a club. However here we are in 2008 at the University of Waterloo facing a vote in an attempt to certify OSSTF as a bargaining unit on campus. The vote is today however the outcome won’t be decide for approximately a month due to some dissagreement in who is in the bargaining unit.

The one thing that does get me about this entire process is how the law in this province favours unions over the individual. Maybe in industrial work environments the method used to unionize makes sense as workers generally may be easily replaced and can be easily bullied. However in a professional work environment, where it can take a few months to a few years before a worker performs at top form with higher education credentials, it feels like the whole process tramples on your rights no matter which side of the fence you sit. The behaviour out of the union itself just feels like they are after members, they don’t actually care about the workers otherwise they wouldn’t pursue unionization where the support is 50-50 at best (here it is 60% against, but they need to vote).

This whole experience has taught me a lot and I’d like to think I managed to get through it, up to this point, as President of the Staff Association (the opposing force) with only being called a few names: Meat puppet, lap dog, etc. Oh and apparently I have been paying people to vote… that would mean I had personal wealth large enough to do that. Cool, someone tell my bank manager ;)

Over the past year or so the MMNP effort has been working on ways to utilize mobile and media based technology on campus. A year ago a pilot project looked at the possibility of students replacing their land lines in residence is relatively smart phones. Lots was learned (primarily that students are shell shocked by the telco cost and don’t really use them even when a large chunk of costs are covered) and the project moved on to different ideas. One of those ideas was a living environment that doubles as an incubator for entrepreneurial students.

Enter 2008 and the announcement of VeloCity. The Daily Bulletin article covers all the details. From the VeloCity site:

“It’s a place where some of UW’s most talented, entrepreneurial, creative and technologically savvy students will be united under one roof to work on the future of mobile communications, web and new media.”

I was involved with the project early on and it is great to see that Sean has taken his idea and made it a reality. I expect to see some exciting things come from this housing experiment. What a great opportunity for some students!

Ever had a bit of technology your use dictated to you by an IT department? Does it not even come close to meeting your expectations or requirements? Is it usually web based technology that is letting you down? This type of problem stems from what I call a ‘square peg, round hole’ philosophy in IT – when decisions of what technology to deploy is based solely on the ability to provide support, not the requirements of the project and/or an analysis of features required by the user. It seems to happen far more often with web based technology.

In a conversation with a colleague over a beer I tried to understand why this happens. Sadly I still don’t understand why, but I do better appreciate the position of people that decide to hammer that square peg in. But I think it because they don’t understand or have an actual use for the web themselves (that is a totally different post).

I believe this happens in every IT department and it stems from the environment. IT finds itself in a situation with limited resources to hire new staff even though they are tracking time on/and tasks and there is an expectation that IT needs to support everyone regardless of expertise. There is a project or group or department that has decided to use a particular technology. Reality kicks in and the service end has to learn to support the technology so a decision is made to apply that same technology to others that have similar but not the same requirements as that project group.

What happens next is ugly. The clients expect something that usually different because they may want the same features but they would apply a different priority to the features they use/need. This influences their expectations on the total experience. Take a content management system (CMS) for example. One group might put a high priority on workflow management, another on user management, another wants a templating scheme, another wants a forum, and another group really wants a wiki. A CMS can do all these things but I can’t think of a CMS that can do them all as well or anywhere near as good as specialized software.

However, CMS vendors will promise support and the ability to meet the demands of the user. This pulls on the support strings of IT. Rarely, if ever, will you find a CMS that delivers to a diverse groups expectations. What happens is that any number of groups become disenfranchised with the software and the overall project of deploying that technology is doomed to failure or mediocre success at best. The CMS vendor comes off either not being paid and/or looking really bad. The IT department comes off looking unprofessional at best which puts pressure on them to produce, and the cycle continues.

What should happen is that the IT department assesses the features as well as the priorities. They evaluate the technology providers based on that clear idea of what are ‘deal killer’ features for people. If it reaches a thresh hold that makes it impossible to please even 70-80% of the clients then IT needs to break down the technologies and groups not force them all onto one.

The web offers the opportunity for this to be easy. Web services, web sites as your API, universal log ins, etc. all make it possible to integrate different solutions on the data level. Sadly I think IT still approaches web apps as black boxes that work in silos.

The moral of the story for anyone building a web based service is that to really be a hit with medium to larger organizations you need to offer integration and openness in your apps. If you can be the folks that develop the integration tools as well as offer your product you can likely charge more based on a successful track record. At least from where I am sitting ;)

Last night I attended StartupCampToronto which was put on by the guys behind StartupNorth. It was a really good event with some intelligent entrepreneurs and a great audience that weren’t afraid to speak up. The format was simple, five minute presentation with roughly 15 minutes for questions. They did let it go over a bit if the conversation was a good one.

It wasn’t until the last presentation that I really go excited though. A couple of students from U of Toronto came with their idea and prototype for a really easy portfolio manager. They had a grand plan for how this can work which had its issues. The crowd jumped on it and offered some great advice which I hope helps them create a successful product. That, I believe, was Simon Woodside’s motivation behind StartupCampWaterloo. When he had an idea for his company/technology it was hard to get that advice to move it along. For students and researchers or anyone else really, it can be hard for them to understand the market their technology might work in. Yes there are organizations designed to help but the community nature of a StartupCamp I believe works better for a lot of people.

A lot of the talk about entrepreneurial learning curve is that you have to fail to succeed. StartupCamp was designed to encourage people to at least try with the support of the community to offer some guidance. Could some failures be avoided by the community helping them figure out the obvious mistakes?

A secondary benefit is the community is enhanced from the fresh ideas and energy out there. With that in mind, next StartupCampWaterloo is February 26th. Looking forward to it.

It has been about two years since the unconferences started in Toronto. Shortly after it started, David Crow coined the community is the framework discussion and helped inspire folks to help build communities. It took me a while but September 29th, 2007 saw the first BarCampWaterloo. We are now six events (plus DemoCampGuelph) into it and I think with StartupCampWaterloo I feel confident saying there is a solid community in Waterloo that finds community driven events useful and are willing to participate.

Why organize these events? Personally I am not an entrepreneur with a few attempts or successes at starting my own business under my belt. I have not experienced the joys and fears of starting a business but I have experienced years of feeling isolated within both the University community and the larger regional community. I have had more web technology contacts in the US than I do in Canada, more of a sense of community when I attend the big Adobe MAX conference.

Starting and continuing a ‘BarCamp’ movement in Waterloo is about the entire tech community: the web developers in big companies, the entrepreneurs, the inventors creating things for fun, the people that are researching the application of technology and/or how people interact with it, the business minded folks that would love to help something grow. However, the desire for topic specific events is there and that is why we (Mic, Simon, Brydon and Ali in Guelph, and myself), with the help of the community, have broken the events into three main forms:

• BarCampWaterloo – something for everyone who attends. We have talked about how to age a good ham, use two keyboards at once, cool coding, and how to build the technology in your business. Its a day long event that strives to include everyone who attends.
• DemoCampGuelph – this event aims to showcase working projects. You demo something that works, no slides, no time to babble.
  
• StartupCampWaterloo – the most recent experiment that borrowed from the spirit of DemoCamp. This event focuses on the start-up experience and aims to give folks a place to get the feedback they need to keep going and succeed.

The events are staggered monthly and all three events offer a place for folks to connect. Through these connections comes a sense of community. Someone other than your dog or the voices in your head that share the same passion as you are out there and they want to help. You may leave an event inspired to try something new at work or in your own business or find something to work with on your next big idea. That is the potential power of the community that I currently see in Waterloo. With the success of the Accelerator Centre and the construction of another Accelerator Centre along with a Research Accelerator Centre it really feels like Waterloo is on the verge of something. Infrastructure (we do need a free community wifi) and the brains are here… a vibrant BarCamping community will certainly help I think.

It is not that I don’t acknowledge the groups that have been organizing events for a while. The first one that comes to mind is WatStart which is an effort led by Gary Will. The launch of the new WatStart site I think offers a great place to organize community resources, I hope people start using it. Then there are some of our now regular BarCampWaterloo sponsors: Communitech and TechCapital, they have done a lot positive things for the entrepreneurs in the community.

No matter where you are I would encourage you to seek out the local community and participate. Every person that contributes enriches the experience for everyone. There are other events in town and groups that meet mingle. DesignCampWaterloo, UX group, a new RailsNite Waterloo, a .NET users group, and others. Get out there and meet people, you never know what could come of it.

Tags: community, BarCampWaterloo, StartupCampWaterloo

The BarCampWaterloo group brings a BarCamp/DemoCamp event to Waterloo that is aimed for those that are interested in or already have a start up. It is called StartupCampWaterloo and will run from 6pm to 9pm on the 23rd of October at the Accelerator Centre on North campus (295 Hagey Blvd). Sign up on the wiki if you are going to attend, all are welcome!