Tools and Practice / Editors, IDEs and Debuggers

Overview

I don’t care which editor/IDE/debugger that you use - it’s your workflow. That said, I do think there is enormous value to be had from a well configured working environment that leverages available tooling. For example, knowing how to use some form of debugger will significantly improve your productivity and reduce the daily frustrations of developing code.

In this section you will find overviews of the range of tools to use and suggestions on how best to configure each tool for the situations I most often use them.

Editors

List of editors that engineers use (sorted alphabetically):

• Atom
• Sublime Text
• vi(m)
• VS Code
• WebStorm

Resources

Sublime Text

Plugins

• PHPcs
• PackageControl
• EditorConfig
• JsPrettier (you will need to configure it to auto-format on save)
• Babel (for JSX syntax–though looking for better option)
• Git

vi(m)

• VimAwesome.com provides a list of vim plugins sorted by how many gitlab dotfiles repositories have integrated the plugin.
• VimCasts short, bite-sized lessons on vim

Plugins

• vim-ale - Asynchronous code linter
• editorconfig
• vim-fugitive - A Git wrapper so awesome, it should be illegal
• vim-go - golang development plugin for vim
• vim-javascript
• vim-plug - Minimalist plugin manager
• vim-prettier
• Recover - Displays a diff before recovering a swap file

VS Code

Plugins

• Prettier
• Path Intellisence