Re:What a Programmer Does (1967) [pdf]
by seanmcdirmid on Saturday September 24, 2016 @02:53PM
(#12572058)
There is throw away code, one offs, and solutions that have immediate but not lasting values. Programming has been overloaded to mean a wide range of activities, from casual data analysis tasks to avionics engineering.
Re:What a Programmer Does (1967) [pdf]
by sztwiorok on Saturday September 24, 2016 @06:52AM
(#12570414)
yes, I have red and I don't agree.
I do not like such a generalization.
a summary of the entire article is:
"a programer does not primarily write code; rather, he primarily writes to another programer about his problem solution."
I agree with one: there are good programers and there are bad programers. I don't agree, that bad programers die young ;) Today there are more bad than good programmers.
Re:What a Programmer Does (1967) [pdf]
by kowdermeister on Saturday September 24, 2016 @07:00AM
(#12570441)
Summary is: communication is more important than writing syntactically correct programs.
No offense, but you have some trouble understanding the language. If you re-read it, it say that young programmer'S code die young, not the programmers themselves :)
Re:What a Programmer Does (1967) [pdf]
by sztwiorok on Saturday September 24, 2016 @07:27AM
(#12570501)
no offence taken.
I agree with this: "communication is more important than writing syntactically correct programs" but article is titled: "what a programmer does" not "what is the most important in a programer job"
Re:What a Programmer Does (1967) [pdf]
by kowdermeister on Sunday September 25, 2016 @07:31AM
(#12574880)
To me, that's equivalent :)*
* that's highly subjective
TLDR; You are not only writing instructions for the compiler but for your future self and your fellow programmers. How can you disagree with that?