Getting Started with Spring Boot

Starting a new project often feels like a balancing act between configuration and boilerplate code. In our recent work on the ApiRestCRUD project, we focused on establishing a clean, maintainable foundation for a RESTful service using the Spring ecosystem.

The Architecture Pattern

To ensure our application remains scalable as it grows, we adopted the

Setting the Scene

In the latest development cycle for TrabajoPractico5, our focus shifted toward enhancing the user experience by defining the primary navigation and data entry points of the application. Building a clean, maintainable UI structure is the foundation of any successful desktop application, especially when ensuring that user inputs—such as adding a new client—are handled with

Standardizing the Repository Foundation

When working on the Calculadora project—a .NET utility application—we recognized the need to establish a cleaner environment for collaborative development. Starting a project on the right foot often means enforcing environment-agnostic standards that prevent local configuration noise from polluting the codebase.

The Problem: Avoiding Configuration

Introduction

Users need to stay informed about events within the application, but building a notification system often introduces complex state management challenges. In the FotazaApp project, we recently implemented a centralized notification system to improve user engagement and visibility.

The Concept

Think of a notification system like a central post office in a bustling city.

Improving Project Architecture

In the ProyectoTransversalG14 project, a Java-based application utilizing MariaDB, we recently undertook a refactoring effort to improve code cleanliness and security. Our primary goal was to modernize the way we manage database connectivity, moving away from hardcoded or redundant connection logic.

The Problem: Redundant Connectivity Logic

Introduction

Building forms that feel intuitive is a challenge. Users often struggle with cluttered inputs and lack of visual hierarchy. I have been working on the IntegradorWeb project to refine our form components, focusing on creating a clean, structured interface that guides the user through the input process effectively.

Rethinking Form Layouts

When designing forms, the goal is to

The Visibility Challenge

Tracking competitive player statistics can be notoriously difficult, especially when the underlying data streams don't align with the expected UI state. In the pubg-stats-tracker project, we recently encountered a frustrating issue where player rankings were failing to appear in the dashboard.

Improving Visual Identity

In the ongoing development of FotazaApp, we recently took a step back to evaluate how our branding is presented to users. A critical part of this experience is the watermark applied to shared content. Previously, our implementation was purely functional—a placeholder that served its purpose during the early development phases but lacked the polish expected in a

Managing user state is a fundamental requirement for most web applications. In the FotazaApp project, we recently shifted our focus toward establishing persistent user sessions to ensure a smoother experience for our authenticated users.

The Role of Session Persistence

When a user logs in, the server needs a way to "remember" that specific user across multiple requests.

The Challenge

Working on the pubg-stats-tracker project involves frequently updating how we interact with external game APIs to keep player metrics accurate. As the project evolves, maintaining a clean and efficient data fetching layer is essential to handle increasing amounts of game data without bloating the application logic.

The Refactor

We recently focused on streamlining the