Replies are listed 'Best First'.
Re: Speicilizing a field
by l2kashe (Deacon) on Feb 25, 2003 at 17:27 UTC
    I believe the question is:

    How do you determine when you have specialized too heavily in a given field

    I think what the AM was attempting to state was, say you use a language to program in (Perl *yay*), and you attempt to learn a new language (C++ || Java || .NET). Have you learned to many perlisms, or rather become to specialized in per, if you cant figure out how to code even the simplest algorithms in said new lang.

    So in response to what I assume the poster was asking, then I think an individual in said circumstance has fallen prey to some degree of cargo-cult coding (note the lack of the word programming there). There is a difference between understanding how to program (define the problem space, divide and conquer, etc..), and producing working 'code' in any given language.

    I mean someone could thoeretically pick up the Camel and the Ram and produce working code, with a complete lack of understanding of how things actually happen. In this case when they migrate to another language, if that language doesn't have the same level of documentation and examples that Perl has, they are obviously going to run into problems they can't solve.

    On another note, there is a difference between what I said above, and being able to "think" in the new language. There is a certain level achieved with any language, when you can quickly sketch out a solution in lang X because you understand the fundamental types for X as well as the flow design and structures X prefers over what Y would use.

    An personal example of such was a simple quasi AI I wrote to traverse an ASCII maze. I managed to bang it out in perl, but had a really hard time porting it to C. Why? Due to my lack of knowledge of the functions available to me in C. I managed to brute force a solution, and have yet to go back and streamline it, but I will get to it some point. Does that mean I'm too specialized in Perl? No. Does that mean I need to get my head around how C works, and what tools are available to me there, what syntax they require, etc? Yes

    /* And the Creator, against his better judgement, wrote man.c */
[reply]
Re: Specializing in a field
by diotalevi (Canon) on Feb 25, 2003 at 04:04 UTC

    When I add, punctuation randomly.

[reply]

      The written word is a very unforgivening means of communication. I always try to assume the best, but your post comes off as condescending and ignorant. Many people from many different countries speaking many different languages come to this site. Ridiculing their spelling, grammar, or punctuation is hardly professional, constructive, or helping to create a good atmosphere here. All it does is limit the number of contributors to this site, do you really want that? Would it not be better to try and understand the poster's point and respond only if you have something constructive to say?

      Take l2kashe's reply in this thread. In my opinion this is far more worthy of the best nodes than some silly, counter-productive obfuscated code, a post stating some module doesn't use strict, or saying be nice to eachother in pretty formatting. l2kashe takes a thread that has been considered for deletion, in which the only reply ridicules the poster (whose first language probably isn't english) and provides a well thought out clarification of what he thinks the poster is asking, and then proceeds to give his serious opinion on the subject. You all could take a lesson from him.

      I think it's also a very sad state of affairs when on a major discussion site of a free and open technology people are deleting these kinds of posts. The fact that it was considered at all is sad, the fact that it was considered by a very prominent member of the Perl community makes it even more so. It's even worse when you see it was actually deleted. The root post is not a worthless flame, it is a well-intentioned question. Since when does Perl monks delete posts by those who are well-meaning and only seeking responses to their questions? What's next? Maybe you should delete this post along with any other criticism .

[reply]

        Rereading this, I should note that diotalevi's post was in all probability just a slightly careless joke and my response was a bit overboard. The main problem is the fact that a well intentioned question was removed because of very minor language errors.

[reply]

        I agree that this post should not have been deleted. It asked a deep question that deserved consideration especially by those who have let some thing or some activity consume their lives in an unhealthy way. For example, A lot of people here probably sit in front of their computers for way too long, but how many are willing to admit it?

        Had this post not been deleted, it would have been like a stop sign for certain people who, deep in their hearts, know that they're not feeling well. It could have helped them stop and 'look both ways' so to speak and consider whether they have indeed specialized in something too much for their own good.

        The Original Post (edited for style and grammar):

        When do you think you are too involved in one field?

        For example, have you ever not had the thinking power to solve the simplest problem in another field which you would have otherwise solved relatively easily.

        I think it is dangerous for your 'human' development. (emphasis mine)

        And although I may be reading into this a bit, when he says "another field", don't just think of work. Think of the other things you could be doing besides work that can actually bring you Joy.

        Peace

[reply]

Back to Meditations