Day 2 opinions – Clarity seems key

News from the conference room: this is a series of blog posts in which blogging experts briefly review key Tech4Africa 2010 talks and panels from Day 1 and 2.

Day 2

Day 2 of the Tech4Africa conference showed a much more relaxed atmosphere shown very evidently in the casual attire of the attendees. It was started off with a great introduction by Marcel Klaasen re-iterating FNB’s commitment to startups and a couple of his view on the state of entrepreneurship in SA.

Soon to follow was a very informal and highly interactive session on Social Media. With the panel all dispising the title of Social Media Guru’s I could help but notice that they all are about as close as you could get… maybe their definition was skewed, but they all seemed to fit the mould of being able to effectively use Social Media to enhance a companies brand – IMHO I don’t know what else would constitute a guru. The topic tended to sit quite heavily in the philosophical side of the media and less on the local case studies. This could this be to the distinct lack of local case studies (Outside of Cell C) but an interesting angle would have been what types of Social Media wold work for different companies? There definitely seemed to be a heavy focus on Twitter and Facebook, but what of Youtube of Flickr?

At the end of the day, the “success” of your social media campaign depends more on the quality of your product and how honest you are with your customers. Apple was highlighted for various reasons, but I think that the case highlights a very interesting point on how to maximise on social media by not interacting. I would have loved to see this discussion between the panel and the audience continue for about 3 hours, just to see what path it would follow and where it would polarize. This method my produce more concrete outcomes and more clearly highlight the relevant points.

The second talk was very different but just as interesting as the panel had taken a well known site and redesigned it. They led us through the very interesting process resulting in a much more effective site layout and flow. Although it was a great concept and they will give the content generated to Payfine.co.za to use as they will, it could have been taken a little further. Possibly with a bidding process by companies and the final product being sold to the company of choice with some of the funds going into sponsorship for the event. it could add a whole new level of hype.

Find here the slides of the presentation “How we redesigned PayFine.co.za, and why you need to know”.

Traditional media as a hotly contested topic was an interesting talk. Mostly due to the lack of continuity in definitions for the terms, with few points that they did agree on Bing that journalism is not only writing. It is all the background research and reporting that goes on. The Traditional Media model of finding a way to make revenue from any means possible and use that revenue to fund the journalism side. Apparently tablets will save Traditional Media by providing a more sexy, appealing way for us to receive verified news.

With a keynote by Clay Shirky to follow and then the afternoon session on entrepreneurship, startups and funding I’m really looking forward to what the last quarter of T4A 2010 has to offer.

Roger Norton
www.rogernorton.net
@rogernort

Location Scaling and Herding Cats

News from the conference room: this is a series of blog posts in which blogging experts briefly review key Tech4Africa 2010 talks and panels from Day 1 and 2.

Day 1

Joe Stump (SimpleGeo) on scaling a business and handling developers.

The masses of data created in web 2.0 has started following Moore’s Law (according to Sergy Brin) and with this increase in data as well as real time tracking it the overload of information becomes a supply and demand problem. The more data you have, the less the data is worth.

There is a big drive for location based information, however the value of this information decreases drastically over distance and time. The relevance of this information depends on: What the information is; Who it is about and What information is Virtually nearby or relevent. With the large adoption of services like FourSquare and MyTown it becomes evident that this gaming style of applications providing relevant location based information are becoming very popular. [As a side fact, more people visit MyTown per day than the total number of people who have accessed FourSquare since its inception.] At the end of the day users are looking for relevant information that can enhance their current experience.

Moving onto online scaling, Joe stressed the necessity of automation with the cloud as well as separating data into partitions from the beginning being a must. An important question that needs to be answered is whether to scale Up or Out. Out is normally better when you are on a budget and expand by getting lots of basic storage; whereas Up would be investing in high-end servers that are generally very costly. The specific language that you use is more based on the application and are not really a factor when scaling.

Another crutial point is having set standards and conventions from the beginning is critical for continuity throughout the business. It lowers the barriers of entry for new team members and makes the different components work together more smoothly, as well as helping if you want to publicize code at a later date. (This became an issue at Digg) Providing this continuity was best done through regular communication between the teams and Joe is an advocate for the SCRUM model to ensure constant communication. Testing was also a must, with different components being tested automatically and peer reviewed before being uploaded. He also believes in a “Swiss Cheese” style of coding which leaves holes in the code to be filled up later.

Dealing with developers can often be a tricky task – mostly due to their passion and personality type. As the core generators of online services they need to be carefully lead through expansion and given enough freedom to work their magic.

Roger Norton
www.rogernorton.net
@rogernort

Beyond growth pains

News from the conference room: this is a series of blog posts in which blogging experts briefly review key Tech4Africa 2010 talks and panels from Day 1 and 2.

Day 1

Beyond growth pains: A Q & A session with some of the global movers of Web 2.0

The social media we have come to know and love has very few prominent players. For growth in that market and developing your platform to giant proportions – with users other than close relatives and distant cousins. Who, better than the whizzes themselves to tell us how?

I sat in on a Q & A session with panelists from Twitter, Yahoo!, Mozilla Foundation and Simplegeo. Boy won’t you be glad I did because below are some of the things they covered.

Q: “What has been your hardest challenge, in your career, and how did you overcome it?”

A: (Joe Stump – Simplegeo) “Finding people I can bounce ideas off of, who have similar challenges at the same level in their growth“

A: (John Resig – Clear Left) “Understanding that the startup life wasn’t for me. It became most rewarding with a community.”

Q: “Is moving away from a small company and going corporate, the death of creativity?”

A: (Dustin Diaz – Twitter) “Twitter is always flowing with ideas. We all have different ideas and the constant challenge is to ways to implement the thinking of different people.”

Aside: Joe Stump had something relevant to say, which was unrelated to the question but makes sense to put here. “My number one rule is to hire people on the assumption that they great and potentially smarter than me.”

Q: “Are we creating a digital divide through building products that highly sophisticated and require more and more bandwidth?”

A: (John Resig – Clear Left) “There is a mobile digital divide that I’m realizing, most things now being developed android phones and the iPhone.”
The panelists earlier noted that the computer as we now use it is moving away from the need of an Operating System. The panelists assert that they spend less time using some of the functionality they once needed Operating Systems for. More people with team members that work remotely use Google Docs and other web based equivalents.

Some questions also came from delegates and this one in particular by Toby Shapshak I found really worth sharing.

Q: “With the browser becoming bigger and essentially what the internet is becoming, how do you fit that into mobile phones for use on cellphone screens?”

A: (Jonathan Snook – Yahoo!) “Get to the core of what you are trying to build and deliver that to your user. Essentially, products developed for the web have to be delivered differently for mobile phones.”

The session was quite eye-opening considering that while developing a product you also have to think of the business element related to the product.

Mongezi Mtati
http://www.mongezimtati.co.za/
@Mongezi

Scale to get big

News from the conference room: this is a series of blog posts in which blogging experts briefly review key Tech4Africa 2010 talks and panels from Day 1 and 2.

Day 1

It’s going to be a flood of data as more people connect more often with their mobiles. Says Joe Stump (co-founder of SimpleGeo, previously main dev bod at Digg): “Each smartphone has six-plus sensors, and it’s not long before they add barometers and temperature sensors and more. Data production is following Moore’s Law.”

He did a simple calculation, working out what happens if you were to tag the phones (just time and location) once every minute for the 500 million Facebook users.
Just this little addition would add 37.2GB of data every minute to the piles that already need to be crunched.
He asks: “How are we going to store, scale and serve this mess?”
His main point is: scaling != performance.
Performance is more about i/o, and not so much in your choice of language. Choose Ruby, choose php, it makes little total impact to large-scale systems, he insists.
Mostly, scaling is a specialisation.
“The more traffic you get, the more specialised your infrastructure needs to be,” he says. The key is automation – bits should be able to be called or started or attached automatically. Use the cloud, but treat everything in the cloud as ephemeral. It can and will just disappear. Expect it.

He discussed the two approaches to scaling – namely out, and up.
If you scale out, you spread load across lots of boxes. If you scale up you get a bigger, faster box. Less complex infrastructure, but a really powerful box can cost millions of bucks – only workable if your service is making big money already.

Other gems of wisdom:
* Partition your data from the very beginning
* Make use of queues – very important part of consistency of user experience.
* Caching is critical – especially in supporting queues. Write a record to cache while it’s processed by queue so that user experience stays OK.

These are lessons learned from long years worrying about things like: how do you handle objects such as the front page story on Digg when it’s getting millions of hits?
His other key advice is about people:
“It takes a lot of people to build, scale and maintain infrastructure – you will grow from one or two to 15 or more.” The human management issues become tricky here: “The first two or three devs on board are going to question every decision management makes.”
A good thought: “Look for a trait in developers: laziness. You want someone who looks for a quicker, better way.”

As your site (and dev team) grows, he advises looking to lower barriers to entry for more junior devs. “Get your codebase to a position where you don’t need to hire a Jedi. Jedis are rare. Jedis are expensive.”
He recommends breaking teams up. 4-6 people work well, at 8 it starts breaking. Get a Jedi, and make them the team leader. Note: team leader, not manager. They should act more like a sports team’s captain. Create frameworks (authentication, error handling) to lower barriers to entry as new coders come on.
And use code repositories. Full stop.

He is very passionate about promote ownership in the codebase, so that individuals work on three of four areas and have responsibility for them.
“As you scale and your code bases grow, from 50,000 lines of code to 400,000 lines, no-one can be effective across the whole base,” he says.
Before you start, design the software – don’t just start coding. He is a big fan of stubbing out the API on a whiteboard.

When it comes to testing – automation is good, and use several methods. If you fix something, make sure you run a test on the old version and make sure it fails it. Apply patch, and make sure it now passes.
Documentation. Build time into your planning for documentation. Even if old and stale it adds historical context, maybe helping you understand later why you made a particular decision.
Do peer reviews. “I’ve never sat in on any peer review and didn’t see at least one show-stopping bug.”

There are a number of ways to scale up using powerful technologies. “When I left Digg we were handling 37,000 requests a second,” he says. Now at SimpleGeo, he runs 15 nodes in one Cassandra cluster, 12 nodes in other cluster.
The numbers will go up (if you are even remotely successful). The technology is getting faster and faster, handling volumes that would have been unthinkable before. “You can get 1500 writes a second on a decent SQL box. A couple of years ago if you asked me if I’d need that, I would have laughed,” says Stump. Right now he is putting 5,000 to 7,000 writes/sec on a Cassandra cluster.

Most South African web developers, even those working for the relative giants like news24.com see only a fraction of these volumes – but one thing is sure. Africa is developing its Internet community fast – it won’t be long before servers talking to thousands of users are talking to millions.

Roger Hislop
www.sentientbeing.co.za
@d0dja

Boiling the Ocean

News from the conference room: this is a series of blog posts in which blogging experts briefly review key Tech4Africa 2010 talks and panels from Day 1 and 2.

Day 1

During his talk “Boiling The Ocean: how a VoIP mobile business is changing the shape of the Mobile Industry” on how Internet Solutions has progressed since he was asked to start it up and take on the main Mobile Providers, Justin Spratt delved into just a few of the obstacles that he had to overcome in making that happen.

It all came about from them wanting to scratch the itch of mobile costs being too high in SA. With variable costs being around 5c per minute and charges around R2 they saw a clear gap to fill. Deciding to do this through VOIP over an enterprises existing WiFi network, they were able to come up with a very viable solution. In order to do this their requirements were to start with extremely talented people, strive for technical excellence (“Nobody does it better than us” – JS) and making sure that the leadership was given a long enough leash to be able to adapt quickly and effectively.

When it came to building the business, creating the core technology was easy. Their first version vastly outperformed the mobile operators. One of the biggest issues was the diversity of Mobile OS. With Blackberry not opening their API and Nokia having 3 OS versions – each not upgradable, this was no easy feat. [On a side not he made a prediction that Blackberry will be in serious decline in the next few years… This is because the customer is not the center of their development. Also that Android will soon overtake the iPhone due to its openness.] With Microsoft being years behind the game they have chosen to focus on writing software for Android, iPhone and Blackberry only.

When looking at moving the main routing through a central place they originally looked in India but soon moved to Israel because of the language barrier.

Deciding to run on a model where companies only pay for what they use and IS covers the setup cost they have managed to bring their prices down, starting at 50c per minute.

As Take-Aways Justin left us with 3 words: Usability, Adapt and Love. For him these were the most important ingredients in their success. Creating the customer at the center of their development was absolutely critical as well as being adaptable as situations and roll-outs differ. Love was needed to be inherent in the product and that “People want to see caring in your eyes”…

For more details, find Justin Spratt’s presentation slides here.

Roger Norton
www.rogernorton.net
@rogernort

Mesh Potatos Become Hot Potatos

News from the conference room: this is a series of blog posts in which blogging experts briefly review key Tech4Africa 2010 talks and panels from Day 1 and 2.

Day 1

The Tech track at Tech4Africa kicked off with a presentation by Steve Song, a Shuttleworth Foundation fellow and a founder of Village Telco project.
His main theme was the high cost of access to basic communications, and the solution developed that can help solve this problem. Which is always a good thing in a solution.
An eye-opening statistic: the bottom 75% income band in Africa spends 50% of their disposable income on mobile services (in SA it’s a touch lower, at 40%, although probably because people earn a bit more here than because our mobile operators are particularly cheap).
If you’re an economist you get to sit back smugly, take a sip of Merlot and say, “See, you see how much they value it? Clearly it delivers the incentive they believe makes it worth the price.” If you’re not an economist you kick them in the head.
If you’re an African leader you wake the hell up, and realise that without driving down the cost of telephone and data access, your people will struggle and struggle to advance (and hence build businesses that pay you tax revenues that leaders can in turn plunder for new presidential palaces, you bastards).
In Steve’s more considered words, “What might an enlightened African leader should say: ‘It’s the cost of access, stupid’.”
His main contention in developing businesses is that to enable innovation, you must lower the cost of failure. When failure is expensive, the lesson learned is to stop wasting money.
With greater communication, more sharing of knowledge and greater transparency across markets comes immediate and marked growth in GDP. A cheaper way to provide telephony services in Africa is vital, and since the mobile operators (and government regulators) are not coming to the party, other options must be found.
His talk then turned to an old Linksys wireless router, the WRT54G. Popular, now getting a little long in the tooth, but based on a Linux core in its firmware. Open Source types compelled Linksys to open up the code under GPL, and they dug in.
They hacked it, and discovered it was a pretty powerful box, with hardware (RAM, CPU, etc) more advanced than its as-shipped specs needed. A whole new industry of hacked WRT54G routers grew up… enthusiasts wrote books about it, codified the OS as OpenWRT.
You can unplug the stub antenna, and add a directional (such as a cheap, home-made cantenna), and talk reliably over many kilometres.
You could hook a bunch together over in a mesh over an area, plug a phone into it, hack it a bit more, and end up with the Mesh Potato.
Mesh, as in the Open Source mesh protocol developed substantially by a woman called Elektra in Germany, POTS as in Plain Old Telephone System (it works with old skool analogue telephone handsets) and an ATA (Analogue Telephone Adapter) to packetise the voice.
Mesh Potato. Get it? It’s cleverer in Spain, where they call them patatas.
The hardware for the box was designed by an Australian hardware engineer called Mr. David Rowe, and then mass produced.
Hacking together some code is easy enough, you may think, but a piece of hardware is an entirely different proposition.
Luckily, not true.
An interesting development, says Song: “Hardware is the new software. You can bring a unique hardware product to market quite quickly and cheaply.”
The Mesh Potato team finalised the design, did some prototypes for testing, then went into production with a manufacturer in China, who was only to happy to give them a good unit price in exchange for the know-how (yay for open source goodness and commodity technology like WiFi and open standards like SIP!).
The final device will be a fairly cute little white box that’s weatherproof (rain, dust and sun) with hardened ports that won’t fry its little heart if some klutz plugs the wrong thing in.
The mesh then connects up a number of standard handsets that can be pulled out the dumpster, allowing a non-profit to set up a local telephone network quickly and exceptionally cheaply.
The little network can be autonomous, or you can add a “server” that’s being developed that has a VoIP connection upstream to a gateway to allow interconnect to national operators.
Song recons they got a 400m range at a setup they ran at the Afrikaburn festival/party/freakshow in the Karoo in the Western Cape a few months back, and with a new version planned using 802.11n, they’re looking for even longer range.
The non-profit part is key, because these organisations can operate a network in many African countries free if they don’t charge. A small business can be set up to be a commercial venture, but then they’d need an ECS class licence (in SA, similar elsewhere).
The box was developed by a team that kicked around ideas and designs across South Africa, Kenya, Tanzania, Uganda.
Song says they’re so far not getting hostility from the incumbent mobile and landline operators, but probably because they’re flying well under the radar. The tolerance may change when the Mesh Potato starts to become widespread.
It’s an interesting future. In the past the only people with the ability to deliver a viable telephone network would have to do it on a national basis. Deep pockets. Exclusive licences. Monopolies. Price gouging. In incumbent operators’ defence, the price to pay for doing a national network is that it would have to meet minimum standards. Expensive, reliable, standardised technology. Think SS7.
That changes with repurposed commodity technology.
Now a village or area in a township can set up a telephone network that services just them cheaply and easily. If it falls over, they know exactly whose door to go knock on. It does the needed job. It’s cheap. It can be grown, and grown.
Rather like ISPs providing VoIP services to small businesses will eat into national operators, so small consumer meshes will eat into national operators.
Is this the democratisation and commoditisation of telephony? These small potatos?

(NOTE: Blogging for the event is done with little time and bandwidth. Apologies for any factual errors, but c’est la vie).

By Roger Hislop
www.sentientbeing.co.za
@d0dja

When Developers Get Antsy

News from the conference room: this is a series of blog posts in which blogging experts briefly review key Tech4Africa 2010 talks and panels from Day 1 and 2.

Day 1

It’s not often in SA that you get to hear a group of developers chew the fat. Well, you get it all the time. But not these developers. Tech4Africa 2010 offered an “Intimate Q&A” panel with Andy Budd (Clear Left), Dustin Diaz (Twitter, previously Google/Gmail), Joe Stump (SimplyGeo, previously Digg), John Resig (Mozilla Foundation (jQuery), Jonathan Snook (Yahoo!). These are guys that are at the coalface of the biggest, most successful Web development projects in the world.

It was a lively, and very funny discussion. First up were some general words of wisdom from Joe Stump, developer extraordinaire (see separate post on his presentation on scaling Web environments to global audience). He’s from the Valley… and he says his greatest asset there is his network. Many great developers, many great companies, many great brains, all sharing information and supporting others. Being commercial competitors doesn’t mean technology people shouldn’t help each other. Developers in Africa should build their networks, build their connections, and don’t be shy to ask for help and to share. Right. Enough serious stuff.

Some great quotable quotes:

* Can we ban the use of the word “Cloud”? Can we maybe use the word “Internet”?

* Question: Are frameworks stopping people investigating the depths of jscript? Answer: No-one wants to investigate the depths of jscript.

* Question: Will Flash be killed by HTML5?
Answer 1: Flash is the Cobol of the Internet.
Answer 2: It won’t go away for a long time, particularly for video.

* There are so many security holes in Flash, and people are driving buses through them.

* We’re getting clients saying, “Can you HTML5 our site?” and I think, “What the hell are you talking about?”

* The website is not the service, its just a gateway to the service.

* In the future, the browser is going to have more direct access to the hardware. The browser will become the OS, with more power and features.
(Ed’s note: What happens when the browser is so powerful and hardware-connected it will replace the OS. Will we then need a small, lightweight browser in the big fat OS-browser?)

* To go global you have to work on a baseline User Interface – don’t just develop for latest browsers, computers and phones.

Roger Hislop
www.sentientbeing.co.za
@d0dja