Using an IDE doesn't make a programmer good, nor does it make code good. I know plenty of shops using Rational and Clearcase, shops that spent major money on tools, whose programmers are terrible and whose code is full of memory leaks.
Obsfucation of talent via monetary expenditure is a typical enterprise IT and development flaw. Some of the highest spend shops I know are also some of the dumbest shops I work with. Fortunately, since I am in sales it works to my advantage. :-) -- Kyle Gonzales Sent from my mobile On Mar 22, 2011, at 12:03 PM, Nathan Hamiel <[email protected]> wrote: > On Tue, 2011-03-22 at 11:36 -0400, Deny IP Any Any wrote: >>> On Tue, Mar 22, 2011 at 11:19 AM, Nathan Hamiel <[email protected]> >> wrote: >>>> Who in their right mind would use VI/VIM for doing actual development? >> >> Quite many use VI/VIM and Emacs for such things. Usually those who use >> either use it for pretty much anything and everything. Can't even recall >> how many times I come across code with the VI stuff at the bottom. >> Though for all I know could be emacs, but pretty sure it was VI. >> > > Define quite many? How large are these organizations? The enterprises I deal > with typically use Vim or Emacs for editing config files or other misc > systems admin stuff. Never for things like developing enterprise > applications. It just seems pretty small time to me. > >> >>> It's >>>> an editor and its use in development for anything beyond writing or >> editing >>>> simple scripts is just not smart. >> >> Well less than ideal, but not smart might be going a bit far. You have >> to have some intelligence to be using VI or Emacs in the first place. >> Its not like nano where the instructions are on the screen and its easy >> to use. I always have to go look up commands anytime I am forced to use >> VI. Emacs I don't believe I have ever touched. >> > > I actually toned it down a bit. I had the word stupid in there instead of > not smart and I stand by it. VI/VIM is not made for what these people are > using it for. Not to mention there is no code intelligence, code completion, > or any of the other useful features of an IDE. The issue that made it in > production wouldn't have made it there if an "real" IDE where being used. > > Let's say you are a singer and that is your job to sing in a band. It's the > equivalent of giving you a megaphone (VI) or a microphone plugged in to a PA > system (IDE). They both amplify your voice but with a microphone you can > always turn up the volume, add effects, or get bigger speakers (IDE > plugins). With a megaphone sooner or later you are going to blow out your > voice. There is something to be said about using the right tool for the > right job. > > >> >>> If the developer were using an actual IDE >>>> he would have seen the beginning line underlined in red indicating a >> syntax >>>> error. The IDE would have alerted them to the fact there was a problem >> and >>>> it wouldn't have made it in to production in the first place. That's >> one >>>> takeaway Tumblr should be thinking about. >>>> >>> >>> The syntax highlighting in VIM would alert them to the invalid syntax, >>> if they were using it. >> >> Or any editor with syntax highlighting, be it an IDE or text editor >> including VIM. Though not all syntax highligters will display broken >> code, that typically is a feature of an IDE. Though the code/mistake >> likely would have been the wrong color either way. >> > > I was referring to the code intelligence of an IDE, which would have > indicated a problem with that particular line. Either way, it's a breakdown > of process. > > > -- > *Nathan Hamiel* > http://hexsec.com > <http://hexsec.com>http://twitter.com/nathanhamiel > blog: www.neohaxor.org --------------------------------------------------------------------- Archive http://marc.info/?l=jaxlug-list&r=1&w=2 RSS Feed http://www.mail-archive.com/[email protected]/maillist.xml Unsubscribe [email protected]
