This homework will prepare you for basic setup for the course.
Properly setting up your Slack profile by providing a picture will help the teaching staff learn your name. Upload a current headshot picture of you (not anyone else, not a cartoon picture of you, etc.) to your profile. Besides, make sure you have your first and last name as part of your profile.
Slack team: http://if1007-2018-1.slack.com (you must use you @cin.ufpe.br e-mail)
Sign into GitHub.
- Create a private repo called HW1.
- Go to Settings, Collaborators and Teams, and add the TAs and instructor as a collaborator (using their unity id).
Solve the first four levels in: http://pcottle.github.io/learnGitBranching/
- Introduction Sequence (10%)
- Ramping Up (5%)
- Moving Work Around (5%)
- A Mixed Bag (5%)
For extra credit, complete "Advanced Topics". (5%)
For submission, you only need to demonstrate completing the levels, which can be done taking a screenshot. However, you should keep track of your solutions to help you remember how to solve these types of issues in the future, or recover if your progress gets lost.
Create a local git repository (using git init) in a new directory. Create a "post-commit" file in .git/hooks/. Inside the file, create a command that will open a web page immediately after a commit is performed to that repo.
Some hints:
- http://stackoverflow.com/questions/8967902/why-do-you-need-to-put-bin-bash-at-the-beginning-of-a-script-file
chmodstartfor windows,openfor mac/linux
In your solution, provide the content of "post-commit". Finally, take a screencast (20 points), or a gif recording of the process. See details below.
Here are some guidelines and links for creating good screencasts. It is good to get ready now to learn how to create demo videos for your future project milestones and career.
A general guideline: Do whatever it would do if you were teaching someone how to do something. For example, you don’t have to show people you typing and creating the whole commit, but you might want to show the contents of the hook in a text editor, before doing a commit.
- camtasia
- https://github.com/justinfrankel/licecap (for simple .gif)
- screencastomatic
- Add more recommendations in Slack
- Keep the content simple - A regular software engineer without knowing anything about your tool should be able to follow you
- Mention your name, unity ID and the tool/source code which you will be testing/demoing when you begin
- Use a headset microphone for good quality audio recording.
- Create a script and rehearse that script
- https://wiki.duraspace.org/plugins/viewsource/viewpagesrc.action?pageId=30218666 (also good suggestions for podcasts)
- From http://www.screencast.com/help/tutorial.aspx?id=403
- Practice on screen movements as they can appear jerky when viewing but not as a user.
- Script out complex parts.
- Speak clearly and enunciate, also, have good sound quality.
- Background noise can be distracting.
- From http://diythemes.com/thesis/how-to-create-screencasts/
- Know what you want to present and present it accordingly.
- Organize your thoughts.
- Rehearse such that your casts does not faulter midway.
- Take time to edit your screencast so it does not feel rough around the edges.
http://assets.techsmith.com/Docs/pdf-camtasiaStudio/Create_Engaging_Screencasts.pdf
- Know your audience.
- Know what your goals.
- Write a script.
- Examples of good quality screencasts:
- https://peepcode.com/
- http://railscasts.com/
- http://tekpub.com/blogs/tekpub-free-bin
Submit in our Slack team, http://if1007-2018-1.slack.com, a MD file containing the following:
- Complete moodle and slack profiles by deadline (25).
- Screenshot of completed git tutorial (25).
- Hooks (25)
- Screencast (25)
For your screenshot embed in the markdown file of your LOGIN-HW1.md. Include a link to your screencast video/gif. Include your concept answers in your markdown file.
Due Next Monday, 17:00.