From 789a86073747f43f7cc142656683f57ec218c54f Mon Sep 17 00:00:00 2001 From: Maria Piper Date: Fri, 9 May 2014 18:08:49 -0700 Subject: [PATCH] curriculum and challenge names updated --- readme.md | 5 +- week_1/4_beginning_HTML_CSS/readme.md | 2 +- week_1/5_HTML_CSS_solo_challenge/readme.md | 2 +- .../my_reflection.md | 0 .../readme.md | 2 +- week_1/7_cultural_blog.md | 25 +++ .../my_reflection.md | 0 .../readme.md | 5 +- week_1/9_cultural_blog.md | 152 ------------------ .../my_reflection.md | 0 .../readme.md | 17 +- week_1/readme.md | 27 ++-- week_2/1_Chrome_Dev_Tools/readme.md | 2 +- week_2/readme.md | 3 + week_2/reflection_guidelines.md | 24 --- week_3/1_git_started/readme.md | 4 +- week_3/2_code_combat/readme.md | 2 +- week_3/3_js_variables_objects/my_solution.js | 2 +- week_3/3_js_variables_objects/readme.md | 6 +- .../readme.md | 2 +- week_3/5_design_cc_mission/readme.md | 9 +- week_3/6_group_project/readme.md | 2 +- week_3/8_cultural_blog.md | 30 ++-- week_3/9_gps1_2/readme.md | 2 +- week_3/readme.md | 2 + week_3/reflection_guidelines.md | 15 -- week_3/reviewing_solutions.md | 37 ----- 27 files changed, 93 insertions(+), 286 deletions(-) rename week_1/{8_technical_blog => 6_technical_blog}/my_reflection.md (100%) rename week_1/{8_technical_blog => 6_technical_blog}/readme.md (95%) create mode 100644 week_1/7_cultural_blog.md rename week_1/{6_wireframing => 8_wireframing}/my_reflection.md (100%) rename week_1/{6_wireframing => 8_wireframing}/readme.md (92%) delete mode 100644 week_1/9_cultural_blog.md rename week_1/{7_get_to_know_your_group => 9_get_to_know_your_group}/my_reflection.md (100%) rename week_1/{7_get_to_know_your_group => 9_get_to_know_your_group}/readme.md (51%) delete mode 100644 week_2/reflection_guidelines.md delete mode 100644 week_3/reflection_guidelines.md delete mode 100644 week_3/reviewing_solutions.md diff --git a/readme.md b/readme.md index a8178978..e4bdaf0e 100644 --- a/readme.md +++ b/readme.md @@ -6,11 +6,12 @@ Welcome to Phase 0! Below you will find links to the curriculum for each week. E ### [Week 2: More HTML/CSS](week_2) ### [Week 3: JavaScript](week_3) -## Unit Goals -- [Peer-Pair program](https://github.com/Devbootcamp/phase_0_handbook/blob/master/peer-pairing_sessions.md) at least 3 times with people in your accountability group. Read about [pairing](https://github.com/Devbootcamp/phase_0_handbook/blob/master/pairing_in_phase_0.md) before hand. +## Unit Requirements +- [Peer-Pair program](https://github.com/Devbootcamp/phase_0_handbook/blob/master/peer-pairing_sessions.md) at least 4 times this unit. Read about [pairing](https://github.com/Devbootcamp/phase_0_handbook/blob/master/pairing_in_phase_0.md). - [Submit feedback](https://socrates.devbootcamp.com/feedback/new) for all pairing sessions. (You should submit at least 3 for peer sessions and 2 for [GPS 1.1 and 1.2](https://github.com/Devbootcamp/phase_0_handbook/blob/master/guided_pairing_sessions.md)) - [Rate Feedback](https://socrates.devbootcamp.com/feedback) at least 20 pieces of other people's feedback. #### How to navigate this repository If you would like to open tabs in a new window, please either right click or hold command while you click. + diff --git a/week_1/4_beginning_HTML_CSS/readme.md b/week_1/4_beginning_HTML_CSS/readme.md index 72f1adf7..633f702a 100644 --- a/week_1/4_beginning_HTML_CSS/readme.md +++ b/week_1/4_beginning_HTML_CSS/readme.md @@ -69,4 +69,4 @@ Create a new css file in your repository called `dbc1.css` and save it to the `s ## Release 4: Reflect -On your local `phase_0_unit_1` repo, edit the [my_reflection.md](./my_reflection.md) file associated with this challenge. Commit your changes and save them to GitHub. +On your local `phase_0_unit_1` repo, edit the [my_reflection.md](my_reflection.md) file associated with this challenge. Commit your changes and save them to GitHub. diff --git a/week_1/5_HTML_CSS_solo_challenge/readme.md b/week_1/5_HTML_CSS_solo_challenge/readme.md index 6ab29327..bbadb045 100644 --- a/week_1/5_HTML_CSS_solo_challenge/readme.md +++ b/week_1/5_HTML_CSS_solo_challenge/readme.md @@ -61,7 +61,7 @@ Add the following to `dbc2.css`: ## Release 2: Reflect -On your local `phase_0_unit_1` repo, edit the [my_reflection.md](./my_reflection.md) file associated with this challenge. Commit your changes and save them to GitHub. +On your local `phase_0_unit_1` repo, edit the [my_reflection.md](my_reflection.md) file associated with this challenge. Commit your changes and save them to GitHub.
diff --git a/week_1/8_technical_blog/my_reflection.md b/week_1/6_technical_blog/my_reflection.md similarity index 100% rename from week_1/8_technical_blog/my_reflection.md rename to week_1/6_technical_blog/my_reflection.md diff --git a/week_1/8_technical_blog/readme.md b/week_1/6_technical_blog/readme.md similarity index 95% rename from week_1/8_technical_blog/readme.md rename to week_1/6_technical_blog/readme.md index b402b54a..b64f5c74 100644 --- a/week_1/8_technical_blog/readme.md +++ b/week_1/6_technical_blog/readme.md @@ -36,5 +36,5 @@ Copy the code from your blog template to a new HTML file called `week1_technical Write a blog post analyzing the 3 sites in terms of user experience and design. Add a link to the `index.html` file for your new blog post! Don't forget to sync your changes to make them live on your github.io site! ## Release 3: Reflect -On your local `phase_0_unit_1` repo, edit the [my_reflection.md](./my_reflection.md) file associated with this challenge. Commit your changes and save them to GitHub. +On your local `phase_0_unit_1` repo, edit the [my_reflection.md](my_reflection.md) file associated with this challenge. Commit your changes and save them to GitHub. diff --git a/week_1/7_cultural_blog.md b/week_1/7_cultural_blog.md new file mode 100644 index 00000000..2a831d5e --- /dev/null +++ b/week_1/7_cultural_blog.md @@ -0,0 +1,25 @@ +[Week 1 Home](./) + +# U1.W1: Cultural Blog: Chefs in the Kitchen + +## Learning Competencies +- Consider DBC's culture and approach to learning +- Predict how you will react to DBC's approach + +## Release 0: Copy your Blog Template +First, create a new HTML file for your this post in your [USERNAME].github.io website. Create a new HTML file and use the date to name it `week3_cultural_blog.html`. Copy the Code from your `blog_template`. + +## Release 1: Kitchen vs. Table +Watch [Shereef's Fireside Chat](http://vimeo.com/85001014) + +## Release 2: Write your Blog! +Based on the video, what's your take on the DBC experience? What is your impression of DBC? How do you see yourself engaging with this type of culture? +Have your expectations of DBC changed? If so, how? Are you excited to participate in this kind of learning environment? Does it make you nervous? + +Talk about what came up for you and anything you want in addition to the questions above. + + +## Release 3: Submission +Link to your blog on the index of your github.io site and sync your changes. + +Share your blog on the google+ community under "Blog Posts!" Read others blogs. What did you like about them? \ No newline at end of file diff --git a/week_1/6_wireframing/my_reflection.md b/week_1/8_wireframing/my_reflection.md similarity index 100% rename from week_1/6_wireframing/my_reflection.md rename to week_1/8_wireframing/my_reflection.md diff --git a/week_1/6_wireframing/readme.md b/week_1/8_wireframing/readme.md similarity index 92% rename from week_1/6_wireframing/readme.md rename to week_1/8_wireframing/readme.md index f8af20e3..18dbb3f6 100644 --- a/week_1/6_wireframing/readme.md +++ b/week_1/8_wireframing/readme.md @@ -1,6 +1,5 @@ # U1.W1: Wireframing - ## Learning Competencies - Explain wireframing - Identify the benefits of wireframing @@ -19,7 +18,7 @@ is often to wireframe it. This process should also help you learn to separate di ## Release 0: Intro to Design Thinking While designers may be "creative" or "artistic", they are also, like -software engineers problem solvers. They just solve problems visually +software engineers, problem solvers. They just solve problems visually instead of with code. For some of you, this may come really naturally; for others it may not. Either is OK. @@ -54,5 +53,5 @@ image sharing site. * Add the image to your html page. ## Release 3: Reflection -On your local `phase_0_unit_1` repo, edit the [my_reflection.md](./my_reflection.md) file associated with this challenge. Commit your changes and save them to GitHub. +On your local `phase_0_unit_1` repo, edit the [my_reflection.md](my_reflection.md) file associated with this challenge. Commit your changes and save them to GitHub. diff --git a/week_1/9_cultural_blog.md b/week_1/9_cultural_blog.md deleted file mode 100644 index d943d964..00000000 --- a/week_1/9_cultural_blog.md +++ /dev/null @@ -1,152 +0,0 @@ -# U1.W1: Exploring your values - -## Learning Competencies -- Identify your core values - -## Release 0: - -First, create a new HTML file for your this post in your [USERNAME].github.io website. Copy the Code from your `blog_template` into a new HTML file and use the date to name it `week1_cultural_blog.html`. - -Once you've opened your file, write a response to each exercise using the HTML you've learned to set up the file: - -## Release 1: - -When you think of the times in your life where you’ve been the -happiest, the proudest, or the most satisfied, which of the following -values come to mind? - -Accomplishment -Accountability -Achievement -Activism -Adventure -Affection -Ambition -Autonomy -Challenge -Close relationships -Commitment -Community -Compassion -Competence -Competition -Confidence -Conformity -Control -Coolness under fire -Cooperation -Courage -Creativity -Credibility -Decisiveness -Economic security -Effectiveness -Efficiency -Enthusiasm -Environmentalism -Excellence -Excitement -Fairness -Faith -Fame -Free time -Freedom -Friendships -Growth -Having a family -Health -Helping other people -Helping society -Honesty -Hospitality -Independence -Influence -Inner harmony -Insight -Inspiration -Integrity -Intellectual status -Introspection -Justice -Knowledge -Leadership -Location -Loyalty -Meaningful work -Mentorship -Merit -Money -Movement -Music -Nature -Openness -Order -Patriotism -Peace -Persistance -Personal development -Physical challenge -Pleasure -Power and authority -Privacy -Public service -Purity -Quality -Recognition -Reputation -Responsibility -Romance -Security -Self-knowledge -Self-reliance -Self-respect -Serenity -Sophistication -Spirituality -Stability -Status -Tranquility -Truth -Vibrancy -Volunteering -Wealth -Will-power -Wisdom -[add any that I missed] - - - -## Release 2: - -Pick one value and write a couple of sentences about why one of the values you chose is important to you. - - - -## Release 3: - -Answer the following for the values you chose in Exercise 1: - -In general, I try to live up to these values: - -Disagree 1 ----- 2 ----- 3 ----- 4 ----- 5 Agree - - - -## Release 4: - -What was the last topic that someone asked for your advice on? - - -## Release 5: Update and Share -Link to your blog on the index of your site and sync your changes. Then email the link to your accountability group. -If you feel comfortable sharing with the group, share your blog on the google+ community under "Blog Posts." - -
- -##### About -These exercises were created to combat Imposter Syndrome, based on [this research](http://blogs.discovermagazine.com/notrocketscience/2010/11/25/15-minute-writing-exercise-closes-the-gender-gap-in-university-level-physics/#.Uynq1a1dUYM) - -##### License -This project is licensed from Ada Institute under Creative Commons Attribution: -http://creativecommons.org/licenses/by/3.0/ - diff --git a/week_1/7_get_to_know_your_group/my_reflection.md b/week_1/9_get_to_know_your_group/my_reflection.md similarity index 100% rename from week_1/7_get_to_know_your_group/my_reflection.md rename to week_1/9_get_to_know_your_group/my_reflection.md diff --git a/week_1/7_get_to_know_your_group/readme.md b/week_1/9_get_to_know_your_group/readme.md similarity index 51% rename from week_1/7_get_to_know_your_group/readme.md rename to week_1/9_get_to_know_your_group/readme.md index 947aeacd..4500eb51 100644 --- a/week_1/7_get_to_know_your_group/readme.md +++ b/week_1/9_get_to_know_your_group/readme.md @@ -14,17 +14,20 @@ Despite popular belief, most software engineers work in teams and there is a str ## Release 0: Intro Email -Once you know who is in your accountability group, send everyone in your group and email **and** edit the [my_reflection.md](./my_reflection.md) file associated with this challenge in your local `phase_0_unit_1` repo,. Commit your changes and save them to GitHub. +Once you know who is in your accountability group, send everyone in your group and email **and** edit the [my_reflection.md](my_reflection.md) file associated with this challenge in your local `phase_0_unit_1` repo,. Commit your changes and save them to GitHub. -* name -* location -* favorite websites -* learning style +* Name +* Location +* Favorite websites +* Gregorc Thinking Style (Abstract Random, Abstract Sequential, Concrete Random, Concrete Sequential) +* Learning style (Visual, Aural, Kinesthetic, Multimodal) ## Release 1: Share your work +**DOUBLE CHECK THAT YOU HAVE ISSUES ENABLED AS A FEATURE ON BOTH OF YOUR REPOSITORIES** + Once you've completed the week's work, send them: -* link to your reflection file +* link to your forked `phase_0_unit_1` repository * link to your [USERNAME].github.io site * link to your wireframe html page -Once you receive someone's reflection, take a look at it and write a comment as an issue on it. +Once you receive someone's work, take a moment to [review](https://github.com/Devbootcamp/phase_0_handbook/blob/master/coding_references/review.md) it and leave comments as issues on their repositories. diff --git a/week_1/readme.md b/week_1/readme.md index cc241ebe..192bf799 100644 --- a/week_1/readme.md +++ b/week_1/readme.md @@ -11,32 +11,29 @@ If you would like to open tabs in a new window, please either right click or hol #### 2. [Set Up Repo](2_set_up_repo) #### 3. [Web Basics](3_web_basics) #### 4. [Beginning HTML & CSS](4_beginning_HTML_CSS) -#### 5. [More HTML & CSS](5_HTML_CSS_solo_challenge) **SOLO Challenge** -#### 6. [Wireframing](6_wireframing/) -#### 7. [Get to know your group](7_get_to_know_your_group) -#### 8. [Technical Blog](8_technical_blog) -#### 9. [Affirming your values](9_cultural_blog.md) +#### 5. [More HTML & CSS SOLO CHALLENGE](5_HTML_CSS_solo_challenge) +#### 6. [Technical Blog](6_technical_blog) +#### 7. [Cultural Blog](7_cultural_blog.md) +#### 8. [Wireframing](8_wireframing/) +#### 9. [Get to know your group](9_get_to_know_your_group) ## Submitting your work - You need to submit your work through on [apply.devbootcamp.com](http://apply.devbootcamp.com) by Sunday at 11:59pm. When you log in, look at your profile page. There should be a "Unit 1 Week 1 Form." Expect to submit your links for each of the following: * Your new website * Each html page created in `unit1_projects` folder -* Your reflection file -* Comparing websites and values blog posts +* Your forked `phase_0_unit_1` repository link +* Your technical and cultural blog posts * Your response to "getting to know your group" -### Fetching changes from DBC's master repo -Sometimes we will make changes to the original repository to clarify instructions. You will need to fetch these changes from the master branch when we announce changes on the google+ community. +NOTE: You will have two separate repositories in Github for Unit 1: Your Github.io site and your phase_0_unit_1 repository. + +## Fetching changes from DBC's master repo +Sometimes we will make changes to the original (Devbootcamp) repository to clarify instructions or add new curriculum. You will need to "fetch" these changes from the master branch when we announce changes on the google+ community. Follow [these](https://github.com/Devbootcamp/phase_0_handbook/blob/master/fetching_changes.md) directions to do this. If you are using a windows or linux, you will need to use the command line instructions. -- If you are doing this from the Github Desktop App, follow [these](http://stackoverflow.com/questions/11394349/upstream-pulls-with-the-github-desktop-client -) -directions. -- If you are doing it from the command line, follow [these](https://help.github.com/articles/syncing-a-fork) directions. ## Remember your Unit Goals! -- Pair at least once this week with a member of your accountability group. *You need to pair 3 times on your own this unit* - Give feedback for each person you paired with. *You need to submit at least 5 pieces of feedback in this unit* - Rate at least 7 pieces of [Meta Feedback](https://socrates.devbootcamp.com/feedback) on Socrates. *You need to rate 20 pieces of feedback per unit* +- Make sure you've signed up for GPS 1.1 and 1.2 (These must be done in a session with guide. They may not be done any other way, so make sure you sign up early!) diff --git a/week_2/1_Chrome_Dev_Tools/readme.md b/week_2/1_Chrome_Dev_Tools/readme.md index 21b23de7..ab63e752 100644 --- a/week_2/1_Chrome_Dev_Tools/readme.md +++ b/week_2/1_Chrome_Dev_Tools/readme.md @@ -37,7 +37,7 @@ Then, visit any blog on [wordpress.com](http://www.wordpress.com) or create your ## Release 3: Reflect -Go to your [Reflection file](my_reflection.md) to write your reflection - include answers to the questions in the file in addition to the [reflection guidelines](../reflection_guidelines.md). +Go to your [Reflection file](my_reflection.md) to write your reflection - include answers to the questions in the file in addition to the [reflection guidelines](https://github.com/Devbootcamp/phase_0_handbook/blob/master/coding_references/reflection_guidelines.md). ## Release 4: Sync and Submit! diff --git a/week_2/readme.md b/week_2/readme.md index c2b6cf3b..b3110fcd 100644 --- a/week_2/readme.md +++ b/week_2/readme.md @@ -1,5 +1,7 @@ # HTML and CSS cont. +Please do not start week 2 until May 19. We will make changes to curriculum and update DBC's master repository. + This week you will go into more depth on HTML and CSS and get more practice. You will also get to play with Dev Tools and consider the implications of responsive Design. Overall, this week's curriculum should give you the opportunity to go into more depth with HTML and have fun solidifying your knowledge! You have a [Cultural Assignment](7_cultural_assignment.md) this week you should look at first. @@ -18,6 +20,7 @@ You have a [Cultural Assignment](7_cultural_assignment.md) this week you should ## Sync DBC's Changes ####It's time to sync changes from DevBootcamp's phase_0_unit 1 master repo! Follow [these instructions](https://github.com/Devbootcamp/phase_0_handbook/blob/master/fetching_changes.md)! + ## Working through the challenges Once you have the entire local repository on your computer, you don't need to read the challenges on github anymore (although we admit, it's prettier). You can open the entire repository in sublime and read the challenges in their original markdown. It will also help you find any link issues, since you can see where they are pointing. If you do find broken links, please let us by posting on the community, but also try to figure out a fix. It will help your markdown skills! diff --git a/week_2/reflection_guidelines.md b/week_2/reflection_guidelines.md deleted file mode 100644 index 5e9a99b9..00000000 --- a/week_2/reflection_guidelines.md +++ /dev/null @@ -1,24 +0,0 @@ -# Your Reflection -When writing your reflection, write it for an audience. Tell a story of what you tried and what you learned. It will make it easier for you to go back and re-teach yourself or know what you were thinking. - -Remember, your reflections aren't just for teachers, they are for your fellow cohort mates as well, so be generous! You could end up helping a fellow student learn something new. - -Answer the following questions (in addition to the challenge-specific questions) in your reflection: - -* What parts of your strategy worked? What problems did you face? -* What questions did you have while coding? What resources did you find to help you answer them? -* What concepts are you having trouble with, or did you just figure something out? If so, what? -* Did you learn any new skills or tricks? -* How confident are you with each of the Learning Competencies? -* Which parts of the challenge did you enjoy? -* Which parts of the challenge did you find tedious? - -## Reviewing Others' Reflections -Email your accoutability group a link to your repo and comment on each other's reflections using the directions in [reviewing solutions](../week_3/reviewing_solutions.md). When you are commenting, try to look at and address the following: - -- Did you learn something from their reflections? -- Did anything resonate with you? -- Did they run into a problem you could help with? -- Are their any concepts you are confused about as well? -- Were you able to follow their logic? -- Do you agree or disagree with their assessment? Be sure to be kind, specific, and actionable with this feedback. \ No newline at end of file diff --git a/week_3/1_git_started/readme.md b/week_3/1_git_started/readme.md index 869a3c53..bc9e82c0 100644 --- a/week_3/1_git_started/readme.md +++ b/week_3/1_git_started/readme.md @@ -36,8 +36,8 @@ Give yourself a little cheatsheet (in order) of commands you'll need to: - Commit locally ## Release 5: Reflect -In the reflection section of your 'my_solution.js` file, reflect on your learning using the [reflection guidelines](../reflection_guidelines.md). ***NOTE: Reflections are mandatory!*** +In the reflection section of your 'my_solution.js` file, reflect on your learning using the [reflection guidelines](https://github.com/Devbootcamp/phase_0_handbook/blob/master/coding_references/reflection_guidelines.md). ***NOTE: Reflections are mandatory!*** ## Release 6: Review -[Review others' solutions](../reviewing_solutions.md) by leaving an issue. Compare their definitions and workflow to yours. Did you have trouble understanding Git or Github? Did they have trouble? Provide actionable, specific, and kind feedback. (You are expected to leave at least two comments for this challenge). +[Review others' solutions](https://github.com/Devbootcamp/phase_0_handbook/blob/master/coding_references/review.md) by leaving an issue. Compare their definitions and workflow to yours. Did you have trouble understanding Git or Github? Did they have trouble? Provide actionable, specific, and kind feedback. (You are expected to leave at least two comments for this challenge). diff --git a/week_3/2_code_combat/readme.md b/week_3/2_code_combat/readme.md index 62c9b04b..5e459903 100644 --- a/week_3/2_code_combat/readme.md +++ b/week_3/2_code_combat/readme.md @@ -35,7 +35,7 @@ When you are finished with all of the campaigns, answer the following questions. - What is the point of the semicolons? ## Release 4: Reflect -In the reflection section of your 'my_solution.js` file, reflect on your learning using the [reflection guidelines](../reflection_guidelines.md). ***NOTE: Reflections are mandatory!*** +In the reflection section of your 'my_solution.js` file, reflect on your learning using the [reflection guidelines](https://github.com/Devbootcamp/phase_0_handbook/blob/master/coding_references/reflection_guidelines.md). ***NOTE: Reflections are mandatory!*** diff --git a/week_3/3_js_variables_objects/my_solution.js b/week_3/3_js_variables_objects/my_solution.js index 2cb5532d..4b6ea08a 100644 --- a/week_3/3_js_variables_objects/my_solution.js +++ b/week_3/3_js_variables_objects/my_solution.js @@ -37,7 +37,7 @@ // __________________________________________ -// Driver Code: Do not alter code below this line. +// Driver Test Code: Do not alter code below this line. function assert(test, message, test_number) { if (!test) { diff --git a/week_3/3_js_variables_objects/readme.md b/week_3/3_js_variables_objects/readme.md index b8df0822..85efb713 100644 --- a/week_3/3_js_variables_objects/readme.md +++ b/week_3/3_js_variables_objects/readme.md @@ -34,7 +34,7 @@ Hint: If you get an error message that says something like ... This is your first introduction to Test-Driven Development (TDD). In this challenge, you will be dependent upon the provided driver code to guide your coding. Read [The Newbie's Guide to Test-Driven Development](http://code.tutsplus.com/tutorials/the-newbies-guide-to-test-driven-development--net-13835) to learn more about TDD if you're interested. ## Release 0: Test-Driven Development -First run your [my_solution.js](./my_solution.js) file in this directory and read the error message, then hypothesize about what you need to write to fix it. +First run your [my_solution.js](my_solution.js) file in this directory and read the error message, then hypothesize about what you need to write to fix it. ## Release 1: Pseudocode Write specific and write step-by-step ideas to pass each test in code-like English. Each line should be something you can easily translate into code. For help with writing pseudocode, take a look at this [pseudocode standard](http://users.csc.calpoly.edu/~jdalbey/SWE/pdl_std.html) example. @@ -58,10 +58,10 @@ Now that you've done all this work, don't forget to sync your changes using the Make sure to edit line 1 to reflect whether you worked on the challenge on your own or with a pair. If you worked with a pair, make sure to put his/her name! ## Release 5: Reflect -In the reflection section of your 'my_solution.js` file, reflect on your learning using the [reflection guidelines](../reflection_guidelines.md). ***NOTE: Reflections are mandatory!*** +In the reflection section of your 'my_solution.js` file, reflect on your learning using the [reflection guidelines](https://github.com/Devbootcamp/phase_0_handbook/blob/master/coding_references/reflection_guidelines.md). ***NOTE: Reflections are mandatory!*** ## Release 6: Review others' Reflections/Solutions. -[Review others' solutions](../reviewing_solutions.md) +[Review others' solutions](https://github.com/Devbootcamp/phase_0_handbook/blob/master/coding_references/review.md) Leave an issue telling the student what they did well and can do better next time with regard to the pseudocode and reflection. Be kind, specific and actionable. (You are expected to leave at least two comments for this challenge). diff --git a/week_3/4_manipulating_js_objects_solo_challenge/readme.md b/week_3/4_manipulating_js_objects_solo_challenge/readme.md index b589ac17..cc04e6dd 100644 --- a/week_3/4_manipulating_js_objects_solo_challenge/readme.md +++ b/week_3/4_manipulating_js_objects_solo_challenge/readme.md @@ -70,7 +70,7 @@ each step, run your code to be certain that the next test has passed. When all of the tests have passed, your final `terah` object will be logged to the console. ## Release 3: Reflect -In the reflection section of your 'my_solution.js` file, reflect on your learning using the [reflection guidelines](../reflection_guidelines.md). ***NOTE: Reflections are mandatory!*** +In the reflection section of your 'my_solution.js` file, reflect on your learning using the [reflection guidelines](https://github.com/Devbootcamp/phase_0_handbook/blob/master/coding_references/reflection_guidelines.md). ***NOTE: Reflections are mandatory!*** ## Release 4: Commit and Sync your changes! Make sure to put everything (pseudocode, initial solution, and reflection) in your [my_solution.js](./my_solution.js) file and sync your changes with your repo on github! diff --git a/week_3/5_design_cc_mission/readme.md b/week_3/5_design_cc_mission/readme.md index 3a64abe8..4f07c325 100644 --- a/week_3/5_design_cc_mission/readme.md +++ b/week_3/5_design_cc_mission/readme.md @@ -16,10 +16,11 @@ This is an open-ended challenge so there are a lot of things you can do with it ## Release 0: Design your Mission -Write an outline of your mission in comments in your [my_solution.js](./my_solution.js) file. Here are some things to think about: +Write an outline of your mission in comments in your [my_solution.js](my_solution.js) file. Here are some things to think about: + 1. Think of some objects and things you would like those objects to do 2. Create a couple objectives (refer to the code combat mission objectives to tailor these to your mission) -3. Hover over the `this` in the code section of any mission. What is it referring to? An object? A function? What kinds of attributes do you want to add to your objects? Create your objects in JavaScript +3. Hover over the `this` in the code section of any mission. What is it referring to? An object? A function? What kinds of attributes do you want to add to your objects? Create your objects in JavaScript. 4. Think of the methods that are necessary to manipulate your objects and add them to your objects. @@ -40,10 +41,10 @@ When you get to the point that your objects and functions are working as well as If you think of a way to improve your code through refactoring, write why you think it's great instead. Do not simply copy the initial solution or leave this section blank, you need to justify the omission of refactoring. ## Release 4: Reflect -In the reflection section of your 'my_solution.js` file, reflect on your learning using the [reflection guidelines](../reflection_guidelines.md). ***NOTE: Reflections are mandatory!*** +In the reflection section of your 'my_solution.js` file, reflect on your learning using the [reflection guidelines](https://github.com/Devbootcamp/phase_0_handbook/blob/master/coding_references/reflection_guidelines.md). ***NOTE: Reflections are mandatory!*** ## Release 5: Review other's solutions -[Review others' solutions](../reviewing_solutions.md) by leaving an issue telling the student what they did well and can do better next time. Be kind, specific and actionable. (You are expected to leave at least two comments for this challenge). +[Review others' solutions](https://github.com/Devbootcamp/phase_0_handbook/blob/master/coding_references/review.md) by leaving an issue telling the student what they did well and can do better next time. Be kind, specific and actionable. (You are expected to leave at least two comments for this challenge). ## Optimize your Learning (Optional) Add your JavaScript objects to an HTML page. Use CSS to make it pretty. What about ascii art? Then look up how to manipulate objects on a page with JavaScript using your functions... \ No newline at end of file diff --git a/week_3/6_group_project/readme.md b/week_3/6_group_project/readme.md index c22c5272..aa80634e 100644 --- a/week_3/6_group_project/readme.md +++ b/week_3/6_group_project/readme.md @@ -70,7 +70,7 @@ When the first person receives the refactored code from the last person, she/he For everyone: When you receive the summary email, send your repo link to the other students in your accountability group. Look at the two people who followed you (go to the top if you're at the bottom) and comment on each. ## Release 5: Reflect -In the reflection section of your formerly named 'my_solution.js` file, reflect on your learning using the [reflection guidelines](../reflection_guidelines.md). Also answer the following: +In the reflection section of your formerly named 'my_solution.js` file, reflect on your learning using the [reflection guidelines](https://github.com/Devbootcamp/phase_0_handbook/blob/master/coding_references/reflection_guidelines.md). Also answer the following: - What was this experience like? - Was your group successful in passing the tests? - What did you learn about writing user stories, pseudocoding, writing code, refactoring, etc.? diff --git a/week_3/8_cultural_blog.md b/week_3/8_cultural_blog.md index b59945fd..6a2fad57 100644 --- a/week_3/8_cultural_blog.md +++ b/week_3/8_cultural_blog.md @@ -1,25 +1,29 @@ [Week 3 Home](./) -# U1.W3: Cultural Blog: Chefs in the Kitchen +# U1.W3: Cultural Blog: Your Thinking Style and Learning ## Learning Competencies -- Consider DBC's culture and approach to learning -- Predict how you will react to DBC's approach +- Research your thinking style +- Consider strategies for adapting your learning to your thinking style ## Release 0: Copy your Blog Template -First, create a new HTML file for your this post in your [USERNAME].github.io website. Create a new HTML file and use the date to name it `week3_cultural_blog.html`. Copy the Code from your `blog_template`. +Copy your blog tempate into a new HTML file named `week9_cultural.html`. -## Release 1: Kitchen vs. Table -Watch [Shereef's Fireside Chat](http://vimeo.com/85001014) +## Release 1: Research -## Release 2: Write your Blog! -Based on the video, what's your take on the DBC experience? What is your impression of DBC? How do you see yourself engaging with this type of culture? -Have your expectations of DBC changed? If so, how? Are you excited to participate in this kind of learning environment? Does it make you nervous? +Remember your [Gregorc Thinking Style](http://web.cortland.edu/andersmd/learning/gregorc.htm) from your pre-Phase 0 work? If you can't remember what you are, retake the [personal thinking style](http://www.thelearningweb.net/personalthink.html) quiz. + +Now research your thinking style and consider how you can use your understanding of your thinking style to your advantage at DBC. + +Consider your experience in Phase 0 to this point. What has been the biggest struggle for you? Is it related to the way you think and learn or is it related to something else. If it's related to your learning style, start thinking of strategies to help you. Put some plans of action in place. -Talk about what came up for you and anything you want in addition to the questions above. +## Release 2: Write your Blog! +Address the questions above in your blog post. + +## Release 3: Publish +Link to your blog on the index of your github.io site and sync your changes. -## Release 3: Submission -Link to your blog on the index of your github.io site and sync your changes. +Share your blog on the google+ community under "Blog Posts!" Read others blogs. What did you like about them? What can you learn from others? -Share your blog on the google+ community under "Blog Posts!" Read others blogs. What did you like about them? \ No newline at end of file +## Release 4: Read at least 2 other students' blog posts. Try to find at least one who has the same thinking style(s) as you. Did they have similar ideas? What do you think it would be like to pair with them? \ No newline at end of file diff --git a/week_3/9_gps1_2/readme.md b/week_3/9_gps1_2/readme.md index b30720ec..46192b4a 100644 --- a/week_3/9_gps1_2/readme.md +++ b/week_3/9_gps1_2/readme.md @@ -76,4 +76,4 @@ try adding something new to your system! Want to manage something new from your Or maybe a way to display/advertise your business? Get in there and Code with the Stars! ## Release 6: Reflect -In the reflection section of your 'my_solution.js` file, reflect on your learning using the [reflection guidelines](../reflection_guidelines.md). ***NOTE: Reflections are mandatory!*** +In the reflection section of your 'my_solution.js` file, reflect on your learning using the [reflection guidelines](https://github.com/Devbootcamp/phase_0_handbook/blob/master/coding_references/reflection_guidelines.md). ***NOTE: Reflections are mandatory!*** diff --git a/week_3/readme.md b/week_3/readme.md index e71606a2..050d2597 100644 --- a/week_3/readme.md +++ b/week_3/readme.md @@ -1,5 +1,7 @@ # Introduction to JavaScript +Please do not start week 2 until May 26. We will make changes to curriculum and update DBC's master repository. + JavaScript is known as the "language of the web." It is a powerful object-oriented language (Ruby is as well). It is light-weight and can communicate with the browser. This week, we will introduce you to basic JavaScript syntax. The goal is not to teach you JavaScript, rather, we want you to feel comfortable with simple variables and functions. You will not begin using JavaScript until Phase 2 in Dev Bootcamp, but don't worry if you feel like you will forget everything. You will have the chance to review in the last two weeks of Phase 0 and the weekend before you begin Phase 2. Moreover, professional programmers look up information and syntax all the time. They don't have everything memorized either, so think of this as an introduction. The more you use JavaScript the more you will remember. For our purposes here, we want you to learn basics so that you can easily re-learn them later. diff --git a/week_3/reflection_guidelines.md b/week_3/reflection_guidelines.md deleted file mode 100644 index afa84728..00000000 --- a/week_3/reflection_guidelines.md +++ /dev/null @@ -1,15 +0,0 @@ -#Reflection Guidelines - -When writing your reflection, write it for an audience. Tell a story of what you tried and what you learned. It will make it easier for you to go back and re-teach yourself or know what you were thinking. - -Remember, your reflections aren't just for teachers, they are for your fellow cohort mates as well, so be generous! You could end up helping a fellow student learn something new. - -Answer the following questions (in addition to the challenge-specific questions) in your reflection: - -* What parts of your strategy worked? What problems did you face? -* What questions did you have while coding? What resources did you find to help you answer them? -* What concepts are you having trouble with, or did you just figure something out? If so, what? -* Did you learn any new skills or tricks? -* How confident are you with each of the Learning Competencies? -* Which parts of the challenge did you enjoy? -* Which parts of the challenge did you find tedious? \ No newline at end of file diff --git a/week_3/reviewing_solutions.md b/week_3/reviewing_solutions.md deleted file mode 100644 index c645c1fb..00000000 --- a/week_3/reviewing_solutions.md +++ /dev/null @@ -1,37 +0,0 @@ -# Reviewing Solutions - -### How to find other solutions -Take a look at some other students' solutions to the challenges. To do this, go to the fork icon at the top of your repo. There -should be a number next to it. Click on the number. It will take you to a graph, but above the graph, there will be a "Members" tab. -Click on it. You should then see all the forks by other students. - -### How to create a new issue -1. Click on "Issues" -2. Click on "New Issue" -3. Write your feedback (with a title) using Markdown. You can preview your markdown by clicking on the "Preview" tab. -4. When you finish, click "Submit new issue" - -### Feedback -Practice writing kind, actionable, specific feedback to other students. - -Here are some sample questions to use: -- If you were going to implement the pseudocode, would it be easy to follow? -- Was the pseudocode detailed enough that you would be able to implement it easily? -- Was the pseudocode verbose? Was it clear? -- Proper Variable Naming - make the variable name descriptive and concise - * Avoid naming variables after the data structure (array, string, arr, hash, hsh, etc) - * Avoid numbered variables (var1, var2, var3) - * Avoid single character names (i, x, n) -- Proper Method Naming - *The name should reflect the method's single responsibility -- Keep it DRY - * Condense repetitive code - * Create new methods to encapsulate common functions -- Did you like the logic? -- Was every variable necessary) -- What did the student do well? -- What could they have done better? -- How was their reflection? -- Did you learn anything from this solution? -- Did they struggle with the same concepts according to their reflection? -- Were you able to tell how they worked through the challenge based on their reflection? \ No newline at end of file