A good monospaced font and they can look really sharp!
I will definitely give this tool a shot.
I will also shout out monodraw as a really nice little application for building generic ASCII diagrams- https://monodraw.helftone.com/
1,979 karma · joined February 26, 2019
A good monospaced font and they can look really sharp!
I will definitely give this tool a shot.
I will also shout out monodraw as a really nice little application for building generic ASCII diagrams- https://monodraw.helftone.com/
This gets more and more difficult with modern development practices. Development benefits greatly from fast release cycles and quick iteration- the other job functions do not! QA is certainly included there.
I think that inherent conflict is what is causing developers to increasingly managing their own operations, technical writing, testing, etc.
You were on the money with “UI just a reflection of the folders/files on disk that the AI updates.
There is no real UI integration with the AI, other than the UI embedding the chat interface of a coding agent (using an embedded terminal)
The UI just uses a filesystem watcher to keep track of updates to the relevant directories or files.
If you win? Good luck collecting damages from China, and have fun suing the next brand that starts selling the same machine in different plastic
I switched jobs somewhat recently. At my previous job, where I was on the codebase for years, I knew where the changes should be and what they should look like. So I tried to jump directly to implementation with the AI because I didn't need much help planning and the AI got confused and did an awful job.
In a new codebase, where I had no idea how things are structured, I started the process by using AI to understand where the relevant code is, the call hierarchies and side effects, etc.
I have found by using the AI to conduct the initial investigation, it was then very easy to get the AI to generate an effective spec, and then it was relatively easy to get the AI to generate the code to that spec. That flow works much better than trying to one shot implementation
They aren't worth bothering with for one off tasks or supervised workflows.
The major advantage is that a tool can provide a more opinionated interface to the API then your openAPI definition.If the API is generic, then it may have more verbose output or more complex input then is ideal for the use case. Tools are a good place to bake any opinion in that might make it easier to use for the LLM
Google/facebook do that today, because the content they're showing is created pre-ad, and the ads have to be injected after the fact.
With AI- the content is being generated in the same place that the ads are being injected, which allows us to be much more subtle about it.
How much do you think a car company would pay for to put special training weight on their marketing materials? I would guess big money
It seems to me that these AI companies are seeing no shortage of cash investments either.
If you are a startup, and you want to buy AI infrastructure, you would typically sell equity to a VC and use that money to buy infrastructure.
If the AI infrastructure vendor would offer to buy that equity, rather than a VC, that’s preferable because you may get ongoing special treatment from the vendor once they have a stake. So it’ a great deal for the startup.
For the infra vendor- you can likely get a good deal on the investment, you get some exposure to higher upside, and it may be useful to manage your cash flow.
Seems like strategic high value moves to me. It’s no wonder the market likes it
You can debate all day whether bringing your own tools is a good thing vs giving the LLM a generic shell tool and an API doc and letting it run curls. I like tools because it brings reproducibility.
MCP is really just a json RPC spec. json RPC can take place over a variety of transports and under a variety of auth mechanisms- MCP doesn't need to spec a transport or auth mechanism.
I totally agree with everybody that most MCP clients are half assed and remote MCP is not well supported, but that's a business problem
Every LLM tool today either runs locally (cursor, zed, IDEs, etc.) so can run MCP servers as local processses w/ no auth, or is run by an LLM provider where interoperability is not a business priority. So the remote MCP story has not been fleshed out
In isolation, freedom is wonderful. In practice, maybe not? If a member of the star trek crew abused twinkies to the extent that they were lethargic or unhealthy, it would negatively impact the mission.
There is some compromise between freedoms and social resposibility
Your complaint is likely a product design decision rather than a engineering capacity prioritization one. As you've noted the fix is pretty trivial. I imagine that some designer or product person is intentionally holding this back for one reason or another
In the sentence you provided, you make a series of points, link them together, and provide examples. If not an em dash, you would have required some other form of punctuation to communicate the same meaning
The LLM, in comparison, communicated a single point with a similar amount of punctuation. If not an em dash- it could have used no punctuation at all.