Want to save 1 hour a day everyday on coding?
Do you want to save an hour a day when coding? I hope you do, because I’m going to show you how can do it with the workflow we’re building in Automating Your Workflow :)
Let’s begin.
Here are some things you can automate away (or improve):
1. Automatically refresh the browser (live-reloading) - 10 mins
Whenever you manage to refresh the browser automatically, you save a second or two from your life. This 1-2 seconds doesn’t seem like much as first, but it adds up in the day.
Let’s assume you work for five hours a day, and you refresh your browser twice a minute. That adds up to 600 refreshes (or 10 mins saved).
An added benefit here is that you don’t have to alt-tab and hit refresh on the browser, which saves you some keystrokes as well. This, I feel, is the best part of live-reloading.
2. Faster compile times - 70mins
I remember I wanting to punch my Macbook when I had to wait over 15 seconds to get my Sass to compile every single time. (I did not, luckily).
Waiting always seems like an eternity. The more you wait, the less things you get done. That’s why we go for speed when setting up the workflow.
For example, we use LibSass for faster Sass to CSS conversion. It can potentially reduce your 15-second compile times to less than a second.
If you worked for five hours a day, and you compile once a minute, you save 4,200 seconds (or 70mins).
In addition to LibSass, we also ensure things like optimization processes are cached as much as possible to reduce the compile times. More speed FTW!
3. Error notifications - 30mins to 2hours
Have you had times where you spend half a day trying to find out what’s wrong with your code, and finally discover that it was due to a small error? Nasty feeling, isn’t it?
That’s why we setup processes to check code for any errors, and notify us whenever something is wrong. You get alerted of your mistakes instead of having to hunt for them.
Well, this one is hard to estimate. There’s no way to tell how long you’ll spend debugging silly mistakes. From personal experience, it probably saves me between 30mins to 2 hours a day in the long term.
4. Writing Modular Code - 10mins
Have you had trouble looking for your code as your project grows? What about your team?
How about problems with trying to read large pieces of code?
The workflow we’re going to create allows you to modularize your HTML, CSS and JavaScript files. It lets you keep code small and reusable. This means your team has an easier time trying to read everyones’ code.
You also get to choose how to organize your files so you know how to find them easily. For instance, I’m able to find my code within seconds because I know how they’re split up.
Well, this one is though to estimate as well. I’ll just leave it as 10 mins. :)
5. Stress-free deployment - 15mins
Ah. A pain in the ass if you’re FTPing into your servers manually to deploy your website. It’s difficult to know whether you missed anything out, and you might have the constant worry that you broke your site.
In the workflow we’re going to create, we setup the project in a way that we can deploy immediately with Git or Gulp. This basically takes the pain out of the deployment process, and you can be sure that the new website will be completely updated.
Once you get the workflow, it’s going to be deploy and forget. I’d say this saves you 15mins considering FTPing takes up to 15 mins or so (to deploy website of a decent size) while Git / Gulp takes less than a minute.
Note: The amount of time you save and the amount I save can be totally different depending on what your workflow is right now :)
Anyway, it’s easy to get these time saving benefits into your workflow. You don’t have to be an expert developer. I’ll guide you step by step on how to achieve some of these benefits in the sample chapters you’ve downloaded.
All you have to do is read through the sample chapters! (Click on this link if you misplaced your copy)
If you have any questions, just hit reply to this email and I’ll be happy to help.
Stay awesome,
Zell
PS: You don’t only save time when you set a workflow up for yourself. You’d get other benefits as well. I’ll talk about them in the next few emails to come.