All of a sudden it occurs to me that two people can be called 'programmer' and do radically different things. Surely the typical programmer's toolbox is: an editor, a compiler/interpreter/magic lisp box/whatever, and possibly a debugger.
similar to my toolbox, as an embedded engineer, the number of compilers that I have on my computer is about 8 installation for various different micros, along with this is the same number of debuggers.
I think the title should be "A typical .NET/Microsoft programmers toolbox", as most of the tools listed are useable by MS devs. Case in point, I'm a web developer and I don't have/need most of these in my working laptop (an mba11).
> An editor, a shell and a browser is all you need.
That's great that those are all you need, but they aren't all I need. I wouldn't be able to do the work I do with only those tools. And you wouldn't be able to do the work I do with only those tools either. :-)
Not comparing the value of my work or yours or our skills in selecting and using tools, just saying that the work we do is quite different, and requires different tools, even though we may both be called programmers.
> I feel sorry for all MS devs who have to use so many platform-specific tools.
Don't feel sorry. I'm not even an MS dev these days and I have a very lengthy list of tools I use routinely. (See elsewhere on this page.) And I like it that way: I'm happy that there are so many great tools available to me.
Seems more like "A typical Jeremy Morgan Toolbox". Most of that would be superfluous for being typical in the general sense of a text editor, a reader of some sort, and an execution environment.
