Improvements to the lesson material

[ashwinvis]

Syntax

https://enccs.github.io/julia-intro/syntax-intro/

• Composability: use the using DifferentialEquations: ODE... instead of plain using DifferentialEquations. So it is clear that we compose functions from packages.
• Add comparison to Python or Matlab code in the beginning.
• Expand "Functions can be combined by composition" example. Reason: f(g(3)) is not remarkable, since it looks like it is calling two plain functions. but perhaps if you add a step h(x) = f(g(x)) it could be?
• Add the term multiple dispatch around Additional methods . However it was not clear to me why f(x::Int64, y::Int64). should allow a floating point input with f(3.0, 4.0).
• In Working with files, can we use something other than f so we don't give an impression that it is a function? Also add the term do-block.
• After showing throw, show an example of Stacktrace. And explain how to read it. It looks very different from Python's Tracebacks.
• Style conventions: change upper camel case with Pascal case? camelCase and PascalCase.

[ashwinvis]

General

• Instructor guide: configure colors in Juliia REPL or ensure a color theme in terminal. The yellow below is hardly legible:

[ashwinvis]

Special features of Julia

https://enccs.github.io/julia-intro/overview/

• Emphasize in text why redefining struct Point2D is "dangerous, since we shadow and override the older definintion". And how outer constructor.
• In https://enccs.github.io/julia-intro/overview/#type-stability, explain who to read @code_warntype output. Also run the macro with relu_unstable. Show Why did relu_unstable(1) did not warn but relu_unstable(1.1) did.
• Same goes for other macros like @code_lowered and @code_typed. You can use solution blocks with drop-down to explain outputs.
• Perhaps a simpler example for a macro than using _make_wilkinson? Very hard to digest what is going with :(...), $pol, $name and Symbol suddenly appearing. What is pol anyway... ah it is polynomial. Or explain that function with comments. Would it have been better to use _make_wilkinson(n, x) to start with and to specialize the function based on argument, rather than parsing from name = Symbol(:wilkinson_, n), which it seems to be trying to do. Anyways, perhaps a better example is needed.
• Also I was unsure what the macro block does, since it calls the function unchanged.

macro make_wilkinson(n)
  return _make_wilkinson(n)
end

• [ ]

[ashwinvis]

Developing in Julia

https://enccs.github.io/julia-intro/development/#environments

• Describe the need for using Revise by adding a new function to Points.jl?
• Here we say using https://enccs.github.io/julia-intro/development/#environments is a good idea. Should we add that to our own setup, in Julia HPDA / HPC?
• Example usage of PkgTemplates, such that you do not have to pre-configure Git username etc.

Ecosystem

https://enccs.github.io/julia-intro/scientific-computing/#

• Add Clima, JuliaGPU etc which are relevant but missing.

[ashwinvis]

Also was the term "homoiconic" ever explained?