This article details Lalamove's 2025 "Big Cleanup" initiative that identified and removed over 30% of dead Java code and more than 100 obsolete DB fields, describing the tools, SA plugin, BigClean scanner, MyBatis interceptor, and quality‑assurance strategies used to ensure safe, efficient code slimming.
This article explains how a long‑standing Java backend service was instrumented with JVM agents and JaCoCo to collect execution coverage, visualize results in an IntelliJ IDEA plugin, and systematically remove dead code, improving maintainability while minimizing impact on production performance.
Learn when and why to remove files from a Git repository, and follow step‑by‑step commands—git rm, git rm --cached, and git rm -r—plus committing and pushing changes—to keep your codebase clean, organized, and free of redundant files.
Google’s massive monorepo contains billions of lines of code, and the Sesenmann project automatically identifies and removes dead code by analyzing build dependencies, runtime logs, and test coverage, dramatically cutting maintenance costs while navigating technical and cultural challenges.
The author, a mobile development team leader, shares a detailed account of a recent iOS codebase refactoring, describing the removal of unused libraries and code, architectural improvements, memory‑leak fixes, and best‑practice guidelines such as avoiding singletons, unnecessary layers, and over‑reliance on third‑party frameworks.
This guide walks you through practical steps for assessing, testing, version‑controlling, incrementally refactoring, and simplifying messy legacy code so you can safely improve maintainability without introducing new bugs.
