I really love to code, and sometimes the ideas come so fast, my head, that I just can't wait to get
him down into the editor.
So I need to make sure my editor can keep up with me and do everything I need so it doesn't block those
ideas from coming out.
And that's one of the top reasons I use code is my editor.
When we choose our tools, we each have our own reasons for doing so.
So let me share with you my top reasons for using code.
No one code is vast, I mean, I love how lightweight this tool is, it's so fast, it opens fast and
it's multi instant.
So I can have multiple instances and toggle between different projects.
Sometimes I've got four or five these open.
Need a new one, great to stop a new instance or go to terminal and do Code Bam opens right up, I don't
see any spinners.
I don't see any funny messages about please wait, it's great because it just gets out of the way.
And that's important because.
Well, one be on my list is I'm faster with code.
I mean, I just love how fast the tool is, I can edit fast, I can debug fast, I can navigate fast.
And by the way, if I said it's fast.
When I'm writing Inside of code, I feel like the tool is letting me get my thoughts out of my head
and get them down quickly.
It's a much more fluid process.
All right, so number two code is cross platform.
This is great because a lot of times I work on a Mac and OS X, but I also have to flip over to Windows
on my Lenovo.
So it's really important for me to be able to work on both platforms.
And the people I work with on my team, they work with a variety of different kinds of machines, so
whether it's Linux or OSX or Windows, I know that code is going to help me out.
Number three is that code has a debugger, I can't tell you how many times I've been sitting, looking
at some node code and kind of resisting going and debugging it through node inspector.
Are cranking up another tool, because I don't feel like waiting for it to get ready to debug code makes
it easy to debug.
Got a problem, set a break point press run, bam.
There we go.
Number four code has Rich Intellisense, so weatherman see Sharper TypeScript or JavaScript with iOS
five or six using Jason.
It's great because I get all this Intellisense and autocomplete, not to mention all the hints in the
hovering and other features that you get.
And well, number five for me is kind of a cop out, it's really a bunch of features on one because
code has a ton of refactoring features.
This just makes it easy to change code because I'm convinced that I don't know about you, but I spend
more time changing and reading code than I do writing it.
So I write my code and then I have to tweak it and change it or refactor it.
So it's important to me that my tool makes it easy for me to refactor and I can run tasks in there like
gulper graunt directly from the code.
I can go to symbols or files or tasks, look at all references.
It makes it just a keystroke away for anything I need to do.
And sometimes code will give me a hint that maybe it thinks I should be refactoring something.
It just puts a little light bulb up there.
And when you're working with all these different kinds of technologies and frameworks, it makes it
an easy choice to use a tool that can handle all of them.
And if you're looking for their 15 second elevator pitch on why I use code.
Is to me, it fits perfectly in that sweet spot between the Ed and the idee for most of what I do in
my own workflow.
So that's an important piece there.
The editor in the IDY, what is the difference between those?
Let's take a deeper look at that.