Quiz collegato alla guida · Medio Livello
Quiz sull'intelligenza artificiale per scrittori tecnici
Testa la documentazione assistita dall'intelligenza artificiale: docs-as-code con Vale e CI, tipi di contenuto Diátaxis, test di esempi di codice e scrittura di documenti per il recupero dell'intelligenza artificiale.
Domanda 1 di 8
Che cosa fa il linter Vale in un flusso di lavoro docs-as-code?
Anteprima di ogni domanda8 domande
Le risposte e le spiegazioni vengono visualizzate mentre rispondi al quiz.
- Che cosa fa il linter Vale in un flusso di lavoro docs-as-code?
- Generates API reference pages from code
- Hosts the documentation website
- Checks prose against style-guide rules and gives the same result every time
- Translates docs into other languages
- Cosa descrive meglio i documenti come codice?
- Documentation kept in version control and reviewed and built like code
- Writing documentation only inside code comments
- Using AI to write all docs automatically
- Publishing documentation as PDF only
- Quali quattro tipi di contenuto separa il framework Diátaxis?
- Blogs, emails, slides and videos
- Tutorials, how-to guides, reference and explanation
- Drafts, reviews, approvals and archives
- Beginner, intermediate, advanced and expert
- Perché gli esempi di codice generati dall'intelligenza artificiale dovrebbero essere eseguiti come test?
- Tests make pages load faster
- Search engines require tested code
- Testing replaces the need for a style guide
- Models can invent plausible parameters or flags, and tests catch them before readers do
- Qual è la proposta llms.txt?
- A suggested file that points language models to a site's key documentation
- A legal license for AI training
- A style guide published by Microsoft
- A required format for all API specs
- Which writing practice helps AI assistants that retrieve documentation?
- Long pages with no headings
- Frequent references like 'as mentioned above'
- Self-contained sections with descriptive headings and explicit product names
- Putting all content in images
- How was API reference documentation commonly produced before generative AI?
- It was always written entirely by hand
- It was generated from specs or code comments with tools such as Swagger UI, Redoc or Sphinx autodoc
- It did not exist
- It was produced by speech recognition
- According to the guide, where does a technical writer add the most value alongside AI?
- Typing faster than the model
- Avoiding version control
- Removing all human review
- Checking accuracy, deciding what users need and structuring information