thoughts about software and sensible security.


Kotlin’s invoke: it looks like a duck, quacks like a duck, but isn’t a duck


SUMMARY: Kotlin has given us a fresh perspective on some very ingrained OO-habits, particularly the pervasive use of nouns for objects that have only one public method.

Speaking like a native

Pronouncing a foreign language so convincingly that you can pass for a native speaker is one of the hardest tricks to pull off. While it comes natural to young children it is something that very few adults ever master. That is because our ears have become attuned to the speech habits of our native language and we interpret every foreign language according to these patterns. (more…)

The case for Kotlin


Ryan Cooke puts the euphoria about Kotlin into perspective in his post by highlighting some of the challenges in using it for production. He makes some good points, to which I would like to add my own.

He mentions that Kotlin has only recently reached the top 50 in the TIOBE index. Actually I think that’s no mean achievement, given that this ranking is calculated from the number of search engine results for queries containing the name of the language. Kotlin simply hasn’t been around long enough to amass that much internet presence. It says little about growth potential, whereas the recent benediction by Google as a first-class Android language bodes well. (more…)

thoughts about software and sensible security.

Recent Posts

Jasper on twitter

Convention over configuration and add security later. The trouble with CRUD is that it’s pretty crude. New blog
h J R
Software security isn’t very visible to end users and stakeholders. It’s the lack of it that is.
h J R
No Photoshop trickery: this really is Patsy’s way to show who’s boss.
h J R
Who are you calling null, #kobo?
h J R
All software start to resemble the inside of Salisbury Cathedral: a clever patchwork that can barely support its we…
h J R