When working on an application that needs to be translated into multiple languages, there is always the possibility of missing some of the strings that need to be translated. You can always switch into one of the other translations and look around for anything that didn’t get translated, but this has a couple of problems:

I have re-released ExtraCatalogs, an alternative MessageCatalog for Visualworks Smalltalk that supports XLIFF-format files.

I’ve recently been attending rogue.rb meetups. At the last few meetups, we’ve been playing with writing a maze solver, an exercise taken from the Ruby Programming Challenge For Newbies series.

One of the more powerful features of dynamically-typed languages like Smalltalk and Ruby is that of duck typing. As long as an object responds to the right messages for a given context, it can be used within that context no matter what actual type it has.

I’ve recently been learning RSpec after spending most of my career using the xUnit family of testing frameworks, including minitest.

Smalltalk had one of the first implementations of the Observer design pattern. Over the years, Visualworks Smalltalk has had several different implementations of this pattern, from the original #changed/#update approach, to #triggerEvent:, to Announcements.

I regularly listen to the EntreLeadership Podcast, and I highly recommend it.

For the past ten weeks, I’ve been writing about Affordances and Programming Languages.

I previously released DoubleAgents, a test-double library for Visualworks Smalltalk.

I have just released Threequals, which provides a Ruby-like #=== operator for Visualworks Smalltalk.