• (cs) in reply to Forgottenlord
    Anonymous:
    *Enter the office holding the bat

    "Hi, guys.  Since you guys seem so interested in testing programs by running through the code in reality with various inputs, I thought you could all help me with the testing of this new ganster-type first-person-shooter game we're working on in the Las Vegas office."

    A first-person shooter, and you are using a club?  Where is your Uzi?  You would not want the embarrassment of not having a distance weapon at the appropriate time, now would you?

    See how important it is to check the design before proceeding?  It can also save money.  (If you are far enough away (because you are using a distance weapon), you need not worry to protect your clothes from blood spatters.)

    Sincerely,

    Gene Wirchenko


  • (cs)

    This doesn't suprise me.   When I received my BS/CS back in the mid 80's, my advisor was from India.  He told me that was a common practice back then in India.  There were so few computers that most students rarely used an 'actual' computer.  They 'ran' their code on paper by having others reviewing the code.

    He tried to tell me that made for BETTER developers because by the time they got in front of a 'real' computer, everything already ran fine.

    Come to think of it, my advisior was a real a**hole.

    DaleWill

  • (cs) in reply to codeman
    codeman:

    Wait, let's do it right: he should have printed out the power point presentation, put it on a wooden table, taken a digital picture, ...




    <FONT face=Tahoma>maybe they decided that placing the source code in the wooden table, taking a digital picture, etc... would take too much time for their compiler in another location to actually compile it so they just gamble with "the source looks good enough to me"...

    tsk tsk...time management...



    </FONT>
  • WTF Batman (unregistered) in reply to Gene Wirchenko
    Gene Wirchenko:

    It can also save money.  (If you are far enough away (because you are using a distance weapon), you need not worry to protect your clothes from blood spatters.)



    I'm thinking the FPS of choice would be called "Grand Theft ICBM".
  • (cs) in reply to dalewill
    dalewill:
    This doesn't suprise me.   When I received my BS/CS back in the mid 80's, my advisor was from India.  He told me that was a common practice back then in India.  There were so few computers that most students rarely used an 'actual' computer.  They 'ran' their code on paper by having others reviewing the code.

    He tried to tell me that made for BETTER developers because by the time they got in front of a 'real' computer, everything already ran fine.


    Deskchecking is a good practice, because to check your program this way, you have to know what the computer will do.  There is no running it through the debugger and hoping for magic.  It is not a replacement for on-line checking though, but it can result in much fewer bugs, because, done right, it helps weed out lick-and-a-promise coding.

    Sincerely,

    Gene Wirchenko

  • Miles Archer (unregistered) in reply to dalewill

    My dad was a real old school programmer - having gotten started in the 1950s. He always insisted that it's better to desk check (paper test, whatever) your code before typing it in. It's not a ridiculous thing to suggest in a situation where computing resources are scarce.

    What's crazy is outsourcing to a company/country that can't afford computers in this day and age.

  • (cs) in reply to Miles Archer
    Miles Archer:

    My dad was a real old school programmer - having gotten started in the 1950s. He always insisted that it's better to desk check (paper test, whatever) your code before typing it in. It's not a ridiculous thing to suggest in a situation where computing resources are scarce.



    When I was a CS major in the mid-80s (I actually have a split college career, one summer break lasting 13 years), we were encouraged to desk check as much as possible. Probably because compiling and producing the program's output made about 20 pages of 132-column green-bar paper: 19 pages of source, traces, and debugging information, and 1 page showing your "magic square" or whatever. Since I was paying exorbiant fees for activities that I didn't partake in (the school was a basketball arena that they decided needed a small university attched to it), I printed as many reams as I wanted, or until the guy behind the desk shut me down.
  • John (unregistered) in reply to Rank Amateur

    Once, as a teenager when I was stuck at camp for a couple weeks (a real camp, not even electricity), I wrote a message board program in a notebook, rewriting each module as needed, tearing out and burning (in the campfire) obsolete code, debugging it by tracing through it mentally; when I got home I transcribed it, and it worked flawlessly (single user dial-up, so no thread deadlock type things were possible)...

    I hated camping.

  • (cs) in reply to codeman
    codeman:

    Not sure if this is the right place to ask this...

    I've been reading this forum for a while, and have seen zillions of references to Paula and her Brillance (I've even made a couple myself), but can't find the original post (searching doesn't help as every reference to either is returned).

    Given this forum's content, I can imagine the context, but I am curious to read it for myself: does anyone have a link to the original Paula post?



    Now THAT'S what I call a WTF!

    And what's up with the "Quote" button only working when logged in?
  • Monomelodies (unregistered) in reply to John
    Anonymous:

    Once, as a teenager when I was stuck at camp for a couple weeks (a real camp, not even electricity), I wrote a message board program in a notebook, rewriting each module as needed, tearing out and burning (in the campfire) obsolete code, debugging it by tracing through it mentally; when I got home I transcribed it, and it worked flawlessly (single user dial-up, so no thread deadlock type things were possible)...

    I hated camping.



    That sounds familiar. I used to do that all the time back in the day when laptops weren't very affordable to the average person.
    Last year, I worked briefly (very briefly, but that's another story) for a company where they required me to code in BBEdit. It wasn't until after a few weeks I noticed line numbers were off by default in it. Not a single typo or error thus far.
    Still, I wouldn't try to sell my notebook-code (that's notebook as in paper, not laptop) without testing it first. It's just hilarious.
  • Mr Beeper (unregistered)

    Dude: Paula Bean T-Shirts.  Instant recognition wherever you go.  Alex, please make and sell them.

  • 3 Hurried 2 login (unregistered) in reply to GoatCheez
    GoatCheez:


    <rant>... baseball bat ...
    </rant>


    A cricket bat would be both more available and more effective.
  • (cs) in reply to Mr Beeper
    Anonymous:

    Dude: Paula Bean T-Shirts.  Instant recognition wherever you go.  Alex, please make and sell them.




    i'm looking forward to that too... :)



  • qualified_trash (unregistered) in reply to Mr Beeper

    Which year was this in? I left India in 1999 and have lived in the US since. I used to have a 486 based PC at home with a dot matrix printer. We had to submit a final semester project and I made good money allowing my classmates to use the Printer to print their project reports out as the school had restricted lab time and the CS students use to monopolize the lab :-))

  • 3 Hurried 2 login (unregistered) in reply to Ixpah
    Ixpah:


    So true, and from my own experience, I don't demo anything I have never seen, not even if it was coded by my most trusted and skilled colleague. Even if the application does work with little trouble, what are the chances you will know how to operate it? (I think relying soley on your initial specifications would be a mistake.)


    It was actually India, and as I've implied in another post it was either go with what we had or nothing, i.e. be in with a small chance or zero chance. I think the contract was worth something like £500,000 so it was worth the risk, although I'm sure I didn't think so once I saw the code.


    1.  I an so happy that a participator is taking part in the conversation.  You get 10,000 attaboys for sticking around while the universe of WTF readers gives you serious stick for being one of the perpetrators.

    2. As you know 10,000 attaboys do not even begin to mitigate.  I've been where I felt like I was going to a hanging, but at least I knew that it was coming.

    As usual, the real WTF was actually perpetrated back when the project was being managed so competently.  Your company should have required the project manager, as his last activity as an employee, to be the guy in front of the room at the demonstration.
  • 3 Hurried 2 login (unregistered) in reply to Miles Archer
    Anonymous:

    My dad was a real old school programmer - having gotten started in the 1950s. He always insisted that it's better to desk check (paper test, whatever) your code before typing it in. It's not a ridiculous thing to suggest in a situation where computing resources are scarce.

    I learned to program when desk checking was mandatory but I had unlimited run time on a 370/145 so I programed iteratively, letting the compiler and tracer assist.  Little did I know that this was the way things would be today.


    What's crazy is outsourcing to a company/country that can't afford computers in this day and age.



    The money may have been rerouted to a Swiss account...according to my research.
  • Jonathan Thompson (unregistered)

    I sincerely hope your company sued the company/people in India for breach of contract, and at least recovered every cent paid thus far for their "work" because if that "code" was a car, that'd be subject to Lemon Laws!  I'd also hope that all future projects would never involve that company in India, because they've clearly demonstrated that they can't be trusted to provide anything of value.

  • (cs) in reply to 3 Hurried 2 login
    Anonymous:
    GoatCheez:


    <rant>... baseball bat ...
    </rant>


    A cricket bat would be both more available and more effective.


    That's the second time someone suggested a cricket bat. They don't sell those here (unless you look hard)! Cricket is basically non-existant in the US. Also, I REALLY doubt a cricket bat could hold up to this:

    http://www.aluminumbats.com/index.asp?PageAction=VIEWPROD&ProdID=1664

    I still carry an old-school aluminum TPX Slugger in my backseat.... just in case ;-)
  • ChiefCrazyTalk (unregistered) in reply to Miles Archer
    Anonymous:

    My dad was a real old school programmer - having gotten started in the 1950s. He always insisted that it's better to desk check (paper test, whatever) your code before typing it in. It's not a ridiculous thing to suggest in a situation where computing resources are scarce.

    What's crazy is outsourcing to a company/country that can't afford computers in this day and age.

    I'm an old school programmer myself (although not THAT old school) and used to write portions of programs by hand "back in the day" to help figure out the logic, etc. Since development tools (not to mention compilers) have gotten better and better, however, it's been decades since I've had to do anything like that.

  • ChiefCrazyTalk (unregistered) in reply to Mr Beeper
    Anonymous:

    Dude: Paula Bean T-Shirts.  Instant recognition wherever you go.  Alex, please make and sell them.

    I'll take one, size XL. The front could say "Paula Bean" and the back would say "Brillant!"

  • (cs)

    Oh boy, that one just takes the cake.

    Bring it back, I want a slice!

    giggles

  • Lynn (unregistered)

    These guys didn't follow the golden rule... If it compiles, it must work! (TM)

  • (cs) in reply to GoatCheez
    GoatCheez:
    That's the second time someone suggested a cricket bat. They don't sell those here (unless you look hard)! Cricket is basically non-existant in the US. Also, I REALLY doubt a cricket bat could hold up to this:

    http://www.aluminumbats.com/index.asp?PageAction=VIEWPROD&ProdID=1664


    Special sale price, too:

    Reg price                         149.97
    109.95 (crossed out)

    Sincerely,

    Gene Wirchenko

  • Me (unregistered) in reply to Gene Wirchenko
    Gene Wirchenko:
    GoatCheez:
    That's the second time someone suggested a cricket bat. They don't sell those here (unless you look hard)! Cricket is basically non-existant in the US. Also, I REALLY doubt a cricket bat could hold up to this:

    http://www.aluminumbats.com/index.asp?PageAction=VIEWPROD&ProdID=1664


    Special sale price, too:

    Reg price                         149.97
    109.95 (crossed out)

    Sincerely,

    Gene Wirchenko



    It's actually 189.95

    Sincerely,

    Me.
  • some guy (unregistered) in reply to pbounaix
    pbounaix:

    testing schmesting!

     

    how you can develop something and not replicate the production environment is like coding in the dark....



    If you code in the dark usually the glow from the screen helps quite a bit.
  • (cs) in reply to Gene Wirchenko
    Gene Wirchenko:
    GoatCheez:
    That's the second time someone suggested a cricket bat. They don't sell those here (unless you look hard)! Cricket is basically non-existant in the US. Also, I REALLY doubt a cricket bat could hold up to this:

    http://www.aluminumbats.com/index.asp?PageAction=VIEWPROD&ProdID=1664


    Special sale price, too:

    Reg price                         149.97
    109.95 (crossed out)

    Sincerely,

    Gene Wirchenko



    ROFLMAO! I can't believe I didn't notice that! I can't figure out the words to describe how WTF'd up me linking that on this is. ROFLMAO...

    Gotta love those -36.4% sales!
  • : (unregistered) in reply to xrT
    xrT:
    codeman:

    Wait, let's do it right: he should have printed out the power point presentation, put it on a wooden table, taken a digital picture, ...




    <font face="Tahoma">maybe they decided that placing the source code in the wooden table, taking a digital picture, etc... would take too much time for their compiler in another location to actually compile it so they just gamble with "the source looks good enough to me"...

    tsk tsk...time management...

    </font>


    They might have well just faxed the code to the other end, and have it 'run' on paper there.  Would save all that time typing it into a computer...
  • (cs) in reply to GoatCheez
    GoatCheez:
    Gene Wirchenko:
    GoatCheez:
    That's the second time someone suggested a cricket bat. They don't sell those here (unless you look hard)! Cricket is basically non-existant in the US. Also, I REALLY doubt a cricket bat could hold up to this:

    http://www.aluminumbats.com/index.asp?PageAction=VIEWPROD&ProdID=1664


    Special sale price, too:

    Reg price                         149.97
    109.95 (crossed out)


    ROFLMAO! I can't believe I didn't notice that! I can't figure out the words to describe how WTF'd up me linking that on this is. ROFLMAO...

    Gotta love those -36.4% sales!


    As was pointed out upthread, it is actually 189.95 crossed out, but it looks as if it is 109.95 as the "0" and "8" are the same except for the line where a strikeout goes.  Characters that are too similar can be a WTF.  Another of these can be seen in proofreading text in Times New Roman: "bam" and "barn" look very similar.

    The explosives went off with a bam, and the barn collapsed.

    Sincerely,

    Gene Wirchenko

  • bandi (unregistered)

    Reminds me the years I spent at one of the universities in central Europe. All of the programming exams must be done on paper. And it was only four-five years ago. I hope the situation has been changed since then...

  • Frost (unregistered) in reply to Ixpah

    Ixpah:
    byte_lancer:
    Ixpah:

    It was actually India, and as I've implied in another post it was either go with what we had or nothing, i.e. be in with a small chance or zero chance. I think the contract was worth something like £500,000 so it was worth the risk, although I'm sure I didn't think so once I saw the code.

    Err, sorry to ask, but cant you give a hint on which WTF company this happens to be?
    I really want to avoid this one.


    Hmm... how to answer that without the risk of libel...
    http://sambharmafia.blogspot.com/2005/09/back-to-square-d.html
    That "maybe" the one.

     

    Here in the US, truth is an absolute defense against libel claims.

     

  • (cs) in reply to R.Flowers
    R.Flowers:
    ...Example: "Excuse me, I have to go to the bathroom because I have crapped my pants..." :)
    <font size="5">I</font>n polite society we refer to this as "soiling ones drawers," but it smells the same.
  • Matthew Greet (unregistered)

    There's actually a worse engineering philosophy than 'if it compiles, ship it'?

    Must drill hole in head to let madness out.

  • RsD (unregistered)

    my company beleives in out sourcing too :(
    one time they sent me a code that can never run so I called their(out source comapy) team leader and told him the code u've sent can never run, he told it's very strange it's working here, I was like to the line number x and read it for me, when he did that I said again this code can never run it's like hardcoded division by zero, he answred but it's strange it's working here, did u change anything in your environment?
    I wish I had a gun that works over seas at that time.

  • foo (unregistered) in reply to bandi

    I'm studying at University of Cambridge, and we still take all exams, including programming, on paper. Minor typos and omissions are not counted as mistakes, and in some cases, you can even replace the code with an algorithm description.

    The only annoyance is not being able to fit more than a few lines between existing ones, but otherwise it is a good idea. Before you write something, you have to understand what you are doing and exactly how the program should work. Having access to a compiler makes it tempting to write something that looks like as it might work without thinking, but the write - fix until compiles - test - fix cycle usually ends in a mess that even no amount of unit testing will help.

    If the algorithm in question is not something you write every few weeks, then it is a good idea to write/sketch the algorithm on paper in pseudocode in real life as well.
     

  • 3 Hurried 2 login (unregistered) in reply to GoatCheez
    GoatCheez:


    That's the second time someone suggested a cricket bat. They don't sell those here (unless you look hard)! Cricket is basically non-existant in the US.


    The suggestion is keyed to the remark, not where you happen to be writing from.

    1.  The company in question was in India (read the early responses). I doubt, even today, one would easilly find a baseball bat in Delhi, Mumbai or Chennai, except at the US Embassy compound.

    2.  Comparing the damage a baseball bat would do versus a cricket bat is something like delivering code that has never been run - seriously, have you hefted a cricket bat?  The shape alone makes it a formidable weapon.  Think Claymore versus Foil...
  • (cs) in reply to Frost
    Frost:
    Here in the US, truth is an absolute defense against libel claims.


    Only if you can afford to pay your lawyer...

  • (cs) in reply to gwenhwyfaer

    We really, really, really need some kind of formal worldwide control over who is allowed to work in this industry.........

  • Robert Synnott (unregistered) in reply to GoatCheez
    GoatCheez:
    That's the second time someone suggested a cricket bat. They don't sell those here (unless you look hard)! Cricket is basically non-existant in the US.

    It's quite popular in India tho.

    Anonymous:
    Reminds me the years I spent at one of the universities in central Europe. All of the programming exams must be done on paper. And it was only four-five years ago. I hope the situation has been changed since then...

    I hope it hasn't. At my university (Trinity College Dublin, Ireland) we do all exams on paper. This would seem to me to be a good thing; access to a compiler would only help the clueless. Language is generally also optional; one lecturer in particular likes to do his examples in something vaguely Algol-like; he makes the syntax up as he goes along.

    Anonymous:

    Here in the US, truth is an absolute defense against libel claims.

     

    As it is in most countries, in fact. The difficulty is generally in establishing the truth.

  • (cs) in reply to ChiefCrazyTalk
    Anonymous:
    Anonymous:

    Dude: Paula Bean T-Shirts.  Instant recognition wherever you go.  Alex, please make and sell them.

    I'll take one, size XL. The front could say "Paula Bean" and the back would say "Brillant!"



    You could do a golf shirt, have TDWTF logo on the front (left breast, small) and
    <font>public class</font> paulaBean {

    <font>private String</font> paula = <font>"Brillant"</font>;

    <font>public String</font> getPaula() {
    <font>return</font> paula;
    }
    }

    on the back :P

  • (cs) in reply to tster
    tster:
    if you can't afford to buy something, you really shouldn't try to use it to make money.   makes me want to open a burger joint and serve raw hamburgers and tell people they taste good on paper but we have no grill.


    Call the joint "Little Sumerian's", and explain how ancient people didn't usually have propane grills to cook the meat, so that's why you serve them raw.  (They didn't have ground beef, either, but don't remind them about that part.)

    Besides, lots of people prefer raw beef, as it's juicier and tastes better!
  • Somebody or other (unregistered) in reply to Gene Wirchenko
    Gene Wirchenko:
    As was pointed out upthread, it is actually 189.95 crossed out, but it looks as if it is 109.95 as the "0" and "8" are the same except for the line where a strikeout goes.  Characters that are too similar can be a WTF.  Another of these can be seen in proofreading text in Times New Roman: "bam" and "barn" look very similar.

    The explosives went off with a bam, and the barn collapsed.

    Sincerely,

    Gene Wirchenko

    Kinda reminds me of a couple years ago, when the Canadian Broadcasting Corporation (CBC) came up with a new on-air graphics package that was designed to make every digit look as similar as possible, so that if you're sitting in a bar you had no possible way of seeing how much time was left in the (hockey) game, or what the score was, unless you moved to within inches of the screen.

    They changed it again about a week later.
  • RevEng (unregistered) in reply to 3 Hurried 2 login
    Anonymous:

    <snip>
    As usual, the real WTF was actually perpetrated back when the project was being managed so competently.  Your company should have required the project manager, as his last activity as an employee, to be the guy in front of the room at the demonstration.


    Sounds like having him plead his case to the firing squad.  "But Your Honour, I thought they had tested it thoroughly!"
  • (cs) in reply to foo

    Anonymous:
    I'm studying at University of Cambridge, and we still take all exams, including programming, on paper. Minor typos and omissions are not counted as mistakes, and in some cases, you can even replace the code with an algorithm description.

    The only annoyance is not being able to fit more than a few lines between existing ones, but otherwise it is a good idea. Before you write something, you have to understand what you are doing and exactly how the program should work. Having access to a compiler makes it tempting to write something that looks like as it might work without thinking, but the write - fix until compiles - test - fix cycle usually ends in a mess that even no amount of unit testing will help.

    If the algorithm in question is not something you write every few weeks, then it is a good idea to write/sketch the algorithm on paper in pseudocode in real life as well.
     

    I'm european, and we also make all exams in paper in University of Lleida (Spain, Catalonia). Of course, you are also required to do laboratory classes and produce a working program that fulfills certain requirements. If you fail to produce the program, or the program is not good enough, you fail the whole subject.

    However, even if you are required to scrawl lots of code in the exam, actually getting a running program is considered important enough that they'll give you important incentives.

    If you fail the exam but you make correctly the program, the mark for the program can be preserved for one year, so you'll only need to repeat the exam if you try the same subject the following year*. That applies for all subjects requiring laboratory classes, including some physics and maths (ever used Mathematica?).

    Until just a few years ago, the program requirements were given only on photocopies. Maybe a subtle reminder that real programming needs as many lines of detailed printed specifications as lines of actual code?

    * Teachers can be persuaded to preserve your exam mark, in case you fail the program part, but this one is not an official politic :P

    Now focus your mind and imagine a "Computers II" paper exam, where you are required to program in x386 assembler.....

  • maht (unregistered)


    "Beware of bugs in the above code; I have only proved it correct, not tried it."
    Donald Knuth

  • (cs) in reply to Volmarias

    Volmarias:
    "OH YEAH? MOVL $MYCOCK, %YOURMOM"

    Aaahahaha!

  • Konosoke (unregistered)

    You have no idea. It is a training, so when they power supply is gone, they can still work on paper!
    That's the way M$ Windows is done, they know and they try to be as famous than M$.


    P.D.: Please, excuse my english if something is wrong, because I am not an english natural speaker.

  • (cs)

    Read the log of an IRC conversation between John Cowan and a friend (here identified only as “victim”) on the horrors of Cobol. As John says, “it’s interesting to watch ‘victim’ disintegrate as the eldritch nature of the language is sloooowly borne in upon him.”

  • Erlando (unregistered) in reply to Pingmaster
    Pingmaster:
    Anonymous:
    Anonymous:

    Dude: Paula Bean T-Shirts.  Instant recognition wherever you go.  Alex, please make and sell them.

    I'll take one, size XL. The front could say "Paula Bean" and the back would say "Brillant!"



    You could do a golf shirt, have TDWTF logo on the front (left breast, small) and
    <font>public class</font> paulaBean {

    <font>private String</font> paula = <font>"Brillant"</font>;

    <font>public String</font> getPaula() {
    <font>return</font> paula;
    }
    }

    on the back :P



    Here's one try: http://www.cafepress.com/paulabean

    Not using TDWTF logo though..

  • qbolec (unregistered) in reply to GoatCheez

    After reading several threads here I had thought you guys would like to join the people that live in a bliss of not having COBOL nor Oracle...but yet I've read completely oposite statement from you.

    [This just reminds me old good Polish joke, when the profesor examines a student of politology who apparently knows completely nothing about current situation in the country, nor in politics stage...not even knowing what the name of the president was. So after having no answer to several such questions, profesor was ready to ask: and where do you come from? ... and started dreaming to leave work, move to that city in the middle of nowhere and froget about all this crap]

  • .* (unregistered) in reply to qbolec
    Anonymous:
    a student of politology


    WTF? There's a name for the study of Poland?

Leave a comment on “Of Course We Tested It ...”

Log In or post as a guest

Replying to comment #:

« Return to Article