
Learning path
Progressive route with exercises, labs and technical practice organized by learning stage.
- Solved exercises
- Practice challenges
- Documentation by stage
Projects
Projects are shown with context: what was learned, current status and why not everything should be presented as a final portfolio piece.
Ecosystem map
Learning is for practice, academia is for evidence and portfolio is for a future professional selection.

Progressive route with exercises, labs and technical practice organized by learning stage.

Index of academic projects and submissions with context, technologies and safe publishing criteria.

Space prepared to select projects that demonstrate real professional value.
Reviewed evidence
These projects are learning evidence. They include progress, technologies and publishing criteria.

Academic Java system for managing patients, appointments, doctors and schedules in a clinical workflow.
Organize a basic academic clinic workflow: patients, doctors, appointments and schedules.
I practiced data structures, simple persistence, console menus and progressive code organization.
Improve interface, validations and responsibility separation before treating it as portfolio work.

Academic database project to organize inventory, products, sales and queries for a hardware store context.
Model inventory, products, sales and queries for an academic hardware-store context.
I reinforced relational design, queries and data organization criteria.
Prepare a custom cover and public documentation without unnecessary delivery-context references.

Academic Java project focused on design patterns, responsibility separation and business-rule organization.
Build an academic system base applying patterns and responsibility separation.
I am connecting class design, business rules and patterns with a more maintainable structure.
Keep current logic stable while the project is completed, then review publishing, cover and documentation.