Coding Ninja

Ask us programmers our skill set and we can confidently iterate them. When required to document our skill set such as in a Curriculum Vitae _(resume)._ We can objectively list them along with meta data about language competence. That’s great! nothing wrong with this, that is if communication with computers are the focus. Software development does not occur in isolation, it occurs between other people. Some of those people happen to be programmers like us. [Read More]

This post is a response to Jeff Attwoods post Please don’t learn to code (15th may 2012). I agree with 90% of this post, but I wanted to present a slight twist: I whole heartledly agree with Jeff when he say’s that its nonsensical that “every-one should learn to program”. Jeff offers an analogy about plumbing and he is correct in this regard. However I will need to re-visit this analogy later. [Read More]

This is a response to Steve Yegge Post: programming’s dirtiest little secret that was made on September 10, 2008 (so a little old) :) I highly suggest you read the original article if you have not yet done so. Although its rather long, I understand where Steve is coming from. To sum his central tenet would go something like this: non-touch-typists have to make sacrifices in order to sustain their productivity [Read More]

There are two ways of constructing a software design: One way is to make it so simple that there are obviously no deficiencies and the other way is to make it so complicated that there are no obvious deficiencies. — C.A.R. Hoare, The 1980 ACM Turing Award Lecture The computing scientist’s main challenge is not to get confused by the complexities of his own making. — E. [Read More]