I have three activities with slightly different tools and workflows. * Generic Everything is under Subversion, my employer's VCS of choice. Briefs usually co

I have three activities with slightly different tools and workflows. * Generic Everything is under Subversion, my employer's VCS of choice. Briefs usually come as Word/Excel/Powerpoint files. Compositions usually come as messy Photoshop files that I spend too much time tidying up. Emails are the basis of interaction between departments (we have tried other means but they all failed for one reason or another) and we use Mantis for tracking bugs. I'm on Mac OS X. * HTML/CSS/JS frontend dev When I start a project, I do it with a small script that creates a standard project and puts it under version control. Once it's done, I tipically open the README in Vim, populate it with a bunch of infos on the project and a TODO list. That file is my entry point in the project: $ cd /path/to/project $ vim README Subsequent file navigation is done from Vim itself (either with built-in commands or with CtrlP), keeping the README in its own tab. A tags file for my CSS and JS is generated at the root of the project every time I leave insert mode for better navigation. On the browser side, I used an "autoreload" extension for a long time and now I use tincr http://tin.cr http://tin.cr which works very well. Deployment is never handled by me but is a manual task done with FileZilla, :-( I'm sorry to say that we have no internal guidelines on anything. * "Heavy" AS3 dev (whole apps/sites) Almost everything is done in Flash Builder (with a vim plugin called vrapper) for my new projects or on an old PC in FlashDevelop (used by two previous coworkers) for legacy projects. I also use a little Java app called Vizzy to show debug info when the app is not run from Flash Builder. * "Light" Flash dev (banners) Everything is done in the Flash IDE itself. At home, it's typical linux hackery: terminal+vim.