Lab 1 Slides Agenda Introductions and Ice Breakers

Lab 1 Slides

Agenda ● Introductions and Ice Breakers (10 minutes) ● Class Logistics (10 - 20 minutes) ○ ○ ○ Office Hours Lab Format Projects ■ Extra Credit ■ Late Days Basic Autograder Info What to do if you have questions Tips to succeed in EECS 183 ● Class Material Review (20 - 30 minutes) ● Lab Time (1 hour +/- )

Important Upcoming Dates ● ● 1/21 – MLK day 1/22 – Lab 1 due 1/25 – Project 1 is due 1/29 – Add/Drop deadline

Introductions and Icebreakers ● Split up into pairs and discuss: ● Name, year, major, blah etc. ● Where you’re from ● How much programming/computer science you’ve studied before ● Favorite/least favorite class last semester and why

Class Logistics ● ● Find everything but your grades at https: //eecs 183. org/ If you have questions, check Piazza first - someone may have already asked If not, post a question Next step is to go to office hours - check the website ○ There at least 5 hours of office hours every weekday ● DON’T CHEAT! It’s a much bigger deal than you might think, and the smallest infraction can result in major consequences

Lab Format ● Review and discuss lecture topics from previous week ● I try to introduce new and interesting concepts when appropriate ● Practice problems and code similar to project concepts and exam questions ● Tips for testing ● Work on lab and ask questions (Free OH!)

Office Hours ● 3: 00 -8: 00 M, W, Th, F; 3: 00 -7: 30 Tu. (6 -7: 30 T, 6: 30 -8 W) ● 3 rd Floor of Duderstadt: Follow Brady to Office Hours on EECS 183 website! ● Once you arrive, go to https: //lobster. eecs. umich. edu/queue and sign up for the OH queue ● If we aren’t currently helping you when Office Hours end, YOU ARE OUT OF LUCK. Office hours are more packed near the due dates of projects, so START PROJECTS EARLY!

The Autograder ● The Autograder will execute/test your code, and you will be graded on the accuracy of your algorithm. After submitting your code, you will receive an email with: ○ ○ ○ Your score The test cases you passed Detailed info of the FIRST test case you failed ● Max of 2 submits to the Autograder per day with feedback. All further submits will only state whether your code compiles. ○ Exception: on only ONE day before the project is due, you may submit a 3 rd time with feedback ● For Labs: max of 10 submits to the Autograder per day ● LAST submit (+ style points) = final grade ● You can download the files you submitted

How to do well in EECS 183 ● ● ● USE YOUR RESOURCES! YOU HAVE SO MANY OF THEM! Post frequently on Piazza Start Projects ASAP Go to Office Hours with specific questions. No “My code isn’t working help” Plan before you code! Avoid “spaghetti” code. Work with others - talk through the logic out loud ○ ○ There is nothing more helpful than teaching others something you just learned Piazza is also a good place to learn through teaching

Xcode and Visual ● What is an IDE? ○ Integrated Development Environment ● Some staff members are able to work with both XC and VS

How Coding Works ● ● You type up source code The IDE sends your code through a compiler The compiler generates object code (0’s and 1’s) from your source code Your computer uses object code to execute commands (like printing “Hello World” in a window)

Algorithms ● An algorithm is well-defined strategy for solving a problem ○ ○ ○ Counting people in a room Finding a certain page in a book Picking teams with captains ● Some algorithms are faster and use less memory than others ○ You’ll learn about these in EECS 281

Operators + * % / -

Data Types ● ● ● bool char int double string

Variable Names C++ rules: ● ● Can start with a letter or _ Can contain any letters, numbers, or _ Can’t be a reserved word Case sensitive Style rules: ● Must be camel. Case or snake_case ● Must be meaningful

Lab Time ● Labs are posted on eecs 183. org under schedule ● You can work by yourself or with a partner or team ● Follow the lab instructions ● If you have any questions, ask me! ● Lab 1 is due Tuesday 1/22 at 6: 00 pm but you can submit it whenever you are finished