I definitely don’t want to write @Retry as an annotation; for sure, that part should be in the code, like many more use-cases of annotations, should be in the ‘main’ code. I get the impression that we are close to agreement here.

I’m not so sure we would agree on the approach to configuration, but that’s yet another topic. While configuration should be externalised, and the appropriate aspects managed by e.g. operations, you don’t need annotations to implement that, and going further, I think you can implement that batter without annotations. But, as I said, that’s probably another topic :)

--

--

Software engineer, Functional Programming and Scala enthusiast, SoftwareMill co-founder

Love podcasts or audiobooks? Learn on the go with our new app.

Get the Medium app

A button that says 'Download on the App Store', and if clicked it will lead you to the iOS App store
A button that says 'Get it on, Google Play', and if clicked it will lead you to the Google Play store
Adam Warski

Adam Warski

Software engineer, Functional Programming and Scala enthusiast, SoftwareMill co-founder

More from Medium

Ultimate Guide For Pro-Active Stores !

The Best Tips to Revive Your Furniture with Decorative Laminate Sheets

My Pomodoro Technique:

3 Journal Prompts to Help Integrate Work and Prayer for Spiritual Growth to Fully Live the Day —…