lpetit

Hello,

It was an attempt (from a non-native english speaker, so maybe the literal translation from french did not have the same exact meaning) to feel like "There's a sense of urgency for me to go there, I can feel, I know this will be good, for me, for the project" => the "have to go" has since been replaced / complemented by an explanation on the page.

Sorry, as a non native english speaker, such subtleties can escape. Correctedn thanks!

Yes, this was confusing, and is now hopefully addressed in the new version of the text. Thanks for pointing this out,

Laurent

Challenge yourself by thinking whether you could write better java code, in the light of your new knowledge from the clojure side. Straightforward example: produce far more orthogonal java code by using composition and the strategy pattern more, programming more to interfaces and delegating more some "general" work on interfaced objects to static methods in helper classes, etc.

That is, don't throw the baby with the bath water. Though coming with more "boilerplate" (as in "more ceremony"), there are still ways of programming in java that can make you happy at the end of the day: when you feel that your code is more DRY (which does not necessarily mean less code, BTW), and more orthogonal (more interfaces -e.g. callback interfaces- are generally a step in the right direction, though not necessarily a general rule).