Awesome! @Ninthony, it's a great tool for speeding up the development process. Also, I enjoyed looking at that map graphic you shared - there are many directions you can go in your future as a developer, and I would say it's a matter of what kind of work interests you the most. Focus on the frontend if you like design and visual results, focus on the backend if you like organization and problem-solving (generalizing, but you get the idea).
So far I haven't had the luxury of specializing in either, so I'm on a quest to become the best 'full-stack engineer' I can be. It's not a bad goal to understand both halves of the equation!
@neckerson how do you handle updates made by another devloper? For me as someone who is working with another person, he's constantly making changes and so am I. So though I can work locally now, if he ever makes an edit to any of these files I'm guessing I'll have to redownload them? This kind of seems like a pain, dont know if there's a way around it though.
You are not the first person to have this problem. What you're looking to implement is something called 'source control'. It's a way for multiple people to work on the same files, tracking and merging their changes as they do so.
There have been many source control systems used over time, but one of the most popular today is Git. You can learn how to use it via this tutorial, and other resources.
@CarloBernava I wouldn't let the 'maintenance mode' scare you away if you're interested in this project. So far I haven't felt the pinch of Slate's beta-mode too badly. The jankiest aspect of the setup seems to be SSL permissions when you're previewing the site in your browser - some Shopify plugins (i.e. Product Reviews) won't load unless you log into your Shopify store and preview the theme via the online interface there -- it's not a true local development environment yet.
Otherwise, you'll probably be happy with Theme Kit -- it's a straightforward way to speed up your theme workflow and preview your changes faster!