Documenting code, one commit at a time.
Maintaining a personal portfolio requires a balance between aesthetic presentation and functional utility. In the development of the Plantilla project, the goal was to transform a static landing page into an interactive hub, starting with a fundamental feature: a direct communication channel for visitors.
Previously, the site served purely as a static
Deploying PHP applications across different environments often reveals hidden assumptions in hardcoded paths. In the EntrenoPHP project, we recently focused on refactoring route resolution to ensure the application remains portable when migrating from local Apache setups to cloud-hosted environments like Google Cloud.
Building interactive web pages often starts with a fundamental challenge: bridging the gap between static HTML and dynamic user behavior. Recently, while working on the 2_desarrollo_cliente project, I revisited the core principles of DOM manipulation, reinforcing how effectively we can transform static elements into living components.
When you start learning client-side
The aws-rekognition project serves as a foundational bridge for integrating computer vision capabilities into web applications. By leveraging cloud-native AI services, we can process and analyze image data directly within our application flow.
Implementing computer vision in a traditional web stack often presents hurdles, including:
As the tallermakinonbikes project grew, the visual identity of our landing page began to lag behind our actual service offerings. The footer was becoming cluttered, and our graphical assets were struggling to maintain a consistent aesthetic across different screen resolutions. We needed a cleaner approach to manage our layout updates without inflating our maintenance overhead.
Maintaining a clean project structure is like keeping a toolbox organized. When you know exactly where your initialization scripts live, you spend less time searching for tools and more time building. Recently, I spent time cleaning up the repository structure in Portfolio_react to ensure the initialization logic aligns with modern development standards.
Over time, as a project
Maintaining a clean separation between structure and style is one of the most persistent challenges in React development. I recently took a deep look at the CardExperience component in my Portfolio_react project, specifically focusing on how CSS architecture impacts component readability and long-term maintainability.
Over time, as I added new features to the
