Especially since nowadays the IDE's are so exceptionally good for taking care of the syntax for most of stuff.
Personally, that is one of things I detest about modern IDE's. Code Completion and tips is a good idea - and it does help a person
out from having to type the entire statement out, but that is a feature I always turn off. Maybe I am being bias and I like typing,
however, I do find that not having the IDE bring up a endless menu of all the classes associated with the object, makes me have
to physically memorise exactly what the class is and how to spell it etc. - Again just my personal view on the matter
vi->edit->gcc->"Error: Stack overflow"->pull hairs->vi -rinse'n'repeat cycle
I've been there my friend - as have most members on this forum i'm guessing. Coming from a strict C background
gives you nightmares that may forever haunt you. Especially when the solution was staring you in the face
The amount of knowledge is in question tho! I don't really really agree with the many tutorials that dwell deep in to precision of types, different utilities and control flow nuances before introducing the conceptual thinking and OO basics.
Now this I also agree with to an extent. I do feel it is vital to learn most principles of structured programming concepts,
and going by some books I own or have owned on various languages, they do seem to dwell too long on a simplistic
subject such as what a int is, what an if statement is etc. I also understand that some people find it harder to understand it
than others, and thats O.K - learning is half the fun. But does a novice really need to know all this spread over a
ridiculous amount of pages and lectures Before he/she has even touched a class? No - in my view
KeepItSmartKeepItSimple applies here.
Overall - great read and a fair and accurate argument and addition to the discussion. Thank you!
Wishes Ada xx