Case 04 Rails · MySQL · React
DPMS: sustained quality on an international industrial platform
An international digital project-management platform for a global industrial company. As part of the team, I worked on the Rails APIs, MySQL modeling and business rules, with testing and code review built into delivery.
Context
DPMS is an international digital project-management platform used by a global company in the industrial sector. The work was done through Oxeanbits, as part of a team.
Industrial projects accumulate specific rules, and a platform used internationally has to evolve carefully: every change can affect teams that depend on it daily.
Problem
Evolving a platform with many business rules without introducing regressions takes more than shipping features. It takes tests that protect behavior, code review and standards the whole team follows.
Part of the interface still relied on legacy JavaScript and jQuery, which made it hard to reuse behavior and evolve screens.
My responsibility
I built and evolved Ruby on Rails REST APIs and worked on the backend architecture, MySQL data modeling and business rules, with automated tests.
I took part in code reviews, refactoring and the definition of standards. On the frontend, I contributed to maintaining the legacy interfaces and to the React modernization, a team effort covered in its own case.
Decision
Automated tests and code review are part of delivery, not an optional step after it. The project's history records test coverage above 90%.
That number belongs to DPMS. It is not a current measurement or a rule I apply to every project.
Alternatives and trade-offs
Present-day analysis written for this site. It is not a record of the alternatives evaluated at the time.
- High coverage does not prove the absence of defects. The value lies in tests that describe behavior and protect business rules during refactoring; tests that merely mirror the implementation raise the number without raising confidence.
- Requiring tests and review on every change makes each delivery a little slower in the short term. On a platform with many rules, that cost is usually lower than fixing regressions in production.
Implementation
The work combined feature development with keeping the codebase healthy.
APIs and business rules
Rails REST APIs and the business rules behind project management.
Data modeling
MySQL modeling that kept pace with new functionality.
Quality
Automated tests, code review, refactoring and technical standards shared by the team.
Interface
Maintenance of legacy JavaScript and jQuery screens and participation in the migration to React.
Outcome
A codebase with test coverage above 90% in the project's history, reviewed code and shared standards, which makes it safer to change the platform.
Internal metrics record me as the repository's leading individual contributor. Those are activity indicators, not measures of quality or business impact.