In all fairness, a stunningly clever insight can make things seem so obvious that you forget how hard it was to have that original insight. This kind of brevit

In all fairness, a stunningly clever insight can make things seem so obvious that you forget how hard it was to have that original insight. This kind of brevity is extremely helpful when thinking about a problem. You "just" have to grok the mechanics thoroughly. This really helps in designing effective higher level abstractions. Unequivocally admonishing brevity for ostensible readability kind of ignores the trade offs. I think there are other ways to bootstrap grokkability without having to sacrifice the conceptual clarity of nicely compact code.