Ruby and Ada
Yes, they couldn't be more different: duck typing the former, very strong typing the latter.
Duck typing is not as robust as strong typing, but its flexibility makes it very easy to write some fast-and-dirty code. Typical use case: if I have some text file that I need to process to extract information or if I need to write some networking code for an extemporaneous need.
However, for larger and longer-lived software I prefer the order that Ada can enforce to your code.
Sure, you could do the same with C or Ruby by choosing some coding convention, but having the compiler enforcing it and checking it before you can run the code it is much better. How many times I had to run some code again and again in order to find a bug that would have been spotted at compile time by Ada.
We're a place where coders share, stay up-to-date and grow their careers.
We strive for transparency and don't collect excess data.