| Date | Week | Topic |
|---|---|---|
| Week 01 | ||
| Week 02 | ||
| Week 03 | ||
| Week 04 | ||
| Week 05 | ||
| Week 06 | ||
| Week 07 | ||
| Week 08 | ||
| Week 09 | ||
| Week 10 | ||
| Week 11 | ||
| Week 12 | ||
| Week 13 | ||
| Week 14 | ||
| Week 15 | ||
| Week 16 | ||
| GRADUATION |
| Time | Topic |
|---|---|
| 1:00 - 1:30 | Stand Up |
| 1:30 - 2:00 | OS Contribution Kickoff |
| 2:00 - 3:00 | Learn how to judge Apps for Good w/Karen & Peter |
| 3:00 - 3:30 | One on one : Internship Talk & Reviewing Apps for Good |
| 3:30 - 4:00 | Internship Reflection Survey |
| 4:00 - 5:00 | Week 1 Retrospective |
To give back to the community and to help keep up on code, try to identify an open source opportunity that you can work on. Start by reading 8 simple steps for contributing to open source Then try to find a project to work on, which can be difficult, here are some ways to get
- Code Triage and Open Hatch are great tools to help search for projects
- Find a suitable bug or request on Github Issues
- If you ever wished "Geee... I wish gem X did Z", that may be a good oppurtunity to communiciate with the author about adding the feature.
- Whenever you experience a plain ol' bug in a gem, fix it and submit a pull request.
If you find a project that would allow for multiple contributors or pairing, share!
| Time | Topic |
|---|---|
| 1:00 - 4:00 | One on One Review of Internship* |
| 1:00 - 2:00 | Apps for good reviews |
| 2:00 - 4:00 | Language swap / OS / Personal Project time |
| 4:00 - 5:00 | Week 1 Retrospective |
This week will will spend most of our time doing two things:
- Taking time to expand our knowledge through focused work, we will often have time on Thursdays for this kind of thing, ongoing ideas are totally acceptable here:
- Meet with other who are learning that same new language as you
- Code review any open source code from your company (keep your NDA in mind)
- Code review personal projects
- Start a small project together, this could be a Hello World app or something to work on over the course of your entire internship
- Identify and contribute to an open source project
- Begin or continue a personal project
- Meet with other who are learning that same new language as you
- Meeting with an instructor to review your internship experience. Plan to talk about:
- Issues that you see arising
- Your understanding of your role as a developer
- The technical problems you face
- Your contributions so far
*One on ones will be during the other activities
REMINDER Headcount for luncheon.
| Time | Topic |
|---|---|
| 1:00 - 5:00 | One on One Review of Internship* |
| 1:00 - 3:00 | Apps for good reviews |
| 3:00 - 4:00 | Language swap / OS / Personal Project time |
| 4:00 - 5:00 | Week 3 Retrospective |
This week will will spend most of our time doing three things:
- Review Apps for good apps.
- Each student should review 10 additional apps (or until all apps have at least 3 reviews)
- Two groups of three should tackle the technical submissions together.
- Taking time to expand our knowledge through focused work, we will often have time on Thursdays for this kind of thing, ongoing ideas are totally acceptable here:
- Meet with other who are learning that same new language as you
- Code review any open source code from your company (keep you NDA in mind)
- Code review personal projects
- Start a small project together, this could be a Hello World app or something to work on over the course of your entire internship
- Identify and contribute to an open source project
- Begin or continue a personal project
- Meet with other who are learning that same new language as you
- Meeting with an instructor to review your internship experience. Plan to talk about:
- Issues that you see arising
- Your understanding of your role as a developer
- The technical problems you face
- Your contributions so far
*One on ones will be during the other activities
| Time | Topic |
|---|---|
| 1:00 - 2:00 | One on One Review of Internship* |
| 1:00 - 4:00 | Independent Project / Study |
| 4:00 - 5:00 | Week 4 Retrospective |
To give back to the community and to help keep up on code, try to identify an open source opportunity that you can work on. Start by reading 8 simple steps for contributing to open source Then try to find a project to work on, which can be difficult, here are some ways to get
- Code Triage and Open Hatch are great tools to help search for projects
- Find a suitable bug or request on Github Issues
- If you ever wished "Geee... I wish gem X did Z", that may be a good oppurtunity to communiciate with the author about adding the feature.
- Whenever you experience a plain ol' bug in a gem, fix it and submit a pull request.
If you find a project that would allow for multiple contributors or pairing, share!
- 42 Data Structures in 42 days
- SQL Puzzles see SQLFiddle
- Create NPM Logo in CSS see CodePen
- Create a web framework gem that can deploy on Heroku using Rack
| Time | Topic |
|---|---|
| 1:00 - 2:00 | Ada Apps Sign Up |
| 2:00 - 4:00 | Language Primer |
| 4:00 - 5:00 | Info Session Prep (no retro) |
Write a primer for future students who may be learning the language and/or frameworks that you are currently learning. Include:
- Layperson introduction with some of the specs, strengths, and use cases
- Resources for installation and getting started
- "Hello World" tutorial of the language
- A list of common problems or errors that were difficult to understand or find solutions (be very specific)
- Anything that you wish someone would have told you before you started.
To get started clone the Ada repo.
Create a new markdown file for the topic that you want to write about, the name
of the file should be descriptive of what you are covering python-django.md.
Feel free to push your file up at any time. If there are conflicts in file names,
then please rename your file being more specific or simply putting a -2 at the end.
- 42 Data Structures in 42 days
- SQL Puzzles see SQLFiddle
- Create NPM Logo in CSS see CodePen
- Create a web framework gem that can deploy on Heroku using Rack
| Time | Topic |
|---|---|
| 1:00 - 1:30 | Week 6 Internship Survey |
| 1:30 - 4:00 | Language Primer |
| 4:00 - 5:00 | Retro |
Write a primer for future students who may be learning the language and/or frameworks that you are currently learning. Include:
- Layperson introduction with some of the specs, strengths, and use cases
- Resources for installation and getting started
- "Hello World" tutorial of the language
- A list of common problems or errors that were difficult to understand or find solutions (be very specific)
- Anything that you wish someone would have told you before you started.
To get started clone the Ada repo.
Create a new markdown file for the topic that you want to write about, the name
of the file should be descriptive of what you are covering python-django.md.
Feel free to push your file up at any time. If there are conflicts in file names,
then please rename your file being more specific or simply putting a -2 at the end.
- 42 Data Structures in 42 days
- SQL Puzzles see SQLFiddle
- Create NPM Logo in CSS see CodePen
- Create a web framework gem that can deploy on Heroku using Rack
| Time | Topic |
|---|---|
| 1:00 - 4:00 | Review Applications* |
| 1:00 - 4:00 | Open Work Hours |
| 4:00 - 5:00 | Retro |
*As of 6/18 we have completed 598 reviews, I estimate that we will need to complete about 1,000 to have full coverage (~5 reviews/submission) for round 1. If everyone completes 33 additional reviews we will be done!
After completing reviews (or if you've completed > 100 already) then feel free to work on anything you want. Some students have asked for the opportunity to pair and get help on problems they are having, this kind of in-class free time is always a good time for this kind of work. Alternately you can work on the project listed below.
Write a primer for future students who may be learning the language and/or frameworks that you are currently learning. Include:
- Layperson introduction with some of the specs, strengths, and use cases
- Resources for installation and getting started
- "Hello World" tutorial of the language
- A list of common problems or errors that were difficult to understand or find solutions (be very specific)
- Anything that you wish someone would have told you before you started.
To get started clone the Ada repo.
Create a new markdown file for the topic that you want to write about, the name
of the file should be descriptive of what you are covering python-django.md.
Feel free to push your file up at any time. If there are conflicts in file names,
then please rename your file being more specific or simply putting a -2 at the end.
- 42 Data Structures in 42 days
- SQL Puzzles see SQLFiddle
- Create NPM Logo in CSS see CodePen
- Create a web framework gem that can deploy on Heroku using Rack
| Time | Topic |
|---|---|
| 1:00 - 4:00 | Open Work Hours |
| 4:00 - 5:00 | Retro |
Work on anything that you would like
Write a primer for future students who may be learning the language and/or frameworks that you are currently learning. Include:
- Layperson introduction with some of the specs, strengths, and use cases
- Resources for installation and getting started
- "Hello World" tutorial of the language
- A list of common problems or errors that were difficult to understand or find solutions (be very specific)
- Anything that you wish someone would have told you before you started.
To get started clone the Ada repo.
Create a new markdown file for the topic that you want to write about, the name
of the file should be descriptive of what you are covering python-django.md.
Feel free to push your file up at any time. If there are conflicts in file names,
then please rename your file being more specific or simply putting a -2 at the end.
- CodeWars
- 42 Data Structures in 42 days
- SQL Puzzles see SQLFiddle
- Create NPM Logo in CSS see CodePen
- Create a web framework gem that can deploy on Heroku using Rack
| Time | Topic |
|---|---|
| 1:00 - 4:00 | Primers (due today) |
| 4:00 - 5:00 | Retro |
Write a primer for future students who may be learning the language and/or frameworks that you are currently learning. Today the following minimum will be due:
- Layperson introduction with some of the specs, strengths, and use cases
- Install guide and/or notes on expected preinstalled tools (only for dependencies)
- "Hello World" (or equivalent) tutorial
- A link to the official docs and at least 3 other resources
To get started clone the Ada repo.
Create a new markdown file for the topic that you want to write about, the name
of the file should be descriptive of what you are covering python-django.md.
Feel free to push your file up at any time. If there are conflicts in file names,
then please rename your file being more specific or simply putting a -2 at the end.
- CodeWars
- 42 Data Structures in 42 days
- SQL Puzzles see SQLFiddle
- Create NPM Logo in CSS see CodePen
- Create a web framework gem that can deploy on Heroku using Rack
| Time | Topic |
|---|---|
| 1:00 - 4:30 | Open Source Project |
| 4:30 - 5:00 | Retro |
Bookis and Elise are going to be in cohort 2 interviews until 3:30. We'll have interviewees coming into the classroom, so feel free to chat - but don't divulge any secrets! ;) Otherwise, please get started on the Open Source Project:
Over the next 6 weeks, you'll be spending the majority of your Ada class time contributing to an open source project of your choice. This project is meant to give you some dedicated time to work on and give back to the OSS community (without OSS, we wouldn't have been able to teach Ruby in class)!
- Depending on the size/scope of the contribution, submit a minimum of one pull request to an OSS project or library no later than 8/27.
- Complete 3 blog posts about the project: one due this week (selecting/starting OSS project), one due 8/6 (check in on progress), and one due at the completion of the project on 8/27 (retrospective).
- Prepare a 5 minute talk about the project/library and your contribution to present during Cohort 2's first week of class (9/2-9/5).
Read 8 simple steps for contributing to open source and How to contribute to an open source project. Then, try to find at least one project that's interesting and needs help. (At least one because you may want to have a couple of options if one goes nowhere). If you find a project that would allow for multiple contributors or pairing, share! If you've already been contributing to an open source project and would like to continue, you are welcome to do so.
Check out the below tools to get started:
- Code Triage and Open Hatch are great tools to help search for projects.
- Find a suitable bug or request on Github Issues
- If you ever wished "Geee... I wish gem X did Z", that may be a good opportunity to communicate with the author about adding the feature. Occasionally, libraries will have contribution protocols in the project README.
- Experienced a plain ol' bug in a gem? Fix it and submit a pull request.
- Advice from the internet: RubyGems Adoption Center RailsBridge's BridgeTroll project Django: Andrew from Foundry has offered to help anyone interested in contribution. KDE and GNOME projects: Ian can help get you started. RSpec
Write about your experience searching for an OSS project and submit URL to Canvas. What was appealing about projects? What made the search difficult? What project(s) are you planning to contribute to, and why?
| Time | Topic |
|---|---|
| 1:00 - 3:00 | Open Source Project |
| 3:00 - 3:30 | Lightning Talks (Sign up on board) |
| 3:30 - 4:00 | HHH's & Liz Cascadia Talk |
| 4:00 - 5:00 | Retro |
Over the next 6 weeks, you'll be spending the majority of your Ada class time contributing to an open source project of your choice. This project is meant to give you some dedicated time to work on and give back to the OSS community (without OSS, we wouldn't have been able to teach Ruby in class)!
- Depending on the size/scope of the contribution, submit a minimum of one pull request to an OSS project or library no later than 8/27.
- Complete 3 blog posts about the project: one due this week (selecting/starting OSS project), one due 8/6 (check in on progress), and one due at the completion of the project on 8/27 (retrospective).
- Prepare a 5 minute talk about the project/library and your contribution to present during Cohort 2's first week of class (9/2-9/5).
Read 8 simple steps for contributing to open source and How to contribute to an open source project. Then, try to find at least one project that's interesting and needs help. (At least one because you may want to have a couple of options if one goes nowhere). If you find a project that would allow for multiple contributors or pairing, share! If you've already been contributing to an open source project and would like to continue, you are welcome to do so.
Submit on Canvas. Write about your experience so far. What project did you choose? What progress have you made so far? Has any thing been easier than you would have assumed? Has anything been more difficult than you anticipated? If so how are you solving the problem? Are you working with others? etc...
| Time | Topic |
|---|---|
| 1:00 - 1:30 | Cohort 2 Admin |
| 1:30 - 3:30 | Open Source Project (Blog Post #2 Due) |
| 3:30 - 4:00 | 90 Day form Review |
| 4:00 - 5:00 | Retro |
- Classroom Mentors
- Schedules
- Brainstorming
Over the next 6 weeks, you'll be spending the majority of your Ada class time contributing to an open source project of your choice. This project is meant to give you some dedicated time to work on and give back to the OSS community (without OSS, we wouldn't have been able to teach Ruby in class)!
- Depending on the size/scope of the contribution, submit a minimum of one pull request to an OSS project or library no later than 8/27.
- Complete 3 blog posts about the project: one due this week (selecting/starting OSS project), one due 8/6 (check in on progress), and one due at the completion of the project on 8/27 (retrospective).
- Prepare a 5 minute talk about the project/library and your contribution to present during Cohort 2's first week of class (9/2-9/5).
Read 8 simple steps for contributing to open source and How to contribute to an open source project. Then, try to find at least one project that's interesting and needs help. (At least one because you may want to have a couple of options if one goes nowhere). If you find a project that would allow for multiple contributors or pairing, share! If you've already been contributing to an open source project and would like to continue, you are welcome to do so.
Submit on Canvas. Write about your experience so far. What project did you choose? What progress have you made so far? Has any thing been easier than you would have assumed? Has anything been more difficult than you anticipated? If so how are you solving the problem? Are you working with others? etc...
| Time | Topic |
|---|---|
| 1:30 - 4:00 | Open Source Project |
| 4:00 - 5:00 | Retro |
Over the next 6 weeks, you'll be spending the majority of your Ada class time contributing to an open source project of your choice. This project is meant to give you some dedicated time to work on and give back to the OSS community (without OSS, we wouldn't have been able to teach Ruby in class)!
- Depending on the size/scope of the contribution, submit a minimum of one pull request to an OSS project or library no later than 8/27.
- Complete 3 blog posts about the project: one due this week (selecting/starting OSS project), one due 8/6 (check in on progress), and one due at the completion of the project on 8/27 (retrospective).
- Prepare a 5 minute talk about the project/library and your contribution to present during Cohort 2's first week of class (9/2-9/5).
Read 8 simple steps for contributing to open source and How to contribute to an open source project. Then, try to find at least one project that's interesting and needs help. (At least one because you may want to have a couple of options if one goes nowhere). If you find a project that would allow for multiple contributors or pairing, share! If you've already been contributing to an open source project and would like to continue, you are welcome to do so.