These are some notes on a String Calculator kata implemented in object-oriented way as a collaboration of entities. By entities we will consider different implementations of the same abstraction that emerged from the different input string formats. This kata implementation is object-oriented and tends to follow the object-oriented behavioral decomposition.

These are some notes on a String Calculator kata implemented in object-oriented way as a collaboration of entities. By entities we will consider different implementations of the same abstraction that emerged from the different input string formats. This kata implementation is object-oriented and tends to follow the object-oriented structural decomposition.

These are some notes on a String Calculator kata implemented in an “object-oriented” way as a single unit of work without state. Why the air-quotes are used? Because it is not true object-oriented ways of doing things, even though the class keyword is used. This kata implementation tends to be sort of procedural, but in a good way.

These are some notes on a String Calculator kata implemented in an “object-oriented” way as a single unit of work with state. Why the air-quotes are used? Because it is not a true object-oriented way of doing things, even though the class keyword and state are used. This kata implementation tends to be sort of procedural.

The big thing about practicing katas is not just to finish them, but the possibility to rethink them while repeating. This works best when you try to rewrite a kata in different paradigms and compare the solutions. Today, I want to talk about a String Calculator kata and its object-oriented implementation. Beyond that, we are going to take a look at decomposition and some object-oriented design principles. Let’s dive into it.

Recently, I had a chance to participate in yet another event organized by Software Crafters Barcelona.