2️⃣ The second prototype is a deck-building card game – you fight monsters, in order to kill your opponent. Win battles to gain new cards. If you make it to the end, you get your Git diploma! :D
Da (bei 2️⃣) brauch' ich glaub' eine Spielanleitung, @blinry. Was bedeuten die verschiedenen Zahlen auf den Karten? Was ist das Spielziel, was die Spielmechanik / die Spielregeln?
Und was ist die Verbindung zu Git? Sind Karten Datei-Inhalte und Slots mögliche Dateinamen? Was wenn ich Dateien und Commits auf dem Kommandozeile rechts erstelle?
Sieht vielversprechend aus, aber ich blick noch nicht wirklich durch.
3️⃣ The third prototype is a playground where you can get achievements for doing certain Git operations like "Create a merge conflict". This unlocks new command cards!
Here's the poll! Which of these ideas would you rather see polished and released into the world? (Feel free to answer without trying all of them.)
It would also be super helpful to us if you would tell us why!
We're not super sure who the audience for the final tool is, by the way. But we want to help people to build better intuitions and a deep understanding of how Git works!
@blinry Disclaimer: I haven't used the sites, just going from your toots - so huge grain of salt.
I like the idea of the playground since imho it's a good middle ground between staying close to day-to-day git usage and gamification to force and direct exploration.
The explorer seems too far on the dry side for me (overwhelming people with the graph theory going on in the background) whereas the card game goes too far in the other direction - I'm having trouble seeing the git behind the game.
@blinry As someone who (more or less) knows the ins and outs of Git and who has to sometimes teach Git to others, I think I might use the node explorer already in its current state. I often draw (on paper or whiteboards) what happens in certain Git scenarios when one runs certain commands. With the node explorer, I could just show it instead of having to draw so much.
It might be useful to be able to load existing repositories into it. (I haven't yet tried whether git clone <public URL> works.)
@blinry For autodidactic learning, the node explorer (at least in its current state) provides too little guidance. But it could complement other, already-existing learning materials, by showing what actually goes on at what I'd consider the boundary of what usual repo visualization tools (gitk, https://learngitbranching.js.org, etc.) show and what would be "behind the scenes". A quite interesting place in Git's levels of abstraction, indeed, and one useful for understanding a lot of Git's documentation.
@blinry The achievement playground also seems promising, but at the current state feels kinda repetitive. It's cool though that it doesn't only teach Git but also some other basic command line usage.
The cards in the achievement playground didn't really work for me: They inserted different punctuation to the terminal than shown on the card, e.g. :: instead of >>. (I had my session set up with
loadkeys de_CH-latin1
, so I guess they simulate virtual keypresses without regard of the keymap?)
@blinry Eh, don't worry. That's how Linux systems work by default. Just thought it might be useful to point out, as maybe this could be automated (or completely avoided by having characters rather than keypresses as the input — though then special terminal stuff like ctrl-r for search might not work.)
Add comment