Skip to main content
The 2025 Developer Survey results are in. Explore insights into technology and tools, careers, community and more. View results.
Software Engineering

Return to Answer

replaced http://stackoverflow.com/ with https://stackoverflow.com/
Source Link
Community Bot
Community Bot
  • 1

I've contemplated this exact situation.

This is what I plan for my team:

  • Mix C# with F#, this can be done by using C# for the majority of the code-base. Where heavy data processing is required, write the associated functions in F# and put it inside a dll, or reference it. Example hereExample here

  • Slowly re-factor your existing code-base in the above fashion.

  • Not all code has to be functional.

  • Get your team to learn the basics of Haskell, LISP over the weekends.

  • Get them to learn F#, by trying to solve Euler Project puzzles (that helped me a lot when I was learning F#). Again this should be something done say over the week end, or during work time if you want set a day aside for "training".

I've contemplated this exact situation.

This is what I plan for my team:

  • Mix C# with F#, this can be done by using C# for the majority of the code-base. Where heavy data processing is required, write the associated functions in F# and put it inside a dll, or reference it. Example here

  • Slowly re-factor your existing code-base in the above fashion.

  • Not all code has to be functional.

  • Get your team to learn the basics of Haskell, LISP over the weekends.

  • Get them to learn F#, by trying to solve Euler Project puzzles (that helped me a lot when I was learning F#). Again this should be something done say over the week end, or during work time if you want set a day aside for "training".

I've contemplated this exact situation.

This is what I plan for my team:

  • Mix C# with F#, this can be done by using C# for the majority of the code-base. Where heavy data processing is required, write the associated functions in F# and put it inside a dll, or reference it. Example here

  • Slowly re-factor your existing code-base in the above fashion.

  • Not all code has to be functional.

  • Get your team to learn the basics of Haskell, LISP over the weekends.

  • Get them to learn F#, by trying to solve Euler Project puzzles (that helped me a lot when I was learning F#). Again this should be something done say over the week end, or during work time if you want set a day aside for "training".

added 23 characters in body
Source Link
Darknight
Darknight
  • 12.2k
  • 1
  • 40
  • 58

I've contemplated this exact situation.

This is what I plan for my team:

  • Mix C# with F#, this can be done by using C# for the majority of the code-base. Where heavy data processing is required, write the associated functions in F# and put it inside a dll, or reference it. Example here

  • Slowly re-factor your existing code-base in the above fashion.

  • Not all code has to be functional.

  • Get your team to learn the basics of Haskell, LISP over the weekends.

  • Get them to learn F#, by trying to solve Euler Project puzzles (that helped me a lot when I was learning F#). Again this should be something done say over the week end, or during work time if you want set a day aside for "training".

I've contemplated this exact situation.

This is what I plan for my team:

  • Mix C# with F#, this can be done by using C# for the majority of the code-base. Where heavy data processing is required, write the associated functions in F# and put it inside a dll, or reference it. Example here

  • Slowly re-factor your existing code-base in the above fashion.

  • Not all code has to be functional.

  • Get your team to learn the basics of Haskell, LISP over the weekends.

  • Get them to learn F#, by trying to solve Euler Project puzzles (that helped me a lot). Again this should be something done say over the week end, or during work time if you want set a day aside for "training".

I've contemplated this exact situation.

This is what I plan for my team:

  • Mix C# with F#, this can be done by using C# for the majority of the code-base. Where heavy data processing is required, write the associated functions in F# and put it inside a dll, or reference it. Example here

  • Slowly re-factor your existing code-base in the above fashion.

  • Not all code has to be functional.

  • Get your team to learn the basics of Haskell, LISP over the weekends.

  • Get them to learn F#, by trying to solve Euler Project puzzles (that helped me a lot when I was learning F#). Again this should be something done say over the week end, or during work time if you want set a day aside for "training".

Source Link
Darknight
Darknight
  • 12.2k
  • 1
  • 40
  • 58

I've contemplated this exact situation.

This is what I plan for my team:

  • Mix C# with F#, this can be done by using C# for the majority of the code-base. Where heavy data processing is required, write the associated functions in F# and put it inside a dll, or reference it. Example here

  • Slowly re-factor your existing code-base in the above fashion.

  • Not all code has to be functional.

  • Get your team to learn the basics of Haskell, LISP over the weekends.

  • Get them to learn F#, by trying to solve Euler Project puzzles (that helped me a lot). Again this should be something done say over the week end, or during work time if you want set a day aside for "training".

Post Made Community Wiki