Wednesday, May 6, 2009

Code Complete 3, Etc

1. Pragmatic Programmer (Hunt and Thamas 2000)
2. Jon Bentley, Programming Pearls, 2nd ed. (Bentley 2000)
3. Kent Beck, Exteme Programming Explained: Embrace Change (Beck 2000)
4. Steve Maguire, Writing Solid Code - Microsoft's Techniques for Developing Bug-Free C Software (maguire 1993)
5. The Practice of Programming, by Brian Kernighan and Rob Pike (Kernighan and Pike 1999)

Code Complete 2, Daily Build, Smoke Test, and Tools

Daily Build, Smoke Test, and Tools
In your project,
1. "do you have 'daily build' system?"
And 2. "do you use 'Smoke Test'?"

Tools
1. www.sdmagazine.com/jolts
2. Hunt, Andrew and David Thomas. The Pragmatic Programmer. Boston. MA: Addison-Wesley, 2000
3. Vaughn-Nichols, Steven. "Building Better Software with Better Tools." IEEE Computer, September 2003, pp. 12.14
4. Glass, Robert L. Software Conflict: Essays on the Art and Science of Software Engineering. Englewood Cliffs, NJ: Yourdon Press, 1991
5. Jones, Capers, Estimating Software Coast. New York, NY: McGraw-Hill, 1998
Boehm, Barry, et al. Software Cost Estimation with Costs II. Reading, MA: Addison-Wesley, 2000

Monday, May 4, 2009

Wish list of books

Wish list of books.
How many books can I read in this year?
The number is the wish order of reading.

4. The Psychology of Computer Programming,
by Gerald M. Weinberg (프로그래밍 심리학)
1. The Practice of Programming,
by Brian W. Kernighan and Rob Pike. (프로그래밍 수련법)
Programming Challenges,
by Steven S. Skiena, Miguel Revilla (프로그래머 두뇌 단련 퍼즐 44제)
2. The Pragmatic Programmer,
by Andrew Hunt, David Thomas (실용주의 프로그래머)
My Job Went to India: 52 Ways to Save Your Job,
by Chad Fowler (사랑하지 않으면 떠나라)
3. 겸손한 개발자가 만든 거만한 소프트웨어,
by
5. ship it,
by Jared Richardson, Will Gwaltney, Jr
0. 디테일의 힘,
by 왕중추