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

Coding Off Days!!!

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

    #31
    Originally posted by Churchill
    Sounds like an enlightened approach.

    That bastard would've been first out of the door when I took over the project. Closely followed by yourself.

    Communication and teamwork is the way forward.

    huh?? Spod is that really you saying the above? or are you just taking the pi$$ again and as usually I missed the point ...

    Anyway you really meant that then horra ! strange how I was thinking that I never read a useful post of yours before - but now - that's a first

    is your new love making you soft?

    Comment


      #32
      Originally posted by SandyDown
      huh?? Spod is that really you saying the above? or are you just taking the pi$$ again and as usually I missed the point ...

      Anyway you really meant that then horra ! strange how I was thinking that I never read a useful post of yours before - but now - that's a first

      is your new love making you soft?
      Not soft at all. Anything but. My priority is to get the product shipped on time and to quality. Anything that gets in my way gets redeployed. Usually(but not always) out of the fecking door! That includes staff members, not just contractors.

      When I interview a software engineer, I know he can do the job. I'm interviewing him to see if I want him to do the job!

      Comment


        #33
        Absolutely. Teamwork is what makes a product work. Not some lone "guru" locked in a dark room writing "super code" no one understands.

        Peer reviews and pair programmers. Lots of communication and idea sharing. Lots of upfront design and lots of unit tests.

        Anything else is just some geek hacking and it's goodbye quality and deadlines, hello bug reports and patches.

        Comment


          #34
          Originally posted by DimPrawn
          Absolutely. Teamwork is what makes a product work. Not some lone "guru" locked in a dark room writing "super code" no one understands.

          Peer reviews and pair programmers. Lots of communication and idea sharing. Lots of upfront design and lots of unit tests.

          Anything else is just some geek hacking and it's goodbye quality and deadlines, hello bug reports and patches.

          Oh my ... how you code monkeys have grown, at last the penny dropped for you ... brings a tear to my eyes,

          Comment


            #35
            The sarcasm is absolutely dripping around here today.

            Comment


              #36
              Dim and Churchy - if you two dont trust your developers, and insist they have study buddies to hold hands with during work hours, then good for you.

              Who reviews your plans?
              The pope is a tard.

              Comment


                #37
                Originally posted by SallyAnne
                Dim and Churchy - if you two dont trust your developers, and insist they have study buddies to hold hands with during work hours, then good for you.

                Who reviews your plans?

                Nothing to do with trust, I am not a developer, but always have people QAing my work products, its a very natural thing to do, I also help QAing my colleagues work (this is the whole point of review and sign off stages in any project plan). This practice is something developers need to get in board with, but most don't have the confidence.

                Comment


                  #38
                  Originally posted by DimPrawn
                  Absolutely. Teamwork is what makes a product work. Not some lone "guru" locked in a dark room writing "super code" no one understands.
                  Yeah, but can you imagine if you have to work with AtW and listen to his SKA speeches or house-price crash, not to mention the proximity of the moustachios. Are you still against the idea of the dark room?
                  I've seen much of the rest of the world. It is brutal and cruel and dark, Rome is the light.

                  Comment


                    #39
                    Originally posted by SouthRoute55
                    Nothing to do with trust, I am not a developer, but always have people QAing my work products, its a very natural thing to do, I also help QAing my colleagues work (this is the whole point of review and sign off stages in any project plan). This practice is something developers need to get in board with, but most don't have the confidence.

                    Dont have the confidence? What a strange thing to say.

                    So you thnk the majority of developers are either crap or think they're crap then?
                    The pope is a tard.

                    Comment


                      #40
                      "99% of everything is crap"

                      - Theodore Sturgeon

                      Comment

                      Working...
                      X