I have been a casual Sublime Text user for some time now (around 4 years). I primarily used it to write code in languages I was tinkering around with. My first exposure to writing code was in around 2005, when I was freestyling with HTML/CSS to customize my public MySpace profile. Then, I could never imagine how powerful a tool like Sublime Text 3 could be. Over the course of this week, I was exposed to many of the built in functions of the editor and how to extend it using add on packages and custom snippets.
I use the default theme in my Sublime Text 3 configuration in conjunction the Solarized Dark color scheme. According to many, the Solarized color pallet is less strenuous on the eyes. Also, I prefer to work in dim light, so Solarized Dark is my color scheme of choice.
My favorite package, thus far, is Emmet. When I was first exposed to HTML\CSS, I could never imagine using a tool like Emmet for code generation. Emmet takes abbreviations of HTML in what is essentially an equation and expands it to complete nested code. It uses symbols to differentiate between elements that are either parent|child relationship vs siblings. Additionally, symbols can be used to add id’s or classes to elements. Still, I am fascinated by how much more efficient this package makes the process of writing markup.
There are also many useful built-in keyboard functions. For myself, I think it’s a tie for most useful keyboard shortcuts, split screen view and multiple cursor editing. Split screen view is powerful for comparing and referencing code for homogeneity and debugging. Multiple cursor editing is such a time saver. The list goes on and on for Sublime’s built-in functions, but those definitely stand out to me and will be ones that I will use heavily.
As software developers, we take pride in not having to repeat ourselves by writing modular code. With custom snippets, our code has the opportunity to become even modular by creating templates for code that we use frequently and allowing us to plug in the syntax that does change. This is definitely a useful feature for any developer. I, myself, will be inspecting my code weekly to examine any trends and create snippets for code I recreate.
Total Study Time Day 0-6: 35 Hours.