The story of how we accidentally built a code refactoring tool. It started with a simple question: “Why is our code so messy?” Six months later, that question turned into Refactron v0.1.0 — an AI-powered tool that does what every developer secretly wishes they could do: clean up code automatically. We tried it on our own codebase first. The results were… eye-opening. Turns out we had more technical debt than some small countries have actual debt. But here’s the thing — it works. ✅ 98 tests passing. ✅ 90% coverage. And code that’s actually cleaner and more readable. Now it’s live on PyPI for everyone to try (and judge our code quality 😅). $ pip install refactron Docs: https://lnkd.in/dmdtpBCC Website: https://refactron.us.kg/ P.S: If you find any bugs, they’re probably features we haven’t documented yet. #Python #CodeRefactoring #AI #DeveloperTools #OpenSource
#cfbr
what usually prevent cleaning up a code base? I feel that in most cases it's because it would cause unpredictable breaks with features or changes that are being worked on in parallel by the various team members. If that isn't the case, then what is there to clean up? as these aren't of anyone's concerns To know the code-base holds a very real value as well, which should be considered before tempering with it automatically