How we develop
summary
Overview of how the WebStorm team decides which JavaScript languages, frameworks and tools to support in the IDE, how they track ecosystem changes and balance trade-offs when adding features. Describes concrete product decisions, how new capabilities are designed for WebStorm and explains the IDE’s internal architecture and the team’s development process.
AI-written summary · about
chapters (20)
- 0:00Welcome
- 3:11Our experience
- 8:21Team structure
- 10:29Synchronized releases
- 12:38WebStorm focus
- 14:52Roadmap planning
- 17:23Task prioritization
- 22:26Open issue tracker
- 25:24Using our products
- 27:11Market and tech analysis
- 29:58Rejecting user requests
- 33:13Post-release process
- 35:45Early access and CI
- 36:50Large code changes
- 37:54Testing and QA
- 40:25Performance optimization
- 42:09Testers' role
- 43:59Adapting to new tech
- 44:41Core principles
- 45:25Contact and join
related talks
46mHow We Build WebStorm
02minterviewed – John Lindquist
44mAsk Me Anything (AMA) With the WebStorm Team
07h 57mJetBrains JavaScript Day 2024
52mIDE Tooling for JavaScript
58mHow We Support New Technologies, Languages, and Frameworks in IntelliJ IDEA
07mA quick word about JetBrains now and later
19mLet your tool help you imagine