I did. 1. Stop thinking about the technology at this point, you are just wasting time which could be better used *designing the solution*. Note that technology just implements part of the solution, its not the solution in and by itself. 2. Solve the human factor sub-problem; what privacy concerns will such a solution raise? How will each of them be solved? 3. Some parts of Kenya have no electricity, leave alone internet; how will those people access the solution? 4. We all know the capability of our govt in terms of security, so how can we improve it to be sufficient for such a undertaking. Having all the citizens data in one 'database' is what I think is called a Honeypot, a target sweet enough to awaken the uber hackers who would make those script kiddies who deface websites seems like idiotic morons All I am saying, the problem is letter A in the alphabet, the database and primary keys are letter T, and theres a whole lot of work to do in between, and this work just happens to the most important. On Mon, Jan 30, 2012 at 9:40 AM, Odhiambo Washington <odhiambo@gmail.com>wrote:
@Karunyu,
Could you be a little more specific? Try to be part of the solution by telling us how you'd go about this. Leaving it as it is doesn't help, but simply means we retain the status quo. We need to be the change we want.
On Mon, Jan 30, 2012 at 09:19, Peter Karunyu <pkarunyu@gmail.com> wrote:
I think we are making the classic mistake programmers make; given a problem, jump straight to solving it in technology without doing due diligence and doing the bits in between problem and software.
IMHO, for and undertaking as such as this, the primary key in the database is the LEAST of your problems.
I would think that solving the human issues (privacy, accessibility from ASAL, security etc) would have precedence.
On Sun, Jan 29, 2012 at 6:16 PM, kris njoroge <krsnjo@gmail.com> wrote:
@josh so what would be the primary key or foreign key for that matter? the problem is not the information but the kind of information about you that would be accessible to those who should not have access to it. In the case of the drivers license guess its the amount of information returned to anyone that is the problem and not that the primary key was the social security no. Plus if information about you is being stored in different institutions or government agencies how else would they link your data across all the db's. Any system can be abused be it computers or paper systems. What would you suggest as the next step?
Skunkworks mailing list Skunkworks@lists.my.co.ke ------------ List info, subscribe/unsubscribe http://lists.my.co.ke/cgi-bin/mailman/listinfo/skunkworks ------------
Skunkworks Rules http://my.co.ke/phpbb/viewtopic.php?f=24&t=94 ------------ Other services @ http://my.co.ke
-- Regards, Peter Karunyu -------------------