I did by writing all (if not 95%) of the CLI commands I use when coding (not just developing) into bash/batch scripts so that I could build and deploy my code in the least amount of manual commands as possible. I know that when I'll be more comfortable with Node and NPM scripts, I'll automate stuff even more so that it would reduce time doing redundant work and using less clicks (so GUI tools) when it comes to that kind of thing.

Certainly! Automating my workflow might have boosted my productivity 400% over the past few years!

Things I've done:

• playball Bash script to update images, DB, ruby gems, git, and finally launch the Ruby on Rails application I was working on
• gameover Shut down the same Ruby on Rails app
• remupdate updates images, DB, and git for another app
• eqcssscrapeScrapes stats from a number of different websites and build an HTML report page
• regenerate For ~1 year I wrote 'Todone' files as Markdown and used this command to convert all markdown files to HTML

For me, I've definitely gotten the most mileage out of Bash scripts - whatever OS you use, learning how to script that is going to be worth more than cross-platform scripts, or NPM scripts, etc etc.

Another great thing to do is create aliases and shell functions for things you do frequently but don't run as a workflow. Investing in your OS's shell is the way to go!

(The other part of my 400% productivity boost was when I stopped using a lot of pre-made software and built my own utilities for the tasks I do over and over. I'm not a programmer by trade - I went to school for graphic design, but building my own tools has been my path to success!)

To me it's mostly about hot module replacement(HMR). I am UI developer with browsers, it saves a lot time by adding HMR. Also building apps with a same workflow will reduce the cost of maintaining.

Continuous deployment was the biggest improvement due to automation for me. The motivation was to avoid mistakes from doing manual deploys to staging / production. Start out manual so you understand the process but then quickly automate.

I'm using BitBucket to store the code and have CircleCI watching for commits. CircleCI gets invoked via webhook, fetches the code, builds and tests it, uploads it to the server, and sends an email if it fails.

Yes.

• Describe the development environment using docker-compose. The motivation, initially, was not wanting to have development libraries installed natively in my PC; now it's not having to install everything manually in every developer's computer, as well as having a centralized and easily editable development environment.
• Run tests on pre-commit hook. The motivation was to force me to write more tests (as well as more easily testable code), to prevent leaking errors.
• CI-tool integrated with VCS server that runs tests in an environment similar to production after every push. The motivation was, again, preventing errors.
• Deploy to staging server on successful automatic tests, with the same CI-Tool. The motivation was not having to mind deployment to staging every time.

I've also written simple shell scripts for other, minor, things.

EDIT: This guide I wrote covers how to get started on everything from the list.

https://github.com/hipkiss91/GitTodo Because I wanted it to be easier to manage all my issues :)