Shaking the Stack: Teaching Seismology to Talk Back
Simulation software has a talent for hiding intelligence inside inconvenience. A mature physics code may contain decades of numerical insight, community testing, and domain expertise. Then it asks the user to prove loyalty by editing parameter files, remembering command sequences, managing mesh directories, choosing execution binaries, checking output folders, and pretending that none of this is a productivity tax. This is not because scientists enjoy suffering. Mostly. It is because high-performance scientific software often grows around capability first and usability later. ...