DOC PREVIEW
UW-Madison CS 302 - CS 302 - Wrap up

This preview shows page 1-2 out of 5 pages.

Save
View full document
View full document
Premium Document
Do you want full access? Go Premium and unlock all 5 pages.
Access to all documents
Download any document
Ad free experience
View full document
Premium Document
Do you want full access? Go Premium and unlock all 5 pages.
Access to all documents
Download any document
Ad free experience
Premium Document
Do you want full access? Go Premium and unlock all 5 pages.
Access to all documents
Download any document
Ad free experience

Unformatted text preview:

Copyright © 2005-2007 William C. BentonCS 302: Wrapup1Copyright © 2005-2007 William C. BentonEnd-of-semester info2•Check all of your grades on Learn@UW.•The project is due tonight•Make sure that you go to the exam•in Social Sciences on Sunday morning•if you have a conflict, let me know ASAPCopyright © 2005-2007 William C. BentonAfter 302•I am happy to serve as a reference•if you think you’ll want a reference at some point in the future, let me know as soon as possible•Please keep in touch in any case!3Copyright © 2005-2007 William C. BentonAny project or content questions?4Copyright © 2005-2007 William C. BentonWhat you’ve learned•How to model problems and specify solutions•How to talk about programs•How to think about tradeoffs•Many of the specifics of the Java language•...and many concepts that relate to any language!5Copyright © 2005-2007 William C. Bentonpublic class Hello { public static void main(String[] args) { System.out.println(“Hello, world”); }}6...even in spite of having to deal with a lot of syntax!(What did you think when you first saw this?)Copyright © 2005-2007 William C. BentonWhere from here?7•As a computer science student•As a programmer•As a computer user•As a thoughtful personCopyright © 2005-2007 William C. BentonComputer science•Rich, broad (some might say ill-defined!) field; not just about programming•Many areas to study: architecture, AI, compilers, databases, graphics, modeling, numerical methods, OS, theory•Next steps: CS 367 (algorithms) or CS 354 (hardware organization)•Then 500-level courses in area of interest8Copyright © 2005-2007 William C. BentonProgramming•You’ve learned Java and have the basic tools to start becoming an expert•One suggestion: take 367 (learn about tradeoffs; don’t reinvent the wheel)•Also, program as much as possible!9Copyright © 2005-2007 William C. BentonSome fun projects•A desktop application with “Swing” graphics•A video game•See Java Gaming web page•A (more interesting) web server or service•You’ll have to deal with HTTP/HTML/XML -- most of this has been done for you, though•Music or visual software•see http://processing.org for inspiration10Copyright © 2005-2007 William C. BentonMore projects•Learn a new programming language -- different languages are good for different things•Use the stuff we’ve learned about design and patterns to make real applications•Many application frameworks use MVC:•Cocoa, Core Data (Mac)•Ruby on Rails, Stripes, Django (web apps)11Copyright © 2005-2007 William C. BentonActual student projects•My former 302 students have told me about:•an online, 3D video game•linguistics software to analyze speech patterns •bioinformatics software to search genetic and protein databases12Copyright © 2005-2007 William C. BentonSome books•Design Patterns: Elements of Reusable Object-Oriented Software. Gamma, Helm, Johnson, Vlissides. AW, 199x.•Refactoring: Improving the Design of Existing Code. Fowler. AW, 1999.•Structure and Interpretation of Computer Programs. Abelson & Sussman. MIT Press.•read on-line for free at http://mitpress.mit.edu/sicp/13Copyright © 2005-2007 William C. BentonAs a computer user•Maybe you never want to program again -- but you might have to anyway!•Excel macros, Automator actions, dynamic web pages, shell scripts•these all save time and draw upon the principles we learned•Also, you may develop more sympathy for buggy, late code14Copyright © 2005-2007 William C. Benton15Copyright © 2005-2007 William C. Benton15Copyright © 2005-2007 William C. Benton15early 2007Copyright © 2005-2007 William C. Benton16As a thoughtful person•Even if you’re going to avoid computers henceforth, you’ve gained something from 302•Logic and problem-solving never hurt anyone•Yet, anywayCopyright © 2005-2007 William C. BentonThanks for being a great


View Full Document

UW-Madison CS 302 - CS 302 - Wrap up

Download CS 302 - Wrap up
Our administrator received your request to download this document. We will send you the file to your email shortly.
Loading Unlocking...
Login

Join to view CS 302 - Wrap up and access 3M+ class-specific study document.

or
We will never post anything without your permission.
Don't have an account?
Sign Up

Join to view CS 302 - Wrap up 2 2 and access 3M+ class-specific study document.

or

By creating an account you agree to our Privacy Policy and Terms Of Use

Already a member?