When selecting the chapters for this book, I was lucky enough to get content from people who are successfully using F# to build a really interesting set of applications and systems. So, I have no doubt that you can now see the benefits of F# for your work and that you can think of projects or components where F# would be a great fit. Unfortunately, the world isn’t that simple, and many other factors contribute to the choice of technology, especially in large companies.
In this last part of the book, we look at topics that can help you introduce F# into large and more complex ecosystems. In chapter 11, Chris Ballard talks about F# in the enterprise. You’ll see how to use F# in an enterprise-friendly way; the key takeaway is that your F# projects need to smoothly interoperate, even if that means you occasionally have to resort to using mutable types or do additional work to make the interoperability hassle-free.
In chapter 12, Phil Trelford looks at software quality. The chapter starts from a bigger picture: “What is software quality about?” After answering that question, it covers a wide range of libraries and techniques that you can use to create tests in F#. Tests are often treated as second-class citizens in the codebase, so writing them in F# is a risk-free way of introducing F# into larger organizations. And as you’ll see in Phil’s chapter, testing can be fun!