|
Coders at Work: Reflections on the craft of programmingIt was just basically the way you solve some kind of an unknown puzzleБЂ”make tables and charts and get a little more information here and make a hypothesis. In general when IБЂ™m reading a technical paper, itБЂ™s the same challenge. IБЂ™m trying to get into the authorБЂ™s mind, trying to figure out what the concept is. The more you learn to read other peopleБЂ™s stuff, the more able you are to invent your own in the future, it seems to me. We ought to publish code. The Lions Book is available. And Bill AtkinsonБЂ™s programs are now publicly available thanks to Apple, and it wonБЂ™t be too long before weБЂ™ll be able to read that. ThatБЂ™s well-documented code with lots of pioneering graphics algorithms in it. Seibel: Certainly with open source thereБЂ™s a lot more code out there to read than there use to be. Knuth: Yeah, thatБЂ™s right. But the more varieties of different kinds of notations are still usefulБЂ”donБЂ™t only read the people who code like you. Bibliography The Art of Computer Programming, Donald Knuth (Addison-Wesley, 1997) Beautiful Code: Leading Programmers Explain How They Think, Andy Oram, Greg Wilson (eds.) (OБЂ™Reilly, 2007) Byte, Vol. 6, No. 8, БЂњSmalltalk issue,БЂ«August 1981 Code Complete, Steve McConnell (Microsoft Press, 1993) Compiling with Continuations, Andrew W ...» |
Код для вставки книги в блог HTML
phpBB
текст
|
|