The software primarily deals with the training process. Registration, training delivery, record keeping, etc. Mostly we do client-side web apps with HTTP APIs. You can see some of the API design in my previous posts on Message-base APIs.
I was brought (back) on to modernize our applications, so I had the good fortune to be able to choose the languages and tools. The existing software was already on .NET and much of my experience is there as well. I had been learning F# on my own time for a while using sites like F# For Fun and Profit. So I felt confident enough that it could do what I needed. And that using the functional paradigm had a shot at being more maintainable than what I was doing before.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Cool. F# looks very interesting to me. What are you building with it and how did you the company start to use are not so wide spread language?
The software primarily deals with the training process. Registration, training delivery, record keeping, etc. Mostly we do client-side web apps with HTTP APIs. You can see some of the API design in my previous posts on Message-base APIs.
I was brought (back) on to modernize our applications, so I had the good fortune to be able to choose the languages and tools. The existing software was already on .NET and much of my experience is there as well. I had been learning F# on my own time for a while using sites like F# For Fun and Profit. So I felt confident enough that it could do what I needed. And that using the functional paradigm had a shot at being more maintainable than what I was doing before.