ExpenseTracker banner

ExpenseTracker

Created by: jan.zdan1234
3 devlogs
11h 41m 49s

This project is an expense tracker built with Symfony, used as a learning vehicle for backend fundamentals rather than just a finance app. It focuses on core concepts like domain modeling, persistence with Doctrine, validation, security, and clean…

This project is an expense tracker built with Symfony, used as a learning vehicle for backend fundamentals rather than just a finance app. It focuses on core concepts like domain modeling, persistence with Doctrine, validation, security, and clean architecture. By keeping the business domain simple, the project lets you practice real backend structure, not just framework syntax.

This project uses AI

I am using AI to find how to make a good architecture, i am just asking it how something should be done and i implement this in code

Repository
jan.zdan1234
jan.zdan1234 worked on ExpenseTracker
about 1 month ago
8h 0m logged

I added few dtos, few methods in repositories and i think i added everything in services phase so now i need to make controllers then frontend and production. I did quite a lot and i forgot to post some devlogs sorry. The best part i did is i think BudgetAlertService it was interesting to make :).

Attachment
0
jan.zdan1234
jan.zdan1234 worked on ExpenseTracker
about 1 month ago
0h 23m logged

I added new entity and wrote what i will be doing in future in my README.md file in order to have everything planned and ready to code.

Attachment
0
jan.zdan1234
jan.zdan1234 worked on ExpenseTracker
about 1 month ago
3h 17m logged

Added authentication flow (register, login, refresh token) with DTO-based validation and basic security constraints. The auth layer is now stable enough to unblock further work. Next focus is shifting away from infrastructure toward core system logic: defining responsibilities, domain rules, and actual behavior of the system rather than endpoints and plumbing. Authentication is treated as a solved baseline, not an area for feature creep, so future changes will prioritize business logic clarity and consistency over auth-related tweaks, btw on a photo there is my last pr to mostly complete authentication(most of it was cleaning my code and erasing redundancies)

Attachment
0