and use text editor esp pressing upon vim
but i personally fail to understand their advantage over ide like kdevelop
hence i am less motivated to learn them

it would be nice to hear from the experienced people over here
if any one of you support the two(vim and make etc)pls share their advantages over ide

Well, an IDE certainly has its advantages in coding - it will provide integration (thus the name) with compilers, debuggers, and usually a documentation reference. It may also include a provision to interface your local source code directory with a revision control system (like cvs or svn, or hg, bazar, git, etc) or ftp/sftp. For C++ and Java projects, the IDE may assist you in assembling the scripts and configuration files needed for GNU autotools and Java's Ant for automated compilation upon release.

Where vim comes in is when you need to make a quick edit to a file and you're already on the command line - you don't need the full-fledged IDE - I'd say it's a handy skill to know, and working on the command line as a system admin (even of your own desktop system), vim is the best you can do in a text editor. It has syntax highlighting, sophisticated regular expressions for search and replacement, multi-file support, and much more - dive in and see for yourself how useful it may prove to be for you!

Vim is anywhere and kdevelop might not be available on some other machine.
Text editor might be easier to tame/learn than fighting ide bugs constantly.
Personally I dislke ides because they all always have some minor fault (normally, in gui) somewhere, which makes them incredibly annoying - I havent ever seen perfect IDE to work, that's why I prefer simple tools. I also don't like being dependant on any IDE to code - because if you'll move to another platform/desktop, you will have problems finding alternative. Another reason to use commandline tools with text editor is because they often give you greater control over compilation than "project" used in IDE.

What do you want to become - a person who knows how to press buttons of a given tool or a person who understands how it really works and what is actually happening ?

...and command line tools are more likely to be available (and workable) on low-resource systems. If, for example, you are trying to create code for some kind of embedded Linux system, it may not be possible to run an ide on your target system while it may be possible to do the job if you are familiar with the command line tools.

I would say the speed and inherent simplicity (once u learn to use them) are behind use of CLI tools.

I particularly recommend text editor with syntax highlighting for learning programming.
For large projects, IDEs may be easier to work with.

IDEs may be more useful when making GUIs and stuff, though.

well actually both.its nice to know what's happening behind the scene and finally pressing the button is usually faster then typing some command
and these days Gui isn't much of a overhead for the common machines to bear
i feel i should be using gui most of the times and only use command when i i know that the Gui isn't letting me do what command can let me do

you are true but not many people are in general are forced to use low resource machine nor is an ide quite inaccessible.it was present in all the Linux distros that i have used.secondly running ide on target system may not be required,one can compile it on a a desktop and then transfer to the embedded system.lastly if i have experience with embedded systems will i ever get to know and realize to what you say.

I agree to what you say

i agree to what you say

only time and experiences will season me enough that I mature to find some major bugs.right now for me kdevelop is fine and probably was available in all the distros that ever used

All ides I ever tried had some major bug that ruined experience and made ide useless. In KDevelop it wasn't possible to assign more that 10 shortcuts to make tool windows appear, which wasn't enough. The best GUI in IDE was in MSVS 2005. But it had other horrible features like intellisense, gui bugs, proprietary improvements over C++ standart, etc. So after some searching I decided that all IDEs are crap and using simple editors will be much easier than finding good IDE.

Well, in vim you need to know the commands for editing, saving, etc. which is basically the same as clicking buttons, only less obvious. Knowing vim does not give you an actual understanding of what really happens, neither does an IDE.

I said nothing about a text editor.

I meant the steps involved in producing an executable from sources.

I have always been a text editor/command line kind of guy, but in the recent past I have developed a bit of a fondness for kdevelop.

My prior IDE experience was all with Windows, and M$'s IDEs have always been incredibly frustrating for me to use; I positively DESPISE VS.

An IDE is supposed to help you out by integrating things, but it is easy for the IDE to cross the line from "help you out" to "compel you and annoy you". M$ IDEs are way, way, way across that line, but Kdevelop (IMHO) doesn't cross that line. I like Kdevelop these days for building projects that might run on an arbitrary linux distro because Kdevelop saves me from having to deal with all the intricacies of automake; Kdevelop sets all that up for me.

That said, when I start a new project it is always command line/editor. If I decide later that the complexity of the project requires it, I'll import it into Kdevelop. Presently my rewrite of my commercial program is in Kdevelop, both my satellite communications project and my radar signal processing project are editor/command line (and probably will stay that way).