fazkan

I also asked perplexity to analyze the data in all of these threads, this is what it came up with

https://docs.google.com/spreadsheets/d/1_ASxAG38uP3_vcVqVnhP...

You should have guardrails, that catches these critical paths.

Shipping is a muscle, and every engineer knows how to ship good production code, just that we end up spending too much time, on perfecting tiny details. Just have good engineering discipline. Feature-flags, beta releases.

A good question to ask is why aren't you shipping every week, regardless of how critical your feature is.

looks really cool.

this is actually really cool

its pretty cool, though you might be trying to answer the questions to the meaning of life there.

I would simplify it a bit.

P.S. the correct url is fyikamran.com/llms.txt (you were missing an s)

More details https://substack.com/home/post/p-196485708

I am building docsalot to address this particular problem. It keeps the docs in sync with code

https://docsalot-docs.docsalot.dev/quickstart

We also have a full fledged web-client.

this is one of our customer

https://docs.backboard.io/api-reference/assistants/create

why do I feel that this post itself was written by AI

true, but sometimes basic ideas need to be iterated.

I agree, but honestly the example blog you shared also sounds like AI :). The em-dashes are not helping.

its a study on the market, purely based on empirical observation. Not a theoretical limit on the size of the models.