This is fascinating!

I'm not entirely convinced your program will work, but I completely applaud it, if only for changing your consciousness.

What's interesting is that I am the guy who speaks out in meetings - and I'm the guy that the team will get to communicate their complaints to management or vendors (and will often then leave me to twist in the wind after setting me up for it).

And yet all of your exercises seem terrifying to me! I speak up, even though I'm terrified, because I feel I have to.

It hasn't really worked out positively for my career, though my career has been overall good, and quite entertaining.

What happens rather a lot is that when the disaster I predicted actually happens, it's then dropped in my lap to fix.

I quit a job over that - mainly because I didn't want to spend a year undoing the work I had been complaining about for two.

And that code was pathologically bad. For example, the designer was very big on object-oriented programming, so there were lots of tiny classes, but didn't believe in hiding data, so all members were public and could be changed from anywhere - and were.

Given that the member names were short and repeated dozens of times in similar objects, when some value was wrong, it would take hours or days to find what had happened. By the time they were willing to let me fix it, no significant progress had been made for months.