A very good & sort article with comments. http://arstechnica.com/information-technology/2014/03/information-overload-i-know-too-much-to-program-quickly-what-can-i-do/
Basically the author is saying that he has a problem. He knows so much now, especially trying to anticipate problems, that his coding is slower. And so he is NOT PRODUCTIVE! <quote> Lately, I've been noticing that the more experience I gain, the longer it takes me to complete projects or certain tasks in a project. I'm not going senile yet. It's just that I've seen so many different ways in which things can go wrong. And the potential pitfalls and gotchas that I know about and remember are just getting more and more. Trivial example: it used to be just "okay, write a file here." Now I'm worrying about permissions, locking, concurrency, atomic operations, indirection/frameworks, different file systems, number of files in a directory, predictable temp file names, the quality of randomness in my PRNG, power shortages in the middle of any operation, an understandable API for what I'm doing, proper documentation, etc. In short, the problems have long since moved from "how do I do this" to "what's the best/safest way of doing it." </quote> -- There is nothing more pleasant than traveling and meeting new people! Genghis Khan Maranatha! <>< John McKown ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
