The blog post argues that to effectively circumvent a rule, one first needs to understand its rationale, and it cheekily notes that technically the author didn't actually break the rule in question.
The article discusses why developers should understand the reasoning behind a software rule before attempting to work around it, emphasizing that knowing the rule's purpose can lead to better solutions or reveal hidden risks.
A developer found that a DLL was no longer in memory even though it hadn't been formally unloaded, tracing the issue to Windows' DLL load ordering. When a DLL is loaded at a base address that conflicts with another DLL loaded earlier, the system may relocate it and then later discard the relocated version without clear notification, confusing developers expecting explicit unload.