Integrate content from "Julia for ML"

[gdalle]

@adrhill nicely offered to contribute some of the content he's written for his ML class

https://github.com/adrhill/julia-ml-course

Let's try and see if the structures are compatible!

There are two main lectures of interest:

• https://adrhill.github.io/julia-ml-course/workflows/
• https://adrhill.github.io/julia-ml-course/profiling_debugging/

[jacobusmmsmit]

I like the debugging part! I think we shouldn't base our section too heavily on it as they weren't written for the same audience. For example, I would want ours to be slightly longer text-wise and also include "Tim's global ref trick" from the discourse post.

[jacobusmmsmit]

Oh, and we should definitely talk about semver.

[adrhill]

I like the debugging part!

The section on debugging is heavily based on @Wikunia s awesome blog post "Debugging in Julia - Two different ways"!

I would be glad to contribute!

[gdalle]

I like the debugging part!

And logging too!

Oh, and we should definitely talk about semver.

Yup, especially the quirks like how Julia handles v0.x.y differently than standard semver

[gdalle]

On the more practical aspect, I would like it if our blog posts were maintainable with minimum effort as Julia and package versions go by. This is made easy by Franklin's code running utilities, but it gets more tedious the more screenshots and schematics we add. What do you think?

[adrhill]

I generally agree, but for some interactive tools, screenshots will be hard to avoid (see e.g. the Cthulhu readme).
This depends on whether the goal of this guide is to demonstrate workflows or to point out useful tools.

[gdalle]

I wonder if there is a way to pre-specify the answers to an interactive REPL multiple-choice form like Cthulhu's

[jacobusmmsmit]

@adrhill Do you want to officially take the "debugging" section from me from the Projects tab or would you prefer if I wrote it at first?

[adrhill]

I would be happy to try my hand at it!

Maybe we can find a shorter example to demonstrate the debugger on?

[jacobusmmsmit]

In my head, the debugging section follows the natural progression of sophistication of debugging techniques, where related, but more difficult problems to debug are presented and solved using the next technique in the progression, with the most widely recommendable technique explored in slightly more detail to show how the other problems could be solved using it.

An abstract example is:
We have problem A, which we can solve naively with technique 1.

code or screenshot

But often, we run into related problem B, which technique 1 cannot solve effectively due to XYZ, so instead we use can use technique 2.

code or screenshot

Finally, in a more complex case, may have related problem C, which you can use technique 3 to solve:

example showing how to use technique 3

However, you may not know if you have problem A, B or even problem C, and so a sophisticated technique, technique 3, can be used to better understand the problem in question and identify the solution as such:

example showing how technique 3 fits into the Standard Julia Workflow™ with a relatively complex example

As a println/@show enjoyer, nothing immediately comes to mind about what the examples should be, but I haven't really thought about it yet. Maybe some come to you :)

[gdalle]

See #14