The article revisits Roedy Green's satirical "How To Write Unmaintainable Code" and adapts its tricks into seven concrete techniques—ranging from meaningless variable names to build‑tag mazes—that deliberately cripple AI code assistants like Claude Code while highlighting the trade‑offs for maintainability.
The guide explains how to protect a Java core module deployed on user servers by integrating ProGuard for bytecode obfuscation, Xjar for JAR encryption, and ClassFinal for class‑file encryption, providing Maven plugin configurations, startup commands, and verification that the combined approach renders decompiled code empty or unreadable.
This article reveals five advanced Java tricks—using Unicode escapes in comments, over‑complicating simple logic with bitwise shifts, tampering with Boolean.TRUE via reflection, forcing both branches of an if‑else to run, and leveraging the Unsafe class for low‑level memory manipulation—to deliberately make code hard to understand.
This article outlines a thorough mobile application security testing methodology, covering installation package verification, code obfuscation checks, signature validation, integrity and permission audits, sensitive data handling, keyboard hijacking, account protection, communication encryption, component exposure, and server-side vulnerability assessments such as SQL injection and CSRF.
This guide explains how to protect a SpringBoot-based e‑commerce project from source leakage by using code obfuscation or the ClassFinal Maven plugin, detailing configuration, startup options, decompilation results, and machine‑binding to ensure the packaged jar runs only on authorized servers.
This guide explains how to protect Spring Boot production packages from reverse engineering by applying code obfuscation with ProGuard and full encryption using the ClassFinal Maven plugin, including configuration steps, encrypted startup commands, machine‑binding activation, and the resulting decompilation behavior.
This article explains how to protect Java applications from reverse engineering by using ProGuard for code obfuscation, detailing the creation of a proguard.cfg file, Maven plugin configuration, and the build process to generate an obfuscated JAR.
This article explains why developers forbid debugging in web pages, demonstrates how repeated debugger statements can hide API calls, and provides multiple counter‑measures—including breakpoint deactivation, script ignore lists, Function‑based rewrites, and advanced obfuscated code—to protect frontend JavaScript from inspection.
This article explains how Java source files are compiled into class files, how they can be decompiled, and provides a detailed, code‑rich tutorial on protecting a Spring Boot project by configuring ProGuard through a proguard.cfg file and Maven plugin to produce an obfuscated JAR.
This article explains the concept of in‑memory PHP trojans, provides simple obfuscated source code that deletes itself and persists in RAM, discusses their stealth characteristics, and offers a basic mitigation strategy of terminating the process and removing the generated files.
Explore a series of unconventional Java tricks—from Unicode escape hacks and bitwise tricks to reflection-based Boolean tampering and Unsafe memory manipulation—that let you deliberately obfuscate code, making it hard for teammates to read, modify, or even predict its behavior.
This article explains why Java bytecode is easy to decompile and presents several practical protection methods—including isolation, class file encryption, native code conversion, and various obfuscation techniques—while discussing their advantages, limitations, and typical use cases.
This article examines the security challenges faced by mobile applications, outlines static, dynamic, and business‑level attack vectors, and presents comprehensive hardening techniques—including environment detection, data collection, code and algorithm obfuscation, and virtual‑machine protection—illustrated with iOS‑specific examples and code snippets.
This tongue‑in‑cheek guide enumerates a series of deliberately bad programming techniques—ranging from confusing naming conventions and deceptive comments to absurd design choices and hidden macros—aimed at making code virtually impossible to understand, maintain, or test.
This tongue‑in‑cheek article enumerates a series of deliberately harmful programming practices—from confusing naming conventions and deceptive comments to excessive abstraction, misuse of inheritance, and avoidance of testing—intended to make code virtually impossible to understand, maintain, or debug.
This article provides a comprehensive guide to Android code obfuscation, covering the purpose and benefits of minification, detailed ProGuard/R8 configuration, resource shrinking, desugaring, D8/R8 internals, custom obfuscation dictionaries, and modular ProGuard rules for multi‑module projects.
This article explains why Python developers often need to run JavaScript—especially obfuscated code—during web scraping, demonstrates how to use the ExecJS library to execute both simple and heavily obfuscated JavaScript from Python, and shows that the approach works seamlessly without de‑obfuscation.
This article explores the cat‑and‑mouse battle between crawlers and API endpoints, detailing how dynamic signatures, token‑based authentication, time‑bound hashes, rate‑limiting, and code obfuscation can be used to defend against scraping while also showing how attackers can reverse‑engineer and bypass these defenses.
This article explains the principles and practical implementations of iOS security hardening techniques—including code obfuscation, anti‑debugging, signature verification, and abnormal data detection—illustrated with real‑world examples from the 58.com iOS client.
This article showcases an obscure JavaScript expression built from the characters ()+[]! that, when run in a browser, produces the same result as alert(1), and explains its origin on the Esolang Wiki and a popular GitHub repository.
This tongue‑in‑cheek article enumerates a series of deliberately bad programming practices—from confusing naming conventions and deceptive code tricks to misleading documentation, chaotic design, and the complete avoidance of testing—illustrating how to make software virtually impossible to maintain.
This tutorial explains why iOS code obfuscation is needed, how to prepare the required scripts and PCH file, configure Xcode’s build phases, and apply the obfuscation tool to hide method and variable names, while noting its limitations to .m/.h classes.
The article explains how ProGuard’s incremental obfuscation using –applymapping can cause mapping conflicts when previously assigned method names are overwritten, producing warnings and inconsistent names such as ‘c_’, and details the internal workflow, inline handling, and practical steps to diagnose and resolve these issues.
This article explains how JavaScript’s type coercion rules can be exploited to construct any string or code using only the characters []()+! and demonstrates step‑by‑step how to build letters, functions, and even execute code, illustrating the principles behind the jsFuck obfuscation technique.
The article outlines a comprehensive set of APK‑slimming techniques for the iQIYI Android client—including pluginization, 7‑ZIP recompression, apksigner signing, duplicate‑resource removal, PNG/WebP conversion, library trimming, code obfuscation, R‑class elimination, language‑config pruning and native‑ABI reduction—that together cut the package from 54.2 MB to 28.2 MB.
This article walks through the reverse‑engineering of a compact JavaScript one‑liner that draws a patterned image, refactors it into readable modules, explains each transformation—including variable renaming, loop conversion, ternary expansion, bitwise operations, and switch‑case replacement—while illustrating the underlying math with graphs and code snippets.
