Link to peer grade
Runtime link
Team contributions
- This trimester was pretty difficult in a group point a view, I switched in and out of groups 3 times. Meaning that in the time that people were working on their own project I was busy getting adjusted to the team I was just transferred to. I joined this group 2 weeks prior to the final. Meaning I had 1 week to get ready for N@TM and 2 weeks to get ready for the final review. This posed some challenges for me but regardless I still made sure that I was a useful attribute to the team.
- My commits for this trimester
- Helped Yasha create a schema table with SQlite that could generate/regenerate data tables without any duplicates.
- Worked around group filling in for anyone who was absent the day and do their work for them.
Final review
As I reflect on my experience during this trimester of school, it is clear that I faced some significant challenges. One of the most prominent difficulties I encountered was the constant change in teams, which made it challenging to get work done. As I switched between different groups, I had to adjust to new team dynamics and work processes, which could be time-consuming and frustrating.
Another challenge I faced was that the work I did get done would have to change due to the different groups. Each group had its own approach to completing tasks and achieving goals, which meant that I had to constantly adapt and adjust my work to fit each group's specific requirements. This often resulted in me redoing or tweaking assignments, which was time-consuming and caused me to fall behind on other tasks.
Finally, I also struggled with group members constantly being absent. Whether it was due to illness, personal reasons, or other commitments, having group members who were frequently absent made it difficult to coordinate and complete work effectively. This often led to delays in completing tasks or incomplete work, which added to my workload and stress levels.
Overall, this trimester was challenging due to the constant changes in teams, the need to adapt to different group dynamics and work processes, and the struggle with absent group members. However, I learned valuable lessons about communication, flexibility, and adaptability that I can carry with.
Technical Feature
My feature was a news page in which users can like and dislike certain stock news, if they were too do one of these is would prompt them to fill in a field explaining why they gave that review.
To pull stock news API on my webpage, I followed these steps:
I searched for a reputable and reliable API provider that offered the stock news data I needed. Some popular options included Yahoo Finance, Google Finance, and Bloomberg.
I obtained an API key from the provider. This was usually done by registering for an account on their website, creating an API key, and specifying the endpoints I planned to use.
Using a programming language or web development framework, I made an HTTP request to the API endpoint using the API key. The API typically responded with a JSON or XML formatted data containing the latest stock news updates.
I then parsed the response data and extracted the relevant information, such as the stock name, news headline, date, time, and article link.
To display the stock news updates on my webpage in a user-friendly format, I used HTML, CSS, and JavaScript.
However, there were some difficulties I encountered while pulling a stock news API on my webpage, including:
API Limits: Most API providers had usage limits that restricted the number of API requests I could make in a given period. Therefore, I needed to ensure that my webpage code was optimized to minimize unnecessary API requests and stay within the usage limits.
API Changes: API providers may have updated their API endpoints, changed their response formats, or revoked API keys, which could have broken my webpage code. Therefore, I needed to keep track of any API changes and update my webpage code accordingly.
Security: When using an API key to access a stock news API, I needed to ensure that the API key was kept secure and not exposed to the public. I did this by storing the API key in a secure location, such as a server-side environment variable, and taking other security measures to protect it.
Link to peer grade
Runtime link
Team contributions
Final review
As I reflect on my experience during this trimester of school, it is clear that I faced some significant challenges. One of the most prominent difficulties I encountered was the constant change in teams, which made it challenging to get work done. As I switched between different groups, I had to adjust to new team dynamics and work processes, which could be time-consuming and frustrating.
Another challenge I faced was that the work I did get done would have to change due to the different groups. Each group had its own approach to completing tasks and achieving goals, which meant that I had to constantly adapt and adjust my work to fit each group's specific requirements. This often resulted in me redoing or tweaking assignments, which was time-consuming and caused me to fall behind on other tasks.
Finally, I also struggled with group members constantly being absent. Whether it was due to illness, personal reasons, or other commitments, having group members who were frequently absent made it difficult to coordinate and complete work effectively. This often led to delays in completing tasks or incomplete work, which added to my workload and stress levels.
Overall, this trimester was challenging due to the constant changes in teams, the need to adapt to different group dynamics and work processes, and the struggle with absent group members. However, I learned valuable lessons about communication, flexibility, and adaptability that I can carry with.
Technical Feature
My feature was a news page in which users can like and dislike certain stock news, if they were too do one of these is would prompt them to fill in a field explaining why they gave that review.
To pull stock news API on my webpage, I followed these steps:
I searched for a reputable and reliable API provider that offered the stock news data I needed. Some popular options included Yahoo Finance, Google Finance, and Bloomberg.
I obtained an API key from the provider. This was usually done by registering for an account on their website, creating an API key, and specifying the endpoints I planned to use.
Using a programming language or web development framework, I made an HTTP request to the API endpoint using the API key. The API typically responded with a JSON or XML formatted data containing the latest stock news updates.
I then parsed the response data and extracted the relevant information, such as the stock name, news headline, date, time, and article link.
To display the stock news updates on my webpage in a user-friendly format, I used HTML, CSS, and JavaScript.
However, there were some difficulties I encountered while pulling a stock news API on my webpage, including:
API Limits: Most API providers had usage limits that restricted the number of API requests I could make in a given period. Therefore, I needed to ensure that my webpage code was optimized to minimize unnecessary API requests and stay within the usage limits.
API Changes: API providers may have updated their API endpoints, changed their response formats, or revoked API keys, which could have broken my webpage code. Therefore, I needed to keep track of any API changes and update my webpage code accordingly.
Security: When using an API key to access a stock news API, I needed to ensure that the API key was kept secure and not exposed to the public. I did this by storing the API key in a secure location, such as a server-side environment variable, and taking other security measures to protect it.