@hamiltonulmer Being even greedier as a user, having that tooltip be a (persistent, up to manually clearing) chat window to ask about the code in the broader context satisfies the locality part of explanations that I always like.
@hamiltonulmer I agree that tooltips are a great choice, but maybe not mutually exclusively! Having that short summary (or even just differentiating keywords) with a tooltip on hover of the name or summary would be nice.
@hamiltonulmer I think there are many situations where a very short summary would pick up the slack even in otherwise self documenting code. If my CTE/block name is hard to disambiguate from e.g. its similar neighbors without being annoyingly verbose, autogenerated comments would be helpful.
@hamiltonulmer I’m a pretty big fan of this, especially if it’s searchable (even when not collapsed)! If I’m offloading cognition to those summaries, they would be great to have as somewhat actualized references!
@sebkrier I think it was largely based on vibes, yes, but it might also be correct that it's shifted in the direction of being more negatively impactful because the tech can be more easily (and maliciously) targeted.
@sebkrier I think that since people compensate for the bias in their own experience based off those vibes, applying that correction might not be enough for them to dismiss it now because of a shift in both the vibe and the tech itself!