# The VS Code method: Tightening a developer's inner loop

DevFeed: [The VS Code method: Tightening a developer's inner loop](<https://devfeed.tech/articles/the-vs-code-method-tightening-a-developer-s-inner-loop-10157.md>)

Original publisher: [Read original article](<https://www.figma.com/blog/the-vs-code-method-inner-loop/>)

Author: Alia Fite

Published: 2024-09-19T00:00:00Z

Content type: article

Language: en

Sources: [Figma Blog](<https://devfeed.tech/sources/figma-blog.md>)

Topics: [Visual Studio Code](<https://devfeed.tech/topics/visual-studio-code.md>), [coding](<https://devfeed.tech/topics/coding.md>), [debug](<https://devfeed.tech/topics/debug.md>), [Tooling](<https://devfeed.tech/topics/tooling.md>)

Tags: [debugging](<https://devfeed.tech/tags/debugging.md>), [developer](<https://devfeed.tech/tags/developer.md>), [development](<https://devfeed.tech/tags/development.md>), [extensions](<https://devfeed.tech/tags/extensions.md>), [vs-code](<https://devfeed.tech/tags/vs-code.md>), [workflow](<https://devfeed.tech/tags/workflow.md>)

## AI overview

The article explains how the VS Code team defines and supports developers' "inner loop": repeatedly writing, compiling, debugging, and refining code in the editor. It contrasts this focused cycle with the "outer loop" of collaboration, issue tracking, documentation, terminals, and other tools, and describes features such as Zen Mode and extensions that help reduce distractions and maintain flow.

## Source excerpt

Developers have to split their time between heads-down work and collaborative touchpoints. VS Code aims to reconcile their competing priorities to keep them in the flow.