RailsConf 2023 - Taylor’s Guide to Big Rewrites by Andy Croll

Discover the keys to a successful big rewrite, from setting expectations to prioritizing coverage, and learn how to navigate the unpredictable process with patience, collaboration, and a focus on customer needs.

Key takeaways
  • Maybe don’t publicly shame someone in Slack
  • Sometimes, rewriting software is necessary, but it’s hard and unpredictable
  • Set your own expectations for a smoother process
  • Be patient, as it takes time to figure things out
  • Don’t be afraid to seek help and advice
  • Understand that rewriting software can be stressful, just like life
  • Make sure to prioritize coverage to avoid waste
  • Be prepared for setbacks and mistakes during the process
  • Collaborate with your team and take constructive criticism
  • Don’t be too proud to ask for help or consult experts
  • Rewrite software can be a good opportunity to improve processes and habits
  • Learn from your team’s experiences and acknowledge their struggles
  • Know when to stop and reassess your strategy
  • Don’t neglect the importance of understanding customer needs
  • Stay focused and don’t get distracted by too many features
  • Be aware of the importance of naming conventions in software development
  • Standardize processes to avoid repetition and mistakes
  • Be open to trying new approaches and take calculated risks.