CSE 40872 Lecture 001

Introduction

• Name
• Major
• Year
• Favorite Programming Languages

Primary Course Goal

Practice common problem solving techniques and strategies.

• Identify input and output specifications.

• Apply common data structures and algorithms.

• Program correct and efficient solutions quickly.

  • Test programs for correctness.
  • Analyze programs for correctness and efficiency.

Secondary Course Goal

Prepare for local and regional programming competitions and job interviews.

• Apply lessons and skills learned to competitive programming and in technical examinations.

Of course, have fun!

Programming Contests

• Local contest

  • Compete as individuals or in pairs
  • Run by the local ACM Chapter

• Regional contest

  • Field two teams of 3 programmers
  • Probably at University of Michigan

• Both take place sometime in early November

Not required to compete, but highly encouraged

Course Information

• Website:

  http://cse.nd.edu/courses/cse40872/www

• No required textbook

• Grading:

  • Attendance: 10%
  • Participation: 10%
  • Problems solved: 80%

Course Structure

Monday and Wednesday

Short lecture and then practice on problem of the day.

Friday:

Review week's lectures and discuss solutions to problems.

Solutions to week's problems must be submitted by midnight Friday.

Login

• Use any Linux machine, including the cluster machines.
• Can use ssh to remotely login to machines.

Source Code

• Put code in:

  dropbox/<afsid>/problem<XXX>/problem<XXX>.c
  

• Include name, afsid, and description of problem in source file.

• To compile use:

  gcc -o problem<XXX> problem<XXX>.c
  g++ -o problem<XXX> problem<XXX>.cc
  

Input/Output

For this class and in the programming contests, I/O is done using STDIN and STDOUT.

• Put your input text in input.txt

• After compiling your executable run:

  ./problem<XXX> < input.txt > output.txt
  

• The results of your program will be stored in output.txt

Tips

• Consider the use of bzr, git, hg, for code versioning and syncing.

• Understand the input and output formats:

  • Write the input tests.
  • Work out the problem by hand.

• Bring and use references.

More Tips

• Develop incrementally, compile and test often.

  • Write down pseudocode in comments first.
  • Separate tasks into functions.

• Avoid copying and pasting, repeating yourself.

  • Macros are not evil.
  • Separate tasks into functions.