nix.dev
                                
                                
                                
                                    nix.dev copied to clipboard
                            
                            
                            
                        Do you know about `Teaching Tech Together` book?
(Since discussions are not enabled on this repo, here is an issue, move it appropriately if needed)
I recently came across this incredible resource on how to build a tech course that sticks:
Teaching Tech Together http://teachtogether.tech/en/ (online version)
It talks about a lot of interesting topics around teaching & learning, like:
- how we learn, what happens, how
 - the value of concept map & mental models
 - how to design a lesson, what's important, how to present it bit by bit, ...
 - how to design exercises / examples
 - building a "community of practice" (not just people that learn & forget)
 - and a lot of other things...
 
As you're all putting lots of thoughts on Nix documentation at large, I was wondering if you knew this book, which could be of great guidance in structuring the various tutorials, the book, and other teaching/learning resources, ...
Have a good day/night/... :)
@bew thanks a lot, this does indeed look very valuable. I'm basing my work on How Learning Works (2010), which seems to have a lot of overlap, but Teaching Tech Together is pleasantly focused on tech.
After listening and talking to @ners (a lot...) I am convinced that the Haskell and Nix have very similar issues with onboarding and learning. Here is a Haskell book that I was made aware of today, which has an exemplary outline (or roadmap), and a notable background story of two co-authors, one of which comes from tech and the other from the humanities.
In #265 I propose a similar outline for what nix.dev should eventually become: The Nix Book.
I would go even further now: Let us build an authoritative Nix curriculum that instructors and autodidacts can orient around. It should be driven by the tenets behind Software Carpentry, which I would summarize from Software Carpentry - Lessons Learned as "teaching is hard, let's not waste effort, and instead get together to curate an evidence-based single source of truth on each subject".
Related: #310
I would go even further now: Let us build an authoritative Nix curriculum that instructors and autodidacts can orient around.
Nix autodidact here. I feel my learning has stalled given the amount of time I have to use for nix these days.
I would love designed curricula to use for myself and teach others in my organization.