Re: Learning a new language every year can be dangerous.
"DanHinojosa" <[email protected]>
| Newsgroups | gmane.comp.programming.language-of-the-year |
|---|---|
| Message-ID | <[email protected]> |
--- In [email protected], Wayne <wayne@...> wrote: > > > > > > > > > > > > Now again, it is obvious that there are fan boys for every programming > > > > language. I remember listening to a podcast by Dave Thomas where he > > > > introduced the idea of learning a new language because the language > > > > you are using may not be around and/or maybe you can expand your > > > > mental boundaries about how to code by learning new languages. What > > > > did Dave get for his revolutionary ideas? Threats! It was on an old > > > > AgileToolkit podcast so check out his story. ;) > > > > > > > > It really is interesting how people behave when it comes to > > > > programming knowledge. The smartest people I know are never afraid to > > > > use "I don't know" and they always treat people who don't know, with > > > > respect. I try to live by that code, I may fail, but I make the > > > > greatest effort not to. > > > > > > > > Just some observations. > > > > > > > > > > > > > > > > > > > > > > I found this thread amusing so I looked up your questions on Google. > > > Here's the first. > > > > > > > > http://objectmix.com/c/369520-pointer-programming-even-necessary.html > > <http://objectmix.com/c/369520-pointer-programming-even-necessary.html> > > > > > > I like the way that you characterized the exchange. The first response > > > looks like very thoughtful and helpful. The response you took > > offense to > > > was not referring to your lack of C++ knowledge. The poster simply has > > > the opinion that after 10-15 years of programming in any language that > > > someone should have a little better understanding of how computers work > > > and what pointers. > > > > Let me just address your other content... > > > > "It's incredible that you have programmed for 10-15 years and don't > > know this" is considered helpful in your opinion? > > > > > > > > > > The second is found here: > > > > > > > > http://objectmix.com/c/375425-c-culture-use-dependency-injection-inversion-ofcontrol.html > > <http://objectmix.com/c/375425-c-culture-use-dependency-injection-inversion-ofcontrol.html> > > > > > > Yes, one guy did call you a smart-ass but then your question was > > kind of > > > terse. You really need to look at it from the other persons view. Here > > > you are asking him to take time out of his busy life to help you. You > > > ask a question that has so little information it probably going to take > > > him 15-20 minutes on Google just to figure out what you're talking > > > about. Then it going to take more time for him to write a response. I > > > probably wouldn't have called you a smart-ass but I would not have > > > answered your question either. I find it hard to put more effort into > > > answering a question than was put into asking it. > > > > Ok, here is the deal. It's chicken vs. egg. It is more a pain in the > > ass for me look up if DI is in the C++ CULTURE. Culture being the most > > operative word. That's why in my question I wasn't > > going for any technical information per se, just how seasoned C++ > > programmers program their code and whether it was in their culture. > > It is tough to gauge what is in a programming culture without asking > > programmers themselves. > > > > Up to that point I had no idea that DI would be foreign to them. > > That's why people ask questions, to gain insight (or some gripes in > > this case). As you saw, there were some posters who genuinely either > > asked what DI was, or knew both C++ and DI and gave the help and the > > insight I needed. That's just some good professional courtesy. > > > > All in all, I can't believe you are programmer and don't know the > > difference between programming culture vs. programming patterns > > (kidding). ;) > > > > > > > I am not sure that you got my point. You've been programming for 10-15 > years. I am sure that you understand that 'jargon' is used all over and > can mean different things depending on context (including _culture_) it > being used in. Your question was about jargon an absolutely no context. > Courtesy dictates that you spend at least as much time making your > question easy to answer as it will take to answer the question. I don't mind changing the way I post question, but that was an easy question and it was exactly what I wanted to convey. > > > Since you assert that your questions are serious, might I recommend the > following link. > http://www.google.com/search?hl=en&rls=com.microsoft%3Aen-us%3AIE-SearchBox&q=%22dependency+injection%22+C%2B%2B > > (this is the search result in Google for '"dependency injection" C++') > > The first link covers a lot of the ground that has been covered in this > list. It also points to some libraries that at least 1 C ++ programmer > thinks does something like DI. The second link is to Wikipedia. It has a > brief description of DI and then lists libraries in 10 different > languages that implement to some degree or another DI. > Thanks for the other links, the first one you mentioned is just a copy from a USENET post. Just to reiterate, I just wanted to know the culture of DI in C++, not the technical information of DI in C++ although I don't mind the information. So I set up my question the way I wanted it conveyed.