• 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!

Expensive contractors, take responsibility for your work!

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

    #81
    Originally posted by aussielong View Post
    No, I'll tell you what the problem is and i'm going to sort it out tomorrow. I've let this contractor have to much freedom. I'm going to have to have a word in the morning and sort it out.
    Streuth cobber! No the problem is still you. You allowed this to go on and you are at fault for not pulling the guy up earlier and setting him straight. Perhaps he is simply not as good a developer as you are but it's you as his lead who should be aware of his abilities and limitations. If the quality of his work is that poor then no doubt you have reasonable justification to terminate his contract. The fact of the matter is, your own attitude stinks. You have come on here ranting that your contractors are not good enough, but you as their boss has done jacksh1t about it. If the contractor is not up to the job then who hired him? Was that you?
    Rule Number 1 - Assuming that you have a valid contract in place always try to get your poo onto your timesheet, provided that the timesheet is valid for your current contract and covers the period of time that you are billing for.

    I preferred version 1!

    Comment


      #82
      Originally posted by Churchill View Post
      Not really, I'm just showing you up for the "BillyBullSh!t" merchant that you are.


      Btw, full marks for owning up to the problem. It didn't take you long to start back-pedalling.
      no C++ programmer would do what you have done

      Originally posted by Churchill View Post
      cComment *myPtrHisComment = NULL;

      myPtrHisComment = &hisComment;

      if( myPtrHisComment )
      {
      myPtrHisComment->WHS = TRUE;
      }
      you would do:

      cComment *myPtrHisComment = &hisComment;

      i am not backpeddling. i maintain my point that people should take responsibility for their work.
      Last edited by aussielong; 4 June 2009, 13:11.

      Comment


        #83
        Originally posted by Pogle View Post
        Hmm so you're in a high pressure environment and things are not going well and you're cheesed off with the standard of work your contractors produce.
        Which makes me wonder how you've got time to post on here, surely you'd be better off sorting out your 'boys' ?
        its nighttime here bud

        Comment


          #84
          Originally posted by TonyEnglish View Post
          Streuth cobber! No the problem is still you. You allowed this to go on and you are at fault for not pulling the guy up earlier and setting him straight. Perhaps he is simply not as good a developer as you are but it's you as his lead who should be aware of his abilities and limitations. If the quality of his work is that poor then no doubt you have reasonable justification to terminate his contract. The fact of the matter is, your own attitude stinks. You have come on here ranting that your contractors are not good enough, but you as their boss has done jacktulip about it. If the contractor is not up to the job then who hired him? Was that you?
          I didnt hire him no. The quality of the work is not poor but its the ownership of the quality of the work that i have an issue with. I dont think that putting the hands up and saying "its not my problem" is acceptable from a highly paid contractor. If it was my choice i would sack the f****r. sadly he's right up the PMs a**e. Both public toolboys.

          Comment


            #85
            I'm contracting at an investment bank and the permie dev lead is some arrogant Aussie who couldn't run a bath, let along lead a software team. He's always moaning about lack of testing, and yet at the same time telling us to just get the code out of the door because he needs to make his bonus to make his pay packet somewhere near ours.

            Meanwhile us poor contractors are so busy bodging bits of code, we hardly have time to post on CUK. And now he wants us to mentor the junior permie developers!
            Cats are evil.

            Comment


              #86
              Originally posted by swamp View Post
              I'm contracting at an investment bank and the permie dev lead is some arrogant Aussie who couldn't run a bath, let along lead a software team. He's always moaning about lack of testing, and yet at the same time telling us to just get the code out of the door because he needs to make his bonus to make his pay packet somewhere near ours.

              Meanwhile us poor contractors are so busy bodging bits of code, we hardly have time to post on CUK. And now he wants us to mentor the junior permie developers!
              I'm English.

              F**k this.

              I'm off to bed.

              Comment


                #87
                Originally posted by swamp View Post
                I'm contracting at an investment bank and the permie dev lead is some arrogant Aussie who couldn't run a bath, let along lead a software team. He's always moaning about lack of testing, and yet at the same time telling us to just get the code out of the door because he needs to make his bonus to make his pay packet somewhere near ours.

                Meanwhile us poor contractors are so busy bodging bits of code, we hardly have time to post on CUK. And now he wants us to mentor the junior permie developers!


                +10
                You can lead a fool to wisdom but you can't make him think.

                Comment


                  #88
                  So, to summarise...

                  Developers are writing the unit test scripts. Developers are running the unit test scripts. Modules are passing unit test. Team Lead accepts that module is ready for formal testing. Module fails formal testing. Team Lead looks silly.

                  Have you tried any of:

                  (a) Have someone other than the developer write the unit test script
                  (b) Have someone other than the developer execute the unit test script
                  (c) Have someone review that the later failures are "real" failures rather than deviation from the spec
                  (d) If the Team Lead has doubts about one particular contractor, either doubly check their work and / or get rid of them

                  HTH.
                  Best Forum Advisor 2014
                  Work in the public sector? You can read my FAQ here
                  Click here to get 15% off your first year's IPSE membership

                  Comment


                    #89
                    Originally posted by aussielong View Post
                    no C++ programmer would do what you have done



                    you would do:

                    cComment *myPtrHisComment = &hisComment;

                    i am not backpeddling. i maintain my point that people should take responsibility for their work.
                    No you wouldn't, you'd initialise the pointer to a known value - safety first.
                    Last edited by Churchill; 4 June 2009, 13:32.

                    Comment


                      #90
                      Originally posted by TheFaQQer View Post
                      So, to summarise...

                      Developers are writing the unit test scripts. Developers are running the unit test scripts. Modules are passing unit test. Team Lead accepts that module is ready for formal testing. Module fails formal testing. Team Lead looks silly.

                      Have you tried any of:

                      (a) Have someone other than the developer write the unit test script
                      (b) Have someone other than the developer execute the unit test script
                      (c) Have someone review that the later failures are "real" failures rather than deviation from the spec
                      (d) If the Team Lead has doubts about one particular contractor, either doubly check their work and / or get rid of them

                      HTH.
                      (e) hiring a decent tester and sticking him in the middle of your developers to write test cases, execute unit tests and fetch cups of coffee
                      And what exactly is wrong with an "ad hominem" argument? Dodgy Agent, 16-5-2014

                      Comment

                      Working...
                      X