After typing "git init" in the terminal in the level called "The command line", I then wanted to try my luck so I typed "vim". Now the terminal is stuck. How do I exit vim?
ZZ
Oh My Git: An open source game about learning Git
41–49 of 49 posts
Re: Oh My Git: An open source game about learning Git
#42Earlier quoted context omitted.
Is point 2 serious? Do programmers not read anymore?
If you're going to pitch something as a game, it needs voice. Integration is simple. What's the problem? Are git incantations too powerful to be spoken aloud?
> If you're going to pitch something as a game, it needs voice
No?.. Idk what games you play, but there are an endless mountain of games with no voiceovers. It makes a lot more sense for games that have a lot of text (like this one), because reading is far faster than listening to speech. In general, I vastly prefer text to voice.
Re: Oh My Git: An open source game about learning Git
#43Making games to learn git instead of just making git not an insane mess seems like a pretty obvious cowpath. Bummed we're still trapped here.
Re: Oh My Git: An open source game about learning Git
#44I'm so used to whatever flawed abstractions I have in my head that I fear learning the truth could be detrimental.
Just this morning, I spent over an hour trying to fix things after I made a git mistake. I ended up having to check out a fresh copy and manually reapply my changes.
This sort of thing is why I both fear and hate git.
I'll have to check this game out. My flawed abstractions clearly cause me issues. Maybe it could help.
Re: Oh My Git: An open source game about learning Git
#45Earlier quoted context omitted.
Is point 2 serious? Do programmers not read anymore?
If you're going to pitch something as a game, it needs voice. Integration is simple. What's the problem? Are git incantations too powerful to be spoken aloud?
> If you're going to pitch something as a game, it needs voice.
Why? The majority of the games I have don't include voice.
Re: Oh My Git: An open source game about learning Git
#46Earlier quoted context omitted.
If you're going to pitch something as a game, it needs voice. Integration is simple. What's the problem? Are git incantations too powerful to be spoken aloud?
> If you're going to pitch something as a game, it needs voice No?.. Idk what games you play, but there are an endless mountain of games with no voiceovers. It makes a lot more sense for games that have a lot of text (like this one), because reading is far faster than listening to speech. In general, I vastly prefer text to voice.
Great thing about software, you can turn features on and off.
Re: Oh My Git: An open source game about learning Git
#47This was presented at a conference (maybe FOSDEM?) some years ago. I as impressed, this showed what I had tried to train at work for years with mixed success. Unfortunately there was no .deb or .rpm available at least at the time, that would be acceptable to distribute in Linux shop. So I built one myself. It was not perfectly easy (at least not for a greybeard not used to such game engine stuff), but in the end I go…
As long as the source is available, I always take the provided bins as a convenience versus a default negative attitude.
As long as they look like honest people I let everybody enter my home / borrow my car / access my internet banking / ... versus a default negative attitude?
Re: Oh My Git: An open source game about learning Git
#48Re: Oh My Git: An open source game about learning Git
#49Earlier quoted context omitted.
not if 'never rebase, it is a trick of the devil' is part of the Dogma and adhered to. I'm being a little silly; but a team I worked on moved from P4 -> Git. It was an older develoepr base, so they wrote 1:1 translation wrappers for most P4 commands to git, and forced all developers to use them. Banning Rebase (in private branches, not even main) was one of the requirements to not break the wrappers.
While the idea of writing such wrappers is pretty nice, they still missed out. Rebasing is incredibly useful.
My general consensus on the practice is that it prevents the developers from learning Git. Short-term gain for long-term ignorance. I'm much more a fan of "Learn the tool upfront and reap the benefits", don't handicap the organization from the start.