https://docs.google.com/spreadsheets/d/1_ASxAG38uP3_vcVqVnhP...
505 karma · joined January 12, 2015
https://docs.google.com/spreadsheets/d/1_ASxAG38uP3_vcVqVnhP...
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.
I would simplify it a bit.
P.S. the correct url is fyikamran.com/llms.txt (you were missing an s)
https://docsalot-docs.docsalot.dev/quickstart
We also have a full fledged web-client.
this is one of our customer
I actually spent some time on it, researching the best practices, and tried hard to make it a useful reference for the future, than just another marketing blog.
Feedback on any improvement of the technical limitation, and just the language would be appreciated .
Also would love to understand anything that people do thats different than whats covered in the blog.
Focus on local, non-western LLMs, is not a unique differentiation, I am sure Peec can implement it tomorrow, if you guys want to.
Or were you only looking for differentiation so you can build it at Peec.
If two products are solving the same problem, eventually they will converge on the same feature-set. You should know that better.
I guess, we can all be a little supportive than putting our competitors down, the market is too big
it automatically creates changelog pages from github PR commits. Still trying to nail down the PR diff to changelog generation, mostly context issues. Rn, I basically summarize each diff and then give that as a context for AI to generate structured changelogs. Works well for smaller diffs, larger diffs loose context.
its free, feedback would be appreciated
video showing how it works
I did my research before jumping into this space :)