What ‘Dirty Tricks’ Reveal About Effective Software Engineering

When first reading “Clean Code” sequel, the translator Yusheng laughed at its “earthy” (土) content, noting that such “old‑school” methods are indispensable in software development.

The book, rated 4.5 on Amazon, sparked curiosity about why the translator felt this way.

He relates the experience to practicing the classic “Yun Gong Xun Yin” theme, drawing parallels between timeless melodies and enduring engineering practices.

He discusses the challenges of translating technical books, emphasizing the difficulty of preserving nuance and style, and the risk of errors being exposed by knowledgeable readers.

He shares a “soil method” for safely editing firewall rules: keep a flawless backup configuration and reload it every five minutes via a scheduled task.

This leads to a broader point: many heuristics—experience‑based, rule‑of‑thumb techniques—are essential for solving complex problems within reasonable time, even in the age of AI tools like ChatGPT.

Examples include analyzing commit history to identify hotspots, using the “rubber‑duck” technique to articulate problems, taking breaks to let the subconscious work, and employing simple backup strategies.

He warns that neglecting such fundamentals leads to wasted time on trivial issues like poorly written commit messages or ambiguous API designs.

Ultimately, he encourages readers to adopt these practical heuristics, adapt them to their context, and remember that “dirty tricks” can be powerful allies in building robust software.