Appendix B. F# in my organization
One of the most common difficulties that developers have after they’ve tasted F# is adopting it into their real-world, day-to-day
jobs. I see this difficulty play out in three ways:
- Making the leap from writing scripts and console applications into integrating with the full .NET stack—things such as interoperability
between C# and F#, working with NuGet, and using frameworks such as the ASP .NET Web API.
- Convincing others of the value of using F#, and ultimately getting permission from colleagues or management to give F# a go.
- Understanding how to start using F# in a practical way in an existing tech stack. What areas are safe bets to start using F# that will show its strengths? How should you start applying ...