Edward's CS Journey

  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 wi...

  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...

Milestones Accomplished This week, my main contribution to our capstone project was creating app routes in our repository. I created a route that displayed the data pulled in JSON format. Then I tested that the data could be integrated from our database into our frontend application and shared my results with the team. I also wrote documentation to help my team members set up their own database instances using Docker. Next Steps My plans for next week are to integrate database data into the appropriate pages on the front end. I will also be updating the database schema based on our scheduling algorithm and user information. Once completed, I will share my updates with the team via GitHub.  Challenges The challenges we are currently facing primarily concern updating the database schema to support the scheduling algorithm. We are taking the changes step by step, but will eventually have them connected. No instructor assistance is needed yet. 

Milestones Accomplished This week, our team accomplished many milestones. My main contribution was the draft database schema. I created SQL statements based on the schema sketch we developed as a team. In addition, I imported the problem sets we are using into the database, added fake data to the other tables, and provided a test SQL statement to verify that the tables were being joined correctly.  Next Steps My plans for next week are to connect the database to the frontend by creating app routes in our repository. I will test running our database in a Docker container. Once successful, I will write out instructions for the group to implement to connect their databases locally.  Challenges The challenges we are facing right now are the amount of work on each person’s plate. We are doing our best to take on specific tasks while supporting our other team members. No instructor assistance is needed at this point. Our instructor, Dr. Feng, gave us the push we needed at our last m...