Weekly Project Post #2

Investment portfolio tracker development update

By Matthew Presti

What did you do last week?

My main accomplishment this week was finalizing my project idea. I am building an investment portfolio tracker using Spring Boot and Java. This combines my interest in financial technology with the opportunity to gain experience with enterprise Java development.

I completed my project proposal and created a weekly schedule that breaks down the development process into manageable chunks. I also compiled learning resources for Java and Spring Boot, including documentation, tutorials, and Stack Overflow threads for common implementation challenges.

On the design front, I’m currently working on the initial system architecture by creating entity relationship diagrams for my core data models (User, Portfolio, Stock, and Transaction entities).

I also overhauled my portfolio website with a cleaner, professional template that will better showcase this project’s progress.

What do you plan to do this week?

This week my aim is to transition from planning to building. I’ll set up my development environment by installing JDK 17+, IntelliJ IDEA, and Maven, then create the initial Spring Boot project with essential dependencies (Web, JPA, H2 database, and Security).

On the development side, I plan to implement the core REST API structure by creating basic controller classes and getting the first GET and POST endpoints working for my main entities.

Are there any impediments in your way?

The biggest challenge is the project’s scope–building a full-stack investment tracker is ambitious, and the learning curve for Java and Spring Boot feels somewhat steep. Time management is also challenging with other coursework and life commitments. Finding consistent blocks of focused development time remains challenging.

Reflection on the process you used last week, how can you make the process work better?

The extensive planning phase was the right approach - having a detailed timeline makes the project feel more manageable. However, I may have spent too much time perfecting the proposal and my website instead of doing more tangible work on the project itself. Moving forward, I plan to implement a more iterative approach–get something basic working, then refine and expand.

For this week, I’ll try shorter, more frequent coding sessions rather than waiting for large time blocks. I’m also planning to document progress more frequently with screenshots and brief notes about challenges encountered. I think documenting and being able to explain my decision making process will be great practice for job interviews.