Tool picks

What a tool can do, where it falls short, and who it suits. Notes on use cases and official sources to help you make your own choice.

Long-term use, hands-on trials and source-based research are labelled separately. These are editorial notes, not rankings or purchase advice.

Featured note · Source-based research

VS Code: editing, terminal and debugging in one workspace

Consider VS Code if you want control over your project files, runtime and code changes. Do not expect every project environment to arrive preconfigured.

Read the note

All tool notes 3

3 notes found

Visual Studio CodeCodingSource-based research

VS Code: editing, terminal and debugging in one workspace

A candidate for people moving between code, a terminal and version control. Establish a working project before deciding which extensions to add.

Consider VS Code if you want control over your project files, runtime and code changes. Do not expect every project environment to arrive preconfigured.

Read the note
ObsidianWritingSource-based research

Obsidian: a candidate for people who want local notes

Focus on local Markdown files, links between notes and whether you can maintain your material over time—not how impressive a graph looks.

Try Obsidian if local files and a portable note format matter to you. Test a small collection before building a complicated system.

Read the note
ZoteroResearchSource-based research

Zotero: organize sources and citations before the deadline

For people who regularly collect research, maintain bibliographic information and cite sources—not just format a bibliography at the last minute.

Consider Zotero when your writing needs traceable sources. Organizing them while you read is easier to control than reconstructing a bibliography at the end.

Read the note