When I was fourteen, I wrote space-invader games in BASIC on a VIC-20. If you were interested in computers back in 1982, I bet you did the same. When I was 18, I wrote multi-user dungeons in C on serial terminals attached to a Sun 3. When I was 22, I worked deep down in the guts of a text database system — still C, now on a Sun 3/80 of my very own, with one of those HUGE bitmapped screens with a million black-or-white pixels. I was in touch with my friends from university: we were going to write compilers and operating systems and cool stuff like that — and to some degree, we did. We sent each other our in-progress code, complained about each other’s programming-language designs, and laughed at how inefficient each others’ completely unnecessary reimplementations of malloc() were. [I remember a friend's implementation achieving something like 18% occupancy.]
via reprog.wordpress.com
This is a great blog post which speaks of the loss of creativity in the realm of programming. The comments really add to the article.
My skills are no where near the level the author has. But I recognize the frustration of the "busy work" required to make our projects shine that seem to overtake the actual time it takes to create.
I wonder if this is limited to the corporate environment or if this is part of the price I need to pay in order to master what I'm learning.
Recent Comments