Fix this, but you can't run it.



  • Today is an exercise in frustration. One of my coworkers gave me a large bottle of Crown Royal that is now sitting on my desk, mocking me. I wonder if I'll make it through the day without cracking it open?

    I have this iteration to fix six bugs with a legacy vehicle variant on the trainer we're working on. In this particular case, it's a rather old version of the vehicle. Up until this point, the V1 cab has been installed on one of the motion platforms and hooked up, ready for testing. The V2 cab, which doesn't have the same issues, is sitting on the floor hooked to 'life support' (a pair of computers that fake it into thinking it's on the platform).

    Today, they decided to pull the V1 off the motion platform, and have moved it to the warehouse. There is no plan to re-install it on the motion platform, instead they are putting another of the 'new' variant cabs up there (all platforms are now the 'new' cab type). There is no plan to put it on 'life support' so we can run it off the motion platform, even if there was there are no computers configured for that; it would take a full day of setup to get working. Lastly, it does not run at our desks, as it requires a piece of archaic hardware to properly initialize it's I/O, and we don't have any of those laying around.

    I have until next Friday to fix it's bugs.

    That bottle of Crown may not make it home with me tonight.



  • You get no sympathy from me when you get to play with such cool toys.



  • You'd change your mind if you saw this grotesque mess of a code base...


  • SockDev

    i'm torn.

    should you:

    1. RUN AWAY

    or

    1. OOH SHINY! :-D


  • Discourse numbering strikes again.@accalia said:

    i'm torn.

    should you:

    1. RUN AWAY

    or

    1. OOH SHINY! :-D

    What the balls? It works on quote...


  • SockDev

    i know... i didn't feel like fixing it.





  • Last day without Discourse Bugs: null <t3806p7>



  • @Keith said:

    Discourse numbering strikes again.

    What the balls? It works on quote...

    That's really weird. Once again, Discourse is TRWTF



  • @CodeNinja said:

    I have until next Friday to fix it's bugs.

    That is easy. Remove the apostrophe. Bug fixed. My Dad fixed this permanently at his company: he forbade anyone from using any apostrophes. Any time you are tempted to use one, try to re-write without the apostrophe.



  • Hey, you remember that other thread?

    Yeah. That still applies.



  • @CodeNinja said:

    Today, they decided to pull the V1 off the motion platform, and have moved it to the warehouse. There is no plan to re-install it on the motion platform, instead they are putting another of the 'new' variant cabs up there (all platforms are now the 'new' cab type). There is no plan to put it on 'life support' so we can run it off the motion platform, even if there was there are no computers configured for that; it would take a full day of setup to get working. Lastly, it does not run at our desks, as it requires a piece of archaic hardware to properly initialize it's I/O, and we don't have any of those laying around.

    I have until next Friday to fix it's bugs.

    How much does the company want for that V1 cab? I'd take it home and hack together a replacement for said piece of archaic hardware... :grinning:



  • @Matches said:

    Hey, you remember that other thread?

    Yeah. That still applies.

    This. You can't drycode a bugfix. You can drycode a feature, but that means testing it afterward takes longer. Put in this situation I'd flatout refuse the work - I've got plenty of stuff to do, and it seems like you do as well.



  • @Keith said:

    You get no sympathy from me when you get to play with such cool toys don't understand its/it's.

    FTFY



  • I doubt he can flat out refuse to work, since I think he works for a military type group [somewhere], from what I remember, a defense contractor or something.



  • @Matches said:

    I doubt he can flat out refuse to work, since I think he works for a military type group [somewhere], from what I remember, a defense contractor or something.

    Why couldn't he refuse to work? Being a contractor isn't the same as being in the military.



  • He can refuse to work, but generally speaking it will almost always result in being fired.

    If he's not ready for that step, it's generally not recommended. (Specifically, not working the weekend is one thing, refusing a bug fix on what's presumably military hardware is a completely different thing)



  • @Matches said:

    He can refuse to work, but generally speaking it will almost always result in being fired.

    Yes, in any company. I'm not understanding why you think his situation is special due to the type of employer.



  • At most employers, you can get them to understand that if they don't have an actual install, you can't really debug the code.

    Military generally doesn't care that something doesn't exist to go chase it.



  • Have you experienced this? This sounds like ignorant generalization, is why I ask.



  • @PleegWat said:

    You can't drycode a bugfix. You can drycode a feature, but that means testing it afterward takes longer.

    This is relevant:
    @Donald Knuth said:
    Be careful about using the following code -- I've only proven that it
    works, I haven't tested it.

    You can fix a bug without running the code, but writing provable code is really hard. As an alternative, you can isolate the faulty portion of the application and run it in a host application. It may be easier to just build a new "life support" system, but sometimes you get lucky and the scope of the bug is small enough to tear it out and fiddle with it.


  • Discourse touched me in a no-no place

    @PleegWat said:

    You can't drycode a bugfix.

    Wet-code, Shirley? Or have I interpreted the sense of what you're saying wrongly?



  • Not sure where I got the expression from - may be local. Dry-code as in without ever being able to test it. Like you cannot verify a ship works without letting it into the water.


  • Discourse touched me in a no-no place

    @PleegWat said:

    Dry-code as in without ever being able to test it.

    The jist of the linked article is if you're running it through wet-ware (i.e. just your brain without testing it on a computer) it's wet-code.

    By extension, hardware -> dry-code.



  • @boomzilla said:

    Have you experienced this? This sounds like ignorant generalization, is why I ask.

    I can't speak for him, but I have experienced this. It happens quite frequently, actually.

    @Qwerty said:

    That is easy. Remove the apostrophe. Bug fixed. My Dad fixed this permanently at his company: he forbade anyone from using any apostrophes. Any time you are tempted to use one, try to re-write without the apostrophe.

    D'oh



  • @PJH said:

    The jist of the linked article is if you're running it through wet-ware (i.e. just your brain without testing it on a computer) it's wet-code.

    The analogy that came to my mid originally was dry firing.


  • Discourse touched me in a no-no place

    @Qwerty said:

    That is easy. Remove the apostrophe. Bug fixed. My Dad fixed this permanently at his company: he forbade anyone from using any apostrophes. Any time you are tempted to use one, try to re-write without the apostrophe.

    I wasn't kidding when I said as a rule of thumb, invert the regular rules for apostrophes when dealing with its.


  • Discourse touched me in a no-no place

    @Matches said:

    Military generally doesn't care that something doesn't exist to go chase it.

    Easy solution: If this is the Coast Guard, Navy, or possibly Marines, find a military person and tell them you'll need a box of map squares to fix it.




  • Discourse touched me in a no-no place

    Funny, but now try bringing those to the guy in the next room. And remember, n'est ce pas un pipe, the map is not the territory, etc., etc.



  • @FrostCat said:

    n'est ce pas un pipe



  • So they want you to fix an issue but ultimately there won't be anyway to test the fix short of pushing to "production"? My favorite kind of bug!

    I really do sympathize. I JUST got access to a system image that has traditionally caused my project lots and lots of headache because the system owner likes to lock stuff down tighter than a frog's ass. Yet they won't tell us what they did.

    Turns out I can replicate the issues they report when they give me an image I can test on! Better yet, I can test my fixes and validate they worked! Much magic! Amaze!

    Any way you can make your code for the V1 cab self-wipe its ROM/Disk/Punch-card-stack/whatever-is-mass-storage? Can't have any bugs if the sucker doesn't boot. :stuck_out_tongue:


  • Discourse touched me in a no-no place

    Close e-fucking-nough.


  • Winner of the 2016 Presidential Election

    but the character he used as an apostroph is a single-quote-character, isn't it?

    I think they can be used legit in pretty much any programming language. If you were to remove them, your work might break!

    Filed Under: char Apostrophe = '''; // this will probably not work...


Log in to reply
 

Looks like your connection to What the Daily WTF? was lost, please wait while we try to reconnect.