> Currently you look up on google the error message the compiler gives you this makes me afraid a little. although given the style of your examples i can imagi

> Currently you look up on google the error message the compiler gives you this makes me afraid a little. although given the style of your examples i can imagine you have just not had a problem just because of using simple and permissive, modern languages which are difficult to make mistakes with. due to the nature of compiler errors 99% of the time i can work it out by looking at the line of code. 1% of the time i need to read it carefully because it involves deeply nested C++ templates, and once i find the offending line i fix it 99% of the time in the same way. the remaining tiny fraction i learn something new. but find that most of the google results are people who failed to solve the problem instead of anything useful, and just have to work it out for myself. i will waste time reading stackoverflow posts with no answers, or answers from people who only want to answer, rather than know an answer. occasionally an apple fanboy will rile me by claiming in some comment that everyone is doing it the wrong way and suggesting something so dumb my head nearly explodes. :)