java

Application programming interfaces (APIs) can get whacky, but compiled languages help users to get things semantically correct. And dynamic languages? Their ergonomic “dynamic sauce” ladled over a codebase can sometimes be less than helpful. This post is about how Groovy’s @CompileStatic can help to demystify what is happening at the call site of a method that has the same name and descriptor as another.

I recently had to develop a Java client to interface with an internal service over HTTPS that required client certificate authentication. It is not often that I need to dive into SSL certificates, and doing so usually requires me to step back and relearn some things. This situation was no different, but in an attempt to burn this stuff into my brain, I am writing about it here.