Earlier quoted context omitted.
The typing was never the bottleneck.
Based on what I'm using AI for these days, seems like it always was.
Not everyone is using AI for everything
171–180 of 565 posts
Re: Not everyone is using AI for everything
#172Re: Not everyone is using AI for everything
#173Re: Not everyone is using AI for everything
#174"low effort and convenient" seems to consistently win over "best quality" and this is going to be a downgrade in everything, for everyone
Re: Not everyone is using AI for everything
#175Re: Not everyone is using AI for everything
#176Not everyone but most. And I've been having this discussion with people around me a lot lately and everyone that has the ability to think more than half a step ahead sees it(and frankly we are fed up). I previously discussed how a friend admitted that he's never seen the code that powers his project at an S&P 500 company. Yesterday I was talking to another friend and former coworker who complained that when cloudflar…
Re: Not everyone is using AI for everything
#177Earlier quoted context omitted.
At some level everything an agent does is through a "programmatic interface" (tool calls). Some people might use skill-based scripts, MCPs, or some kind of raw access to a database. My point is that well designed CLIs are the optimal programmatic interface, for many reasons.
Sorry what other option is there? Is it going to create an API call from scratch every time after reading a page of documentation? Wait raw access to the database? That’s one of the options for issuing a refund?
Re: Not everyone is using AI for everything
#178Re: Not everyone is using AI for everything
#179If I worked in marketing/growth for an AI company I would try to consider some ways of breaking through this gap.
Re: Not everyone is using AI for everything
#180Earlier quoted context omitted.
Or just write it yourself?
Because typing “code” takes time and significant amounts of it. We are slowly waking up to the fact, which was always true, that “coding” is just a fanciful preparatory task in order to appease the spirits properly so that we may invoke the spirit of what we are actually after: a live, running process that does useful things. Code is completely useless when separated from that fact. Typing it is a complete waste of t…
That is one of the things code does. It also communicates the developer's thoughts about how that process should work to others. If the latter is neglected, the code becomes very difficult to collaborate on. Very few lines of code that are written are "write once". Mostly they're changed, repeatedly, over time by many people. The live, running process is a very temporary entity by comparison. Yes, it needs to exist and do useful work. No, it is absolutely not the only thing that matters.