Which kind of user is the book written for: It's actually got a pretty broad audience. - It's ideal for "new recruits" fresh to the glamour of programming in the Real World - say up to five years in programming employment. - It's great for students learning to program - it'll really show what "good" programming is - the kind of stuff you learn "up close" when working with exceptional programmers. - It's great for really experienced guys to refresh knowledge, to inspire them once more to write great code, and to use as a mentoring aid.
What the reader is supposed to know in order to follow up the book? - The user is expected to understand basic programming topics. - They are not expected to be a coding God, or to know any particular language. - The book will NOT teach them how to program - It will teach them how to program "properly"!
Which kind of methodology does your book apply (recommend) to achieve code crafting? - I do not favour any one technique or methodology, nor would it be right for me to do so. Different techniques are applicable in different circumstances. If you read the book you'll find out why :-) - The book covers different programming language styles (imperative, declarative, logic, structured, procedural, object-oriented, and so on) - The book discusses development methodologies like agile, waterfall, RUP, V model, etc. - The book discusses various approaches to software documentation, and approaches to code design.