Author: Abou Kone

I am a front end architect with 10+ years of experience in web development. The best part of the process for me is converting ideas into code and solving the technical problems that come along. Alongside providing technical leadership and architectural support to projects spanning multiple industries, I am also experienced in leading discussions with designers, developers, and business stakeholders helping to guide teams in turning complex business workflows or data into easy-to-use web and mobile interfaces. I believe in delivering high quality products and am constantly looking into improving the process and tools use to achieve this goal.

Angular2 Routing Error

~ Abou Kone ~ Leave a comment

One of the better things about Angular2 which had already present in Angular1 was the outputting of meaningful errors whenever they happened within the framework. Unfortunately with the new angular-cli webpack based build, it’s not always easy to understand what is happening with certain errors. Consider this error I recently ran into:

error_handler.js:47 EXCEPTION: Uncaught (in promise): TypeError: Cannot read property ‘_outlets’ of undefined
TypeError: Cannot read property ‘_outlets’ of undefined
at http://localhost:4200/main.bundle.js:13434:56
at forEach (http://localhost:4200/main.bundle.js:5950:13)
at PreActivation.deactiveRouteAndItsChildren (http://localhost:4200/main.bundle.js:13433:99)
at http://localhost:4200/main.bundle.js:13435:19
at forEach (http://localhost:4200/main.bundle.js:5950:13)
at PreActivation.deactiveRouteAndItsChildren (http://localhost:4200/main.bundle.js:13433:99)
at http://localhost:4200/main.bundle.js:13435:19
at forEach (http://localhost:4200/main.bundle.js:5950:13)
at PreActivation.deactiveRouteAndItsChildren (http://localhost:4200/main.bundle.js:13433:99)
at PreActivation.traverseRoutes (http://localhost:4200/main.bundle.js:13418:22)

Can you figure out what is going on? I could not for a while, this happened while trying ti lazy load a module. I checked the component rendered by the path and the <router-outlet> tags where present as expected. It’s not until I checked the component class file that I found a line that did this:

this.router.navigate([‘session’], { relativeTo: this.activatedRoute });

Within the ngOnInit. Bingo! The session path did not exist within all my route definitions.

So the next time this happens to you make sure you are trying to navigate to a path that actually exists in your route definitions.

Angular2 Router Basics

~ Abou Kone ~ Leave a comment

In the learning curve of Angular2 router features, I ran into a bug that left my head scratching. Trying to render a routerLink would not create the necessary href url. As in:

<a  routerLink=”app/people-search” routerLinkActive=”active”><i class=”fa fa-search fa-fw” aria-hidden=”true”></i>People Search</a>

would render to:

<a _ngcontent-rxo-12=”” routerlink=”app/people-search” routerlinkactive=”active”><i _ngcontent-rxo-12=”” aria-hidden=”true” class=”fa fa-search fa-fw”></i>People Search</a>

As you can see, no href rendered, just the routerLink and routerLinkActive directives rendering as all lowercase attributes. Weird.

Well not so if I had actually picked up this line from the documentation:

RouterLink, RouterLinkActive and RouterOutlet are directives provided by the Angular RouterModulepackage. They are readily available for us to use in our template.

Duh.

I added the

import { RouterModule } from ‘@angular/router’;

statement to my module definition file and I was back in business.

Basics.

Understanding the developer ecosystem in West Africa Part II

~ Abou Kone ~ Leave a comment

Disclaimer: This is an opinion based on my experience, observations and interactions in the developer ecosystem in West Africa, more specifically Senegal and Cote d’Ivoire.

In my previous post I talked in general terms about some of the issues affecting the developer ecosystem in West Africa with a promise to dwell more into the details in a subsequent post, so here we are. My initial post briefly touched on the skills gap issue and in this post I will try and focus on the reasons why. To make the writing of this post easier, i will repost the problem statement of my previous

You will hear complaints from local developers that they are not valued enough by local companies with major projects (enterprise) being sent out to Northern Africa (Tunisia or Morocco) or France to be coded at a premium therefore robbing local companies of much needed revenue and developers of much needed opportunities to build and scale major projects. On the flip side, you will hear horror stories from companies that tried local talent and ended being burned bad with awkward solutions that were badly implemented if implemented at all and are a maintenance nightmare making them resolute in exporting the coding work on the next implementation to make sure they end up with a quality product.

How did we get there?

1) Education

This problem is not unique to Africa in general but finding tech talent with employable skills right out of college is difficult. The accepted wisdom amongst the CEOs and managers I talked to was to expect an initial training period after hiring to get to a certain level of productivity out of new hires. From developer themselves, they expressed a certain level of frustration with the quality of the education made available to them in the field of computer science. Complaints covered the sometimes questionable skill level of the instructors to the inability to sometimes being able to practice the craft they are learning due to lack of proper infrastructure. On that end, it’s not unheard of in certain private or public schools to follow a “programming” cursus without ever compiling or writing a single line of code on a computer all the way to graduation. Now as I said earlier, I’ve interviewed my share of college students for internships here in the US that I deemed not qualified because outside of college courses they didn’t have much to offer in terms of usable skills. The ones hired were the ones that went beyond school work and had side projects that showed self-starter spirit, and the ability to learn independently that are actually crucial for a successful developer career. These qualities are universal in my opinion and will apply not matter the context but even in the US, I feel there should be a tighter cooperation between the business community and the Computer Science academia in order to produce the types of graduates that will be day one contributors to businesses (and that means graduates starting businesses as well).

2) Language

This more specifically applies to French speaking West Africa with all coding languages being native English constructs, and most material, tutorials, answers and questions being produced in English, French speaking African developers find themselves at a disadvantage when the only way to get past a nasty bug or implement a new feature based on solid architectural research requires Google Fu skills most natural to English speakers. The good news is that most develop a reading and writing proficiency that helps in most cases but the lack of fluency is definitely an obstacle to better and/or quicker code fluency. This is why at Coders4Africa we insist on being an English only company for conducting every day business as it will only help our French speaking developers being more proficient at their craft.

3) Cultural and Social Context

To each country their own culture and social contextes and in projects that span multiple countries, interactions between team members with different expectations can lead to awkward situations with different level of seriousness to them. For these developers working locally for international clients in the US or Europe, most problems I’ve encountered were focused on communication and that’s understandable. I’ve been part of a distributed team and one of the most successful success factors for this type of team is a high level of intra team communication to make up for the lack of physical proximity. The same concept applies for a client getting their project done remotely, a high level of communication ensures a high level of confidence for the client. The complaints that I have heard from clients the most was that developers would often disappear for long period of times, being unresponsive to emails, and when they presented work it was not up to the client’s requirements. Big surprise. Of course a whole lot can go in there in terms of project management and using some kind of agile project management methodology but if neither the client nor the developer are familiar with it, it makes for a tough interaction.

In terms of work habits as well, and this is more geared towards customers in the US, American are known work horses and expect the same out of their counterparts. Mixing those expectations with the more laid back approach to deadlines and work delivery of certain shops can lead to let’s say unpleasant situations. It’s just not Americans, for expats coming back from Europe or the US and launching startups, this turns out to be one of the most difficult aspects of working locally. Things just happen slower. Of course if the work is geared towards international clients then there is no way you would be able to sustain a business and this requires coaching and training staff to meet these international standards.

4) Exposure

I hesitated a lot to use the term exposure as one of the issues but allow me to use for lack of a better terms in my mind at the time. Throughout the multiple conferences we held for Coders4Africa, the most popular event we held were the developer workshops we held to expose local developers to the different frameworks and tools we used to do our work. This is where the most productive exchanges happened and where I enjoyed the most. Being a front end developer, being able to talk about AngularJS, TDD, build tools, continuous integration, APIs, and seeing the light go on was and is extremely gratifying but when I mentioned exposure, it’s to get back to the point that I know about these concepts and tools for the most part because:

  1. They’re common usage where I worked
  2. I’ve learned about them in school before
  3. I keep myself updated on what’s going on in my industry

To link back to my previous point about education, if the foundation is not solid, it will be difficult for the house to stand strong. Sometimes it’s just a matter of being exposed to the right kind of information. Sure some will tell me that it’s the individual’s responsibility to seek knowledge and get better, which is true to a certain extent, but the ease in doing so is not evenly distributed in the software world. I will expand more on that in my next point

 

5) Thriving business to development ecosystem

I have been fortunate to spend my career here in the US where a lot of the innovation in software development not only takes place but is then actively used by businesses/startups when it is not actually created by businesses/startups. This dynamic environment indirectly ensures that the workforce in general is always up on the latest trends in the industry if not actively at least passively. Programming for the most part in the US is a lucrative occupation, with demand outpacing supply. Businesses have recognized the importance of technology to their bottom line and invest in and compensate their developers properly to attract the best and ensure retention. I feel that is quite not the case yet in West Africa although awareness is increasing. The industry though as a whole needs a serious injection of capital to foster the kind of sustained innovation we see in the US and Europe.

 

The silver lining

Now that I am done painting this apocalyptic picture of this ecosystem,  I would like to end by reminding you that this post is specifically focused on the problematic aspects of the ecosystem. Ask somebody to write a piece about the state of the developer ecosystem in the US and you would get something as grim, certain problems are just universal.  In spite of these problems, what you should remember is the amazing number of skilled developers that defies these odds to bang out crazy good code, launch and support startups. Those are the real heroes in my opinion. I just wanted to talk about these to surface past conversations that I believe are still happening today in order to improve the eco system as a whole. I am a firm believer when it comes to African tech that a rising tide lifts all boats and a thriving African tech ecosystem with international recognition will be a boon for us all. In any case, I hope this starts a conversation where we can all learn from and come up with actionable items to help fix these issues, which is the real goal of these posts.

 

 

 

Understanding the developer ecosystem in West Africa Part I

~ Abou Kone ~ 5 Comments

Disclaimer: I don’t pretend to give scientific result based on accurate polling or any kind of scientific method (outside of observation). This is just a summary of my observations so treat it as what it is meant to, an opinion based on my interactions and experience. Furthermore as my experience extends to Senegal and Cote d’Ivoire so I’d scope my remarks to these two countries even though the title says West Africa.

I was fortunate to have the opportunity to work remotely this summer in both Dakar and Abidjan and it was great to be able to experience my daily developer routine within the slower pace and context of these cities. I was also able to network with local developers and the companies that hire them and get feedback from both parties. It was mind opening and I’ve walked away with a new insight and passion for bettering certain aspects of the current situation I will dwell on shortly.

The Good

Well, I’ll start with the easiest: being home.

On top of my family, being able to see my aging parents on a daily basis was invaluable. Being able to trod the same roads and alleys I’ve been on as a teenager with a new set of eyes and different experiences was great. Seeing old faces, catching up on common acquaintances, shortly, the whole experience of being back after a long time away is good. it’s like finding an old part of yourself that you thought was gone for good.

Getting past the nostalgic personal part, what was really good about banging out code locally?

  • Internet connection: I opened an Orange 4G mobile prepaid account as most people do, and to resume my experience in Dakar, i never felt like I was lacking and that the connection was unusable. That experience also extended to the home DSL connection where i was able to Netflix to my leisure without a noticeable drop in quality. So pushing to Github was definitely not an issue. It was not all rosy though but I’ll expand on that as part of the Bad.
  • Co-Working Spaces: Outside of the Coders4Africa offices, I worked most of the time from Jokkolabs and I enjoyed the space and the professionalism of the staff. Whether it was the Internet connection or finding a private room for calls, everything was handled with the professionalism of a well run operation. Outside of local startup working out the space, I could pick out expats and other nomads working out of the space just like me.
  • The Developer Ecosystem: The constant with the majority of the developers I met was how much more they wanted to know how to get better, asking for tips and feedback. There are actors making things happen in order to elevate the skill level (Noting Leger Djiba and his A2DG initiative ) with meetups and coding events being pretty frequent.

The Bad

For every head there needs to be a tail so I also have to talk about the negatives I either experienced or were brought up during discussions with local actors.

  • Bandwidth: As mentioned earlier, bandwidth was pretty good in Dakar but Abidjan was a different story with a slower bandwidth in general, and areas where I would just lose the connection. This was with an Orange SIM card as well. When it worked it was decent, and I was able to get my work done properly. Your mileage might vary depending on the country.
  • Internet cost: If I am not mistaken decent Internet Access was declared a human right but operators are still treating it as a privilege. The prepaid model is the de-facto operation mode for Internet access in most West African countries but it can run pretty expensive. If i remember correctly, 24 hours of 4G access (2GB max) was billed at about 2 dollars in Dakar, which can run expensive if you don’t pay attention. Home plans for 10MB of ADSL Unlimited Data will run you about $65 a month.
  • Skills Gap: I mentioned earlier that there is a young and eager local workforce and what surfaced through my interactions, and I am talking here from my background and experience as a front end developer, for the most part, they are developing with “antiquated” toolsets , frameworks and processes. I want to clarify that this is not a case of me being a “let’s play with the latest industry toy” fanboy but when you have developers sharing code using email instead of a repository, you know you have a serious problem. This whole discussion in itself deserves an article of its own to get into the other symptoms, causes and  solutions  but there is an undeniable skills gap in general when it comes to software development as it is done by the best. This is one of the reasons why we originally started Coders4Africa in 2009, to create a pan-african community of developers while at the same time providing the training needed to eliminate that skills gap. This has evolved into Gebeya, launched last month in Ethiopia and first in what we hope will be a network of professional training institutions focused on producing polished and skilled techies for the local markets.

The Ugly

Seriously, there is nothing I would qualify as ugly so I would just use this section to summarize an issue that was brought up quite often, both in Dakar and Abidjan, in an attempt to start a discussion. It goes like this:

You will hear complaints from local developers that they are not valued enough by local companies with major projects (enterprise) being sent out to Northern Africa (Tunisia or Morocco) or France to be coded at a premium therefore robbing local companies of much needed revenue and developers of much needed opportunities to build and scale major projects. On the flip side, you will hear horror stories from companies that tried local talent and ended being burned bad with awkward solutions that were badly implemented if implemented at all and are a maintenance nightmare making them resolute in exporting the coding work on the next implementation to make sure they end up with a quality product.

Now before going any further I am not implying that ALL local developers suck, or/and that ALL companies have had bad experiences using local talent to get software built. Based on my limited set of interactions this was a recurring comment which makes me think that the issue is widespread enough to be noticeable by all parties. As i mentioned earlier, this deserves an article of its own that I will hopefully get to later, there are many moving parts to it and I want to give it justice. As they say, where others see problems an entrepreneur sees opportunities and I am working with others to bring a credible solution

I would summarize this first post by saying that it was an eye opening experience for me and I hope to be soon one of the forces with Gebeya, Coders4Africa and others I can’t yet talk about that are working locally (and internationally) to improve the ecosystem so that African software development becomes a force to reckon with.