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

Feedback from Sept 12 at CSU #1

Open
moorepants opened this issue Sep 13, 2014 · 1 comment

Comments

@moorepants
Copy link
Owner

@moorepants moorepants commented Sep 13, 2014

  • Most everyone seemed to enjoy it.
  • About 30 people showed up.
  • Most were undergrads EE students, a few ME undergrads, and a couple of grad students.
  • Only one student had used version control before: subversion from tortoisesvn.
  • One table was very quick with Git and some of the first to finish, so I likely need some way to keep the faster learners from being bored.
  • People were mostly tuckered out after two hours, 5-8 left before we closed it.
  • The fact that vim is the default editor in the Window's Git Bash is not helpful. If you do git commit my_file it opens vim by default instead of their preferred text editor. I should have only showed the git commit my_file.txt -m "message" format to avoid that. But when I showed them the basic vim commands they seemed to be fine with that and would edit with vim, even those it is notorious for being a turn off to new people. I should find out how to change that editor. Why isn't nano installed with Git bash? Here is a solution for setting up Notepad++ with Git: http://stackoverflow.com/questions/10564/how-can-i-set-up-an-editor-to-work-with-git-on-windows
  • People got confused because my applications on Ubuntu were not the same as there's. I need to make sure to use gedit all the time and not vim if that is what they are expected to do.
  • People thought gedit was some command related to git or something. They didn't realize that was how I was opening my gui text editor on Ubuntu called gedit.
  • Many students wanted a copy of what I show to refer to later, which I didn't prepare. I should have that material with the commands available so they can review after the event.
  • Copying and pasting from the Window's Git bash is annoying but doable. You have to right click on the top bar of the window to get the mark, copy, paste screen.
  • I sorely needed helpers that knew what was going on so I didn't have to walk around. When I stopped teaching, the students that were ahead were bored.
  • It took about two hours to talk some about open source, teach the basics or git, show github, and make a pull request with their neighbor. I thought I would have gotten to Python, but that was too optimistic. This was the first time I'd taught Git to people that hadn't used anything like it before.
  • I didn't explain the command line at all, we just started typing commands. It is very unclear to people what the difference of the main command, the secondary command, the optional flags, and the main arguments. A basic explanation of command line standards is needed.
  • I forgot to have them run the git configure commands with their email and username, so git balks the first time they try to commit. We should also have them configure the editor properly for their system.
@moorepants

This comment has been minimized.

Copy link
Owner Author

@moorepants moorepants commented Sep 23, 2014

Looks like SWC has a windows installer that helps deal with some of the windows issues:

https://github.com/swcarpentry/windows-installer/releases/tag/v0.1

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
1 participant
You can’t perform that action at this time.