Making sprint commitments will slow you down and waste your time. Make a forecast, then challenge your team to see how far into the backlog they can get.
"Just use maps to represent data in Clojure," they told me. Heresy! But I've fallen in love with the approach, and would like to share four reasons why.
Reasonable-looking code can hide translation debt and cause great sadness when the team can least afford it. If you spend the time to write some nice tooling for pseudo-translation
