A good code editor is the heart and foundation of a developer’s toolbox.<\/strong><\/p>\n\n\n\n There are a lot of them out there. According to Stack Overflow’s yearly survey<\/a>, 75% of developers, including myself, use Visual Studio Code<\/a>. There’s a reason it’s so popular. VSCode has a very large & well supported plugin ecosystem via the VSCode marketplace. This allows the developer to highly tune their environment to their needs.<\/p>\n\n\n\n I asked the some other web developers at Swarthmore, and they all use VSCode as well. However all of us use different extensions. <\/p>\n\n\n\n As for myself, I use the following extensions (I am going to ignore language support plugins here)<\/p>\n\n\n\n Les Leach<\/strong>, Web Developer at Swarthmore says he and his team makes great use of the Docker extension<\/a>.<\/p>\n\n\n\n Kenny Whitebloom<\/strong>, Frontend Developer at Swarthmore mentions he uses the GitLens<\/a> plugin, which supplements and enhances git support for VSCode.<\/p>\n\n\n\n Michael Kappeler,<\/strong> Web Developer at Swarthmore says that he really likes the rainbow csv<\/a> plugin, which is helpful for working on large csv files. He also uses the Dracula theme<\/a>.<\/p>\n\n\n\n There are other good code editors out there, VSCode just happens to be the most popular.<\/p>\n\n\n\n Some other notable IDEs are Visual Studio<\/a>, JetBrains<\/a> (each language has a different IDE, but they are all fundamentally similar), and if you are on macOS or Linux, zed<\/a>.<\/p>\n\n\n\n Sometimes you don’t want to open an entire IDE to edit a few lines of text. This is where generic text editors shine.<\/p>\n\n\n\n Personally, I use neovim<\/a> for most text editing, or Notepad++<\/a>, depending on if the file is in WSL or not.<\/p>\n\n\n\n Les Leach<\/strong> mentions that he uses BBEdit<\/a> because of it’s powerful text processing capabilities, one of them being a feature called Zap Gremlins<\/strong>, which is useful for finding hidden control characters. (Anyone who has copy + pasted code to their editors know this is a big PITA!)<\/p>\n\n\n\n Other editors (specifically terminal-based ones) include emacs and nano.<\/p>\n\n\n\n It’s important to keep a few browsers installed to ensure your websites look the way they should in each. You can check out the W3C Browser Statistics page<\/a> for a sense of what browsers the internet is using.<\/p>\n\n\n\n I keep Chrome and Firefox around to test.<\/p>\n\n\n\n During development, I tend to use Google Chrome. Chrome<\/a> or Firefox<\/a> are both good choices here, as both have robust developer tools<\/a> (which you will be using a lot!).<\/p>\n\n\n\n Depending on your browser, you may also want to look into automated testing to measure the quality of your site. Lighthouse<\/a> is a great all around testing solution, and has a Firefox Add-On<\/a>. If your testing is more accessibility-forward, aXe devtools<\/a> is great to have, and has both chrome<\/a> and firefox<\/a> extensions.<\/p>\n\n\n\n I asked some of the other developers in ITS what they were using, and Docker seemed to be one of the must-haves. <\/p>\n\n\n\n Les Leach<\/strong> mentions this: Docker<\/a> is one of the best developer tools we use. Docker allows us to develop multiple projects at once without have to install different software packages or server platforms on our workstations to complete the job.<\/p>\n\n\n\n When working in a team settings, docker is a godsend. For those not in the know, or who need a refresher, docker allows you to containerize an entire instance, allowing quick and easy sharing between developers.<\/p>\n\n\n\n Git is an indispensable tool that introduces version control to your project (and so much more). If you are developing anything at all, it’s probably a good idea to make sure your project is using it. If you are looking to learn git, Learn Git Branching<\/a> has a fun game aimed at teaching newcomers.<\/p>\n\n\n\n Or some other AI assistance is a very helpful thing to have while you are developing. I’ve found it useful as a replacement for scrolling through documentation and helping build out react components.<\/p>\n\n\n\n Andrew Ruether<\/strong>, Director of Academic Technology at Swarthmore mentions that he’s used ChatGPT for things like data visualization, SQL queries, and comparing & mutating datasets.<\/p>\n\n\n\n ChatGPT’s DALL-E<\/a> is also very useful for generating images (though most of the time, they are pretty mid, as shown in this article’s featured image).<\/p>\n\n\n\n Most developers also have a go-to tool to test out making requests to APIs.<\/p>\n\n\n\n Les Leach<\/strong> says ARC<\/a> is a useful tool for this.<\/p>\n\n\n\n I’m old-school and like using curl<\/a>, but have used Postman<\/a> for larger projects. I will probably check out ARC soon though, since Postman has become a bit bloated in the past years.<\/p>\n\n\n\n In summary, a code editor, git, and a decent browser (chrome or firefox.. sorry safari users) are the basics of a web developer’s toolbox. <\/p>\n\n\n\n If you are collaborating with others, Docker is a great way to containerize your app so that it runs the same on everyone’s machine.<\/p>\n\n\n\n Do you have any tools you’d like to share? Feel free to email me at aweed1@swarthmore.edu<\/p>\n\n\n\n Cheers!<\/p>\n","protected":false},"excerpt":{"rendered":"Text Editors<\/h2>\n\n\n\n
Browsers<\/h2>\n\n\n\n
Docker<\/h2>\n\n\n\n
Git<\/h2>\n\n\n\n
ChatGPT \/ AI<\/h2>\n\n\n\n
Requests<\/h2>\n\n\n\n
The End? <\/h3>\n\n\n\n