@rogue.hackz & ArkPhase - I've been programming for 20 years, I started on the C88, with vi, on a console based bare bones 0.3 Red Hat. I was taught embedded systems design by a 30+ year senior embedded programmer for NASA. I see absolutely no point in using any of the flashy bullshit most n00bs use these days. The truth is, N00Bs have to use those plugins, and all those "extras", cause they are too busy being too new, to keep track of simple bullshit... If you are incapable of keeping track of your program's execution without needing "documentation", you're a n00b, if you can not deduce your mistakes without needing some "auto error finder", you're a n00b. More importantly, if you can not code in a manner, that is self-secured, and hard to exploit; you are a n00b. Period. So, in other words, you are kids... I am a kid.
Let's get the credentials out of the way, since they appear important.
I've been coding for roughly 27 years. I'm a 'qualified expert'(meaning my aptitude has been tested and verified) in multiple languages and have taught/tutored several, especially C & C++. I've done quite of a bit of embedded development on multiple platforms and have implemented code for systems run by NASA JPL as well as the United States Navy. I have created custom hardware and written drivers for numerous devices. I have assisted in the development of operating systems, kernels, bootloaders, system libraries, service daemons, and more. I have been asked to edit more than one doctoral thesis and assisted with writing the firmware for an MIT robotics project. I have even told genuinely humorous assembly jokes after half a bottle of jager in the middle of the woods with no computer nearby for miles.
Now for the shock & awe: I use so-called 'n00b' features.
I don't personally need it, but I do tend to make use of it when available and properly implemented. Being well-versed or even highly proficient in a language and using features such as auto-completion, object browsers, class maps, flow monitors, etc. are not mutually exclusive. I'll admit that I sometimes find myself fighting with auto-completion specifically when I find it to be less than adequately implemented but that does not mean that I do not find use for such features. Typically, the speed at which usable, functional, efficient, and secure code can be written is improved when using such features. This is true for 'n00bs' as well as for more experienced developers.
I also document my code. I do this for multiple reasons, not the least of which is so that others can more easily understand my methods and reasoning. I also use documentation to indicate the expected state of values at certain points in the code, to remind myself of interfaces, to denote future plans and intentions, and even to supplement the features provided by things like auto-completion.
I also attest to the capabilities of ArkPhaze. ArkPhaze is one of the few people here from whom I accept critical criticism. I respect ArkPhaze as a developer and hacker. You should too.
More importantly; you should consider not just the words you speak(type) but also the wisdom(or lack thereof) behind the message that they provide. One would expect someone of your supposed experience and proficiency to be more aware.