Receber por email
← Voltar para o catálogo

technical-research

Research before craft for long-form technical content. Profile the audience (knowledge level, jobs-to-be-done, prior beliefs), tier sources (primary > peer-reviewed > authoritative > popular > vendor), triangulate every load- bearing claim across three sources, manage evidence types (data, expert quotes, demonstrations, case studies, source code), and apply citation discipline (when, how, link-rot

9estrelas
Atualizado há 4 meses

Ver no GitHub ↗ Licença: MIT

Como adicionar

/plugin marketplace add viktorbezdek/skillstack

O comando exato pode variar conforme o repositório. Confira o README no GitHub.

Para o autor da skill

Cole no README do seu repo

Mostra que sua skill está catalogada na Skillteca, gera backlink e tráfego rastreável.

[![Skillteca](https://www.skillteca.com.br/api/badge/technical-research-viktorbezdek/svg)](https://www.skillteca.com.br/skills/technical-research-viktorbezdek)
#ai

Skills relacionadas

Ver todas de Pesquisa e Web →

Alerta por categoria

Receba novas skills de Pesquisa e Web toda segunda

1 email curto, só com as skills novas de Pesquisa e Web. 4 minutos de leitura, sem spam, cancela com 1 clique.

Você confirma o email no primeiro envio. Sem spam. Cancela com 1 clique.

Ler descrição completa

Technical Research

A claim without a source is a guess. Three sources that copy each other are still one source. The most expensive sentence in a technical article is the one that turns out to be wrong.

The research phase is where most technical articles win or lose. Drafts written from a thin research base produce the same telltale prose: hedged claims, vague benchmarks, "studies show" with no study, anecdotes presented as evidence. Drafts written from a strong research base produce the o

[Description truncada. Veja o README completo no GitHub.]

Compartilhar X LinkedIn