AI didn't disrupt software development. It deleted it.
​
I've been tracking this for a while. The death table:
- App / CRUD backend: dead 2027–28
- Android / mobile: dead 2028–29
- VBA / spreadsheet automation: dead 2030
- Matlab DSP / controls: dead 2031
- Embedded peripheral firmware: dying now
The H1B and F-1 visa pipelines were optimized for exactly this work. They're being deleted with it.
But here's what AI *cannot* do yet: write a formal specification and prove it correct.
Z3 is Microsoft Research's SMT solver. You give it arithmetic constraints — buffer bounds, PID output ranges, ISR reentrancy, timer prescaler validity — and it either returns UNSAT (mathematically impossible to violate) or hands you the exact input that breaks your code. That's not a test. That's a proof.
The paper describes an autonomous remediation loop: AI generates code → Z3/Alloy find violations → diagnostic JSON names the exact line and counterexample → AI corrects → loop runs until UNSAT. No human reviews the commit. The proof is the certificate.
Scipy + numpy + python-control now reproduce Matlab's entire DSP and controls workflow at zero licence cost. The critical difference: Matlab's isstable() returns a Boolean. Z3 UNSAT is a proof. For IEC 61508 and DO-178C certification, that's not a detail.
Full paper + repo: https://doi.org/10.5281/zenodo.19542523 (CC BY 4.0)