So far I've tried to lay out why I think Monte Carlo methods are important and useful, and a few use cases for them. It's time to start talking about Ancho's design and features.
There are three areas I feel that I need to cover. If I covered all of these together, the post would be huge, so I'm going to break them up.
- What other tools are out there, and why are they insufficient? We'll look at a few other software systems that you might use if you had a problem that you wanted to use Monte Carlo methods on.
- What is the overall design of the system, and why? I'll start with a very general, high-level discussion of the design. Then we'll lay out a few defined terms, and wind up by identifying some of the specific underlying technologies I plan to use.
- What features will Ancho eventually have, and which ones will be worked on first? Any project roadmap is out of date the moment it's written, but Yogi Berra said, "If you don't know where you're going, you might not get there."
I started to write this article over last weekend, and what I discovered is that it's genuinely hard to write a detailed technical article for an audience that is partially non-technical, and doesn't know a lot of the terms.