But, since I get asked so often, I will go over my simple local setup.
Let’s begin with the tool most near and dear to my heart. The Stackery CLI lets you deploy all your serverless resources all at once, and has local development superpowers that let your local code get responses from resources inside your AWS cloud. I would love to go into great depth about why our CLI is so great, but we’ve written that piece already :)
There are a few prerequisites that deserve mention on their own:
You’ll need at least two accounts to get started:
And you’ll almost certainly end up using
Though alternatives do exist and Github isn’t integral to my current workflow.
Of course, you have a choice when it comes to IDEs and you can find a surfeit of forums about why one is better than the other. I’ll spare you my own entry about why Microsoft’s VSCode is my choice and instead just say that it is.
Visual Studio code is based closely on the design of Sublime Text, which is still a great code editor though it does cost a bit. Atom, from GitHub, is another free editor with a nice clean interface but I didn’t really find it up to scratch, particularly since it’s hard to find some of the plugins closely related to serverless and AWS.
VSCode has a nice light interface that gives tons of visual space for code. Its most important feature is its fantastic variety of plugins
I’ll note that VSCode has a ton of cool features that I just don’t use: git tracking, and the internal command line are both really useful features that I’m just too used to doing in a separate window. The plugins I do use:
The VS Code + Stackery Plugin unlocks a lot of capabilities:
The only thing I use beyond those listed above is the git CLI. Right now I’m on a very small team and if I were working with more people I might well choose a visual explorer for git.
I use a background image and old-style green text, not because it improves ergonomics but why are we working with computers all day if they don’t look cool?
You can serverless in many different ways, but the goal should always be simplicity— if you’re wrestling with your tools or tracking changes with your team via a spreadsheet, you should probably rethink your setup. Remember serverless is not a technology and you should always be focusing on business logic rather than the details of your platform.