>is there a better way to convey the mental model of a software system? There is UML but that's mainly to explain stuff to non-engineers and turned out to be a

>is there a better way to convey the mental model of a software system? There is UML but that's mainly to explain stuff to non-engineers and turned out to be a total waste of time in 90% of cases. Documentation becomes rapidly outdated and costs money to maintain. Do you want someone updating stupid arrows and boxes in a visio file for $200 an hour? Engineers develop an intuition of why things don't work the way you expect just as a mechanic develops an intuition about why your car doesn't run the way you expect.