Explore >> Select a destination
|
You are here 
|
richardtier.com | ||
| | | | |
blog.mendeley.com
|
|
| | | | | New About Dialogue and it's even closable on Mac! How on earth did we get to this point? Let me tell you a story... Since my last post the Mendeley Desktop team has been very busy indeed! Our "rewrite of some of the internal Mendeley code" has turned into a rewrite of almost all the... | |
| | | | |
anthonysciamanna.com
|
|
| | | | | When I work with developers who haven't practiced Test-Driven Development (TDD) one question often arises, When is code too simple to test? As someone wh... | |
| | | | |
saeedesmaili.com
|
|
| | | | | Many companies are integrating LLM question answering tools into their DevEx toolchain. If you're writing documentation and you'd like to assist these tools to serve people with proper responses to the questions related to what you own, kapa.ai has a few practical tips on optimizing the technical docs for LLMs: A clear hierarchy of headings and subheadings on a page helps LLMs understand the relationships between different sections of your documentation. Troubleshooting sections formatted as Q&A are an effective source for LLMs as they mirror the questions users often ask, making it easier for LLMs to understand and respond to similar questions. Including small, self-standing code snippets can be helpful, especially for products that rely on large and often complex SDKs or APIs. Have a brief description above the code to clarify its purpose and usage. Include comments within the code to explain the logic and functionality. Keep relevant content directly in your docs rather than in linked files such as PDFs, as LLMs have a harder time parsing these. Ensure information conveyed through screenshots is also described in text, as LLMs parse text more efficiently. Clarify all acronyms and specialized terminology within your documentation to aid LLM comprehension. source | |
| | | | |
www.byjp.me
|
|
| | | I'm building a twitterbot to answer questions about things happening on my university campus. Should be fun, I've decided to use Ruby and Active Record as a foundation :) Might be a few days before anything appears on github, I've got a few exams in the near future! | ||
