CS 499 Senior Seminar

GENERAL INFORMATION

This is the website for CS 499 Senior Seminar offered in Fall 2019 and taught by Jeff Kinne. This class will be held MW 10-10:50 in Root Hall A-017.

Office hours are as follows.

• Jeff Kinne - MW noon-3pm, TR 9-11am in Root Hall A-140D.

Click on the links on the left for information about the course.

COURSE ANNOUNCEMENTS

• Here we'll keep notes on announcements for the course.
  Skip to the latest

• August 26
  • Onedrive shared folder - post things there that you are okay with the rest of the class seeing
  • Resumes - let's take a look. See advice at link on left. Get a nice version, have Career Center take a look as well.
  • See links on the top left
  • Project for us to work on? Some that come to mind things that you may not have had much practice with or are "hot" right now - "full stack" (mobile app + web site front end + web site back end + database + cloud), Java, .Net, "data science". Let's start with full stack.
  • Jeff - invite Darby to class.
• August 28
  • For you: revision of your resume, get appointment with Career Center to look at it.
  • For you: try out MIT App Inventor.
  • For Jeff: contact Darby.
• Sept 4
  • All - do an algorithm demo or game in app inventor.
  • All - pick one job to apply to (maybe something you're not really that interested in), and do it.
  • Jeff - contact Darby. Darby is coming Sept 16.
  • Jeff - can we combine app inventor projects into one? Looks like yes, we can use the AI2 Project Merger.
• Sept 16
  • Visit from Career Center, Darby Scism. Slides from today - PDF. Career Readiness Competencies - PDF. Other advice, resources - Career Center.
• Sept 18
  • No meeting this time. Things to do before Monday...
  • Be looking for practice technical interview questions, and send me a link to what you're looking at. I'll compile those for us all to look over.
  • Check out thunkable - it's similar to MIT app inventor but looks like it works on iOS as well.
  • Check out some other cross-platform app framework - from a quick look around I am going to look at React Native, Flutter, PhoneGap (I did use that one a number of years ago and at that time it was okay), and Ionic. I will pick one to try out a bit more to be able to demo on Monday. You all should as well (in particular anyone taking this course for more than 1 credit hour ;)).
  • Go through a tutorial of using gitlab for shared project development, and try out using gitlab.indstate.edu (portal id and password). You can start by putting your resume there.
• Sept 23
  • App framework - React Native (facebook, javascript-based, slightly more mature) or Flutter (google, dart-based)?
  • Thunkable - anyone tried it?
  • Gitlab - coming soon
  • Job updates? Post resumes, cover letters in Onedrive
  • Practice technical interview questions
• Sept 25
  • React - see links page, do the react tutorial
  • Interview questions - post the interview question you had last time to mattermost and also post your correct solution. Post a variation on your question as well
  • Practice easy hackerrank questions on paper - read the question, fully digest what it is asking for, and work out a solution just on paper, and take a few minutes to check your answer on paper. Only after you are pretty sure your solution is correct - then type it in, run it, see if it works. Goal - be able to solve easy problems on paper quickly. Practice basic programming and data structures, and problem types specific to the types of jobs you are applying for.
• Oct 14
  • Tic tac toe react native app
  • Everyone try out the tic tac toe app, make an account and copy it into your account, and try making changes.
• Oct 28
  • See gitlab.indstate.edu for the sorting project we are working on. Readme has your assigned algorithm. Get your algorithm working in javascript and be ready to prove the running time / correctness of your algorithm.
  • To commit your changes...

    	  git add index.js # in your directory
    	  git commit       # and short text for your change, using vim, so i, type message, ESC, :w, :q
    	  git push
    	

    If complains about needing to git pull, then git pull first.
• Nov 4
  • For next time - what is a worst-case example for your algorithm? Can you create it in the code so we can see it run and see how many comparisons?
  • For your algorithm - add in #comparisons, #swaps into your page.
  • Feature requests - see in gitlab.
  • Quicksort - in-place version on the board.
  • Counting sort - some version in html/javascript, UI will be whatever is easiest.
  • Bubblesort - a react version, sortReact.hmtl