For the engineers who inherit other people's code at 3am. Anti-patterns named. Legacy code documented. Hard opinions defended. No vendor allegiance. No tutorials.
Twenty ways PLC, HMI, and SCADA code goes wrong, and what to do instead. The catalogue the publication is built around, in a single downloadable artefact. Enter your email to receive it.
A running taxonomy of the bad habits, code smells, and inherited disasters that make industrial code fragile — each one named, dissected, and fixed.
A running archive of industrial code that was built decades ago, still running today, and worth understanding. Code archaeology, with forward-looking lessons.
The arguments worth picking. The opinions worth defending. Industrial code is software. It deserves the same rigor as any other software.
The field guide grows with submissions. Real industrial code — yours, or something you inherited — reviewed honestly and published anonymously. Most submissions become Anti-Pattern Files. All identifying information is removed before anything is published.