> If someone said they were using VI for development there are a couple > > of assumptions I can make. > > Shame on you, you should know better about assumptions :) >
Sorry but it's experience from working with literally 100's of development shops all over the world and everything from financial to media. I can tell from reading a statement of work most of the time how much experience development shops have. > > 1 is that they don't have any defined standards or standards are not > > being enforced. 2 they probably don't have many defined processes for > > development in general. This is bad all the way around. > > Why can't a company have standards based around VI/VIM or Emacs? What if > the company had a process but it just included VI? > They just don't. They could try I suppose, but the amount of work involved in getting configurations together for these tools is prohibitive for them. Not to mention it's more work that developers have to do. Most shops nowadays are pretty diverse and mostly overworked. So you may have developers in India that you also need to deal with as well as more developers dealing with more than one language. By using a flexible IDE you can give them one tool for the job. Many developers you don't want them messing with their systems. Trust me on this ;) It's not that it's hard or even difficult, it just is something else. You'd be surprised. > Don't get me wrong I use an IDE. But I am not surprised when working in > the FOSS world when I come across programmers that use, or code that was > written with VI/VIM or Emacs. I see it to often for it to be any sort of > shock or surprise. Sometimes I feel like my skills are below par, > because I am not coding in them or doing things as rapid as others. Much > less with the quality that others produce with the crappy tools ;) You have to start thinking globally outside just the FOSS world. That's not how a majority of organizations out there operate. For better or worse right? ;) -- *Nathan Hamiel* http://hexsec.com <http://hexsec.com>http://twitter.com/nathanhamiel blog: www.neohaxor.org
