Found 3 comments on HN
mcguire · 2018-03-27 · Original thread
I found it very interesting for being one of the very few books that deals with code as a formal system.

You don't need to understand the code; you don't need to step through the code. You follow the steps for "extract method" and you go from a working state to another working state with no worries.

The individual refactorings are more-or-less interesting, but as others have said, they're somewhat commonplace now.

Two books that every programmer should read: Software Tools[1] and The Elements of Programming Style[2] by Kernighan and Plauger. Bonus: The Unix Programming Environment[3] by Kernighan and Pike.

[1] https://www.amazon.com/Software-Tools-Pascal-Brian-Kernighan...

[2] https://www.amazon.com/Elements-Programming-Style-2nd/dp/007...

[3] https://www.amazon.com/Unix-Programming-Environment-Prentice...

todd8 · 2017-12-27 · Original thread
First, keep solving problems. Mathematical brainteasers got me started problem solving when I was in grade school. I really like Martin Gardner's books[1] and those by Robert Smullyan[2]. These kinds of problems develop the flexibility of thought that helps find creative solutions.

Actual, specific approaches to tackling tough problems are taught by the famous Hungarian mathematician George Polya in his classic book How to Solve It [3].

Discrete Mathematics is a field that covers a number of areas, but especially in counting problems (from combinatorics) and graph theory there are a number of results that are not hard to grasp but lead to beautiful solutions for real problems. There are many powerful theorems and principles in discrete math that will unlock seemingly impossible problems. Unfortunately, the books for this subject are mostly written for math majors that are interested not only the application of these results but how to prove them and consequently the books may not appeal to everyone. Perhaps something like Schaum's Outline of Discrete Mathematics would suitably cover the way to apply some of the important theorems without bogging down in the proofs.

Finally, I think there is value in doing small interesting programming projects. Two older books, available used, with interesting projects are Etudes for Programmers by Wetherell [5] and Software Tools in Pascal by Kernighan and Plauger [6]. Etudes has my favorite exercise for trying out new programming languages, building an interpreter for the simple TRAC programming language; Software Tools has a number of programs in Pascal that do interesting things, try implementing the programs in your programming language--they cover a range of difficulties and the book has a nice discussion for each that explains why the programs are structured the way they are.

A more advanced book, Structure and Interpretation of Programming Languages, available as a downloadable pdf [7] is a classic book for those wanting to become better programmers.

[1] https://www.amazon.com/Martin-Gardner/e/B000AP8X8G/ref=sr_tc...

[2] https://www.amazon.com/Raymond-M.-Smullyan/e/B000AQ1NF0/ref=...

[3] https://www.amazon.com/How-Solve-Mathematical-Princeton-Scie...

[4] https://www.amazon.com/Schaums-Outline-Discrete-Mathematics-...

[5] https://www.amazon.com/Etudes-Programmers-Charles-Wetherell/...

[6] https://www.amazon.com/Software-Tools-Pascal-Brian-Kernighan...

[7] http://web.mit.edu/alexmv/6.037/sicp.pdf

angrycoder · 2011-02-22 · Original thread
Software Tools in Pascal. There was a previous version with examples written in something called Ratfor, which from what I've read is a hybrid of fortran and C. http://www.amazon.com/Software-Tools-Pascal-Brian-Kernighan/...

Get dozens of book recommendations delivered straight to your inbox every Thursday.