Hard-coding secrets in application code is not ideal.
It makes rolling them hard by coupling them to an artifact, and is not particularly secure, if the artifact itself is compromised.
How do you make your tests aware if you’re running them from your IDE or not? That’s what I’ve been wrestling with, and there were some surprising results, so I thought it would be worth sharing.
Would you like to work in a team where XP is treated seriously? Would you like to work in a great physical environment with great colleagues? Would you like to work for me? Would you like to be an XP/Agile coach in an environment like that?
As always, it started with a bug. We’d been extending the capabilities of one of our services, to allow filtering deals on a new concept. While introducing that new concept, some classes had new fields added. One of those classes implemented equals(), but the method wasn’t updated to…
equals()