Owinna.com: Champion your support by supporting your Champions

Sports have been part of our lives from time immemorial. Almost every person is a fan of some sport in one way or the other. For example myself, I do not like football. I do not know more about football teams and their players. But I love cycling, cross country and hiking. I like watching vaulting and skiing though they are not played in Malawi. Sports are a fun.

Social networks have further the fun of sports. If you check statuses on Twitter and Facebook especially when great teams are playing, you will actually marvel at how tweeps and facebookers adore their favourite teams. The text messages that people send each other, the debates in public places, the expression of happiness in streets! Everything surrounding it depicts how people love sports.

Being a sports fan, Soyapi Mumba, saw the need to champion the support for his champions. He developed Owinna, a site to track competitions within Malawi and most popular ones in the diaspora. Owinna started as simple web page in January 2008. It was hosted under Soyapi's personal site, soyapi.com/owinna. The site received a good feedback from netizens. On a binary date 11/11/11, Owinna was patented with Registrar of Companies in Malawi.

Owinna.com - a sports site

 Four years later after the initial release, Soyapi decided to host it as a separate so as to improve the service that the application was providing. He changed the colour themes from blue to green, created a new logo and favicon and started supporting a mobile version of the site. In January 2012, launched owinna.com launched as a part-time startup. The new Owinna site was developed with a simplistic design in mind. It does not have fancy things and it is fast to load even with sloppy Internet connections.

Now you can follow Owinna on Twitter and Facebook to get up-to-the-minute updates. By following updates from Owinna you champion your support within your peers by supporting your champions! The word Owinna is derived from a Chichewa plural owina meaning winners or champions.

Soyapi Mumba, is a Malawian software developer and blogger. As a developer, he has several applications to his credit. He developed xNumber Puzzle, a cross-number puzzle game that helps you exercise your brain. It is also available on Facebook. He has also developed other useful applications and plugins including a popular Firefox addon, SearchWith, which provides faster way to search highlighted text using various search engine services.

Personally, I owe him a lot, having ushered me to the deep realms of open source. Before I developed the first version of ChicSpell, the Chichewa spell-checker for OpenOffice.org, Soyapi had already started working with Prof. Kevin Scannell on collecting probably the first ever word-list for an electronic Chichewa spellcheker. When he abandoned it, I adopted it which I continue maintaining it with Prof. Scannell. He has also made contributions to other open-source projects including Ushahidi platform, Baobab Touchscreen Toolkit (initially developed by Mike McKay when he was working full time with Baobab Health), and Unicode for Malawi Currency and calendar system.

Having been in software development for more than ten years, Soyapi is now a full time open-source developer working for Baobab Health as the head of software development department. He is almost always on Twitter and Facebook but rarely posts updates as he is busy with Owinna and other cool stuffs. One thing I have learnt in him is that he very quiet and humble, not geeky but technically well-composed. Above all, he loves his name. You cannot miss it on Google, Facebook, Twitter, Github and almost everywhere on the Internet.

Please Don't Learn to Code Versus Please Learn to Code

I have been following the exchange of advices among technophiles around the world. This exchange has been as a result of of a blogpost by Jeff Atwood. Jeff is the co-founder of http://stackoverflow.com/ now under http://stackexchange.com/ alongside Joel Spolsky. I have listed some of the the posts that have headlines around the world. I have deliberately left out forum discussions. 

There is one article by Rob Sobers of varonis.com that was written way back in January but did not catch the attention of many. I have placed it just below that of Jeff. Except for these first two, the articles have been arranged in alphabetical order. I hope you will enjoy them:

• Please Don't Learn to Code http://www.codinghorror.com/blog/2012/05/please-dont-learn-to-code.html

• Please don’t learn to code http://accidentalhacker.com/post/16116466587/please-dont-learn-to-code

•  A Modest Proposal: Please Don’t Learn to Code Because It Will Damage Your Tiny Brain http://inventwithpython.com/blog/2012/05/16/a-modest-proposal-please-dont-learn-to-code-because-it-will-damage-your-tiny-brain/

• Look, I love programming. I also believe programming is important http://pro.benjaminste.in/post/23103344300/look-i-love-programming-i-also-believe?80930240

• New tech advice: don't learn to code http://www.itworld.com/software/277396/new-tech-advice-dont-learn-code

• On Atwood's Please Don't Learn to Code https://gist.github.com/0f61db65bbd2d2cb681a

• On Learning to Code http://www.philterdesign.com/?p=633

• Please Do Learn How to Propose Better Solutions http://smarterware.org/10050/please-do-learn-how-to-propose-better-solutions

• Please Do Learn To Code http://decafbad.com/blog/2012/05/16/please-learn-to-code

• Please Don't Become Anything, Especially Not A Programmer http://learncodethehardway.org/blog/MAY_15_2012.html

• Please don’t learn to code but give it a try http://www.codingninja.co.uk/please-dont-learn-to-code-but-give-it-a-try/

• Please Don’t Learn To Code http://blogs.msdn.com/b/alfredth/archive/2012/05/15/please-don-t-learn-to-code.aspx

• Please Don’t Learn To Code http://www.gizmodo.com.au/2012/05/please-dont-learn-to-code/

• Please Don’t Not Need To Desperately Learn to Code http://www.iamdann.com/2012/05/15/please-dont-not-need-to-desperately-learn-to-code

• Please learn to code http://sachagreif.com/please-learn-to-code/

• Please Learn To Code… If You Feel Like It http://malevolent.com/weblog/archive/2012/05/16/please-learn-to-code

• Please Learn to Think about Abstractions http://www.hanselman.com/blog/PleaseLearnToThinkAboutAbstractions.aspx 

• Please Learn to Write http://www.randsinrepose.com/archives/2012/05/16/please_learn_to_write.html

• Please Understand Learning to Code http://dave.fayr.am/posts/2012-05-15-please-understand-learning-to-code.html

• The First Time I Used Programming At Work http://justinkan.com/2012/5/15/the-first-time-i-used-programming-at-work 

• Why I Desperately Needed to Learn to Code http://influencehacks.com/why-i-desperately-needed-to-learn-to-code
  

• Why I Taught My Daughter To Code (A Little) http://weblogs.asp.net/jgalloway/archive/2012/05/16/why-i-taught-my-daughter-to-code-a-little.aspx

• Why Jeff Atwood is Completely Wrong: Everyone Should Learn to Code http://www.rogerharford.com/jeff-atwood-is-wrong-everyone-should-code

• Why learning to code is not just a horrible trend http://www.digitaltrends.com/computing/why-learning-to-code-is-not-just-a-horrible-trend/ 

How and Why I think I am Devastated: Face of Malawi Plagiarised My Blog Post

I was going through news posted on Hacker News on Y Combinator. Suddenly I bumped on a link that simply said “Plagiarism”, so I was curious to read it. In the article, Joshua Gross, complained that TheNextWeb plagiarised his blog post entitled The $144,146,165 Button. He even cited some sentences where TheNextWeb copied word for word. The article shows he is very much devastated, and I do understand now that he has a good reason why he is devastated like that.

On Friday 11 May 2012, I wrote an article about How and Why I think Malawi has to Move on with Software Localization. I published it on that day because it was the birthday of Professor Kevin Scannell of Saint Louis University, one of my friends and mentors in natural language technologies. Prof. Scannell is the developer of http://indigenoustweets.com/, a site that collects tweets and blogs in under-represented languages. Prof. Scannell and I have been close friends for close to 5 years now and publishing the post was a subtle way (quoting his words on chat) of saying happy birthday to him. I kept the post in my Kanjedza (that is the name of my laptop) since 30 April 2012 when I conceived it.

I developed the blog-post from a comment I made on a picture on Facebook. A friend of mine, Patrick Kalamula of PatKay Graphics, tagged me on a graphic captioned Microsoft Mawu, depicting Microsoft Word with a Chichewa interface. I was a excited about it, a wishful thinking I may call it. I was responding to Patrick's comment that he would not love working on a Chichewa word processor because he finds even the Chichewa bible hard to understand. I can actually hinted that I would just copy and paste-blog it. You can check my comment is still there on Microsoft Mawu.

Joshua Gross article on plagiarism made me think twice about my blog post. I did a simple search on Google to see how many have written something similar to what I just blogged. I was very much astounded to find that Face of Malawi plagiarised my post. I am have been very much devastated too.

What Face of Malawi have done is just making a word for word copy-and-paste of my post. They have not changed anything. I am sure they got it from Twitter where I posted soon after publishing it. What they have managed to do is to paraphrase the article title and add a picture on it. They were too quick to plagiarise such that they copied it before I edited a few things on it. The time I was writing this post, I could still see my silly mistakes on their post:

• But language regulatory bodies and linguists always have great concerns over the “unsupervised growth” of terminologies. (I removed quotes in this statement because the phrase unsupervised growth was italicized and I wanted to keep formatting uniform.)

• Chichewa is just 38% (5/13 — ija, Panopa, pa, ina, yake). (I left the word Panopa titleized)

• I have always argued on elsewhere that it is volatile and unpredictable. (In my original post, I replaced the word Twitter with elsewhere and forgot to remove the preposition on)

You will also notice that the post on Face of Malawi is lacking some statements that I added later on:   

• Both mean the same: "Some banks were opened long ago but they do not have a lot of customers"

• The whole issue of localization comes to a bottleneck because there seem to be a tag of war between developers of new terminologies and users of such terminologies. Terminologists are fast developing new terminologies when the users are not ready or willing to use them. In languages of business, terminologies easily flow in. But that leaves other languages with the task of generating new terminologies or risk dilution.

They have not asked for my permission to repost it on their site. I am a simple blogger, they are a giant website. If you search my article on Google, their plagiarised article is appearing on top. It may look simple but this is distracting. My readers' traffic is technically being detoured from my original post to theirs.

I think what Face of Malawi have done is not good and should not be condoned. There are better ways of copying someone's work. They could drop me an email, asking for permission. Of course, I have no problems in anyone publishing my views but they should inform me first. I am proud to see my views being cherished out there. What I write on my blog are personal views and they cannot even defend why I wrote the way I did, and so they have no authority to plagiarise they way they did. I would ask them to apologise and recognise that I wrote it first. I am sure I have not offended anyone in publishing this.

How and Why I think Malawi has to Move on with Software Localization

We are in the technological era and the use of ICT is not news any more. Even in the remote areas of Africa, we find someone using at least a mobile phone. It has been argued that even smart phones are becoming more popular in villages. This is good news, but not everyone is enjoying this to the maximum. Let's face the reality, a larger section of villagers are not enjoying the services that we all enjoy: blogs, social media (WhatsApp, Twitter, Tumblr, Facebook, Skype, etc), you name them. Most of them just know how to make and answer calls. A few more are able to read and compose text messages, otherwise I have seen many more that do not even know what to do when text messages come on their phones.

I have always argued in various forums that in order to remove this language barrier, software localization is one of the best alternatives to make ICT appropriate to a target population. Localization of software involves adapting technologies to the linguistic, cultural and technical requirements of a target group of people. However if not handled carefully, software localization cannot achieve its intended purposes. One of the problems that native speakers find is to manage the influx of new terminologies that are begging their way into the language vocabulary. Generally, most people do not mind much about that as far as they communicate. But language regulatory bodies and linguists always have great concerns over the unsupervised growth of terminologies.

Somehow, leaving the terminologies to grow by themselves is very dangerous. Since a lot of terminologies that come in are loaned, they pose a lot of threat to the linguistic and phonological structures of the target language. For example, in Chichewa, the term banki is borrowed from the English word bank. The plural is banki or mabanki, and it is not clear yet which is the correct form. Regular users may not necessarily think that this is an issue, but for linguists it poses a lot of problems and inconsistencies in trying to grammatically categorise words like these. You may also wish to recall that Chichewa nouns affect sentence structure because they determine the right argument markers (called agwirizanitsi in Chichewa) to associate with. In Chichewa noun system, the noun banki belongs to class 9. Generally, class 9 plurals are in class 10. Thus, banki (sing. Class 9) => banki (pl. class 10) makes sense, while banki (sing. Class 9) => mabanki (pl. class 2/class 6) does not, yet it is the mostly used plural form. Compare the markers in the following two sentences: Banki zina zinatsegulidwa kale koma zilibe anthu ambiri. and Mabanaki ena anatsegulidwa kale koma alibe anthu ambiri. Both mean the same: "Some banks were opened long ago but they do not have a lot of customers") This is the case with other loanwords like ofesi (office), kapu (cup) et cetera. (For those that do not understand this number-based noun classification system: the word banki sounds to nicely belong to I-Zi class, but using mabanki creates a new classification, I-Ma, which is ungrammatical; just as pluralizations nkhuku => mankhuku and nyanja => manyanja can sound very awkward).

The worst case scenario is where the language becomes completely immersed into another language. Look at this Chichewa sentence in youth slang: Ndatrapa ngini ija magaye. Panopa ndikudona pa nide, titchekana boboo thayimu ina yake. Chichewa is just 38% (5/13 --- ija, panopa, pa, ina, yake). The rest is Chinglish: Chichewalised English. If we juxtapose it with an equivalent English sentence, it can be seen that this phrase is “skin-to-skin transliteratable” (forget about semantics here): I have trapped that thing, guys. I am downing to my den. We will check each other some time. So little by little English is eating away our language and if anything cannot done as soon as possible, we will lose out our beautiful language. Of course, I have a problem with youth slang. I have always argued elsewhere that it is volatile and unpredictable. As such, we cannot rely on it very much though we cannot deny the fact that it is influencing Chichewa language in general.

Linguists tell us that language (just like any cultural element) is dynamic. We take English as an example: In 1500-1600s, no one raised eyebrows if you spoke like this: I hath purposed to come unto thee, but was let hitherto. In this statement let means to prevent from. But you can agree with me that the word let now means allow as depicted in this phrase: Please let me go. This is exactly opposite to the original meaning . Similarly, the word gay does not carry the same meaning it used to carry some few years ago, because it is now more associated with sex orientation and not necessarily excitement. Chichewa has also changed overtime. For example, Chichewa that is in the widely used bible version, Buku Lopatulika ndilo Mawu a Mulungu, was translated by William Percival Johnson in 1912 and ever since it has not been modified. (By this, I am not referring to these parallel translations/versions: Malembo Woyera or Buku Loyera). There are some grammatical and semantical errors but Bible Society of Malawi is afraid to correct them (I don't know why). Leaving that aside, 1912 Chichewa is not the same as 2012 Chichewa. Exactly 100 years have passed and there are a lot of things that have changed about Chichewa language. For example, 1 Timothy 3:6 is translated as Asakhale wophunza. Wophunza means novice, but it took me time (and age) to grasp its meaning and understand that wophunza is the root for wophunzira (student). Nowadays, a better translation would be Asakhale wongobadwa mwatsopano (i.e. He must not be a new convert). In addition, in those days a town was called mudzi but today we know it as tawuni, and indeed tawuni is not mudzi (village). Given another 100 years or so, Pure Chichewa will not be the same.

The whole issue of localization comes to a bottleneck because there seem to be a tag of war between developers of new terminologies and users of such terminologies. Terminologists are fast developing new terminologies when the users are not ready or willing to use them. In languages of business, terminologies easily flow in. But that leaves other languages with the task of generating new terminologies or risk dilution. However, localization when viewed from a positive angle, it is a way of preserving a language. It is well-known that languages from the West are mostly associated with economic influence and are little by little subduing other indigenous languages.

In this technological era, every language that wants to survive has to move with fashion. English is fast adapting. Words like mouse, server, breadcrumbs, web do not have same meanings as they used to before 1960s. Similarly, words like blog, facebook (verb), google (verb), tweet (verb) have just born now with the invention of technology. So what is all this noise I am trying to make? We still need translation for our languages to survive and also for the larger section of Malawians that do not understand English. But we need to adjust with time. The language should retain its originality without imposing unnecessary rigour to contemporary readers/writers.