TPXimpact DX Tech Handbook
  • DX Tech Handbook
  • Processes
    • Decision making
      • RFC Template
    • Communities of practice
    • Dealing with change
    • AI generated code
    • Guidance on billing for junior developers
    • Our hiring process
    • Job Descriptions
  • Working practices
    • Version control
    • Drupal 9 upgrade
    • Site health check list
  • Best practice
    • Non functional requirements
    • Security updates
    • Browser compatibility and testing
    • Writing good commit messages
    • 🚛Load testing
  • 📕Recommended reading
  • Learning resources
    • Learning Drupal
    • Contentful training
    • Acquia DAM Certification
Powered by GitBook
On this page

Was this helpful?

  1. Processes

Dealing with change

PreviousCommunities of practiceNextAI generated code

Last updated 2 years ago

Was this helpful?

Whenever we work on a project or feature that's legacy in nature it will generally be best to value consistency over change. The processes we set today will continuously evolve and it will not always be possible to keep all of our existing codebases in sync with our latest thinking.

This means, for example, if you are tasked with working on a site which makes extensive use of jQuery, you should not introduce React for a single component.

On the other hand, we shouldn't carry long term technical debt. And so if a tool or sub-system requires upgrading in order to provide efficiency before commencing a significant piece of work, then those upgrades should be done first.

This work is licensed under a .

Creative Commons Attribution-ShareAlike 4.0 International License
Creative Commons Licence