From 5c50410ba455df6beb1ffc557648d5e871a08211 Mon Sep 17 00:00:00 2001 From: Amy Quispe Date: Tue, 5 May 2015 19:58:25 -0400 Subject: [PATCH 01/48] Update 8_Intro-Final-Project.md --- lessons/8_Intro-Final-Project.md | 5 +++++ 1 file changed, 5 insertions(+) diff --git a/lessons/8_Intro-Final-Project.md b/lessons/8_Intro-Final-Project.md index b840b80f..c9aecdd4 100644 --- a/lessons/8_Intro-Final-Project.md +++ b/lessons/8_Intro-Final-Project.md @@ -15,6 +15,11 @@ Today we'll go over the [requirements](https://github.com/accesscode-2-1/unit-1/ for the Unit 1 final project. > Exercise: Work with your team to design the project and figure out division of labor. +> 1. Make a git repo for work & make sure both partners can push. +> 2. Create design for app. +> 3. Put together a schedule for group work. +> 4. Figure out who is taking what parts. +> 5. Create your skeleton project & push to github. #### Assessment From d28af4b8c873d9a7871fb411a89a62355f40a1e3 Mon Sep 17 00:00:00 2001 From: Amy Quispe Date: Tue, 5 May 2015 19:58:47 -0400 Subject: [PATCH 02/48] Update 8_Intro-Final-Project.md --- lessons/8_Intro-Final-Project.md | 5 +++++ 1 file changed, 5 insertions(+) diff --git a/lessons/8_Intro-Final-Project.md b/lessons/8_Intro-Final-Project.md index c9aecdd4..092e43d7 100644 --- a/lessons/8_Intro-Final-Project.md +++ b/lessons/8_Intro-Final-Project.md @@ -15,10 +15,15 @@ Today we'll go over the [requirements](https://github.com/accesscode-2-1/unit-1/ for the Unit 1 final project. > Exercise: Work with your team to design the project and figure out division of labor. + > 1. Make a git repo for work & make sure both partners can push. + > 2. Create design for app. + > 3. Put together a schedule for group work. + > 4. Figure out who is taking what parts. + > 5. Create your skeleton project & push to github. #### Assessment From 734b54facb490d45d3a4ba3aa047a484f2d3b9d8 Mon Sep 17 00:00:00 2001 From: Amy Quispe Date: Wed, 6 May 2015 11:40:07 -0400 Subject: [PATCH 03/48] creating weekend lesson plans --- lessons/10_Github-Debugging.md | 0 lessons/11_Android-UI-Basics.md | 0 2 files changed, 0 insertions(+), 0 deletions(-) create mode 100644 lessons/10_Github-Debugging.md create mode 100644 lessons/11_Android-UI-Basics.md diff --git a/lessons/10_Github-Debugging.md b/lessons/10_Github-Debugging.md new file mode 100644 index 00000000..e69de29b diff --git a/lessons/11_Android-UI-Basics.md b/lessons/11_Android-UI-Basics.md new file mode 100644 index 00000000..e69de29b From 27996541c485996ff3c17f9b7140001b76a8d1be Mon Sep 17 00:00:00 2001 From: Alex Qin Date: Thu, 7 May 2015 11:55:35 -0400 Subject: [PATCH 04/48] Update README.md --- README.md | 1 + 1 file changed, 1 insertion(+) diff --git a/README.md b/README.md index 51e58500..67886b68 100644 --- a/README.md +++ b/README.md @@ -19,3 +19,4 @@ Lesson plans, activities and assignments for Unit 1 will be posted here! |---|---| | Apr 25 |
  • **READ** Think Piece: [How to Impress an Interviewer](https://medium.com/@joulee/how-to-impress-an-interviewer-c210d9d8e84a)
  • **WRITE** a Medium post about something technical or non technical you learned this week
  • **GUEST SPEAKER** [Vin Vacanti](speakers/vin-vacanti.md)
| May 1 |
  • **CODE:** [OOP](https://github.com/accesscode-2-1/unit-1/blob/master/homework/week-0.md)
  • **WATCH** Think Piece: [Carol Dweck: The power of believing that you can improve](http://www.ted.com/talks/carol_dweck_the_power_of_believing_that_you_can_improve)
  • **WRITE** a Medium post about something technical or non technical you learned this week
+| May 8 |
  • **CODE:** [Horoscope App](https://github.com/accesscode-2-1/unit-1/blob/master/homework/week-1.md)
  • **READ** Think Piece: [Unlearning Helplessness](http://braythwayt.com/2015/01/20/learned-helplessness.html)
  • **WRITE** a Medium post about something technical or non technical you learned this week
From 803163d81b2e0a582ee5961cdb981bf6b8503bf2 Mon Sep 17 00:00:00 2001 From: Amy Quispe Date: Fri, 8 May 2015 12:11:22 -0400 Subject: [PATCH 05/48] outlines for the day --- lessons/10_Github-Debugging.md | 28 ++++++++++++++++++++++++++++ lessons/11_Android-UI-Basics.md | 15 +++++++++++++++ 2 files changed, 43 insertions(+) diff --git a/lessons/10_Github-Debugging.md b/lessons/10_Github-Debugging.md index e69de29b..6ba7ffa9 100644 --- a/lessons/10_Github-Debugging.md +++ b/lessons/10_Github-Debugging.md @@ -0,0 +1,28 @@ +### Github and Debugging + +#### Objective +Students will learn general software engineering practices and will be able +to navigate Git, have more available debugging tools at their disposal, +and learn the basics of exception handling. + +#### Pre-Work + +[Github & Git Foundations](https://www.youtube.com/playlist?list=PLg7s6cbtAD15G8lNyoaYDuKZSKyJrgwB-) + +#### Do Now (Morning) + +#### Do Now (Afternoon) + +#### Debugging Basics + +##### Printing + +##### Logging + +##### Reading Stack Traces + +#### Exception Handling + +#### Assessment + + diff --git a/lessons/11_Android-UI-Basics.md b/lessons/11_Android-UI-Basics.md index e69de29b..339005c3 100644 --- a/lessons/11_Android-UI-Basics.md +++ b/lessons/11_Android-UI-Basics.md @@ -0,0 +1,15 @@ +### Android UI Basics + +#### Objective + +#### Do Now (Morning) + +#### Lesson (Morning) + +#### Do Now (Afternoon) + +#### Code Review + +#### Group Project + +#### Assessment From 62f8953c069134ccf1c00dc0ede8c5a508febeb2 Mon Sep 17 00:00:00 2001 From: Amy Quispe Date: Fri, 8 May 2015 13:54:55 -0400 Subject: [PATCH 06/48] added github exercises --- lessons/10_Github-Debugging.md | 51 ++++++++++++++++++++++++++++++++++ 1 file changed, 51 insertions(+) diff --git a/lessons/10_Github-Debugging.md b/lessons/10_Github-Debugging.md index 6ba7ffa9..ed7d447c 100644 --- a/lessons/10_Github-Debugging.md +++ b/lessons/10_Github-Debugging.md @@ -11,8 +11,57 @@ and learn the basics of exception handling. #### Do Now (Morning) +Create a new Java class to do the following string operations: +* Reverse - "Quispe" -> "epsiuQ" +* Uppercase words - "i love java" -> "I Love Java" +* Reverse words - "Java Love I" -> "I Love Java" + +#### Git and Github + +*Git* is a version control system. *Github* is a very popular website for storing git repositories and collaborating. + +> Exercise: Partner with the other person at your table. + +> Part I: Fork and Pull +> 1. Create a repository on Github. +> 1. Clone the repository locally, add the Do Now, and push the change to Github. +> 1. Fork your partner's repository. +> 1. Clone the fork of your partner's repository locally. +> 1. Set the upstream to your partner's repository. +> 1. Create a new branch and make changes to the file in your partner's repository. +> 1. Commit and push this change to Github. +> 1. Open a pull request to your partner's repository master. +> 1. Code review the pull request from your partner. +> 1. Respond to all the changes requested on your pull request (either make the change or push back), and push your changes. +> 1. Accept your partner's pull request. + +> Part II: Merge Conflict +> 1. Make your partner a collaborator on your repository. +> 1. Sync your local clone of your repository to origin master. +> 1. Clone your partner's repository locally. +> 1. Make changes to the file in your partner's repository and push. +> 1. Make changes to the file in your own repository and commit. +> 1. Before pushing, sync to origin master. +> 1. Resolve any merge conflicts. +> 1. Push your changes to your repository. + +> Part III: Shared repository +> 1. Sync your local clone of your partner's repository to origin master. +> 1. Create a new branch on your partner's repository. +> 1. Push this branch to Github. +> 1. Make changes to the file on this branch and push. +> 1. Open a pull request from this branch to master. +> 1. Code review your partner's pull request on your repository. +> 1. Respond to all comments on your partner's code review on your pull request (either make changes or push back) and push your changes. +> 1. Go back and forth code reviewing and responding to comments until all comments are resolved. +> 1. If comments can't be resolved, ask a third party to weigh in on your pull requst. +> 1. Once all comments are resolved, accept your partner's pull request. +> 1. Sync your local clones of your repositories to origin master, and delete all resolved branches. + #### Do Now (Afternoon) +Find the pull request for your reviewee from this week's code review. Download and run their horoscope app. If there are any problems with the pull request, please work with your reviewee to fix this pull request. + #### Debugging Basics ##### Printing @@ -21,6 +70,8 @@ and learn the basics of exception handling. ##### Reading Stack Traces +##### Using the Debugger + #### Exception Handling #### Assessment From 0ff17ecb1d65125fbe3395d4069156d603b6c5c7 Mon Sep 17 00:00:00 2001 From: Amy Quispe Date: Fri, 8 May 2015 15:02:27 -0400 Subject: [PATCH 07/48] Update 10_Github-Debugging.md --- lessons/10_Github-Debugging.md | 30 ++++++++++++++++++++++++++++++ 1 file changed, 30 insertions(+) diff --git a/lessons/10_Github-Debugging.md b/lessons/10_Github-Debugging.md index ed7d447c..8aaf430c 100644 --- a/lessons/10_Github-Debugging.md +++ b/lessons/10_Github-Debugging.md @@ -23,39 +23,69 @@ Create a new Java class to do the following string operations: > Exercise: Partner with the other person at your table. > Part I: Fork and Pull + > 1. Create a repository on Github. + > 1. Clone the repository locally, add the Do Now, and push the change to Github. + > 1. Fork your partner's repository. + > 1. Clone the fork of your partner's repository locally. + > 1. Set the upstream to your partner's repository. + > 1. Create a new branch and make changes to the file in your partner's repository. + > 1. Commit and push this change to Github. + > 1. Open a pull request to your partner's repository master. + > 1. Code review the pull request from your partner. + > 1. Respond to all the changes requested on your pull request (either make the change or push back), and push your changes. + > 1. Accept your partner's pull request. > Part II: Merge Conflict + > 1. Make your partner a collaborator on your repository. + > 1. Sync your local clone of your repository to origin master. + > 1. Clone your partner's repository locally. + > 1. Make changes to the file in your partner's repository and push. + > 1. Make changes to the file in your own repository and commit. + > 1. Before pushing, sync to origin master. + > 1. Resolve any merge conflicts. + > 1. Push your changes to your repository. > Part III: Shared repository + > 1. Sync your local clone of your partner's repository to origin master. + > 1. Create a new branch on your partner's repository. + > 1. Push this branch to Github. + > 1. Make changes to the file on this branch and push. + > 1. Open a pull request from this branch to master. + > 1. Code review your partner's pull request on your repository. + > 1. Respond to all comments on your partner's code review on your pull request (either make changes or push back) and push your changes. + > 1. Go back and forth code reviewing and responding to comments until all comments are resolved. + > 1. If comments can't be resolved, ask a third party to weigh in on your pull requst. + > 1. Once all comments are resolved, accept your partner's pull request. + > 1. Sync your local clones of your repositories to origin master, and delete all resolved branches. #### Do Now (Afternoon) From 50c71b5ab8008012c6288865420d51fe40193ca3 Mon Sep 17 00:00:00 2001 From: Amy Quispe Date: Fri, 8 May 2015 15:59:21 -0400 Subject: [PATCH 08/48] adding debug exercise --- .../10_Github-Debugging/src/BuggyClass.java | 62 +++++++++++++++++++ 1 file changed, 62 insertions(+) create mode 100644 exercises/10_Github-Debugging/src/BuggyClass.java diff --git a/exercises/10_Github-Debugging/src/BuggyClass.java b/exercises/10_Github-Debugging/src/BuggyClass.java new file mode 100644 index 00000000..1e5ef256 --- /dev/null +++ b/exercises/10_Github-Debugging/src/BuggyClass.java @@ -0,0 +1,62 @@ +class BuggyClass { + static int N = 1000*1000; + static int TRIES = 100; + static int TOLERANCE = 10; + + static int used_loop = 0; + static int used_recursive = 0; + static int used_divide_and_conquer = 0; + + public static void main(String args) { + int[] A = new int[N]; + int BIG = 1000*1000*1000; + long correct_sum = 0; + for(int i=0; i p; + } + + public static int sum_loop(int[] A){ + int sum = 0; + for(int i=0; i<=A.length; i++) { + sum += A[i]; + } + return sum; + } + + public static int sum_recursive(int i, int[] A){ + if(i==A.length - 1) { + return 0; } + return A[i+1] + sum_recursive(i+1, A); + } + + public static int sum_divide_and_conquer(int lo, int hi, int[] A) { + int mid = A.length/2; + if(lo==hi) { + return A[0]; } + return sum_divide_and_conquer(lo, mid, A) + sum_divide_and_conquer(mid, hi, A); + } + +} \ No newline at end of file From 30bb0ce05ce794a7934d6ae4aebe01c4d3e8b86d Mon Sep 17 00:00:00 2001 From: Amy Quispe Date: Fri, 8 May 2015 16:10:29 -0400 Subject: [PATCH 09/48] fixed up BuggyClass --- exercises/10_Github-Debugging/src/BuggyClass.java | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/exercises/10_Github-Debugging/src/BuggyClass.java b/exercises/10_Github-Debugging/src/BuggyClass.java index 1e5ef256..9ea7c1e9 100644 --- a/exercises/10_Github-Debugging/src/BuggyClass.java +++ b/exercises/10_Github-Debugging/src/BuggyClass.java @@ -1,4 +1,4 @@ -class BuggyClass { +public class BuggyClass { static int N = 1000*1000; static int TRIES = 100; static int TOLERANCE = 10; @@ -7,7 +7,7 @@ class BuggyClass { static int used_recursive = 0; static int used_divide_and_conquer = 0; - public static void main(String args) { + public static void main(String[] args) { int[] A = new int[N]; int BIG = 1000*1000*1000; long correct_sum = 0; From 198c15d365cc9881fbd7bbf9085b72d86d242f41 Mon Sep 17 00:00:00 2001 From: Amy Quispe Date: Fri, 8 May 2015 19:40:40 -0400 Subject: [PATCH 10/48] Update 10_Github-Debugging.md Added Excepti --- lessons/10_Github-Debugging.md | 48 ++++++++++++++++++++++++++++++++++ 1 file changed, 48 insertions(+) diff --git a/lessons/10_Github-Debugging.md b/lessons/10_Github-Debugging.md index 8aaf430c..f0e733d2 100644 --- a/lessons/10_Github-Debugging.md +++ b/lessons/10_Github-Debugging.md @@ -15,6 +15,7 @@ Create a new Java class to do the following string operations: * Reverse - "Quispe" -> "epsiuQ" * Uppercase words - "i love java" -> "I Love Java" * Reverse words - "Java Love I" -> "I Love Java" +* Parse Addition Expression - "3 + (4 + 2)" -> "9". Assume that the only operations are "+" and parentheses. #### Git and Github @@ -96,14 +97,61 @@ Find the pull request for your reviewee from this week's code review. Download a ##### Printing +Printing is a very useful debugging method that you've probably already touched. + ##### Logging + + ##### Reading Stack Traces +Stack traces tell you where + ##### Using the Debugger +> Exercise: Debug [BuggyClass](exercises/10_Github-Debugging/src/BuggyClass.java). BuggyClass attemps to compare several different array addition algorithms, but it's fraught with bugs. Remember, bugs are problems with functionality, not just crashing. It may be tricky to infer what someone *meant* to do with the code - in the future you may have to deal with (and fix!) poorly-documented code written by someone who is no longer at the company, or is otherwise not contactable. + #### Exception Handling +Exceptions are errors generated by your program. These errors normally crash your program, but you can write code to `catch` them and recover. + +First, let's see how to raise an exception. For example, let's say you had a `myDivide` method. Since dividing by zero isn't defined arithmetically, we should raise an exception. + +``` +public static double myDivide(int dividend, int divisor) { + if(divisor == 0){ + throw new IllegalArgumentException("Dividing By Zero"); + } + // implement division here + . + . + . +} +``` + +Once an exception is raised, calling code may handle it. For example, let's say you are using the `myDivide` API for a calculator application. + +``` +public static void myCalculator(String userInput) { + . + . // parse userInput + . + . + try { + myDivide(num1, num2); + } + catch (IllegalArgumentException e) { + alert_user(e.getMessage()); + } + . + . + . + . +} +``` + +Here, we use the exception to alert the user as to what went wrong. Exceptions propogate up the call stack, so the method that called `myCalculator` can also handle the exception. If the exception gets to the top of the call stack, then the program crashes. + #### Assessment From 4c3e219394178ebe826675ba09c631a227f6f88b Mon Sep 17 00:00:00 2001 From: Amy Quispe Date: Fri, 8 May 2015 19:51:12 -0400 Subject: [PATCH 11/48] Update 10_Github-Debugging.md added stack traces --- lessons/10_Github-Debugging.md | 35 +++++++++++++++++++++++++++++----- 1 file changed, 30 insertions(+), 5 deletions(-) diff --git a/lessons/10_Github-Debugging.md b/lessons/10_Github-Debugging.md index f0e733d2..6f5b334e 100644 --- a/lessons/10_Github-Debugging.md +++ b/lessons/10_Github-Debugging.md @@ -95,17 +95,42 @@ Find the pull request for your reviewee from this week's code review. Download a #### Debugging Basics -##### Printing +##### Printing and Logging -Printing is a very useful debugging method that you've probably already touched. +Printing is a very useful debugging method that you've probably already touched. Printing is useful because it can help display intermediate program state. Logging is essentially the same method (i.e. writing state to external output). -##### Logging +##### Reading Stack Traces +Stack traces explain the series of method calls that have led to the current state. For example: +``` +Exception in thread "main" java.lang.ArrayIndexOutOfBoundsException: 1000000 + at BuggyClass.sum_loop(BuggyClass.java:44) + at BuggyClass.find_sum(BuggyClass.java:29) + at BuggyClass.main(BuggyClass.java:19) <5 internal calls> +``` -##### Reading Stack Traces +Means that `main` called `find_sum` on line 19, `find_sum` called `sum_loop` on line 29, and `sum_loop` received an `ArrayIndexOutOfBoundsException` on line 44. On the other hand: + +``` +Exception in thread "main" java.lang.StackOverflowError + at BuggyClass.sum_recursive(BuggyClass.java:50) + at BuggyClass.sum_recursive(BuggyClass.java:52) + at BuggyClass.sum_recursive(BuggyClass.java:52) + at BuggyClass.sum_recursive(BuggyClass.java:52) + at BuggyClass.sum_recursive(BuggyClass.java:52) + at BuggyClass.sum_recursive(BuggyClass.java:52) + at BuggyClass.sum_recursive(BuggyClass.java:52) + at BuggyClass.sum_recursive(BuggyClass.java:52) + at BuggyClass.sum_recursive(BuggyClass.java:52) + at BuggyClass.sum_recursive(BuggyClass.java:52) + at BuggyClass.sum_recursive(BuggyClass.java:52) + . + . + . +``` -Stack traces tell you where +means that `sum_recursive` infinitely calls itself and eventually crashes. ##### Using the Debugger From 6f51eaaaea382d7af5b6483edf90ae575a5a7643 Mon Sep 17 00:00:00 2001 From: Amy Quispe Date: Fri, 8 May 2015 23:31:39 -0400 Subject: [PATCH 12/48] Update 10_Github-Debugging.md --- lessons/10_Github-Debugging.md | 47 +++++++++++++++++++++++++++++++--- 1 file changed, 44 insertions(+), 3 deletions(-) diff --git a/lessons/10_Github-Debugging.md b/lessons/10_Github-Debugging.md index 6f5b334e..6f88adaa 100644 --- a/lessons/10_Github-Debugging.md +++ b/lessons/10_Github-Debugging.md @@ -21,6 +21,34 @@ Create a new Java class to do the following string operations: *Git* is a version control system. *Github* is a very popular website for storing git repositories and collaborating. +Some basic git commands: + +| Command | Description | +|---------|-------------| +| git init | Creates a new git repository | +| git clone [path] | Creates a local copy of a repository | +| git add | Adds a file or directory to staging | +| git rm | Adds the removal of a file or directory to staging | +| git commit | Commits staged changes to head | +| git push origin [branch] | Push changes to [branch] at remote | +| git status | Lists staged changes and changes that have not get been staged | +| git fetch | Get remote changes | +| git pull | Get remote changes and merge | +| git branch | List branches and indicate current branch | +| git branch [branchname] | Create new branch called [branchname] | +| git checkout [branchname] | Switch to branch called [branchname] | +| git checkout -b [branchname] | Create a new branch called [branchname] and switch to it | +| git blame | Revision and author of a line of the file | +| git log | Show commit logs | +| git diff | Show changes between commits | + +Other vocabulary: +* Fork: A copy of a repository. +* Master: The main branch. +* Origin: The remote repository. +* Upstream: The repository that origin copied. +* Branch: A series of changes starting at a particular commit. + > Exercise: Partner with the other person at your table. > Part I: Fork and Pull @@ -95,9 +123,12 @@ Find the pull request for your reviewee from this week's code review. Download a #### Debugging Basics -##### Printing and Logging +##### Variable Scope -Printing is a very useful debugging method that you've probably already touched. Printing is useful because it can help display intermediate program state. Logging is essentially the same method (i.e. writing state to external output). +A few rules about variable scope: +* Anything declared between {} belongs only to that block. This also goes for the signature of a loop. +* Anything declared in a method only exists for the scope of that method. +* Reference class variables using the `this` keyword. ##### Reading Stack Traces @@ -132,8 +163,14 @@ Exception in thread "main" java.lang.StackOverflowError means that `sum_recursive` infinitely calls itself and eventually crashes. +##### Printing and Logging + +Printing is a very useful debugging method that you've probably already touched. Printing is useful because it can help display intermediate program state. Logging is essentially the same method (i.e. writing state to external output). + ##### Using the Debugger +The debugger allows you to set breakpoints in your code. When you run your code, the execution stops when it reaches a breakpoint. At this point, you can inspect the current state of the program as well as step through the code line by line. + > Exercise: Debug [BuggyClass](exercises/10_Github-Debugging/src/BuggyClass.java). BuggyClass attemps to compare several different array addition algorithms, but it's fraught with bugs. Remember, bugs are problems with functionality, not just crashing. It may be tricky to infer what someone *meant* to do with the code - in the future you may have to deal with (and fix!) poorly-documented code written by someone who is no longer at the company, or is otherwise not contactable. #### Exception Handling @@ -177,6 +214,10 @@ public static void myCalculator(String userInput) { Here, we use the exception to alert the user as to what went wrong. Exceptions propogate up the call stack, so the method that called `myCalculator` can also handle the exception. If the exception gets to the top of the call stack, then the program crashes. -#### Assessment +#### Bonus +[Project Euler Problem 20](https://projecteuler.net/problem=20) + +#### Assessment +What does the first line in the call stack indicate? From d635cf55ce01b2131c0742b14b117a6e9e27cdf6 Mon Sep 17 00:00:00 2001 From: Amy Quispe Date: Fri, 8 May 2015 23:39:10 -0400 Subject: [PATCH 13/48] Update README.md --- README.md | 11 ++++++++--- 1 file changed, 8 insertions(+), 3 deletions(-) diff --git a/README.md b/README.md index 67886b68..5f3bbfeb 100644 --- a/README.md +++ b/README.md @@ -9,10 +9,14 @@ Lesson plans, activities and assignments for Unit 1 will be posted here! 0 | Apr 21 | 0 | [Android Prework](lessons/0_Android-Prework.md) 1 | Apr 23 | 0 | [Android Studio & Structure of an Android Project](lessons/1_Android-Studio-Structure-of-Android-Project.md) 2 | Apr 25 | 0 | [Inheritance and Interfaces](lessons/2_Interfaces-And-Inheritance) - 3 | Apr 26 | 0 | [Generics and Abstract Classes](/lessons/3_Generics-and-Abstract-Classes.md) + 3 | Apr 26 | 1 | [Generics and Abstract Classes](/lessons/3_Generics-and-Abstract-Classes.md) 4 | Apr 28 | 1 | [Anatomy of the Android Manifest](/lessons/4_Anatomy_Manifest.md) - 5 | May 02 | 1 | [Android Resources] (lessons/6_Android-Resources.md) - 6 | May 03 | 1 | [Activity Lifecycle](lessons/7_Android-Lifecycle.md) + 5 | Apr 30 | 1 | [OOP and Intents](exercises/5_OOP-and-Intents) + 6 | May 02 | 1 | [Android Resources] (lessons/6_Android-Resources.md) + 7 | May 03 | 2 | [Activity Lifecycle](lessons/7_Android-Lifecycle.md) + 8 | May 05 | 2 | [Intro to Final Project](lessons/8_Intro-Final-Project.md) + 9 | May 07 | 2 | [Android Exercises](https://github.com/shurane/unit-1-exercises) + 10 | May 09 | 2 | [Github and Debugging](lessons/10_Github-Debugging.md) ### Homework | Due Date | Homework| @@ -20,3 +24,4 @@ Lesson plans, activities and assignments for Unit 1 will be posted here! | Apr 25 |
  • **READ** Think Piece: [How to Impress an Interviewer](https://medium.com/@joulee/how-to-impress-an-interviewer-c210d9d8e84a)
  • **WRITE** a Medium post about something technical or non technical you learned this week
  • **GUEST SPEAKER** [Vin Vacanti](speakers/vin-vacanti.md)
| May 1 |
  • **CODE:** [OOP](https://github.com/accesscode-2-1/unit-1/blob/master/homework/week-0.md)
  • **WATCH** Think Piece: [Carol Dweck: The power of believing that you can improve](http://www.ted.com/talks/carol_dweck_the_power_of_believing_that_you_can_improve)
  • **WRITE** a Medium post about something technical or non technical you learned this week
| May 8 |
  • **CODE:** [Horoscope App](https://github.com/accesscode-2-1/unit-1/blob/master/homework/week-1.md)
  • **READ** Think Piece: [Unlearning Helplessness](http://braythwayt.com/2015/01/20/learned-helplessness.html)
  • **WRITE** a Medium post about something technical or non technical you learned this week
+| May 15 |