Advanced 6 topic areas 21+ exercises

Developer Tools Engineer

Developer Tools Engineers build the editors, language servers, debuggers, and code intelligence infrastructure that software developers use every day. Their daily English covers writing LSP specification proposals, documenting extension APIs, presenting language server performance improvements, and writing developer-facing documentation for new editor features. This path covers the specialized vocabulary of editor tooling, language server protocols, and code analysis infrastructure.

Start first exercise → Browse all exercises

Topics covered

Language Server Protocol
Debug Adapter Protocol
Tree-sitter grammars
VS Code extension API
Code intelligence
Editor infrastructure

Vocabulary spotlight

4 terms every Developer Tools Engineer should know in English:

LSP n.

Language Server Protocol — a JSON-RPC protocol that standardises how editors (clients) communicate with language-specific intelligence servers — enabling one language implementation to work across all LSP-supporting editors

"Implementing an LSP server for our domain-specific language immediately gave developers go-to-definition, hover docs, and diagnostics in VS Code, Neovim, and Emacs."

diagnostic n.

An error, warning, or hint reported by the language server about a specific code location — displayed as inline squiggles or in the Problems panel

"The language server emits a diagnostic for every unused import, helping developers clean up code before committing."

tree-sitter n.

An incremental parsing library that builds a concrete syntax tree for a source file in real time as the user types — used for syntax highlighting, code folding, and structural code analysis

"We wrote a tree-sitter grammar for our query language, which enabled accurate syntax highlighting in 15 editors immediately."

semantic tokens n.

LSP-based color tokens that allow a language server to provide fine-grained, semantically-aware syntax highlighting beyond what textmate grammars can express

"Semantic tokens let us highlight local variables differently from parameters — something token-based regex grammars cannot distinguish."

Open full glossary →

📚 Vocabulary Reference

Key terms organised by category for Developer Tools Engineers:

Protocols

LSPLanguage Server ProtocolDAPDebug Adapter ProtocolJSON-RPCcapability negotiationinitialize requesttextDocumentworkspaceserver capability

Language Intelligence

diagnosticcode actionhovergo to definitionfind referencesrename symbolcompletionsignature helpinlay hintsemantic tokens

Parsing & Syntax

tree-sitterconcrete syntax treeabstract syntax treeparser combinatorgrammarTextMate grammartokenizerlexerincremental parsingsyntax node

Editor Extension

VS Code extensionVSIXextension manifestactivation eventextension hostwebviewMonaco EditorCodeMirrorZed extensionextension API

Study full vocabulary modules →

Recommended exercises

CI/CD Pipeline Language 5 exercises

Exercises

Technical Writing for API Documentation 3 exercises

Writing

Code Quality Metrics Language 5 exercises

Exercises

Reading Technical Documentation 3 exercises

Reading

Monorepo & Build Systems Vocabulary 5 exercises

Vocabulary

Real-world scenarios you'll practise

Writing an LSP feature proposal: specifying the request/response format, error conditions, and client capability negotiation for a new language server feature
Documenting a VS Code extension: writing the README, feature overview, configuration reference, and known limitations for an extension marketplace listing
Presenting language server performance improvements: explaining the incremental parsing improvements and their impact on time-to-first-diagnostic
Writing a tree-sitter grammar specification: documenting the grammar rules, node types, and test corpus for a domain-specific language