Current Couch-to-5k progress, it was a walk/run/walk 5m/20m/5m and is probably the farthest I've ever properly run in quite a long long time.
#knackered#couchto5k#c25k
doh, of course, you're quite right about that too. Urgh, the real world is hard for me to think about. Okay, I'm converted :D
This is why I stick to tools and libraries - apps are too hard for my tiny little brain :D
I often find, since the sanitised data for dev is usually prod data anonymised (stripped of PII if you will), though admittedly sometimes truncated too, I'm not entirely sure if a rich event stream (though massively useful) would be sufficient to entirely prevent a need for gdb.
That's a risk, I agree, but as you say, there's compliance issues at stake. I guess your best bet at that point is that you have to have some kind of shoulder-surfing checker watching any prod-read-only-access for compliance, which is limited to determining a test case to add.
If you qualify that with a *production* server then I agree entirely. No reason to prevent them from sshing a dev cluster for full-on debugging. Dev clusters should have sanitised data anyway
given how long I have to spend fighting with Windows or macos just to make it vaguely useful to me, I find config files which can be revision controlled far preferable. I think most people underplay the time cost for non - Linux setup.