Dirty like a cheap whore. :p
But, my employer demanded it, and they pay me well.
Regarding Java and JAR dependencies - yep, there's a shitton of them. We have transitioned to using Maven and artifactory repositories to manage dependencies (both within the IntelliJ IDE and on our build systems, and that problem has largely been solved.
We often map beans that pull those "hardcodes" out of property files/resource bundles and fill them in to either the XML declarations or annotated objects. Its my view that hard coding magic into code is largely bad practice unless they truly are constants.
But, my employer demanded it, and they pay me well.
Regarding Java and JAR dependencies - yep, there's a shitton of them. We have transitioned to using Maven and artifactory repositories to manage dependencies (both within the IntelliJ IDE and on our build systems, and that problem has largely been solved.
We often map beans that pull those "hardcodes" out of property files/resource bundles and fill them in to either the XML declarations or annotated objects. Its my view that hard coding magic into code is largely bad practice unless they truly are constants.
