Effective game development and not only

Tools that help make life easier and speed up everyday tasks are the weakness of many developers. This story is about such things. A few months ago I wrote a video of my game development workflow for a comment on Habré.
After that, I promised to paint how everything is arranged there. The time has come.

Here is the video of the development process

Livereload

The video solves the problem of fast iterations when developing flash games. We need to see the result for debugging the gameplay. For this, I use the livereload tool ( livereload ). The brainchild of the Russian developer to the word. You can collect it for free on your own or pay the author.

So, we need to catch the source save event and then collect the flash file for this event. To do this, tick the “Run a custom command after processing changes” and write your script to build the flash file. In my case, this is haxe, haxenme and build is very simple -
“ nme build MyGame.nmml flash -web ”.
Haxenme creates the Export / flash / bin folder, where index.html is located, which already contains our flash file. Now in order to bring the USB flash drive into the browser, just start a simple http server -
“ python -m SimpleHTTPServer 8000 ”.
In the browser (chrome || firefox) - 127.0.0.1:8000/ and click on the livereload widget, which will catch the changes and reload the page.

Tmux, teamocil

Actually, there is a lot of action at the very beginning, but they can be automated. For this, I use tmux, teamocil (http://remiprev.github.com/teamocil/).
For the game, I created a teamocil yml file for the initial actions -
Config File GIST
')
I work on several projects at once. Each project requires its own console and certain steps to start development.
Here for example I want to continue to write the game. To do this, I close the tmux session - ctrl-b + d. Run tmux again. I execute teamocil game - here. And voila everything is ready, it remains to open the browser and dial 127.0.0.1:8000.

Vim

For developing anything, I use vim. If the project is large and there are a lot of op, then sometimes I use ide, but this is a special case. Vim is a common case for developing on everything and everywhere. Here is an example of developing one of my projects -


In this video, the steps are clearly visible: tmux, teamocil, vim and browser to your taste.

My settings for vim are in github.com/Partysun/.dotfiles

The main project now is totallicks.com - a service for music education. The project is big and I do several different tmux sessions for it at once. Separately frontend and separate backend. In the backend form, I cut the console like a real ide. Separately, a window for tests and for vim, and a separate one for the server and logs.
In vim, the main workflow is built on cmd-T. Quick jump to the file, if you need to open several tabs and jump between them. I often use gi to jump to the last change. Another ctrl-o and ctrl-i for jumping to the latest changes directly between files.

At this point I will pause. If you're interested, I'll record a video with effective work in vim / tmux style with details.