Originally Posted by marfig
I'm thinking more in terms of the process of development as a whole. Not so much, specific tasks directly related to programming. You eventually have some code editor opened, external documentation, auxiliary applications of all sorts, possibly even a local database... essentially we tend to end up with a working set of applications that is ripe with file IO operations going in the background to support them.
Oh, whoops; I misunderstood
I wholeheartedly agree that the general workflow will be much
better when working with an SSD. That doesn't only apply for coders, but any developer or heavy multi-tasker. Once you become spoiled to a near-lack of waiting for a file to open or program to load, it's really, really difficult to go back.
I upgraded to an SSD a couple of months ago (I was long overdue, thanks to laziness) and in general still can't get over the super-fast response of the OS as a whole. In the time I used to load an OS and a single application I am already raring to go with five or six applications loaded on an SSD. It's impossible to consider running an OS on an SSD again ;-)
If it fits your budget, I wouldn't hesitate to recommend upgrading to an SSD to improve workflow.