Documenting code, one commit at a time.
Starting a new project feels like staring at a blank canvas. When I recently initialized my project, EstreFlores/MiPrimerProyectoNext, I wanted to ensure the foundation was set up for scale rather than just speed.
Modern web development often prioritizes frameworks that handle the heavy lifting of routing and build optimization, which is why I chose the Next.
Getting started with a new framework can be daunting, but diving into the EstreFlores/MiPrimerProyectoNext project served as the perfect catalyst for exploring the Next.js ecosystem. The goal was simple: move beyond basic static sites and leverage a modern, performance-first architecture.
Transitioning into this project meant embracing the component-based paradigm
This post reflects on the process of wrapping up MiPrimerProyectoNext, a project focused on building a foundational application using React. Getting a project to a 'completed' state is a milestone that every developer experiences differently.
Working on MiPrimerProyectoNext allowed for a focused look at how React manages component-based architecture.
Building a robust application often feels like building a house: if the foundation isn't solid, the roof will eventually sag. With the PokedexEstre project, we are focusing on modularity by implementing Hexagonal Architecture, ensuring our core business logic remains decoupled from the UI and external data sources.
In many front-end projects, the logic for
When working on the PokeDexEstre project, we recently ran into a frustrating roadblock where the application build process would consistently fail during deployment to Netlify. These types of failures are often silent killers in CI/CD pipelines, where local development environments work perfectly but production builds break due to subtle environment
