1 pointby melvinroest4 hours ago1 comment
  • electsaudit0q4 hours ago
    Finally a sensible refactoring guide that doesnt immediately jump to 'rewrite everything in a new framework'. The step-by-step approach here is exactly what real projects need. Though I'd add one thing - before touching anything, make sure you have some kind of test coverage even if its just smoke tests. Ive seen so many 'cleanups' that break things because nobody verified the behavior first.
    • 4 hours ago
      undefined