Eve's whole focus on "observability" of code and data seems kind of overwhelming imo...<p>I mean, the 2 most successful paradigms for "full-strength" interaction with computers are (1) code in general purpose programming languages and (2) spreadsheets. And they both have one thing in common: <i>only code or only data is visible most of the time (or by default)!</i> I think this is for one simple reason: that's all our monkey brains can take, we only want a small narrow window into one of these 2 domains, and we can barely handle that. We don't really want to "see the data flow" or "the code behind the cells", we want things hidden away 99% of the time, and we want to be spared from the paralyzing effect of endless choice that allowing us to interact with everything would cause.<p>I think the problems people would most appreciate solving are instead:<p>(1) how to switch between code-first and data-first mode in the same tool<p>(2) how to build a successful repository/marketplace of good enough "components" usable in your tool (and "NPM of Excell plugins" but for your tool)<p>I think people mostly fall clearly into two camps: either <i>completely overwhelmed</i> by their current tools already, anything even slightly more complex and their "brain would explode", or <i>they just want full power for their technical task</i> (so they'll use something semi-domain-specific like Jupyter notebook). I think "designing for humans" should be based or deisngning for <i>limitations,</i> for <i>neuroticism</i> and for <i>somewhat illogical/irrational behavior</i> ...that's what best describes <i>human</i> users and that's what Excell got brilliantly right. You can be resentfully angry, lazy, overwhelmed and ADHDed, all at the same time, in one of the worse days of your life, and you'll still get something done with Excell.