Re: Learning a new language every year can be dangerous.

--- In [email protected], Wayne <wayne@...> wrote:
>
> DanHinojosa wrote:
> >
> > So this year I decided to go backwards and not learn a new language
> > but relearn an old language I forgot too much about, C++. I did this
> > because I really want to get into Linux development including its
core.
> >
> > So every language has it's zealots and I know that, and wow are they
> > angry and pious these days. I did a few posts on the C++ usenet group.
> >
> > My first post was: Is pointer programming even necessary?
> >
> > So let me explain the reason for asking. Thinking about it, I thought
> > all programming languages had object variables that hold object
> > references. Ooops, well that's learning for ya. I got the answer with
> > the help of a poster, which is awesome. But some of the responses
> > from other posters are definitely unhelpful. In this case...
> >
> > "It's incredible that you have programmed for 10-15 years and don't
> > know this. "
> > and
> > "It would be a good idea to understand, at least to some rough
> > approximation,
> > what you're attempting to ask about. :-) "
> >
> > Yikes. Just need a little love....
> >
> > So the next post was even better, my question:
> > Is it in the C++ culture to use Dependency Injection/Inversion of
Control?
> >
> > Here it comes...
> >
> > "You are clearly trying to be a smart-ass by using complicated
> > terminology that only few people are acquainted with, clearly on
> > purpose. If you don't want people to think you are a smart-ass,
explain
> > your terminology before using it."
> >
> > Sounds like some one has daddy issues.
> >
> > 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
> 
> 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
> 
> 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). ;)