Agilis
2008-07-30, 13:15
As a number of you probably know, I'm always plotting new articles to write, and one is getting to the point where it's almost pen to paper time --- the tools that we use on projects. Use the right tool for the job, that's how it's supposed to be. The trick is, how do you know you've found the right tool, how do you know if there's something better if you get too settled down?
Now the obvious way (to me) to frame the article is move from what I use right now, figure out what needs they fill, why those needs are applicable to others, and what influenced me to select that one tool over all the others out there.
But depending on the project, the needs change. Depending on the user, the selection process is different. So, I put the question to you guys. What tools do you use to get your project work done. There are general themes to things, we need to work with text, or communicate, or hack an engine, etc. However, the way they are expressed differs from person to person.
I'm particularly interested in developers, since besides IDA, hex editors, and general purpose programming languages, I have no clue what the specifics are.
Hopefully, as I see more responses, I get a sense of whether the notion I have in my head that I'll write about is close, or wildly different. Either way, an article will be coming in a week or two probably.
In broad categories (don't let my categories restrict your responses), for me:
Version control/remote storage
Subversion
TortoiseSVN on win32, straight svn on *nix
Script/text editing
vim/gVim for plaintext scripts
Texniccenter + XeLaTeX for novelizations and related "print" work
Dictionaries/References
EPWING based Green Goddess on ebView
Yahoo's Kokugo dictionary
Wikipedia/Google
Communication
Email
IRC
Subversion (commit log comments work for tiny teams of 2 >_> )
Now the obvious way (to me) to frame the article is move from what I use right now, figure out what needs they fill, why those needs are applicable to others, and what influenced me to select that one tool over all the others out there.
But depending on the project, the needs change. Depending on the user, the selection process is different. So, I put the question to you guys. What tools do you use to get your project work done. There are general themes to things, we need to work with text, or communicate, or hack an engine, etc. However, the way they are expressed differs from person to person.
I'm particularly interested in developers, since besides IDA, hex editors, and general purpose programming languages, I have no clue what the specifics are.
Hopefully, as I see more responses, I get a sense of whether the notion I have in my head that I'll write about is close, or wildly different. Either way, an article will be coming in a week or two probably.
In broad categories (don't let my categories restrict your responses), for me:
Version control/remote storage
Subversion
TortoiseSVN on win32, straight svn on *nix
Script/text editing
vim/gVim for plaintext scripts
Texniccenter + XeLaTeX for novelizations and related "print" work
Dictionaries/References
EPWING based Green Goddess on ebView
Yahoo's Kokugo dictionary
Wikipedia/Google
Communication
IRC
Subversion (commit log comments work for tiny teams of 2 >_> )