If first attempt to refactor was over-engineered. They same will happen with the the new stack. New tools won't resolve problems. Start deleting the code.
"We know, for example, that iterating on existing solutions is more likely to improve software than a full rewrite. The dangers of full rewrites have been documented. Joel Spolsky and Stack Overflow described them as “the single worst strategic mistake that any software company can make.” - Kill It with Fire - Manage Aging Computer Systems (and Future Proof Modern Ones) by Marianne Bellotti
Rewrites fail more often than not. Which is why Apple’s recent announcement that they will be rewriting their foundational frameworks in Swift caught me by surprise. The bigger the company, the bigger the stakes.
in emacs org-mode you can archive some tasks, text - it will move it to another text file ex. archive.txt with the timestamp or archiving it. Beside this keep your file in git. so you delete text & make explicit commit message that something was removed.
I don't know if I'll ever find a cooler, more interactive, intuitive, and featureful markdown language and implementation. I use it daily to track issues and progress at work. I use it to document the code, because it can be exported to really any format necessary.
I mean come on, the table editor and Babel still make me grin every time I use them. Truly genius.
