Month: October 2022

I am half way through my final quarter and it hasn’t hit me yet that I will be graduating in about a month! Another thing I still can’t believe is that I was able to secure a job before I graduated. I can finally call myself a SWE! I start my job in Jan. Remote work out of Seattle. This leaves me a month of “free time” in which I do plan on refreshing myself with the tech stack I used during my internship that led to the job offer.

Switching gears to my classes, I am fortunate that CS381 releases their modules a few weeks ahead. I am currently on week 8 of the modules. This helps me focus more time to working on my capstone project which is seeing an uptick in the amount of work each week. My capstone project is very Docker heavy and luckily I do have some experience working with it. However, what does take time is getting myself familiar with their codebase. At this point in time, I feel that I have an understanding of how the codebase’s individual parts work, but still need to figure out how to connect them all together.

My teammates have been great and very communicative. We have all made progress, albeit slowly, on the parts of our project (frontend/backend) that we are responsible for. On top of that, we also started to meet an extra 2 days/week (3 total) as sort of a checkup on where we are at or if any of us need help. These are all good signs in completing a project!

I’m about a quarter of the way through my final quarter at OSU and I could not be more excited. For the first three weeks, I was able to get a few weeks ahead of the modules in CS381. The class has been really interesting and informative so far. I do admit I spent a little too long on the first two labs, but apparently each successive lab gets easier.

Looking at CS467, the first few weeks have been a little slow for our team as our sponsor and lead engineer have been slowly giving us their requirements and access to their repo. We signed the NDA monday of this week and just received access to their github repo today which my team and I will familiarize ourselves with their codebase. Very exciting stuff!

My team will present our functional requirements to them tomorrow morning in which then they would be able to paint us the true picture of what they expect and/or want out of the capstone. Me and my team have been waiting to get started and excited to get to work, despite the time crunch we are under due to starting a little later.

Only issue I see there being is the due dates and requirements of Progress Report #1. The requirements ask for a video of our progress, however, with only 2-3 days between us “starting” after our meeting with the sponsors and the actual due date of the Report, the video will have minimal content. This is something I will bring up to our TA, who has been really understanding, flexible, and great with their communication.