4 ms·

My current quest is to take something from the business domain I work in and implement the bizarre math stuff (which I don't get all of) in a backend in F# with

My current quest is to take something from the business domain I work in and implement the bizarre math stuff (which I don't get all of) in a backend in F# with a frontend in Javascript (I'm fluent in neither). I've tried it before (with different technologies), and although it didn't make me an expert in either field, I've found it neatly ties most things together. Oh, and it's usually fun, especially if you put somewhat bizarre obstacles in your way (remember, it's a learning experience, not production code). It could be something elaborate like http://www.xpteam.com/jeff/writings/objectcalisthenics.rtf http://www.xpteam.com/jeff/writings/objectcalisthenics.rtf or just a concious decision to implement a part of the design in a part of the system where it isn't most obviously at home.

jfarmer 12y ago
If your goal is to learn those two languages, I'd instead pick a problem/domain you understand very well and then express the various aspects of that problem in both F# and JavaScript rather than implementing some aspects in F# and some aspects in JavaScript. This will help you develop a better sense of how F# and JavaScript differ as languages, what ideas are natural in one but unnatural in another, the conventions and idioms around tackling certain problems, and so on.
- dblarons 12y ago
  I once worked with an engineer who implemented the card game hearts in every language he learned. After the first implementation, you don't have to spend so much time thinking about the problem domain and can focus on finding the most idiomatic solution in the new language. The other benefit is that the project always has a clear endpoint.