Context
Each project explains why it exists.
Projects
Technical evidence without confusing progress with portfolio
Projects are shown with context: what problem they address, what I learned, which technologies I used and where you can review them.
Evidence organized by path, progress and learning.
Progress
The bar shows real status, not appearance.
Review
Learning is summarized with technical judgment.
Ecosystem map
Each space has a clear role
Learning is for practice, academia is for evidence and portfolio is for a future professional selection.
Learning path
Progressive route with exercises, labs and technical practice organized by learning stage.
- Solved exercises
- Practice challenges
- Documentation by stage
Academic evidence
Index of academic projects and submissions with context, technologies and technical evidence.
- Submitted projects
- Academic context
- Technical evidence
Portfolio in progress
Space prepared to select projects that demonstrate real professional value.
- Curated projects
- Improvements before publishing
- Future professional evidence
Evidence path
Academic projects ordered by path
These projects read as a path: data, software construction, patterns, backend and frontend. Institution remains visible, but the main order is the learning journey.
100%
Java Inventory Management
Academic console application for registering, viewing, updating, deleting and selling products through Java fundamentals and object-oriented programming.
JavaOOPArraysExceptions
- Product CRUD
- Sales and stock control
- Validation and basic reports
Problem
Organize a small in-memory inventory and control basic product operations without relying on a database.
What I learned
I applied arrays, methods, classes, encapsulation, input validation and exception handling in a complete console workflow.
What I would improve
Add persistence, automated tests and collections when those topics match the learning level.
100%
Clinical Management with Data Structures
Academic Java system for managing patients, appointments, doctors and schedules in a clinical workflow.
JavaOOPData structuresCSV
- Patient and appointment management
- Applied data structures
- Academic persistence and reports
Problem
Organize a basic academic clinic workflow: patients, doctors, appointments and schedules.
What I learned
I practiced data structures, simple persistence, console menus and progressive code organization.
What I would improve
Improve the interface, strengthen clinical validations and separate care workflow, persistence and reporting logic more clearly.
100%
Commercial Management DB
Academic database project for organizing users, customers, products, inventory, sales, auditing and pricing policies in SQL Server.
SQL ServerT-SQLRelational modelPEPS/FIFO
- Relational model
- Stored procedures, triggers and auditing
- PEPS/FIFO inventory and sales
Problem
Model inventory, products, sales, auditing and pricing policies for a hardware-store scenario in an academic context.
What I learned
I strengthened relational design, T-SQL, referential integrity, stored procedures, triggers, auditing and PEPS/FIFO inventory control.
What I would improve
Document expected results for each validation, add a complete restoration guide and expand analytical queries for sales and inventory.
100%
Sales Management with Design Patterns
Academic Java console system for hardware-store sales and inventory, applying OOP, GRASP and GOF patterns over a defendable sales workflow.
JavaOOPGRASPGOF patternsConsole
- Console sale flow with customer, user, products and stock
- Subtotal, VAT, total and minimum-stock alert
- Factory Method, Builder, Command, Adapter, Facade, Observer and State
Problem
Organize a hardware-store sales flow without concentrating product creation, state rules, alerts and totals in a single class.
What I learned
I applied Controller, Factory Method, Builder, Command, Adapter, Facade, Observer and State to separate responsibilities and make the flow easier to defend.
What I would improve
Evolve a new version with a UI, persistence or tests without changing the already defended base logic.
100%
SUNAT Query API
Academic backend project developed at Tecsup to practice external service integration, controllers and API organization.
JavaSpring BootOpenFeignH2
- REST API
- External integration
- Backend practice
Problem
Practice querying external information through an API and organizing the flow with Spring Boot.
What I learned
I reinforced controllers, services, HTTP consumption, endpoint testing and basic responsibility separation.
What I would improve
Add query caching, provider-error auditing and retry handling to improve stability when external services fail.
90%
Products and Orders Backend
Academic backend submission focused on services, persistence and application structure with Spring Boot.
JavaSpring BootPostgreSQLDocker
- Backend services
- Persistence
- Products and orders
Problem
Consolidate an assessable backend application with routes, data and enough technical organization for an academic delivery.
What I learned
I practiced project structure, persistence, endpoints and technical delivery criteria.
What I would improve
Connect the product and order flow more clearly, add stock validations and prepare integration tests between services.
100%
React Product Catalog
Academic frontend practice to manage products, consume services and organize components in a React application.
ReactViteJavaScriptFetch API
- Product catalog
- API consumption
- React frontend
Problem
Practice a functional interface to list, create, edit and delete products from a web application.
What I learned
I reinforced components, state, forms, service consumption and the basic flow of a frontend app.
What I would improve
Add search, status filters, price and stock validations, and better visual feedback for loading, errors and success.