Held: Tuesday, 2 September 2014

Back to Outline 02 - An Introduction to ADT Design. On to Outline 04 - An Overview of Java.

Summary

We begin to explore the program development tools that we will be using in this course, and that I hope you will continue to use in your future work.

Related Pages

• Reading: An Introduction to Version Control with Git
• Reading: The Eclipse Integrated Development Environment
• Lab: Eclipse
• Lab: Command-Line Git
• EBoard 3 (Source 3) (HTML 3)

Overview

• Tools for software development.
• Eclipse.
• Git.

Administrivia

• Thursday at 11 am, I will hold a review session. It's an opportunity for you to ask anything (primarily about this class, but if there aren't questions about this class, I'll answer other CS questions).
• Sorry about the bad link on my home page. It should be fixed now.
• My office hours are now posted on the course Web. MThF 1:45-3:15, plus walking hours from 1:15-1:45. There's also a signup sheet outside my office.

Upcoming Work

• HW3 to be distributed on Wednesday.
• Daily lab writeup: http://bit.ly/207writeup
• Readings for Wednesday:
  • Basics of Object-Oriented Problem Solving
  • An Introduction to Java
  • Simple Java for C Programmers

Extra Credit Opportunities

• Note: Please send a short (one paragraph) reflection on any extra credit activity you attend. And reflect, don't summarize.

Academic

• CS extra Thursday: Adam Arsenault on his work at FSF.
• CS table Friday: The Mythical Man-Month.

Peer Support

• Men's Soccer, Wednesday, 5pm

Miscellaneous

• Second-year students get extra credit for doing the second-year science retreat. (It appears that they sent postcards over the summer and will send email soon.)

Fun Things

• Awesome show at the Faulconer gallery.

Tools for Software Development

• This course is partially about building software. And so we'll look at the tools and other resources that good programmers use to support software development.
• Their are some obvious ones, some that you've probably used in your prior courses.
  • Editors let you create your code, and sometimes even help you better understand the code (e.g., by doing syntax highlighting or providing easy navigation features).
  • Compilers translate your source code into executable code.
  • Debuggers, like gdb, help you identify bugs.
    (Print statements are not a debugger, even though they occasionally have their role in tracking down errors.)
  • Style checkers see if your code "makes sense".
  • References tell you more about the libraries and such that you use.
  • ...
• We'll be exploring (at least) three other kinds of tools this semester.
  • Source Code Management Systems provide a way to keep a history of your project and to more easily collaborate with others.
  • Integrated Development Environments (IDEs) are the "kitchen sink" of software development. They tie together lots and lots of useful tools.
  • Unit Testing Frameworks help you identify the existence of errors in your code. (Your debugger should still help you track it down.)
• Git will be our source code management system, Eclipse our IDE, and JUnit our testing framework. All three are popular in "the real world".

Lab on Eclipse

• Do (the lab on Eclipse)[../labs/eclipse.html]. Ask questions!

Lab on Git

• Do (the lab on Git from the command line)[../labs/git-command-line.html]. Ask questions!