Skip to content

Instantly share code, notes, and snippets.

@saberg1
Last active April 21, 2021 20:37
Show Gist options
  • Save saberg1/dc4df8ea74a1c57ef66ae82b4563bade to your computer and use it in GitHub Desktop.
Save saberg1/dc4df8ea74a1c57ef66ae82b4563bade to your computer and use it in GitHub Desktop.
Paired Project Reflection Gist
** Intention Timer - Group Project **
What is one personal/professional takeaway from this project?
- To allow breathing space, be it taking breaks or walking away for the night to allow for a refreshed eyes to look at the same problem.
What is one technical takeaway from this project?
- To investigate more into my available resources and take adnvatage of all infront of me.
Based on these takeaways, what is something you want to focus on for the next project?
- With my next project being the final solo, i will be focusing more on time mangement to allow for my breaks to not feel rushed when doing the project
One technical challenge we faced as a group was getting the timer to function.
- Instead of the three of us trying to get one function to operate correct, we decided to just tackle the problem solo and whom ever can come up with a solution, tell the group and then explain to us how you came to the conclusion so it could be a learning experience for us all. When Ashton showed us her solution it became so clear how.
What is your approach to working on a team?
- My approach to all teams is to allow everyone to speak and be heard so all the ideas can be put into consideration so we can have a good starting place to attack and solve the problem.
** RomCom - Paired Project**
This was our first time to work with another developer and actually make a product. We had to maniuplate the DOM to display only the objects seletected by the user. We only had to code for the JavaScript on this project.
It was the second to last day of the project and my partner suggested we just torch the project and start over. After being very adament about our work that is already done, i was able to convince him that all was needed was a line by line reading of the code to find out where the bug was that was causing havoc on our application.
Anytime faced with what seems an unsovlable problem is the best time for self improvement. First i always try to search for a solution through the internet. Either it be scouring the MDN or stackoverflow trying to find a solution that best fits my requirements. But if all else fails, I know I have a great support team that will always point me in the right direction. That team being my mentor and rock.
To never, ever have a variable the same name. It cause so many errors until we could track it down and rectify the problem. My next project I will be sure to not convolute the variable naming of the code.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment