(high level overview)
- overview of the project
- explanation of file structure
- instructions for cloning/forking and running the project locally
| What went well? | What could be improved? | What did not go well? | What feedback do you have for your teammate(s) that might help them in future projects/on the job? | |
|---|---|---|---|---|
| Process | Organization! We've made great progress and got a large portion of the MVP done. Mostly really solid communication for PRs. Everyone is working really hard. | Planning of tasks and communicating what everyone is working on could be improved. We may have wasted some time because people were working on redundant tasks. Utilizing github for communication could be better. Specifically, we could be using "request changes" in a PR review in order to better communicate changes. | Sage wishes she had reached out to Dione sooner about OAuth problems and feels she has wasted a lot of time of it. Jack: making assumptions about what our API is going to return which would have been helpful for building out database table for obituaries. Stella: not clear on what functionality I could be |
My parents and grandparents used to read the obituary section of the newspaper everyday. They would discuss the people who they knew or knew of, send condolences to the next of kin, and make plans to go to the funeral. Have you ever been scrolling mindlessly through Facebook only to discover that someone you know died? It is shocking and traumatic. Death notifications don't belong interspersed amongst the nonsense of social media. They belong on their own platform; one that is built with the dignity of the deceased in mind. Obituary Hub will be a social platform built to pay respect to the deceased, celebrate their lives, send condolences to the next of kin, and where those interested in contemplating death and impermanence can go to read obituaries.
Template for DTR
Project: Brownfield of Dreams (Nightmares?)
Group Member Names: Stella Bonnie & Ross Perry
Project Expectations:
What does each group member hope to get out of this project?
check_it algorthim checking?It is checking if each opening and closing bracket, paranethesis, or curly brace in a pair are present, by setting the opening character as a key and the closing character as a value in the open_close method. It returns true or false based on whether both in the pair are present and nested properly.
This algorithm might be what is underlying the errors that Ruby returns (and the linter detects in atom) when we forget to use close all of our hashes and arrays and nested stuff properly.