Switch Audience
Text Editors — Your Workshop, Not Just a Notepad
Book Index
Chapter Weight
22
Why do it this way?
You could write a novel with a crayon on a napkin. The story would still be a story. But you wouldn't, because the tool matters — not just for comfort, but for what becomes possible.
A text editor is where you will spend most of your working life as a web developer. Every HTML file, every stylesheet, every PHP function, every configuration file, every line of JavaScript that works perfectly and then somehow doesn't — all of it flows through your editor. It is your workbench. The difference between a bare workbench and a well-equipped one is not whether you can do the job. It's how long it takes, how many mistakes you catch before they matter, and whether you finish the day feeling like a craftsperson or a person who fought their tools all afternoon.
A bad editor — or a good editor used badly — will let you make mistakes it could have caught. It will let you forget to close a tag, mistype a function name, and stare at a broken layout for forty-five minutes because a single quotation mark decided to go on vacation. A good editor, configured for the work you do, will catch that quotation mark before you even save the file.
This is not about personal preference in the way that, say, your coffee order is personal preference. Your editor affects your output, your error rate, and honestly your mood. It is worth spending twenty minutes understanding what a modern code editor can do before you spend the next several years inside one.
How to do it:
A modern code editor is not Microsoft Word for code. It is an environment. The features that matter for web development are:
Syntax highlighting — the editor reads the language you're writing and colors it accordingly. A misplaced bracket turns a color it shouldn't be. You see the mistake before it breaks anything.
Autocomplete — the editor knows what functions, variables, and tags exist in your project and offers to finish your sentences. This is not laziness. This is fewer typos.
Integrated terminal — run commands without leaving the editor. For Drupal work this means Composer, Drush, and Git all within arm's reach of the file you're editing.
Extensions — the editor becomes aware of your specific stack. Twig templates, PHP linting, CSS validation — installable in minutes.
Git integration — see what changed, stage commits, and review diffs without switching applications.
Visual Studio Code — VSCode — does all of this, is free, runs on every operating system, has a vast extension library, and has become the de facto standard in web development. It is the recommendation here. Not because it is the only answer, but because it is the best return on zero dollars, and the community around it means that whatever problem you have, someone has already written the extension.
Download it at code.visualstudio.com. Spend an hour in it before you customize anything. Then start adding extensions for the languages you work in.
Alterative Options
Text editors are like opinions — everyone has one, and some people have several. The landscape is enormous, ranging from the sublime to the inexplicable.
Notepad — it ships with Windows, it opens files, and that is the complete list of its qualifications. You can write code in it the same way you can dig a foundation with a soup spoon. Technically possible. Not recommended.
Sublime Text — fast, lightweight, and beloved by developers who discovered it before VSCode existed. Still excellent. Technically paid, though it will remind you of that fact politely and indefinitely without actually stopping you.
PhpStorm — a full IDE (Integrated Development Environment) with deep PHP and Drupal awareness. Powerful, opinionated, and $250 a year. Worth it if you're billing at professional rates and want the editor to do heavy lifting. Overkill if you're just getting started.
Cursor — a newer AI-native editor built on VSCode's foundation. Interesting if you want AI assistance woven into the editing experience itself rather than bolted on.
Vim / Neovim — ancient, modal, and still used by developers who enjoy explaining why they use Vim. There is a learning curve that several people have described as a cliff. It is extraordinarily powerful once mastered. It will also teach you that there are many ways to exit a text editor and all of them require knowing the right incantation.
The honest answer is that VSCode is where you should start, and possibly where you should stay. It is free, it is everywhere, and the time you would spend mastering an alternative is time you could spend building something.