I've managed to fix it -- thanks for pointing it out! In the Substack editor, the code blocks feature (which does preserve spacing) is separate from the teletype formatting option that I was using (which does not preserve spacing).
Apr 15, 2023·edited Apr 15, 2023Liked by Stefan Ciobaca
1.–4. and 9. You're teaching your stuff in an order that doesn't fit the language you're using :) Just re-order when you introduce what. A very refreshing take on that is used in the book https://atypeofprogramming.com/. It may serve as an inspiration. If you ever encounter "white lies" you know that you'll have to think again. For me as a student there's nothing I hate more than that.
Oh and why do you "introduce the λ-Calculus later"? I mean that's the basically the foundation for functional programming, so that should be introduced as early as possible.
I don't see any indentation in the code snippets in this article at all. Has Substack stripped it away?
Seems so. I will try to fix it.
I've managed to fix it -- thanks for pointing it out! In the Substack editor, the code blocks feature (which does preserve spacing) is separate from the teletype formatting option that I was using (which does not preserve spacing).
Thank you! Now section 7 makes a lot more sense. :-)
1.–4. and 9. You're teaching your stuff in an order that doesn't fit the language you're using :) Just re-order when you introduce what. A very refreshing take on that is used in the book https://atypeofprogramming.com/. It may serve as an inspiration. If you ever encounter "white lies" you know that you'll have to think again. For me as a student there's nothing I hate more than that.
Oh and why do you "introduce the λ-Calculus later"? I mean that's the basically the foundation for functional programming, so that should be introduced as early as possible.
Thanks for the tips. So what would an ideal order be?