The image in the description is dead.
what a kata
I definitely agree, since the instructions say "with the strings filtered out", not "with only the integers returned". The other solutions seem to just be passing the test cases, as opposed to fully following the instructions. Perhaps a random test with different data-types could be added?
I like this approach in part because it filters out strings rather than returning numbers.
This code can be used on arrays that contain more data types than just Strings and Numbers,
and will return the array less the Strings.
Can't see the UML because the image is not longer available :)
The definition for Goose is not correct, the method with out body seems like definition for interface.
public class Goose
The description is bad: There are only 3 lines describing the actual tasks and they aren't even indicative (create new concrete behavior classes to fully take advantage of the Strategy Pattern and the Duck Class below, okay, but how? What to do? And how it's tested?). Then it's pages of information that looks like it's dumped from a tutorial page somewhere, without emphasising the key points of the concept. If I want to read something like that I can directly read off the Wikipedia page or something, no need for you to reproduce the whole article.
create new concrete behavior classes to fully take advantage of the Strategy Pattern and the Duck Class below
(Besides, what you did is just putting the top 3 google search result of "C# strategy pattern" in the links section. Do you think this is an subtitute for actually explaining how to do it by any stretch? It's lazy and responsible, to the least.)
The emphasis and relative portions of the descriptions is unbalanced and it needs refactoring.
This comment is hidden because it contains spoiler information about the solution
Java translation kumited. :)
Great kata, thanks!