I want to start a tutorial series for Gwion, accessible to beginners.
For those who don't know Gwion, it is an interpreted programming language, strongly typed, running on a stack VM and with a very strong relation to time, as its main use is sound/music generation.
Right now, I think it should start like:
- Set things up: installing the language and libraries needed
- Sequential programming: Just set up a sequence of instruction
- Use functions: Put instructions in a function and use it instead. Leverage this post to demonstrate function overloading
- Use your Own classes: Use a class instead of a function and demonstrate inheritance.
Later on will come templating for functions and classes, lambdas, functions pointers...
Does it seem correct for you?
If not, how would you order things?
Any advice will be greatly appreciated.
Top comments (3)
Yes, there is something missing.
You should start with: Who should learn this and why?
If you are doing this project, you probably want to help a specific subset of people to do something right?
You are asking them to make an effort to learn Gwion, you have to explain first what kind of positive changes it could bring to their lives if they do the effort of learning it.
You make some point.
But maybe I should point to some (non-existing now)
MOTIVATION.mdor similar?Thanks for your comment, I'll probably delay publishing this series until I have an answer for this, but it'll anyway make the project better.
Well yes and no. You need a motivation part, but it should be the first thing people see on your website.