Fin

As I close this final chapter of my CS undergraduate academic career, the only things I can say are that I'm tired and that it finally paid off! I've absorbed a ton, especially the core concepts that'll serve as my foundation going forward. It's changed how I think and approach problems, both in tech and life.

Next up: landing a software engineering position. I've got some side project ideas I want to develop in my spare time, maybe turn them into something profitable. Down the road, I'm considering a master's in robotics. We'll see where this journey takes me.

Capstone Project: Journal 7

As I approach the end of this CS program I have been a part of, and the project I have been working on, week 15 brought significant progress to our project. I focused on polishing existing features and giving the app a fresh, updated look. It's impressive how much far the DKOMP project has come since the initial design phase, and implementation.

Looking ahead to our final week, my goal is to tie up any loose ends and ensure the project is in a state that allows for future development. I wish I could do more but I simply don't have enough time anymore.

During week 15, time management was a challenge, with the deadline creating some pressure.

Capstone Project: Journal 6

Week 14 marked significant progress on the dkomp project, as I focused on enhancing performance and successfully integrated websockets. The journey wasn't without issues, however, as I found myself juggling multiple tasks simultaneously, learning new concepts, getting rid of bugs, and trying my best to push the project forward.

By the end of week 15 refining the existing features was the main focus.

The main challenge I faced during week 14 was the need to rapidly learn new things while maintaining project momentum.

Capstone Project: Journal 5

This week, I assisted in setting up an Express API backend for the projects and overcame some technical issues we were having. We've made significant progress, and for the upcoming week, I plan on continuing to develop the backend communication for the project. Additionally, I'm planning to improve the overall look of the application to enhance its appearance.

At this stage, we/I am not facing many significant challenges. Most of the technical hurdles have been resolved, which is a very good thing. The main focus now is completing all necessary tasks within the limited time remaining.

Capstone Project: Journal 4

This past week I focused on refactoring my code for my DKOMP capstone project, improving its modularity and flexibility. The main accomplishment was successfully merging the different proof-of-concept chart branches from my teammates into one cohesive whole.

For the upcoming week, my goal is to complete many of the half-finished core features. If time allows, I'll also start working on some of the optional features we've discussed. So far, the project has progressed smoothly without any significant challenges. I'll continue to update on the project's development as it moves forward.

Capstone Project: Journal 3

 Last week saw some progress on the DKOMP capstone project. I managed to implement reading from the graph API and established the coordinate system for the main chart, which forms the project's foundation. Additionally, I built nodes for the chart using the graph API.

For the upcoming week, the focus will be on merging different code from various proofs of concept into a single branch, improving the integration between the backend and frontend chart, and continuing feature development. While there haven't been major challenges so far, the time constraint remains a factor, given the amount of work still to be done. However, it seems manageable at this point.

Capstone Project: Journal 2

This Week

I worked on the interactive chart for the project I'm building with my team. I was able to devise a solution for correctly detecting the positioning of each node within the chart. This was a huge win because it is one of the fundamental pieces for this project to work. Almost everything related to the interactivity of this project depends on successfully detecting the positioning of the nodes. There were many challenges, particularly dealing with edge cases, but I overcame them by stepping back, reevaluating the problem and my solution, and identifying the necessary changes. 

Next Week

I plan to continue working on the ruler that goes along with the chart on the left-hand side. The ruler is heavily dependent on the chart and the ability to detect where the nodes are located. This ruler is similar to a Y-axis legend on an interactive financial chart. It needs to stretch to reveal more detailed information as you zoom in and shrink to provide an overview as you zoom out of the chart.

Challenges

The only challenges I'm currently facing are technical ones. These do not require the instructor's involvement; they are general problem-solving obstacles that I will overcome as I become more familiar with the technology I'm implementing.