Here’s some background about my current project, feel free to skip straight to the tips section below.
As of recently I’ve been hired as an undergrad research assistant at UTK. I’m developing a reimplementation of PatchWorks by Austin Henley (who I’m working for).
The new project is now named CodeRibbon, since we’re essentially starting from a clean slate in terms of codebase, and we’re rethinking a few human interaction factors.
For the reimplementation we wanted something that can be used in the real world, since the plan is to make CodeRibbon open source and easy to install & use.
In the end we chose to make it an Atom plugin because of how easily and rapidly we can prototype and design a full IDE experience. It’s not called “the most hackable editor” for nothing.
So here are some useful tips I’ve learned while working on Atom plugins.