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

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

    #11
    I remember a using a dos program once that became more and more insulting with its error messages the more times you made a mistake typing in the parameters.

    tim

    Comment


      #12
      I wrote a random insult generator in BASIC while working at GEC. We had minutes of fun with that.

      Comment


        #13
        Originally posted by cojak
        Worked at one place where an aspberger programmer insisted on variables like ROAST-BEEF and CARROTS.

        Needless to say only he could debug the code.

        I would have fired the tosser...
        No doubt that programmer was far more intelligent than you kojak. Why else would you be jealous?

        Comment


          #14
          Originally posted by tim123
          I remember a using a dos program once that became more and more insulting with its error messages the more times you made a mistake typing in the parameters.

          tim
          There was a research project at Sheffield University where they wrote something like that. They were trying to find out what aspects of the interface made computers most difficult to use, and hence know to concentrate on fixing those problems. IIRC it was called Abusive Response System Environment, (one of those where they started with the acronym and worked back to the name.)
          Insanity: repeating the same actions, but expecting different results.
          threadeds website, and here's my blog.

          Comment


            #15
            Originally posted by threaded
            There was a research project at Sheffield University where they wrote something like that. They were trying to find out what aspects of the interface made computers most difficult to use, and hence know to concentrate on fixing those problems. IIRC it was called Abusive Response System Environment, (one of those where they started with the acronym and worked back to the name.)
            NTL use it in their call centres now.
            Serving religion with the contempt it deserves...

            Comment


              #16
              I once worked with a guy who wrote code such as:

              Code:
              On Error Goto Cleethorpes
              He was a contractor, so he deliberately wrote code that no-one else understood.
              Vieze Oude Man

              Comment


                #17
                I used to do things like that in my coding days - how about a geographically accurate OS macro that started at John o'Groats and exited at Lands End. The code was so boring to write, you had to spice it up somehow. Or another one that would echo your CLI typing in reverse font from the right of the screen? Or one I wrote to scare off a user who kept playing with commands to "see what they did" on a production system - Death.com switched off all the interrupt commands and started to display messages that looked like it was wiping the system disk (I installed it under the name Help.com). Happy days...

                My favourite was a CMOS design that the analyser s/w (Dracula?) couldn't resolve, and kept throwing up strange error messages. They eventually put it under a microscope and discovered the designer had drawn a picture of a duck in the middle of the circuit, and the analyser was trying to rationalise the connections of the circuit to the drawing...
                Blog? What blog...?

                Comment

                Working...
                X