crosen99

I got off a quick GPT trying to explore the following theme, and I think the results are promising:

In the ever-evolving landscape of creative expression, a new horizon emerges: AI agents. Imagine authors and publishers releasing these agents as they do books or video games, creating interactive narratives and personalized adventures. This is more than just storytelling; it’s a revolution in how we experience and engage with content. AI agents could soon become our guides, companions, and co-conspirators in worlds crafted by human creativity and AI innovation. Are we ready to embark on this new journey? The next chapter in storytelling is being written, and it’s one where the reader becomes a part of the tale.

Well said, and fully agree. If you horse race two approaches, you can of course arbitrarily arrive at a winner based solely on the version of each approach you choose. You need a deeper look if you want to generalize.

They stumbled into a position where they can make a crap ton of money going up the stack, which can fund the ongoing march toward AGI. (The revenue not only is cash in their pocket, but it’s also driving up their evaluation for future investment.)

> we've heard that when people were using chains/agents they often wanted to see what exactly was going on inside, or change it in someway.

I certainly agree, but I'm having trouble seeing how templates help with this. The templates appear to be a consolidation of examples like those that were already emphasized in the current documentation. This is nice to have, but what does it do to elucidate the inner workings?

The biggest challenge I’m trying to track isn’t on the list: online learning. The difficulties with getting LLMs to absorb new knowledge without catastrophic forgetting is a key factor making us so reliant on techniques like retrieval augmented generation. While RAG is very powerful, it’s only as good as the information retrieval step and context size, which quite often aren’t good enough.

You might wonder if these harbingers are actually tuned into an alternate and consistent set of values not shared by the majority, rather than simply irrational consumers. In that same vein, you might wonder if the product managers of these failed products are part of that same cohort.

I keep going back to LangChain thinking it just hasn't found its legs yet, but every time I do I retreat exasperated. I don't find their abstractions useful or intuitive, and their documentation is woefully scattered and incomplete. Things are moving so quickly with LLMs that theirs is no easy task, but so far they haven't really cracked the nut of making LLM app development easier.

Strong disagree. The way I see it, any successful customer service operation needs to have three things in place:

1. Properly defined and articulated customer service policies and procedures

2. A training program that adequately prepares agents to know, understand and apply those policies and procedures

3. Sufficient inherent capability and disposition of the customer service agents to apply that training

My take is that the (relevant) inherent capabilities of LLMs at even at this early stage are as strong or stronger than what I see in the human customer service agents I typically deal with. And the disposition of an LLM can be arbitrarily good through fine-tuning and prompt engineering.

As such, any company that gets 1. and 2. right has a high chance of providing a better support experience by replacing human agents with LLMs.

> AIs, at their current level of development, don’t perceive objects in the way that we do – they understand commonly occurring patterns.

You see this claim everywhere - that AI operates on statistics and patterns and not actual understanding. But human understanding is entirely about statistics and patterns. When a human sees a collection of particles and recognizes it as, say, a car, all they are doing is recognizing the car-like patterns in how the particles are organized that have a strong statistical correlation with prior observations of things classified as a car. Am I missing something?

Not substacks, but I start my mornings reading the TLDR and the TLDR AI newsletters. Lots of overlap with the sort of tech that HN covers. TLDR AI is very useful to keep your finger on the rapidly changing pulse in the world of ML.

This “new technique called implicit code execution” sounds a lot like an early version of the ChatGPT Code Interpreter plug-in.

I wanted to give this a whirl by creating an event triggered workflow, but I got stuck pretty quickly.

I had imagined creating a workflow that would be triggered by the occurrence of some external event, such as a row being added to a Google Sheet. But after struggling with the UX and documentation for a bit, I think I finally worked out that this is not consistent with Fastgen's concept of an event triggered workflow, and that these workflows can actually only be triggered within an API call or workflow that occurs within my Fastgen environment.

Is that correct? If so, I don't believe it's clear or obvious, so perhaps it makes sense to spell this all out more clearly in the UX and documentation. Also, the sort of event trigger I had in mind is an essential aspect of many similar low code tools (i.e. make.com, bubble.io), so it may be worth considering adding this functionality unless you want Fastgen to be all about inbound API calls.