CST 489/499 Week 12 Learning Journal

-

 Milestones Accomplished

This week, my main contribution to our capstone project was developing a way to make our code editor functional. Right now, we are using Piston to test a user's code and need to provide feedback on the test cases. I created another table that held information that accompanied the problem, which allowed Piston to return the results of running the user code. I also modified the frontend so that the user was informed whether all test cases passed and, if not, what errors occurred. 

In addition, I corrected database errors that prevented information from being displayed and removed issues incompatible with our current database setup. 

Finally, I tested another team member's authorization branch and created instructions that any developer could follow to set up authentication and authorization in the database. 

Next Steps

My plans for next week are to continue providing feedback on other team members' GitHub PRs. There are quite a few open. I will also add the functionality to our dev branch to ensure everything works properly. In addition, I hope to set up the first few slides for our presentation in preparation for the outline due in Week 14. 

Challenges

The challenge we are currently facing is the merging of our work. Many of us have been working on specific parts of the code and making PRs. After they are approved, they are pushed into dev/main. However, we have not been the best at keeping our branches up to date when this happens, which is leading to some functional issues in the new features we are developing. We have discussed this in our group and have developed a workflow to prevent this issue in the future. No assistance is needed from our instructor at this time.

Comments

Post a Comment

Popular posts from this blog

CST 438 Week 6 Learning Journal

-
Image
Compute as a Service An example of CaaS This week, we were assigned to read the chapter Compute As A Service from Software Engineering at Google . When the code is production-ready, it is important to find a compute service that will meet the organization's needs and follow best practices. Some best practices of a compute service include automation, workload types, data handling, and implementing distributed system concepts.  The first best practice for a service is to leverage automation. In this case, we are referring to handling failures such as container crashing or dealing with an unhealthy job or machine. Containers and machines should be used as "cattle" for services to be healthy, which means that when one crashes, another can pick up the job and continue forward.  The next best practice is handling different types of workloads. A service should be designed to handle batch jobs and serving jobs. Batch jobs are short-lived jobs that are split into small chunks by ...
Read more

CST 489/499 Week 11 Learning Journal

-
  Milestones Accomplished This week, my main contribution to our capstone project was to convert our data-fetching logic to use server-side rendering (SSR) instead of client-side fetching. Previously, I was using `useEffect`  on the client to load data, which could expose sensitive information in our API calls. I refactored the logic by creating a server-side function that securely retrieves the data on the server and then passes it to the client component as props for rendering. This helps protect sensitive data and improves initial load performance. In addition, I helped a team member implement authentication with Supabase. We successfully created a new account using Supabase Authentication and simulated logging in and out.  Next Steps My plans for next week are to update the database so that the Supabase Authentication table is properly linked to our User table. I also plan to revise the User table structure to focus on user-specific profile information rather than aut...
Read more

CST 334 Week 1 Journal Entry

-
Image
Week 1: Introduction to Operating Systems One of the main topics that I learned about this week in CST 334 was operating systems and the role they play in running programs. Operation Systems have two main tasks. One of the tasks is to provide an abstraction layer to the user. This layer shields hardware information from the user, as the user should not have access to it. In addition to the layer of abstraction, the operating system also acts as a resource manager. It optimizes the use of the resources in a computer while allocating them to each program in a fair and equitable manner.  Both of these tasks are completed with the help of two modes provided by the CPU: kernel mode and user mode. While in user mode, the information about the hardware is hidden, and the user is provided an address space to do the intended job. This mode provides the user with access to user, application, and system programs. While in kernel mode, the administor has access to hardware and can change the m...
Read more