• Visitors can check out the Forum FAQ by clicking this link. You have to register before you can post: click the REGISTER link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below. View our Forum Privacy Policy.
  • Want to receive the latest contracting news and advice straight to your inbox? Sign up to the ContractorUK newsletter here. Every sign up will also be entered into a draw to WIN £100 Amazon vouchers!

What turds have you been asked to polish?

Collapse
X
  •  
  • Filter
  • Time
  • Show
Clear All
new posts

    #51
    Originally posted by doodab View Post
    It's a question of intelligence and experience. Even the most intelligent amongst us require practice to master a complex skill.

    0 0 = usually doesn't work anyway

    1 0 = usually works, often complex and impossible for an outsider to follow, not designed for maintainability or extendibility and eventually ends up a mess

    0 1 = usually works, mostly well structured with occasional inclusions

    1 1 = this is the stuff you learn from

    Many problems stem from "polyglots" who use C idioms when coding in a modern object oriented language, leaving a trail of null pointers & invalid objects in their wake and completely ignoring the standard libraries, although thankfully this seems to be dying out now. Another good one is people who implement components that deploy into a threaded framework, but because they have no direct interaction with the threading mechanisms they fail to understand the implications for shared data.
    This is exactly the kind of w@nk that has got us into the situation we are in. These issues are trivial. Youre grasping at straws. Your "1 1" is noddy bob code. You wouldnt know proper stuff if it bit you on the nose.

    Read my previous post on this thread and have a good think about it. You can learn from it.
    Last edited by aussielong; 19 October 2012, 11:55.

    Comment


      #52
      Originally posted by BrilloPad View Post
      I find that, beyond a certain point, the more intelligent the developer the worse the code.

      Some people like to prove how clever they are by making things as complex as possible.
      Obligatory Brian Kernighan quote:
      Everyone knows that debugging is twice as hard as writing a program in the first place. So if you're as clever as you can be when you write it, how will you ever debug it?
      - "The Elements of Programming Style", 2nd edition, chapter 2

      Comment


        #53
        Originally posted by aussielong View Post
        This is exactly the kind of w@nk that has got us into the situation we are in. These issues are trivial. Youre grasping at straws. Your "1 1" is noddy bob code. You wouldnt know proper stuff if it bit you on the nose.

        Read my previous post on this thread and have a good think about it. You can learn from it.
        Oh do shut up you silly little man.

        The code written by intelligent, experienced people is both the well written code and the right code, as per your earlier post. That's the point. The code monkeys taught rules turn out the 0 1 code.
        While you're waiting, read the free novel we sent you. It's a Spanish story about a guy named 'Manual.'

        Comment


          #54
          Originally posted by BrilloPad View Post
          I find that, beyond a certain point, the more intelligent the developer the worse the code.

          Some people like to prove how clever they are by making things as complex as possible.
          I agree with your second statement, but not the first.

          I've worked with people that possessed abstract intelligence, and I've worked with people that weren't as academic. I found they were equally capable of using over-engineered anti-patterns in an effort to disguise the fact that they didn't really know what they were doing or why. But I've honestly never met an effective developer that wasn't also very intelligent.

          I'd never treat someone merely having an advanced degree of learning as a red flag in and of itself, any more than I'd rule out someone with the right work experience but no academic background to speak of. At the end of the day it comes down to the person. You find out soon enough whether they're merely "book clever", or have the ability to apply what they know to practical problems.

          Comment


            #55
            Originally posted by aussielong View Post
            This is exactly the kind of w@nk that has got us into the situation we are in. These issues are trivial. Youre grasping at straws. Your "1 1" is noddy bob code. You wouldnt know proper stuff if it bit you on the nose.

            Read my previous post on this thread and have a good think about it. You can learn from it.
            Given your lack of team working skills, the amount of noise you feel you need to make about how clever you are, and the fact you seem never to have met anyone better than you, i'd have you down somwhere in the (0.3,0.3) to (0.6, 0.6) range.
            While you're waiting, read the free novel we sent you. It's a Spanish story about a guy named 'Manual.'

            Comment


              #56
              Originally posted by doodab View Post
              Given your lack of team working skills, the amount of noise you feel you need to make about how clever you are, and the fact you seem never to have met anyone better than you, i'd have you down somwhere in the (0.3,0.3) to (0.6, 0.6) range.
              Oh come on. I'm just bantering with youse.

              You didn't used to take yourself this seriously at biology and genesis.

              I have very little ego. I'm a martial artist.

              Comment


                #57
                Originally posted by BrilloPad View Post
                I find that, beyond a certain point, the more intelligent the developer the worse the code.

                Some people like to prove how clever they are by making things as complex as possible.
                Lots of truth there.

                There is something else as well though. maintainability.

                quite often you are left with a mess on your hands because the coder has not considered who will come after him.
                I worked with a highly intelligent (yet self-effacing) self taught visual basic coder. He worked his nuts off, one of the hardest working, effective guys you could ever meet.
                If he had a bug, he could find it and fix it in minutes. seconds maybe.

                I had absolutely no chance of working in it. it would have taken me days to find that bug. i didnt even bother trying after the first time.

                on the other hand, a contractor working in a zillion different environments, and a zillion hand overs, will write stuff for the guy who will follow him . and not for himself

                it's an effort and a seperate skill to be able to do this



                (\__/)
                (>'.'<)
                ("")("") Born to Drink. Forced to Work

                Comment


                  #58
                  Originally posted by aussielong View Post
                  Oh come on. I'm just bantering with youse.

                  You didn't used to take yourself this seriously at biology and genesis.

                  I have very little ego. I'm a pi$$ artist.
                  FTFY but that was such an easy shot even suity could have done it.
                  merely at clientco for the entertainment

                  Comment


                    #59
                    ..

                    Originally posted by EternalOptimist View Post
                    Lots of truth there.

                    There is something else as well though. maintainability.

                    quite often you are left with a mess on your hands because the coder has not considered who will come after him.
                    I worked with a highly intelligent (yet self-effacing) self taught visual basic coder. He worked his nuts off, one of the hardest working, effective guys you could ever meet.
                    If he had a bug, he could find it and fix it in minutes. seconds maybe.

                    I had absolutely no chance of working in it. it would have taken me days to find that bug. i didnt even bother trying after the first time.

                    on the other hand, a contractor working in a zillion different environments, and a zillion hand overs, will write stuff for the guy who will follow him . and not for himself

                    it's an effort and a seperate skill to be able to do this



                    +1 also it is a frame of mind, you are either in it or not. If anyone on the team is not 'in the zone' any individual efforts to this end are largely wasted too.

                    Comment


                      #60
                      Originally posted by Gentile View Post
                      . But I've honestly never met an effective developer that wasn't also very intelligent.
                      .
                      Rubbish. Effective coding isn't rocket science, it just requires an IQ slightly above average.
                      As evidenced by how few good coders go on to do more difficult stuff.
                      Hard Brexit now!
                      #prayfornodeal

                      Comment

                      Working...
                      X