nilirl

Sure and that's a new technique for indexing and querying.

Where's the new design tension? Indexes always had to be monitored for freshness and queries have always needed cleaning or parsing.

Maybe I'm old but where exactly are the "dragons"?

How is RAG any different from the search systems we've been building before LLMs? Is it the sudden need for everyone to design a search API and engine that's driven this trend?

If so, I'd like to see more design patterns around existing search problems:

- Correcting or backtracking based on feedback.

- Measuring relevance.

- Comparison with task-based pre-written queries. Does every LLM task need a full blown search engine? Why not a tightly scoped domain API for data retrieval?

My point was your needs and problems are not everyone's needs and problems.

I don't want to think of memory management in most projects, I want to focus on business logic, so I use Node.js instead of Rust, even if the latter gives me more control.

Similarly, I don't want to think of DOM management in most projects, I want to focus on data dependencies, so I use React instead of Web Components, even if the latter gives me more control.

> The idea of reactivity came from or was popularized by Angular.js

No, spreadsheets popularized reactivity. And the general point is incredibly weak.

Don't use frameworks and make your own? Sure, have your fun. But then try teaching your framework to your company of 1000 and see how quickly you realize your view of the "problems" are only a slice of the pie.

This website is straining my brain. Ads that bounce around? Sheesh.

Even with AI I think your animations were high effort. Great job!

> I actually don't have any personal criticisms of Jarred

The whole post felt like a personal criticism of Jarred.

Am I the only one not getting the hate for the website? The site looks fine to me. What about it is bad?

> Truly robust engineering isn’t about what works for most; it’s about gracefully handling the edge cases.

How do you justify this when you factor in cost and time?

Not prevent, just not provide very responsive feedback, right?

I don't know, I understand the principle, but I don't see how you can determine the value of a principle outside of a specific context.

Even for accessibility, we can't target every context in the name of being accessible. We still have to pick which contexts of inaccessibility we'll need to support with more attention.

I understand the design principle but I would argue it's a bad implementation principle.

Engineering attention is finite. Why would you spend time thinking about 8 clicks when most people will only need ~3?

Not all user-action possibilities are equally important, and if they are, then you better have infinite resources to spend on engineering.

I don't want to hate without cause, so I read the prize winning entry 'The June'.

So, now, I can hate with cause: it reads like someone who cares about what their MFA friends think.

Meaning, it puts most of its emphasis on description, and so little on situational engagement. Which makes sense, I suppose, for an LLM.

Honest question: Does the founder end up making money this way? Can you really get rich building a failed business?

I wasn't trying to argue against democracy. I was asking about how we make it feel better.