Idk my tin-hat theory is a bit different. I agree with some of it - I think TDD, reactive programming and to some extent Rust is about job security, but I think Agile and code review is all about taking code ownership away from developers and commodifying programming.
I think Rust solves a real problem personally. TDD is honestly a bit too much, but testing is good. Reactive programming I don't know much about. For agile, I always thought of it as a way of putting the responsibility of projects back into the clients hands. Since you're always following what he's telling you each week/two weeks, if he's unsatisfied at the end, it's easy to gently tell him that you only did what he asked for, compared to the more "waterfall" where he could argue that you didn't meet the requirements. Code review I'm not sure, I haven't experienced it much.
