I was a proofreader for the book, and my feedback to Alex greatly influenced the style of presentation. I am happy to call myself one of his disciples. I find the material fascinating, and it has totally changed the way I write code, even Java code.
Some of Alex's "methods" are radical despite the vague wording I am providing:
- Progamming is about two things: algorithms and data structures.
- Think very hard about every line of code you write.
- Understand the structure of the problem you are trying to solve.
- Good code is often rewritten to be better.
- The goal is to write code that is both as general and as fast as possible.
- Naming things correctly is very important.
- Often the core of an algorithm is already a well-understood idea.
- If your function computes something interesting, return it.
How does that turn into source code? My posts on StackOverflow were done after this improvement in my understanding, so you can read those if you want. Otherwise, I'm not sure how to answer your question to your satisfaction.