dr-neptune
Joined 4 years ago
Joined 4 years ago
Quantitative Finance. I have a math background and relish the chance to explore some applications of probability theory. Most of my readings have been about options pricing since there is a lot of mathematics to explore there
My second recent passion is synthesizer. I got a hardware semi-modular synth last year and I've had a ton of fun patching with real wires, twisting knobs and tinkering with loops. As a bonus, it feels like programming but I'm able to be away from the screen while doing it
The rest of the blog has a bunch of inspiring content for the aspiring Racketeer that isn't catering to students or programming language theory researchers
Over time you will find yourself dredging up all kinds of ideas without meaning to (while doing other things) and before you know it you will have a long list that can then be prioritized and explored
https://github.com/google/python-fire
Gooey can do (CLI -> GUI):
The book starts from axiomatic arithmetic and works all the way up to what you would need as a mathematics major with a focus on pure mathematics. He also manages to touch some beautiful areas like geometry, abstract algebra, symmetry, linear algebra, set theory and more.
There are only a handful of exercises at the end of each section and they are very good at locking in the concepts. I finished a mathematics degree and realized afterwards that there just wasn't enough of a focus on the concepts and beauty. Even with 4 years of math experience, this book still managed to open my eyes
> The target ability:
> 1. To understand the theory behind the algorithms
> 2. To implement an algorithm on a dataset of choice. (Data cleaning and management should also be learned)
> 3. Read research publications and try to implement them.
There are many different ways that people do ML/DL research these days. Some people do more theory-work which will necessarily be more focused on mathematics, and others do more of an applied approach which will be more focused on coding and iterating.
For theory-driven work, I think Michael I Jordans list is still pretty solid:
> https://news.ycombinator.com/item?id=1055389
I would focus on the fundamentals first though:
1. get a solid background in mathematics
- analysis (a suggestion is Baby Rudin)
- probability (Grimmet and Stirzaker, maybe something with measure theory after)
- statistics (Casella and Berger or Wasserman's book is a good start)
2. get a solid foundation in statistical machine learning - Introduction to Statistical Learning is a fantastic start
- Then choose 1 or both of the following:
- Elements of Statistical Learning for a Frequentist Approach
- Pattern Recognition & Machine Learning for a Bayesian Approach
3. get a baseline understanding of deep learning - the deep learning book by Goodfellow is decent
- start reading papers here and trying to implement them
If you get through to this last step, you are probably solid enough to get a job building models. If that's the route you want, then begin iterating on learning about new approaches in papers (look for papers with code / data) and implementing them.If you want to go the academic route, you have enough of a view of the field to begin specializing further. Choose a sub-domain and dig deep if you want to do more deep learning work. Maybe revisit Michael I Jordan's list if you're still confused about where to go. A lot of those books will feel a lot more familiar.
Best of luck!
It's even nicer for some sites like Wikipedia because it goes directly to the page if theres an exact match instead of the intermediate search results page
- grammarly (mostly excellent, I ignore some suggestions)
- reading books more with stylistic elements that push the boundaries of what you're used to. I write technical blogs, but I've found some inspiration reading very different writing. Some examples are Thomas Pynchon, James Joyce, Greg Egan
- setting up constraints. Can you explain this in less sentences without making a long run-on sentence? How concise can you make this whole post? On the flipside, can you avoid all the most common adjectives when describing something? If you take a tokenized word count on your work, what words do you rely on? Can you delete them?