Tools of the Trade: Weekly Activities

Go up to the main README file

Weekly videos, readings, and activities: (Jump to end of page)

Week 1: Course Introduction, Resume, LinkedIn

• Watch the following video presentation on the course YouTube channel
  • Week 1: Course Introduction
  • Week 1: LinkedIn (parts 1 and 2)
  • Week 1: Resume Workshop
• Activities: do the following things afterwards:
  • Read some tips on creating a good CV here: pages 18-19 and 20-27 of 2019-2020 Hoos Guide for helpful information to aid in the making of a CV.
  • Create or edit an existing basic one page CV and submit it on Collab.
  • Create a basic LinkedIn profile and then put your name, ID, and a link to it into this Google doc
  • More details about these activities found in the videos.
• Submission deadline: Friday, Sept. 4, 5pm. Use Assignment Submission link on main page and select Week 1 CV assignment.
• Further reading or activities (optional):
  • Check out links to career services: UVA, UVA engineering and computing or UVA Wise.
  • Set up an appointment to talk to review your resume or LinkedIn profile. (You can do this anytime during the term, and it will count as a Professional Development activity for the course. Might be better to do it later when you have more to put on your resume?)

Week 2: IDEs and Version Control

• Watch the following video presentation on the course YouTube channel
  • Week 2: Introduction to IDEs
  • Week 2: Source Control Management
• Activities: do the following things afterwards:
  • Download buggyfizzbuzz.py/buggyfizzbuzz.cpp/buggyfizzbuzz.java based on your language preference.
  • Debug the code and fill in data when stepping through the program using the instructions in the code file.
  • Refactor a variable to have a better name that fits it’s usage (i.e. from x to id) and use Extra Method.
  • Rename the file to fizzbuzz.py/cpp/java
  • Build and run the fizzbuzz.py/cpp/java file and submit a screenshot of your program’s output to Collab.
  • Submit the code files fizzbuzz.py/cpp/java and the screenshot to Collab.
  • Go on to Github.com and sign up for an account, and then go to https://education.github.com/pack to register for your Github Education Student Pack. (Please do this, but there is nothing to submit for the GitHub activities this week.)
  • More details about these activities are found in the videos.
• Submission deadline: Friday, Sept. 11, 5pm. Go to Collab->Assignments and select IDE Week 2 Assignment.
• Resources mentioned in the slides
  • VS Code installation video for Windows and Mac (If you do not yet use the command-line on your Mac, it’s fine if you don’t understand the parts of the video that talk about the command-line and only need to watch up to 2:35)
  • For more on finding, installing, and managing extensions see Extensions
  • For more extensions, you could look at this document More Extensions
  • For Java, you need to have installed a Java Development Kit (a JDK) along with the VS Code extension. If you don’t have a JDK installed, get OpenJDK from https://adoptopenjdk.net (It’s fine to use the default choices for Java version 11 and for the JVM).
  • For C++, this tutorial should be helpful C++
  • For Demo code, download product.py

Week 3: GitHub

• For this week’s lesson, view it on our YouTube

• For demo video, view it on our YouTube

• Open a new folder in VSCode.

• Create a new file in that folder called “index.html”. You can do this by going into your file explorer and creating a new file.

  • If you have a mac, you can create a file called index.html by typing in the terminal.
    touch index.html

• Open index.html and paste in this code

• Look at index.html and make sure that it produces the same output.
  open index.html

• Create a new repository in GitHub.

• In your VSCode Terminal, put in the following code:
  git init
git add .
git commit -m "Initial commit"

• On GitHub, copy the code from the second option “…or push an existing repository from the command line” and paste it in your terminal.
  git remote add origin https://github.com/GITHUB_USERNAME/REPO_NAME.git
git branch -M master
git push -u origin master
  

• Go to the Settings and scroll down to GitHub Pages.

• Click source and select “master” from the dropdown. You should see a blue box that says it’s ready to be published.

• Wait approximately 5 minutes and refresh. When that blue box changes to green, click the hyperlink and your page will be available for viewing from any device!

• Turn the link in the green box into the “Week 3: GitHub” assignment on Collab for this week’s grade

• Resources for learning more about Web Development

  • FreeCodeCamp
  • Codecademy

• GitHub Portfolio Templates

  • developerFolio
  • Portfolio Demo

Week 4: Bash + CLI

• Here is the lesson and activity demo for the week!

1. Launching Terminal
   • If you have a Windows,
     • install Git, using all the default settings.
     • launch the “Git Bash” program either by clicking on the “Launch Git Bash” checkbox at the last stage of Git installation or by clicking on your Windows icon and typing in “Git Bash” and clicking on the result
   • If you have a Mac,
     • Hit CMD+Space and enter “terminal” and hit Enter
2. Type the following into the Git Bash command line: ssh bandit0@bandit.labs.overthewire.org -p 2220
3. Type in “Yes”, then hit Enter
4. Enter the password: bandit0
5. You are now playing the Bandit wargame!
   • Have fun and try to get as far as you can
   • Once you feel you’ve done enough (totally up to you), turn in the level name that you got up to (e.g. Level 5 -> Level 6) and the latest password you captured

Week 5: Build Automation and Build Tools

• Watch the videos on the course YouTube channel
  • Week 5: Intro. to Build Automation
  • Then choose at least 1 of these 3 other Week 5 videos: Python Demo; C++ Build Tool CMake; Gradle and Java
  • As explained in the Intro video, from the 3 choices, pick the language that you want to use for your activities!
  • Note that some of the videos have links etc in the comments just below the video to help you with installation etc.
• Activities: do the following things afterwards. (You could do the first two before or while watching the demo video.)
  • Install the build tool you’ve chosen to work with, if you need to.
    • Note: If using Gradle on Windows, some users have found they need to set the environment variable GRADLE_HOME to the directory where Gradle is installed, and also set JAVA_HOME to the directory where their JDK is installed.
  • Clone the GitHub repo https://github.com/hortonuva/tools-course-build-code with the project files and make sure you can repeat the demo done in the video, by building and running the demo project.
  • Next, create a new project using the build tool and language of your choice that meets the specification for the “Wahoovian Matrix Transformation” program, described here. Use what you’ve learned about Git and GitHub with this new project, and put your project files in a public repo in your own GitHub account. (Need help or reminders about this? Please just ask us for help!)
  • More details about these activities found in the videos.
• Submission deadline: Saturday, Oct. 3, 5pm.
  • Use Assignment Submission link on main page and select Week 5 assignment.
  • All you will need to submit will be the URL of your GitHub repo with your files for the Wahoovian Matrix Transformation project.
• Further reading or activities (optional):
  • If you know one of the other languages, watch the video and do the demo for a 2nd language.
  • Find a tutorial or the documentation for the build-tool and learn some additional features.
  • Think about some other functionality you think would be helpful that might be supported by a 3rd party library. Use a web search to look for libraries that support that for your choice of language. Find some demo code for that library that you can try out, and use your build tool to incorporate that library into a project with that demo code.
  • Take an assignment from a previous course or a current course, and set up that assignment to use a build tool (and maybe Git also).
  • Loggers really are important in realistic large SW systems, so you could read more on how the logger for your language is used.
    • If you choose Java, find a tutorial on log4j 2 that explains how to use a Java property file to control how the logger works.

Week 6: Testing

• Watch the videos on the course YouTube channel
  • CS1501 Week 6: Testing
  • Then choose at least 1 of these 3 other Week 6 videos:
    • Week 6: Testing with Python (Disclaimer: pyunit and unittest are spoken interchangeably in the video – these are two well-known libraries that accomplish testing, but are not the same thing. Sorry for any confusion!) GitHub
    • Week 6: Using Catch2 to do demo testing on C++ code
    • Week 6: JUnit Demo
  • The activity’s class is written in python, but the answers can be answered in pseudocode. Reference the example test case in the activity document for more info!
  • Note that some of the videos have links etc in the comments just below the video to help you with installation etc.
• Activities: do the following things afterwards.
  • Pull up the Activity Google Doc using this link: Week 6 Activity: Testing
  • Make a copy of the Week 6 Activity Google Doc (File -> Make a Copy) and locate it in your own Google Drive
  • Write in your answers to the questions provided on the doc
  • After answering all the questions, download the file as a PDF (File -> Download -> PDF Document (pdf)
  • Rename the pdf file to “< First Name >_< Last Name >_week6activity.pdf
  • Submit to Collab in the Assignments tab by the deadline.
• Submission deadline: Friday, Oct. 9, 11:59pm.
  • Collaboration in groups is encouraged but not required! Use the Discord server (link in Piazza) to set up teams.
  • Use Assignment Submission link on Collab and select the Week 6 assignment.
  • All you will need to submit will be the the Week 6 Assignment file in PDF Format.
• Further reading or activities (optional):
  • If you know one or more of the other languages, watch the video(s).
  • Make your own class on VSCode and try the tests yourself! Or even better, try to implement tests on existing project you’re working on! (Installation required)
  • Utilize what you learned in Week 5: Build Tools, and look up how to perform testing using build tools!
  • Find a tutorial or the documentation for a software test and learn some additional features.

Week 7: Data

• Update on 10/23: We have several technical problems with Week 7’s production that due to circumstances were hard to fix quickly. The info below has a link to a re-recording of the video, and a new link to the Google Colab file that since the original link was not accessible to everyone. See the announcements on Piazza and Discord about a revised due-date.
• For this week, we will only be using Python. If you are unfamiliar with the syntax, please view this video. The necessary parts of the video are marked with an * in the description.
• Please watch the newly re-recorded version of Introduction to Jupyter Notebooks and Data. Original copy (which was low-res) is still there but try the new one first.
• Here is the weekly assignment on Google Colab. Use this link if that one doesn’t work!
  • Data needed Pokemon data
  • If you would like to use Juptyer for this assignment, please save this notebook of Google Colab in a .ipynb format.
  • The instructions as well as reference documents are found in the template notebook.

Week 8: Industry Representatives Talk about Internships

• Week 8 activities and the assignment are described here.
• You’ll watch some recorded videos of interviews and write a short report.
• Submit a PDF of your report to Assignments on Collab. The due date is Friday, Oct. 23 at 5:00 pm.

Week 9: Industry Lingo

• Watch the videos on the course YouTube channel
  • CS1501 Week 9: Agile and Scrum
  • The weekly activity is geared toward a high level understanding of the tech industry lingo, so there will be no Demo Videos to watch for Week 9.
• Activities: do the following tasks afterwards.
  • Pull up the Activity Google Doc using this link: Week 9 Activity - Industry Lingo
  • Make a copy of the Week 9 Activity Google Doc (File -> Make a Copy) and locate it in your own Google Drive
  • Write in your answers to the questions provided on the doc
  • After answering all the questions, download the file as a PDF (File -> Download -> PDF Document (pdf)
  • Rename the pdf file to “< First Name >_< Last Name >_week9activity.pdf
  • Submit to Collab in the Assignments tab by the deadline.
• Submission deadline: Friday, Oct. 30, 11:59pm.
  • Collaboration in groups is encouraged but not required! Use the Discord server (link in Piazza) to set up teams.
  • If you are collaborating with others, write their name and Computing ID on the sheet, and EACH MEMBER OF THE GROUP must submit their completed document!
  • Use Assignment Submission link on Collab and select the Week 9 assignment.
  • All you will need to submit will be the the Week 9 Assignment file in PDF Format.
• Further reading or activities (optional):
  • The official Agile Manifesto
  • Read further on the values and principles of the Agile Manifesto

Week 10: CI/CD

• Check out the slides on Continuous Integration/Continuous Development.
• Watch the video on our course YouTube channel.
• Complete this assignment and submit it through Collab!

Week 11: Databases

• Watch the videos on the course YouTube channel
  • CS1501 Week 11: Databases
  • CS1501 Week 11: Database Demo
• Activities: do the following tasks afterwards.
  • Pull up the Activity Google Doc using this link: Week 11 Activity - Databases
  • Make a copy of the Week 11 Activity Google Doc (File -> Make a Copy) and locate it in your own Google Drive
  • Write in your answers to the questions provided on the doc
  • You will need to open up this SQL Fiddle Link in your browser to complete the assignment
  • After answering all the questions, download the file as a PDF (File -> Download -> PDF Document (pdf)
  • Rename the pdf file to “< First Name >_< Last Name >_week11activity.pdf
  • Submit to Collab in the Assignments tab by the deadline.
• Submission deadline: Saturday, Nov. 14, 11:59pm.
  • Collaboration in groups is encouraged but not required! Use the Discord server (link in Piazza) to set up teams.
  • If you are collaborating with others, add their name and Computing ID on the sheet, and EACH MEMBER OF THE GROUP must submit their completed document!
  • Use Assignment Submission link on Collab and select the Week 11 assignment.
  • All you will need to submit will be the the Week 11 Assignment file in PDF Format.
• Further reading or activities (optional):
  • More in depth SQL Tutorial

Week 12: Final Project & Professional Development

• There will be no new lecture content for this week. This a good time to brush up on previous lectures on the course YouTube channel
• Activities:
  • There will be TWO parts to this assignment: LinkedIn Update and Github Pull Request
  • Part 1: Update your LinkedIn account profile using the following checklist below
    • Update your Experience section with up to date information and include 2 bullet points for each position describing your role.
    • Add Relevent Coursework to your profile
    • Add to your Skills section with all of the programming languages and software you have used in the course
    • Make sure you have a comprehensive About section
    • Upload your resume onto your LinkedIn Account profile (note: make sure not to include any personal information on your uploaded resume that you would not feel comfortable releasing to the public)
  • Part 2: Make a Github Pull Request to the following Repository
    • Follow the instructions written in the Readme.md file in the Github repo to complete the acitvity.
    • TA Madi will be holding a Git-based Office Hours sometime this week for those of you who need additional assistance in Git setup.
• Submission deadline: Friday, Nov. 20, 11:59pm.
  • To submit Part 1 of the assignment, use the Assignment Submission link on Collab and select the Week 12 assignment.
    • You will need to copy and paste your LinkedIn Profile link into the text submission box with the items mentioned above.
  • To submit Part 2 of the assignment, the Readme.md file in the Github repo will have instructions on how to submit your pull request.
  • Both Parts must be completed to recieve a passing grade for this assignment
• Announcements:
  • Remember, this is your last assignment for this class. Make sure you have successfully completed enough assignments to pass.
  • The deadline to make requests for assignment extentions and regrades is Friday, Nov. 20, 11:59pm to provide the staff ample time to handle the request