Should I pick up a functional programming language?
- by Statement
I have recently been more concerned about the way I write my code. After reading a few books on design patterns (and overzealous implementation of them, I'm sure) I have shifted my thinking greatly toward encapsulating that which change. I tend to notice that I write less interfaces and more method-oriented code, where I love to spruce life into old classes with predicates, actions and other delegate tasks. I tend to think that it's often the actions that change, so I encapsulate those. I even often, although not always, break down interfaces to a single method, and then I prefer to use a delegate for the task instead of forcing client code to create a new class.
So I guess it then hit me. Should I be doing functional programming instead?
Edit: I may have a misconception about functional programming.
Currently my language of choice is C#, and I come from a C++ background. I work as a game developer but I am currently unemployed.
I have a great passion for architecture. My virtues are clean, flexible, reusable and maintainable code. I don't know if I have been poisoned by these ways or if it is for the better. Am I having a refactoring fever or should I move on? I understand this might be a question about "use the right tool for the job", but I'd like to hear your thoughts.
Should I pick up a functional language? One of my fear factors is to leave the comfort of Visual Studio.
