An Under-Appreciated Fact: We Don't Know How We Program
A text full of intreaguing ideas, like:
''
It is so basic that nobody in the software industry notices it, but nobody outside the industry knows it. The fact is this: there is no process for programming.
''
and
''
Like many developers I took a 3 year degree course in this stuff. But at no point during those three years did any lecturer actually tell me how to program. Like everyone else, I absorbed it through osmosis.
''
and even more interesting
''
Some of the discussion here, and on Reddit and Hacker News is arguing that many other important activities are creative, such as architecture and graphic design. Note that I didn't actually mention "architecture" as a profession, I said "designing a house" (i.e. the next McMansion on the subdivision, not one of Frank Lloyd Wright's creations). People give architects and graphic designers room to be creative because social convention declares that their work needs it. The problem for software is that non-software-developers don't see anything creative about it.
''
and finally
''
Declaring software to be creative looks to the rest of the world like a sort of "art envy", or else special pleading to be let off the hook for project overruns and unreliable software. Emphasising the lack of a foundational process helps demonstrate that software really does have something in common with the "creative" activities.
''
After reading this I have to go back and sip a bit from my copy of the tao of programming :D
Thus spake the master programmer:
``After three days without programming, life becomes meaningless.''
Monday, May 05, 2008
Paul says: "there is no process for programming."
By at 22:08
Section: weird - thought provoking - probabily wrong - stimulating
Subscribe to:
Post Comments (Atom)
2 comments:
There are some definition of process for software development, but they approach the problem from an engineering point of view of "artefact" to be built. So top-down, and there is no clue on how to actually code. First because coding, seen as a process of craftsmanship, cannot be subject to a process, since it is a creative activity. Second, if it is wanted to be subject to some kind of process, then, what you consider is the I/O of the process. Leaving the rest to the 'black box' assumption.
Therefore, as you can see, the question has no right to exist ;-)
Wow... that's real Tao
As for myself, I like the middle-out approach a lot :D
Post a Comment