✦ AUGHTY ✦ Four of Five 24 AUGHTY Five jobs between 2015 and 2026. Four worked. The fifth did not. There is a pattern here. I would like to show you what an engineer does with a pattern. And what HR does instead. 2015 to 2026. Five jobs. Five managers. Four good fit. Left me alone. No mid-flight priority changes. Engaging work. Then a fifth. Poor fit. Burnt out. I am told I am the problem. FIVE JOBS, 2015–2026 ✓ 2015 ✓ 2015 ✓ 2015–16 ✓ 2016–19 ✗ 2019–26 Pattern: four of five worked. The brain in each row is the same brain. Method: Compare the five cases. Find what is the same across all. Find what is different. The thing that varies with the outcome is the cause. AN ENGINEER ASKS: WHAT CHANGED? Job 1 Job 2 Job 3 Job 4 Job 5 brain → CONSTANT manager → VARIABLE outcome ✓ ✓ ✓ ✓ ✗ follows the variable The outcome tracks the variable. Not the constant. A debugger would isolate the manager as the cause. A debugger would not blame the line of code that never changed. HR concluded the constant is the cause. The first four managers handled it intuitively. They left me alone. They did not change priorities mid-build. The work was engaging. The brain bent. The output was excellent. The first was 27. I was 39. Tenure is not the variable. The accommodation was supposed to be in my file. It wasn't. The first four did not need to read it. The fifth would have needed to. There was nothing to read. I have not spoken to the manager in three months. The skip insists I perform the task the accommodation exempts. An engineer troubleshoots a dataset like this. HR looked. HR declined to troubleshoot. The brain is the constant. The brain did not change in eleven years. I am told to file for the accommodation that should already be on file.