Wednesday, July 23, 2014

Codelabs and Hackathons and Contests.... Oh my!

Hackathon at the iHub in Nairobi

Hey there!
How is it going?
How have you all been?
Thank you for stopping by.
Its been a while since we last hung out, hopefully not too long though.
The last few months have been very very interesting to say the least.
To start with I was at my third Google I/O , arguably one of their biggest developer events in the world. It is always quite an experience to see how the future of tech is shaping up.
Also my wife (I called her my C.E.O) and I joyously welcomed our first child to our family (our little startup). The boy promptly declared that he was not satisfied with the position of director on the board and after subjecting us to a couple of sleepless nights made a case at an extraordinary board meeting to be made chairman of the board.  The motion was quickly passed and now he appears to be settled and happy in his new role of having the final word on all aspects of the company (family) affairs. In fact I had to take advantage of the fact that he is currently napping to start drafting this post. Its been an awesome and interesting experience. One thing I can relate it to is having a new smartphone that gets automatic OS updates every 12 hours. So you are constantly discovering new features….simply amazing!

So….back to the matter!
Like the title of the post suggests I want to invest this stolen time in talking about 3 event types that contribute to the lifeblood of any tech community. If you have been involved in anything tech in Africa in the last 4-5 years, you must at worst have heard these words mentioned at least once or at best attended or participated in at least one of them.  I want to talk a bit about them today because every time I mention them or I hear people refer to them I find that everyone has a very different understanding not necessarily of what they are, but of what they can (or are meant to) achieve. I would like to put down a few of my own thoughts on the subject, they may be right, they may be wrong...they may also change but what the hell….here goes. I will be leveraging on my experience (limited I might add) of participating in, facilitating and organizing a number of codelab events, hackathons and contests.
First let’s refresh our minds as to the basic nature of these 3 initiatives at least as seen through my eyes.

Codelab Events
First off … codelabs. This is a bit of a confusing one because the word codelab could refer to one of two things:
The original meaning which I got from typing “what is a codelab?” in my favorite search engine is:
CodeLab is an online program for learning and practicing computer programming‘ --
I would go further to remove the “online” part and say that a codelab is a program for learning and practicing computer programming since this can be (or should be able to be) done whether there is internet access or not depending on if the technology being used requires internet access to work or to be used.  So that's what a codelab is fundamentally. It is basically some code that helps you understand how a particular technology works. The technology could be as basic as a simple algorithm (like sorting or searching) or a more complex technology like Cloud computing or a vendor specific API/Platform like Android or the Google Drive API. This code is usually arranged in such a way that you need to do a little work e.g. typing in some extra lines of code or doing some configuration to get the code to run and in the process you learn more about how the technology works. The codelab should also contain instructions on how to get this done. Think about it as the chemistry practicals you did at school but this time instead of beakers and pipettes you have your computer and instead of all sorts of chemicals , you have code. Here is an example of a codelab that teaches you about Chrome Apps and here is Google App Engine with Python. There are tons of free and open codelabs out there for almost any technology you can think of so knock yourself out.
Now there are also codelab events, which are events where people come together (or are called together) to learn more about a particular technology by going or being taken through a particular codelab (or set of codelabs) together.  Many times these events are also referred to as…..codelabs :-). The typical format is as follows:
Someone...or some people who have experience with the technology in question gives a brief overview of the technology and then optionally works the attendees through the codelab so that they can see what it takes to get the code up and running.
Next the attendees attempt to get the code up and running themselves, with the guidance of the experts/facilitators and at the end of the day hopefully everybody should have  successfully run the code and learnt something. If there is time and some extra resources available, it is not unheard of to have some sort of mixer after the event where the attendees can network amidst finger food and drinks. Everything should not take more than 2-3 hours, 4 at the most if you are having a mixer. I have personally run a successful codelab in one hour and for my definition of successful I will refer to a statement by my former colleague Bob Aman who once said that at the end of a successful codelab, most of the people who attended should leave with at least one of two feelings: first being the feeling of having learnt something and second being the feeling of having achieved something. Again think of it as a chemistry lab practical where you succeed in creating salt and water by mixing an acid and alkaline and the litmus paper turns purple.

Wikipedia and its accompanying references do an awesome job of describing what a hackathon is and what its all about but just in case you are too lazy to read I will state it here:

A hackathon (also known as a hack day, hackfest or codefest) is an event in which computer programmers and others involved in software development, including graphic designers, interface designers and project managers, collaborate intensively on software projects.Occasionally, there is a hardware component as well. Hackathons typically last between a day and a week. Some hackathons are intended simply for educational or social purposes, although in many cases the goal is to create usable software. Hackathons tend to have a specific focus, which can include the programming language used, the operating system, an application, an API, or the subject and the demographic group of the programmers. In other cases, there is no restriction on the type of software being created.
This article on Wired does a great job of describing a typical hackathon (you SHOULD read it).

Developer Contests
Software developer contests (to give them their full name) come in different varieties but in the end they all have the aim of selecting the “best” software from a set of submitted software. “Best” in this case depends on criteria specified by the organizers of the competition.  These contests could be organized by a tech company e.g. Google, Microsoft or Samsung or by a community e.g the Africa Android Challenge. Contests could be either based on a particular technology, platform/language, problem space or on features of the resulting software. Personally I like to divide developer contests into two categories:
Those where contestants are forced by the contest rules to create something for the purpose of the contest and those where they are not and so can submit software that they built 10 years ago or that has been in use for the past 2 years. I personally generally prefer the first kind because in my opinion that is where people learn the most by pushing themselves to and beyond their limits. It also brings new content into the ecosystem.

Note that it is possible to combine two or more of the above to achieve different things. For example, you can have a codelab before a hackathon if the aim is to hack based on a particular technology or API so that attendees can familiarize themselves with the technology in question before they start hacking. You could also combine a contest and a hackathon by awarding a prize to the “best” result of the hackathon, again best in this case depends on the criteria set by the organizers. You can also chain the three of them up by having a codelab before the hackathon and then awarding some kind of prize or have a series of codelab and hackathons over the duration of a contest and so on. now that we have gone through the three items, Lets discuss them a bit with particular reference to perceptions and statements I have come across in various face to face discussions, online articles and discussion threads on social media.

Hackathons are bad because they usually produce bad code
There is a school of thought that discourages hackathons because it is generally believed that code produced from scratch in record time usually while consuming beer and doritos (and sometimes with little sleep) while chatting with friends/acquaintances can never lead to anything useful.
I refuse to subscribe to this school because I think that while the second part of this heading may be true, the first part does not have to be. Yes, hackathons rarely produce stellar code that is ready for the production server, unless of course the purpose of the hackathon was to fix bugs / clean up code or the developers in question are from mount Olympus (trust me, there are developers like that, i know a few).  In my humble opinion , most times, the best that you can and should expect from a hackathon is a proof of concept or a working prototype. Woe unto you if you believe that hackathons will guarantee you production ready code, again unless the hackathon or a good portion of it is dedicated to code fixing not code creating. Normally, the real work starts after the hackathon. Apart from producing great prototypes and POCs, hackathons are also a great way to accelerate progress on an existing project you are working on. Its kind of like the same way being in a library motivates most people to read, being in a coding environment with other developers motivates people to work beyond their normal capacity so next time you feel that coding alone in your room is not getting you anywhere as fast as you would like, look for a hackathon near you to attend….or better still organize one. You would be amazed at how much progress you will make.
Hackathons like all the initiatives we are discussing in this post are also a great way to meet people of similar interest.

Serious developers / tech entrepreneurs do not take part in contests
There is another school of thought that says that serious developers or entrepreneurs do not take part in contests because frankly they are a waste of time , are mainly hype and do not produce amazing apps. To this I say : It depends on (1) what the people who organized the contest had in mind when they organized it, (2) what the people who are taking part in the contest want to get out of the contest and (3) what your definition of a serious developer/tech entrepreneur is.
Firstly , the motivation behind organizing a developer contest is everything because it determines to a large extent how the contest is organized and what opportunities are available for the the people who chose to compete. Some contests are purely marketing events to create general awareness, some contests are designed to educate the contestants or encourage them to educate themselves on particular technologies , others are a mixture of the two. Like I hinted earlier I am partial to contests that force people to create something new because there is a greater chance of education and growth on the part of the contestants such that even if they do not win the grand prize, they definitely gain something valuable in terms of knowledge and skillset.
Secondly , I believe that what people get out of a contest depends on what they want to get out of it.  The way I see it , a developer contest can serve different purposes to different types of developers. For the startup or established company, the contest could be an opportunity to launch a new product or feature by helping you overcome inertia. It does this by offering you an incentive to start (the chance of winning a prize) , a deadline you can work towards (contest submission date) and honest feedback on your new product or feature through the judges feedback (I believe a good contest should have judges feedback). And hey, even if you do not win, you have at least started on that new product or feature that you have been planning for the past 3 years. For an upcoming or student developer, a contest offers you an opportunity to improve yourself by learning under pressure (one of the best ways to learn). If you have never created production level code before , this will be the closest you will come to doing so. The deadline and the opportunity to win a prize is great motivation to stay awake for nights on end hacking away and learning all the way. Something that is very hard to do when there is no pressure. And even if you do not win, you find that your skillset and knowledge will increase by at least a factor of 2, making you readier for the job market than you have ever been. For platform  based contests , they provide a unique opportunity to get introduced to new technologies and APIs for those who are interested with a chance of winning something for your trouble. It is not usually a good idea to leave other productive work that you are doing to take part in a contest for contest sake, but if you fall into any of the above categories, you may want to take another look at ongoing contests.
Thirdly, what is a serious developer or entrepreneur to you ? That depends. I know a number of serious developers and startups who have caught their big break through contests. Examples are Fans Connect Online , creators of AfriNolly who created the product during the Android Developer Challenge for Sub Saharan Africa and Collabspot from the Philippines who are  products of the Google Apps Developer Challenge, or Ultradox and Neutron drive also products of the Google Apps Developer Challenge. There is also FunnyLeni from the stables of INITS. These guys went into these contests with a plan and made it work for themselves.
This is not to say that people who belong to the earlier stated school of thought are just blabbing though, they do have a point in that there are people who have declared themselves career contest developers, who move from contest to contest year in , year out making a living off the prize money. While this is a perfectly legal business model, I would only say that if you are one of this group be sure to reassess your motives ASAP as you just might achieve more if you decided to focus your energies on building something sustainable.

Contests are not useful because they do not produce amazing apps
I will have to agree with one aspect of the above with a slight remix: Contests generally do not produce amazing apps…..immediately after the contest. They produce POCs and Prototypes, in a few cases very good POCs and prototypes, that can actually be put in the hands of an end user. I have found that the real value in the apps usually comes out about 3-6 months AFTER the contest has ended, because like I said regarding hackathons, the real work starts when the contest has ended, you have your POC or prototype, and you you have valuable feedback from the judges in the contest and other people who have taken a look at your work. Then you go back to the drawing board and turn that POC/prototype into a PRODUCT or give it up altogether if it does not make sense...or if you did not believe strongly enough in it in the first place. Sadly only about 10% (a guesstimate) of developers who take part in contests actually do this. All the examples of successful products from the contests I talked of above truly came into their own about 3-6 months after the contests that initially brought them to life.

Hackathons , Codelabs and Contests are only for startup/community oriented developers and not for enterprise type developers
The Idea here is that all these communal hacking stuff , contests and codelabs are things that only the wider, new age , entrepreneurial, community , startup types do. In other words its just for the spiders and not the bridge walkers. Developers or software companies who work for telcos or banks or companies that service corporates and conglomerates with licensed or off the shelf software have no business taking part in any of these activities.
To this I say : BIG MISTAKE! You do not know what you are missing out on. I can think of so many reasons why thinking like this is a big mistake but I will mention the top three.
First these initiatives can easily be organized internally to help the company to be more productive. As a CTO of a tech reliant company, nothing stops you from organizing a weekend hackathon, to either meet a deadline or brainstorm/prototype a new product/feature. You could have members of your dev team prepare and run codelabs on their favorite technology for the rest of the team...or have an internal contest to pick the best implementation of a new feature. It all depends on how you want to play it. Trust me, the results you will accomplish may just blow your mind even if it's just for the increased team collaboration that you will achieve or even the creativity that could be unleashed .It could also be a welcome release from the straight jacketed approach that many of such companies use and the beauty of this is that you could implement it for a developer team of 2 or 200.
Another reason is that the externally or community-organized initiatives is a great way to scout new talent, put your name out there so that new upcoming developers see your company as a viable career option and also know what new technologies are out there so that your company does not get left behind by the competition. We all know how easy it is to stay stuck on one technology for many years while the world moves on and then one day you wake to find that someone has eaten your lunch. Even as a developer in one of such companies one day you find out that you have become unemployable , because you are still stuck on technology of 2005 and the only company that can employ you is the company you work for you are stuck there at their mercy.
The third reason is one I have already mentioned. Participating in these initiatives can help you either launch a  new product or add a new feature to an existing product.
I will add a fourth reason, which for me is the most important, showing up and taking part is an important piece of building a tech ecosystem and strong community. The more the merrier. I believe this is important for the long term sustainability of tech on this continent. Believe me, the company/job/career you save by doing this may be your own.

I would like to hear your thoughts on what I have said so far, I get the feeling that there are a lot of aspects still uncovered. Let me know what you think and maybe we could look at them in another post, or in an online discussion.  
This post has mainly looked at things from the perspective of the participant. Next time, we will examine things from the point of view of the organizer and try to answer questions like which initiatives make sense, for which purpose and so on. Hopefully that should be a much shorter post :-).

For now…...I think I hear my chairman stirring….ssssshhhhhhh…..

Thursday, May 1, 2014

The Abyss of the Great Outdoors ....and the Spider Generation

I am slowly getting used to the fact that I will be lucky if get to write to this blog more than twice a year.
I had been meaning to put down a few thoughts for the past few months, but never got round to it. There a lot of reasons why I could not do it...but I will be honest today and tell you it was procrastination ...there ...i said it!

Cele’s Article

I was however jolted out my happy state of work filled bliss by an article on LinkedIn by my friend Celestine Ezeokoye which I think is well worth a read (its not a very long go the link). To give you a summary of what Celestine is saying: Nigeria already has a thriving tech industry. He goes on to list a number of heavy hitting Nigerian tech firms that were started locally by locals and have grown to become giants on the tech landscape and are doing quite the extent that some of them have received up to 90M USD in funding and so on. Celestine encourages the current generation of tech entrepreneurs to do more to stand on the shoulders of the now established tech entrepreneurship giants who have done so much and learnt so much to achieve success in this rough socio-economic landscape that is Nigeria. He says that we should also do more to promote the successes of these guys who have silently gone about their business in building great tech companies that are looking to stand the test of time ( the article, its not as long as this one).

I agree with what Celestine said in that article. There are many Nigerians (indeed Africans) young and not so young who have managed to build businesses based on technology that they bootstrapped with less than $2K USD in funding (from their wallets, family , friends etc) that are doing very very very well. For the purpose of this write up , “very very very well” means having staff of 15 and above and making revenues of more than $1M per annum. You do not find many of these peeps on Social Media or blogs sharing wisdom on best practices of tech entrepreneurship, startup culture  and so on. A number of reasons have been given for this. Some say that people who are busy running a successful business do not have time for social media or tech meetups. Others say that they live and work in a world where sharing wisdom could give your competition the required ammunition to put one over you. Which ever way you choose to look at it, there is a lot to learn from those who have done it...and are still doing it in the tech space in Africa and I would want to dedicate some lines in this article to join Celestine in encouraging our current generation of tech entrepreneurs to spend more time in the company of these people and learn a thing or two. Invite them to more of your meetups, ask them deep questions, encourage them to share more. I would also like to appeal to these tech entrepreneurs who are doing very very very well to make themselves available for people to learn from their experiences. Spare a few hours from your very busy schedules and make time for the community. Share your wisdom. There is a lot you can teach …. there is also a lot you can learn….and gain and I will talk more about that in the following paragraphs.

Abyss of the Great Outdoors

I would like to spend a little time to talk about the other side of Celestine’s article that we may or may not miss. But first I would like to introduce a concept I like to call the Abyss of the Great Outdoors, It is an abyss that runs parallel to the other abyss that we are all familiar with i.e. the Digital Divide. It’s an abyss that i alluded to in my earlier article on the African programmer and the sun. It is the great wide gulf that exists between the tech entrepreneur and his/her end user, the proverbial man or woman on the street. It is this abyss that makes it almost impossible for a single coder sitting in his or her room in Lagos, Nairobi or Bridge Town (a suburb of Cape Town) to create a product or service that will become an instant hit with 120 million people in Nigeria,  43 million people in Kenya or 51 million people in South Africa. It can be measured in terms of the amount of pain (physical, emotional, psychological , financial and spiritual) that a tech entrepreneur has to go through to directly reach his or her first 1,000 end users. It is an abyss that surrounds us to the extent that we do not notice it and take it for granted. Mind you, this abyss is not peculiar to Africa or emerging market countries because it also exists in places like the United States and Europe. The difference is that in those countries it has been bridged to a large extent. What do I mean by bridging?  lets talk a bit about that.

The abyss of the great outdoors

Over the years , indeed over the centuries a number of industries have built bridges over the Abyss of the Great Outdoors, often at very great expense. Some of these industries that we are familiar with are : the Banks, the schools, more recently the Telcos and the largest of all, the government agencies. These bridges come in different forms, shapes and sizes ranging from banking halls and ATMs to telco service centers, SMS to mobile phones, radio and TV etc. If you want to think about the cost of building a bridge across the abyss , consider the fact that according to this article on as at 2004, a single base station was selling for about $25,000 or more.You could also think about the cost of setting up a bank branch in your neighbourhood and then multiply this by the number of base stations or bank branches across your country to get an idea.

Zim, Oby and the corporate bridge

Anyways for a long time these were the only bridges available for crossing the abyss of the great outdoors. I will illustrate this with a story about a fictitious pal of mine named Chukwuzimuzo (An Igbo name which in english means God show me the way). Lets call him Zim for short.

So Zim is a sharp guy who can churn out awesome code in any programming language faster than you can type an email. One day Zim comes up with this awesome idea to create a service targeted at young university students in Nigeria. This service allows them study and collaborate online while providing them with much needed educational content and for that he hopes to earn a small fee from each student. I am sure we have seen or heard of this model or similar models targeted at this or another audience. So lets take a look at the abyss between Zim and his intended users. Note that the assumption here is that Zim’s product/service meets the minimum required awesomeness level:
  • First is access to the students, how can Zim get his product/service in the face of the student. Lets call her Obianuju (Another Igbo name which means “The child that came in the time of plenty”), Oby for short
  • Second, how can Zim convince Oby that his service is the best thing since sliced bread such that she is convinced to use it and possibly pay for it?
  • Third, If and when Oby decides to use Zim’s service or product, how can Zim get paid? After all he is not running a charity service #boysmustfeed
  • Fourth, how does Zim maintain a relationship with Oby so that she keeps using the service and product and it keeps improving i.e. customer service and all that good stuff?
If Zim, is to solve these problems, then he has to successfully cross the abyss of the great outdoors. But how can he do this? Remember...this is an abyss we are talking about here.

Now in the days before the internet revolution really (and I mean really) hit Africa ( i.e circa 1996 - 2006), the options open to Zim would look something like this:
  • Setup a meeting with the authorities of the school to tell them about his new service and convince them as to why his service is the one thing that would make their university an Ivy league school in the next 2 years . This means meetings and presentations during office hours, meetings and presentations outside office hours (with a couple of drinks here and there), more meetings, more presentations and a whole lot of other stuff
  • If the school agrees that this makes sense to them , then they need to decide on how to collect money from Oby and her colleagues. One option could be to include the service charge as part of the school fees which the students pay the school and give Zim a cut. Most times they would rather pay Zim off once and for all with a license fee and then charge the students anyway. This means more meetings, more presentation, more drinks and so on.
  • Then when all is settled, Zim and his service can now go live. The school makes an announcement to Oby and her colleagues that Zim’s platform is now the platform of choice for extracurricular studies and that henceforth they will be charged an extracurricular study fee which amounts to about 1% of their current school fees so its not a big deal. Almost instantly Zim has about 30,000 users available at day one of his product launch.
  • In many cases, the platform will not be known to Oby as Zim’s platform but as the school’s platform (white labelling) so Zim stays in the background and happily collects a slice of the 1% service charge
  • A lot of times, Zim is not even in the background because he has been paid off with a one-time license fee and only shows up when there is need for maintenance for which he gets paid a maintenance stipend.

So why on earth does Zim have to get in touch with the school in order to reach Oby? After all his product is for extracurricular studies, so what business does the school have in the whole thing? Well you see, in this particular case the school has built a bridge to Oby, by virtue of the relationship between the school and Oby. The school has almost 24/7 access to Oby via the school bulletin board (or school email etc). This relationship is made possible because the school has something that Oby needs: A university degree. The school can get Oby’s attention whenever they need to. Zim cannot. So Zim needs to get to Oby through the school. There are of course other ways that Zim could get to Oby , for example he could get in Oby’s face via an SMS to Oby’s phone and charge Oby via her airtime but this would mean going through the same process I listed above but this time with a telco, who just happened to build the bridge to Oby and her phone through SMS and their billing system. Zim could also go through Oby’s bank who have a bridge to Oby virtue of her bank account and their banking halls and ATMs…..or he could choose to get the ears of the ministry of education who have the almighty bridge: Policy.
Now if you can think back to the period I am referring to without the school , the telco, the bank or the government in the equation and you put yourself in the shoes of ZIm trying to reach Oby, you will begin to understand exactly what I mean by the abyss of the great outdoors. It is indeed an abyss: wide, dark and full of things that want to eat you.

The “Open Web” Bridge

Now let us look at a world where there is another that connects the tech entrepreneur DIRECTLY to the user without any need for physical meetings and the like. This bridge connects directly from the techie sitting in his self contained house with laptop to the front of the end user. Today it is (or usually is) the open internet, a.k.a the web. That is what i meant by the abyss being more or less fully bridged in countries like the USA and in Europe where the web is ubiquitous and part of everyday life. Most of the population can be reached via this bridge. This (in my opinion) is why the stories abound of great tech companies founded from dorm rooms and garages. The people in these stories had a bridge that linked them to their first real users across the abyss of the great outdoors.

There are a number of things required to cross the bridges built and maintained by the large corporates and government apart from basic entrepreneurship and technical skills. A number of things come to mind first like presentation skills, dressing the part when you show up for meetings, learning the corporate etiquette and culture of the organization that owns the bridge that Zim is trying to cross, negotiation skills because you need to negotiate the toll for crossing their bridge. But then there is the big one: the connections. You do not just stroll up to a telco , school, government agency or bank and say : I want to use your bridge, give me access. You need to speak with the right person or else you will be speaking for years to come with no results.  Now consider if Zim is a pimple-faced guy just fresh from undergrad or in his final year, what do you think are his chances of negotiating the corporate bridge with his sharp brains, bright ideas and coding skills? Particularly in our environment at a time when ageism ( stereotyping and discriminating against individuals or groups on the basis of their age)  and classism (prejudice or discrimination on the basis of social class) ruled the day?  I would say somewhere between slim and nil.
Now this differs from the internet bridge where Zim deploys his app , configures a payment method, does some internet and social media marketing and is up and long thing. The users of his service need not know that Zim is a university undergrad or fresh graduate who came up with this idea while decapitating bottles of beer with his mates 2 weeks ago.

There are however aspects to the open web bridge that are not always obvious or necessary on the corporate bridge for example if Zim are using the internet bridge, Zim has to be ready to carry out 100 different updates to his service in a year if need be because the users (and their usage patterns) demand it. For the corporate bridge this may not be necessary, once the corporate is happy, Zim is happy. Not so on the internet bridge, Zim needs to be on his toes monitoring Oby , her colleagues and their usage patterns. He needs to be able to change his business and marketing model overnight if need be.  He may not always need to do this if he is using the corporate bridge as he has SLAs and licensing agreements to cover his behind.
Also on the internet bridge, user experience is a do or die affair. The ease of use of Zim’s product / service (e.g. where Zim placed a particular button or the font he used for a particular piece of text) could make the difference between Zim being the next Google and his service  being just another waste of internet bandwidth. Not so on the corporate bridge. I you do not believe me, next time you are in a large corporate environment, take a look at their intranet and then take a look at your favorite social network, the difference is 7UP.
Lets not even go into things like recruiting and managing tech and other talent for both scenarios , that is a like 4 different blog posts on its own, the first of which was this one.
Bottomline what I am trying to say is that skills and knowledge needed by Zim to thrive via the open web bridge are different from those needed to thrive on the corporate bridge.

The Spider generation

Now let us come home.
Image from

On our dear continent, the open web bridge is still being built, policy by policy, base station by base station, dongle by dongle, web-enabled phone by web-enabled phone, app by app, payment system by payment system and awareness event by awareness event. It is a painful process but it is sweet pain (like the type you get from push ups) for those of us who have dedicated our future to the pursuit of success on the African soil. We have slowly moved from when there were only the corporate owned bridges to a time when we have a bridge under construction, this bridge has a few strands connecting both sides which we hope will support the full structure in the years to come.

The new tech companies in Africa that are coming up today are like spiders trying to stretch a web across an abyss, the abyss of the great outdoors. Have you ever wondered how spiders manage to build webs across roads or wide open spaces? Yes? Well then read this short article from the New York Times. In summary I will quote some excerpts directly:

Spiders that build the familiar orb-shaped web usually start with a single superstrength strand called a bridge thread or bridge line.
First, the material for the bridge thread emerges from one of the spider’s specialized silk glands and is formed into a strand by its spinnerets. The loose end is drawn out by gravity or the breeze and allowed to blow in the prevailing wind

And now the most interesting part:

If the strand does not make contact with something and attach to it, the spider may gobble up the strand and recycle its proteins, then try again. If the gap is bridged, the spider reinforces the strand and uses it to start the web.

Does that remind you of any tech startup you have met in Africa in the last 4 years?

These startups are pioneers trying to do stuff that may have been done before in a place where it has never been done before and in a way that it has never been done before. They are not waiting for the bridge to be completely built before they get on...they are on the bridge...building along with (and in many cases ahead of ) the builders. They stand at the edge of the partially built bridge and extend their webs to an unseen and yet unknown destination.
I salute them.
I salute them because they have a lot to teach us, they are in the laboratory….the field laboratory….the laboratory overlooking the depths of the abyss. They are carrying out experiments everyday, many of these experiments fail, a few pass, when it fails, they recycle their energy the way the spider recycles its web proteins and they try again another day. A lot of the lessons they have learnt cannot be thought by any tech entrepreneur or business school in the world be they from Silicon Valley….or Lagos who has not walked in their shoes ….not on this path. Simply because this path has not been walked before. Because there was no path…. it is an abyss.
I salute the likes of Konga,, Iroko, Jobberman to mention a few. I salute all the startups hiding away in the likes of the Co Creation Hub , the iHub, MEST, iSpace, 88mph , IDEA Hub and a host of other incubators and tech hubs scattered around the continent.  I salute you and I root for you because you are the spiders...building a web across the abyss. I salute you because if you manage to build this bridge, it will be a bridge not just to one billion African users...but also to the 5 billion users across the emerging markets of the world.

Let us learn from each other

Yes, there is a lot to learn from the tech entrepreneurs who have found success plying the corporate bridge, things like tech entrepreneurship 101,how to run a company and manage people,  how to scale into the corporate world, how to leverage on corporates for success, how to use what you have to get what you want etc. But when it comes to how to locate , target, convince and convert the man or woman on the African street from scratch , with nothing more than a value proposition and keep them loyal to your brand, there may be a thing or two that the corporate bridge users can learn from the current generation of spiders.
I  know of a number of corporate bridge walkers who are trying to cross over to the open web and are beginning to realize that it is not a walk in the park. They have met with varying degrees of success but are all quick to appreciate that it is a different ball game.

I believe that increased collaboration between the spiders and the corporate bridge walkers will result in this bridge being built faster….with more rewards for all at the end of the bridge. We all have a role to play. Let us think about what it is….and play it.

I wrote this while listening to this awesome YouTube playlist of Congolese music (I was bitten by the bug in DR Congo this April). If you encounter any typos ...horrible grammar etc, blame it on the playlist. And give me some credit...its a tough job writing and dancing at the same time