Yeah it’s hard to think of a clear improvement to the title. I think I’m mostly trying to point out that thinking about legible vs illegible safety problems leads to a number of interesting implications that people may not have realized. At this point the karma is probably high enough to help attract readers despite the boring title, so I’ll probably just leave it as is.
Makes sense, although want to flag one more argument that, the takeaways people tend to remember from posts are ones that are encapsulated in their titles. “Musings on X” style posts tend not to be remembered as much, and I think this is a fairly important post for people to remember.
Yeah it’s hard to think of a clear improvement to the title. I think I’m mostly trying to point out that thinking about legible vs illegible safety problems leads to a number of interesting implications that people may not have realized. At this point the karma is probably high enough to help attract readers despite the boring title, so I’ll probably just leave it as is.
Makes sense, although want to flag one more argument that, the takeaways people tend to remember from posts are ones that are encapsulated in their titles. “Musings on X” style posts tend not to be remembered as much, and I think this is a fairly important post for people to remember.
Making illegible alignment problems legible to decision-makers efficiently reduces risky deployments
Make alignment problems legible to decision-makers
Explaining problems to decision-makers is often more efficient than trying to solve them yourself.
Explain problems don’t solve them (the reductio)
Explain problems
Explaining problems clearly helps you solve them and gets others to help.
I favor the 2nd for alignment and the last as a general principle.