Our Strategy for Keeping Up with Rapid Tech Innovation
Technology agencies are expected to have an opinion about every new framework. We would rather test one than repeat its marketing. Our process is simple: experiment internally, use it on a suitable project, and keep it only if the team and the client gain something measurable.
A Culture of Curiosity and Experimentation
As Technical Director, part of my role is to give people room to investigate tools that interest them. A small prototype is cheaper than discovering halfway through a client project that a promising framework is immature, poorly documented or wrong for the team.
New hires often introduce tools through personal projects or previous jobs. Seniority does not give anyone a monopoly on good technical ideas; it does, however, make us responsible for testing those ideas before a client carries the risk.
Transitioning Through Tech Stacks
We built our early reputation with PHP and Symfony. Symfony changed considerably, and our applications changed with it: from server-rendered monoliths to systems with APIs serving separate web and mobile interfaces.
Symfony remains useful, but it is no longer the automatic answer. We adopted Node.js and Python when projects justified them, then retained those skills because later projects had similar needs.
On the frontend, we worked with Angular, React and Vue. Vue became our usual choice because the team could work productively with it and introduce it gradually into existing PHP projects. We still choose around the product and the client’s existing stack rather than forcing every project into the same template.
For mobile work, React Native and Flutter each have a place. The decision depends on the product, required device features, existing code and the people who will maintain it.
Embracing AI and New Methodologies
AI tools are now part of our development workflow, but “uses AI” is not a quality standard. We use them to explore unfamiliar code, draft tests, review alternatives and automate repetitive work. Their output still needs the same review as code written by a person—sometimes more, because a confident answer can be subtly wrong.
Our squad model is less fashionable than it sounds: give a client a stable mix of product, design and development skills, then let that group learn the product over time. It works better for evolving software than repeatedly estimating isolated features as fixed-price projects.
Continuous Learning and Skill Development
We run internal workshops and let developers move between technologies when a project and their experience make that sensible. Training React Native while it was still in beta is one example; learning Node.js and Python for demanding client projects is another. Some experiments disappear. The useful ones become part of the agency.
Choosing, Not Chasing
Keeping up does not mean adopting everything early. It means knowing enough to choose deliberately, explain the trade-offs and support the result after launch. That is the technical culture we want to maintain as the tools continue to change.
The next article looks at the people behind those technical choices and what we learned about recruiting and retention in Bangkok.
The Outsourcify Story #6: Attracting and Retaining Top Talent in Thailand’s Tech Industry
