System Integration
Work to connect applications, data, and services that were not conceived as a single solution. It includes migrations and decoupling of dependencies, with attention to what happens when an external component stops responding.
My career does not follow a single specialty. I have moved from support and automation to systems development, architecture, and team leadership. In each stage I have sought to understand operations and take on the necessary responsibilities to ensure the solution works, from code to its maintenance.
I'm Paynalton and I sign my work with that name. My background includes fullstack development, solution architecture, system integration, and team leadership. I adapt to the needs of the project and participate in both technical decisions and implementation and operations. I started programming at twelve with MS Basic. Before taking my first formal developer position in 2009, I was already building personal projects and tools to automate tasks in other jobs. That habit of learning by solving problems continues to guide my work. I've created enterprise systems, campaign platforms, and services that evolved from urgent needs. I've also led development teams, with responsibilities for hiring, training, architecture, and delivery. Currently, I'm exploring how to work with AI agents while preserving human judgment and building tools that allow for maintaining the context of complex tasks.
June 2025 – present.
Developer
Worked on an engineering team for platform development, combining development, solution architecture, DevOps and SecOps according to project needs. My involvement included integration services, authentication flows and tools to review infrastructure and validate websites.
I currently maintain Pipila as the sole developer, relying on AI. I have also used in-house tools to evaluate AWS infrastructure evidence and check spelling on a Thai website. During this period, I incorporated Azure into my work experience.
My work at Freeway includes an assignment for Mead Johnson; my employer is Freeway.
2020–2025.
Development Manager
I led a team that eventually included fifteen developers. I was responsible for hiring, training and supervision, architecture, estimation, work distribution, deliveries, and relationship with clients. I combined management with the development of solutions and tools that allowed the team to advance despite technical constraints or context changes.
A significant part of my work consisted of resolving blockers. Sometimes it was enough to listen to someone explain the problem; other times, it was necessary to take a step back and return with a different perspective. During this period, projects such as Winner and Pipila emerged.
Notable Contributions:
2019–2020.
Backend Developer
I participated in planning, development, architecture and integration of solutions. In addition to my backend responsibilities, I led three developers. This stage is part of my experience combining implementation with the technical coordination of others.
2018–2019.
Fullstack Developer
I worked on design and development of solutions, troubleshooting and technical coordination. I led two developers and had direct involvement in the construction and review of the systems.
2013–2018.
Development Manager
I was hired specifically to create Onix, an ERP for a corporate with six companies. I was the sole developer during its initial development, which took approximately two years. The system allowed for networked work and integrated processes that previously depended on a platform based on Clipper.
Toward the end, developers were added to maintain the solution; during this stage I led two people. My work also included consulting, networks, security and e-commerce. Later, I resumed Onix to modernize its code and infrastructure.
2012–2013.
Fullstack Developer
I developed websites and web solutions, with participation in architecture, databases, SEO and operational tasks. This stage expanded my experience handling different aspects of a solution from the same technical role.
2011–2012.
Fullstack Developer
I worked on the development of websites and web solutions. During this period I also contributed on my own with themes and aesthetic steamp nad add-ons for GNOME-Look, exploring desktop customization and the creation of shared resources.
2009–2010.
Fullstack Developer
It was my first formally dedicated job in software development. I worked on web solutions, ERP and integrations, after having created personal programs and automation tools in previous jobs.
2007–2009.
Technical Support
In addition to support, I developed applications to automate editorial creation and an intranet. I also participated in website quality testing. These contributions were part of my development experience before taking on a position with that title.
2006–2007.
Technical Support
I worked on on-site support and incident handling. I automated hard drive cloning to speed up computer assembly processes, applying programming to a specific operational need.
2003–2006.
Production Supervisor
I worked on computer equipment assembly and operation of the production area. This experience is part of my background prior to dedicated development positions.
Work to connect applications, data, and services that were not conceived as a single solution. It includes migrations and decoupling of dependencies, with attention to what happens when an external component stops responding.
Design solutions that connect applications, data, and services without losing sight of their operation. I'm interested in understanding where the dependencies are, what happens when a failure occurs, and how to allow the system to evolve. Pipila and the transition of Onix show two ways to approach that work.
Work across different levels of a solution, from the user experience to the services and data. My experience includes enterprise systems, websites, campaigns, and in-house tools. I use platforms such as Astro, Flutter, and Tauri, along with languages and frameworks appropriate for each project.
I participate in infrastructure, deployments, and evolution of existing systems. The modernization of Onix includes dockerization, code migration, AWS, horizontal scaling, and CI/CD. My current work also includes DevOps and SecOps functions, and in the past year I've used Azure.
Work with different agents and models depending on the problem. I distinguish between using AI to build a tool and integrating it into its functionality: Yayauhqui corresponds to the first case and SpellChecker to the second. In complex projects, I prepare intermediate documentation so that agents can reconstruct their context and continue with coherence.
I have led teams of up to fifteen developers, with responsibility for hiring, training, supervision, architecture, and deliveries. I strive to understand what is preventing progress and take action on that blockage, whether technical, of understanding, or of coordination. Listening and helping to organize a problem is part of the work of leadership.
In ONIX, I migrated code from Zend 1.5 to Laminas and prepared an AWS UAT environment. Validation of the modernized system remains a separate stage from the technical migration.
In PÍPILA, I separated record intake from processing through workers and retries to reduce dependence on external service availability.
I am self-taught. I learn by studying documentation, researching how others have approached similar problems, and building solutions that I then test. When a project requires new knowledge, I incorporate that learning into the work and document what is needed to continue and share it.
My first program was in MS Basic, at twelve years old. Over time I developed tools for my jobs and maintained the personal project magodeozmexico.com for years. I also created a program to automate software maintenance in office equipment. These experiences preceded my formal employment as a developer in 2009.
In addition to my jobs and personal projects, I have collaborated on documentation, translations, corrections, and resources for software communities. I have always used the signature Paynalton. Some contributions are old and their links need to be recovered; recent contributions are presented according to their real status.
hello world