<steve>

@Aki when you talk about regulating the theoretical and practical aspects of writing and executing software codes doesn't that responsibility fall with my compiler. coz as far as i am concerned my C++ compiler comply to certain standards.

</steve>

My sentiments are similar to Steve Obbayi's but unlike Conrad will not fully restrain myself from stating much that is in my mind.

Will see if we can get one or two of these KICTB & KEBS people to our Feb 2010 Kenya MSDN Interop meet. Seems they are trying achieve something that no one (software organization or industry body) anywhere in the world has succeeded in doing = creating certification for software developers / engineers - acceptable industry (local and global) wide ....

Tech giants such as Microsoft, Oracle, SAP, Google, IBM etc, when hiring software engineers ask for insight into and experience with certain standards = Platforms (Windows or *nix) and Compilers (C/C++/C#..Java ..) the software engineers will use to improve old or create new technologies. Developer tools even cause software developers to follow (or not) certain practices in their work so ... e.g. FOSS (GPL) tools discourage deliberate obfuscation of software (source) code. Si?

Why not call whatever is being done by the KICTB and KEBS a Promotion (not a Certification of) 'Best Practices' - reviewed or updated every few years?  My position is that certification should be left to major vendors - bound to versions of products (standards). Nothing proves software engineering skills more than PRODUCTS / (or software consumed as) SERVICES