#POCO survey
/* I learned it at the "New Engineering Training Program" after joining IBM as
an electrical engineer in 1964. */
Gads Ed. I was born the year before you joined IBM. I feel like such a neophyte
now. 🙂
/* I recently read about defensive programming in "Writing Solid Code." That's
probably the equivalent term. It turns out the author doesn't approve of using
it blindly (it hides bugs). */
I would estimate that 30% on the average of all code I write is to "monkey
it"… make it safe and unbreakable for users who don't follow instructions.
Can you imagine the impact on corporate software america if software companies
could just write software without monkey code and error checking and rely on
end users with training to use it properly? Dreamland, I know, but I'd be
curious to know how much time a typical product does demand in monkey codeing.
I'll bet my personal percentage is about normal. -dave