If you can’t provide a convincing before/after code for your pattern, you’re selling snake oil.
Welcome!
We agree with David Heinemeier Hanson.
If you propose a programming technique, you should be able to demonstrate as concisely as possible how your proposal is better than what was there before. The before/after approach puts all the facts on the table: you can directly compare the new code to the old code. Only then can you make an informed decision about which one’s better.
The same holds true when you’re learning how to program. Comparing good code to bad code is really helpful when you’re trying to figure out how to code in Java.
We used to teach programming at a university for over six years. After a few lectures, ...
Get Java By Comparison now with the O’Reilly learning platform.
O’Reilly members experience books, live events, courses curated by job role, and more from O’Reilly and nearly 200 top publishers.
