How often do you overestimate and update the development environment and the developer. tools?

I was curious how often other software developers overestimated their development environments and tools. I used to work in a large corporation with tough instruments that everyone hated, but could not do anything about. Therefore, no one ever updated their development environment, because we could not in this environment.

Now that I am in my own startup, I find that I can endlessly spend time on new tools and development environments, but I really should not and cannot afford it. I pledged to spend 1 day a month searching for new development tools and testing them to see if they should be switched.

How often do you test new IDEs, editors, troubleshooting tools, debuggers? Or upgrade to newer versions?

+5
source share
6 answers

I am only updating if I really do not miss any specific functionality, or understand that NOT using one tool instead of another leads to more tasks that take more time / less efficient.

+1
source

, , . , . .

, - . , . , .

, .

-Adam

+4

, . (, IDE, CASE ..) , .

Microsoft, , . OSS , , - , .

+3

IDE,. , , , . dev vim. ( ), DIY. , IDE, , , .

. . . , Subversion 1.4 . Subversion 1.5 .

. , , , . .

. . , , . , , .

, $0,02 .

+3

, . .

, (.. , - vs2008 std edition, ..).

+2

IDE - , . . , - , LINQ, ASP.Net 2.0 3.5 . , . , , , .

- , . QA, , , , . - .

- , Tortoise SVN, . , , - . , , .

OS. , , . , Windows 7, , Vista, , - XP, XP 5 , Windows 2000 Professional NT 4.0 .

PC. There is a policy that every three years we get new cars, which I believe. When I started where I am now, I was on the P4 box, so upgrading to the dual-core box was very enjoyable, as well as a good amount of memory from 2 GB to 4 GB.

+1
source

All Articles