satyanash
Joined 12 years ago
Joined 12 years ago
What terminal / agentic workflows spawn the demonstrated dialogue boxes that require the User to click/reject the action? Aren't most such flows actually inline UIs? And finally, if the core issue is that these confirmation boxes are tied to the terminal that triggered them, which does not autofocus, what's the point of said "big arrow" that is also lurking behind without focus?
If the said "big arrow" automatically gains focus, isn't the real fix here to just make the dialogue boxes themselves gain focus automatically? Both are similarly disruptive anyway.
Either they aren't evil in which case they're being demonized, or they're already evil in which case demonization is redundant.
Keeping aside the motives of people, what is clear is that scale effects of AI cannot be ignored. An AI "learning" millions of pieces of content in a short span is not the same as humans spending time, effort and energy to replicate someone's style. You can argue that its 'neural nets' in both cases, but the massive scale is what separates the two.
A village is not a large family, a city is not a large village, ... and all that.
This is advice I've never seen or received. It's always been the latter, exit early, etc. Languages like Swift even encode this into a feature, a la if guards.
All this, for literally nought
missed opportunity to call it "final final"
Omission of trailing part changes the meaning and makes it clickbaity.
The fact that an "L8" at Google ranks above an OSS maintainer of a super-popular library "L5" is incredibly interesting. How are these levels determined? Doesn't this represent a conflict of interest between the FOSS library and Google's own motivations? The maintainer having to pick between a great paycheck or control of the library (with the impending possibility of Google forking).
All metrics are wrong, some metrics are useful. Finding the useful one and then recognising when it ceases to become useful is the hard problem.
In [PR#572](https://github.com/snowflakedb/spark-snowflake/pull/572), Snowflake has removed this feature in their spark connector without any real explanation.
reach me at satyajeet at kanetkar dot co dot in