15-112 Agenda 5-June

• Where we are:
  • See semester 15-112 syllabus, you’ve made it incredibly far
  • You’re dealing with real world software engineering problems
    • Lots of code
    • Hard debugging
    • Lack of specificity
    • Design decisions
    • Using old code
  • You all made the coding bar
• Up next?
  • Advanced topics
    • You can make a game, can you make an AI for it?
    • Efficiency and a theoretical framework for it
    • Data structures
    • Advanced ways to organize lots of code
  • Fluency bar
• Quiz2
  • this was the fluency bar
  • Median: 72
• Midterm Friday:
  • Up to and including time based animations
  • In class, no recitation that day
  • Practice, there will be time pressure
    • quiz had 5 mins for SA, 5 mins for ROC, 15 for animatoin
    • same idea but with 5-10 or so extra minutes to use across all the problems
  • Use existing midterms, especially S18
• Before the midterm: Tetris
  • What does collaborative mean?
  • Follow the tutorial (learning goal: see what a good design looks like)
• Poll about Monday vs Friday exams
• Break Saturday + Sunday (no hw)
• Fun coding thing of the day:
  • Terminal
  • Showing hidden files ls -a
  • uptime
  • figlet i love 112
• Attendance Check: https://tinyurl.com/summer112att9
• Content
  • Review of quiz1 T/F answers
  • Tips for working on animation problems
    • Think model first
    • View should just reflect the model, don’t set data in redrawAll
    • Code incrementally: get the drawing part to work first, change stuff in init see it react, then go to contollers
    • Don’t be afraid to refactor / change the model
  • What is timerFired?
  • data.timerDelay = 100
  • Moving a rectangle
  • Bouncing rectangle
  • Wraparound rectangle
  • Pausing
  • Making a stopwatch
  • Smooth wrap around (with two rectangles)
  • A player that always moves
  • Acceleration
  • What is happening in the run function?