Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Questions & Feedback 👏 #15

Open
reanimatedmanx opened this issue Sep 5, 2022 · 0 comments
Open

Questions & Feedback 👏 #15

reanimatedmanx opened this issue Sep 5, 2022 · 0 comments

Comments

@reanimatedmanx
Copy link

reanimatedmanx commented Sep 5, 2022

First of all, thank you for doing this, it's yet another amazing piece of work from you and it has an exceptional potential.

Related to git section mostly.

Questions:

  1. Scrolling through git images for example, I had a feeling that I just can't categorize where will this fit into the age range?
  2. Who is this targeted to?

Pardon me if this is indicated in description and I missed it up. 🙏🏼

Feedback:

Obviously it's too complex for kids prior to 10 I guess, I wouldn't be capable of grasping even 10% of this in my early ages.

I do not want to sound harsh but on this example.

https://github.com/girliemac/a-picture-is-worth-a-1000-words/tree/main/git-purr

It's a bit confusing to add aliases as git purr or git puss maybe kids are learning faster, I don't know :)

Also it attempts to explain git pull with this friendly cat images, but it doesn't explain the prerequisites first.

  1. What is git.
  2. What is a repository in git, what is local/remote(origin) repository.
  3. What is a commit (like a small change on the cat)
  4. What is a branch in git's context.

etc.

If this is targeted for mostly adults, then I would say that for me for example it's a bit confusing.

However...the potential is huge if targeting and "refactoring" your work for a younger audience, schools, or special classes.

For that I would suggest to go a bit more on explaining this "quirky" words that accompanies a git command.

I think you should pair with somebody (not me) or ask for massive feedback and improvements on this. Or just incremental refactoring might work with feedback from community. After that try to make this & publish as an ebook. Probably pair with a digital artist as well so it wouldn't have this borders or polish it to the level of the ai section.

Anyways enough of me nitpicking! Great job! 🖖🏼

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant