Simon Harrer
That's a long story. It all started in 2011 when I and Jörg (one of my co-authors) had the opportunity to design two new Java courses at University. In addition to teaching Java and Concurrency on the JVM, we wanted to teach clean code practices through code reviews of the students homeworks, interactive code reviews in class, and code reviews as part of the oral exam. Over the course of six years, we've seen and marked hundreds of thousand lines of Java code by beginners. And we started to see patterns, a lot of them. That's the main source of knowledge for "Java by Comparison".
With the second co-author, Linus, joining our group at University in 2016, we started to collect those anti-patterns, explain why they are problematic, provide a solution, and explan why the solution is better. That's how the two-page layout of "Java by Comparison" is born.
We hope you like it, and that it'll help you become a better programmer! :-)
With the second co-author, Linus, joining our group at University in 2016, we started to collect those anti-patterns, explain why they are problematic, provide a solution, and explan why the solution is better. That's how the two-page layout of "Java by Comparison" is born.
We hope you like it, and that it'll help you become a better programmer! :-)
More Answered Questions
About Goodreads Q&A
Ask and answer questions about books!
You can pose questions to the Goodreads community with Reader Q&A, or ask your favorite author a question with Ask the Author.
See Featured Authors Answering Questions
Learn more