Some of the books I'll be recommending are based on .NET. Do not be discouraged. We shouldn't strive to stick to a specific technology stack. Your ambitions and goals will evolve over time and that might lead you a completely new space. Moreover, there are lessons to be learned from an environment that's different from what you're used to.
"C# in depth" by Jon Skeet (Book)
"F# for C# developers" by Tao Liu (Book)
F# to C# interop tips by Scott Wlaschin (Gist)
Lost from https://blogs.msdn.microsoft.com/ericgu/2004/01/12/minus-100-points/
When I switched over the C# compiler team, I had hoped that I would be able to give some insight into how the design team works, what decisions we make, etc. Language design is a very esoteric field, and there's not a lot written about it (though “Design and evolution of C++“ is a pretty good read). I had hoped that I would be able to do this with concrete examples, as that makes it much easier.
I've been watching for candidate topics to write about, but haven't yet come up with any good ones. One of the problems is that features have a tendency to morph in design (and in whether they'll make it into Whidbey) as time goes by, and it would be bad for me to say, “we're talking about doing“ and then have us decide it wasn't a good idea. Or, for us to decide that doesn't fit into our schedule, or it would break existing code, or any of the other reasons that might cause us to pull a feature. We're generally not comfortable re
| function contractTest(credit, debit, createAccount) { | |
| it('credit account', () => { | |
| const account = createAccount(0); | |
| const credited = credit(account, 50); | |
| expect(credited.balance).toBe(50); | |
| }) | |
| it('debit account with sufficient funds', () => { | |
| const account = createAccount(50); |