1 / 5

Demos

Demos. Wednesday 3:00 p.m. to 5:20 p.m. in ECC and SEM 233 (my office) 20 minutes Please sign up for a 20 minute slot Put stable code snapshot on team web page Zip Tgz Destroy team page after Friday 5:00 p.m. Barzun's Laws of Learning .

tareq
Download Presentation

Demos

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Demos • Wednesday 3:00 p.m. to 5:20 p.m. in ECC and SEM 233 (my office) • 20 minutes • Please sign up for a 20 minute slot • Put stable code snapshot on team web page • Zip • Tgz • Destroy team page after Friday 5:00 p.m.

  2. Barzun's Laws of Learning The simple but difficult arts of paying attention, copying accurately, following an argument, detecting an ambiguity or a false inference, testing guesses by summoning up contrary instances, organizing one's time and one's thought for study -- all these arts -- cannot be taught in the air but only through the difficulties of a defined subject. They cannot be taught in one course or one year, but must be acquired gradually in dozens of connections.

  3. Learning • Learn by experience. How hard is it to work in a team? Why? What will you do different next time? • CS425 is also an introduction to teamwork, CS426 is about using your CS425 experience. • Will not count assignment 8 (unit tested code) • Assignment 9 will be graded on Demo.

  4. Working in Teams is hard • Paying attention • Following an argument (discussion of pros and cons) • Detecting an ambiguity or a false inference • Testing guesses by summoning up contrary instances • Making the case for a design decision • Recognizing team member strengths

  5. Working in an organization • Documentation instead of repeated teaching • Write well. Lists are useful in technical docs • Presentations • Speak well. Pictures are worth … • Making the case • Cogent, logical, arguments • Independence • Learn on your own. What would you like to hear? • What should I do? • Which alternative is best?

More Related