I wrote two lines of code yesterday

They were both wrong.

Comments (32)
  1. Thank you Raymond, I feel so much better now.

  2. Name says:

    Sad part is two wrongs don't make a write :(

  3. MikeBMcL says:

    On the bright side, that's better than writing reams of code and then deciding that your original design was ill-considered such that you have to throw it out and start over. Regardless, you posting that makes me feel much better about my occasional similar experiences.

  4. PastorGL says:

    I even haven't enough time yesterday to write a single line of code. Being a dev team lead sucks.

  5. Programmerman says:

    I know I've been there.

  6. rsola says:

    This post demands a Grumpy Cat picture: http://www.quickmeme.com/…/3u6wwj

  7. JM says:

    That's slightly worse than laboring the entire day to solve a problem, only to find, at the end, that what you thought was a problem was not, and everything you've done so far was (at best) to further your education.

  8. Eric Webb says:

    Reminds me of a quote attributed to Blizzard's Bob Fitch:

    "All programs can be optimized, and all programs have bugs; therefore all programs can be optimized to one line that doesn’t work."

  9. Danny says:

    "This code is not valid according to the Win32 ABI. If the "push rsp" takes a stack overflow, your process will be terminated due to missing unwind data"

    Above ones?

  10. Me says:

    I wrote no lines of code yesterday, and they were all wrong.

  11. JDP says:

    This post demands a Grumpy Cat picture:

    He's already had a bad day. Don't make the problem worse.

  12. Steve says:

    Hah! I wrote 10 lines of code and only 8 were wrong. Oh, Wait.

  13. rsola says:

    Hey, it was an innocent joke. No offense intended.

  14. Let me guess: they were both Perl, and they were both complete programs.

  15. Dave says:

    Do you also know two facts about ducks?

  16. JDP says:

    Maurits: If it were perl, both lines would have both been correct, just not for the problem you were trying to solve.

  17. sirin says:

    That's why I like being unemployed.

    So I have enough time to write hundreds of lines everyday

  18. James says:

    That's productive work by someone. One day to find out beats six months after release.

  19. parkrrrr says:

    @Me: Fortunately, they were all correct as well.

  20. alexx says:

    Why don't you have a Twitter account?

  21. Killer{R} says:

    Post them here.. Let us find what is wrong :)

  22. David Crowell says:

    That's an excellent metric.  You *only* wrote two incorrect lines.  :D

  23. cheong00 says:

    ; I even haven't enough time yesterday to write a single line of code. Being a dev team lead sucks.

    Btw, being a Dev that your customers have your direct phone line AND mobile phone number sxxks more. Especially when your customer is doing 7×24 business.

    I left that company shortly because of health problem.

  24. @cheong00 says:

    That's why I never give out my cell number. I've repeated told people that I have a personal cellphone for family but no work cellphone.

  25. cheong00 says:

    ;That's why I never give out my cell number.

    The sad part is that they're given out by company's salesperson, not by myself. They went and reached HR to get my mobile number from my application form, and HR gave it without second thought.

    Since that in every company I worked for, I make an effort to convey the idea to my colleagues that "Giving out others mobile numbers without the number owner's consent is betrayal that's not to be forgiven."

  26. SomeGuyOnTheInternet says:

    IMO giving customers your cellphone number is a good way to rapidly become a better programmer.

  27. cheong00 says:

    @SomeGuyOnTheInternet: Not when you're on second week of your job, and your primary responsibility is maintenance of old code written by other ex-staffs.

    And it's plain disastrous when the old code itself don't live well and generates so much support calls that prevents you actually try to "read through the code", let alone do any improvement to it. Everytime the "quick and dirty patch" on it adds another level of complexity and makes it even harder for future maintainer to read.

    Nevermind, let me let forget about that company.

  28. Dave says:

    IMO giving customers your cellphone number is a good way to rapidly

    become a better programmer.

    Not when you end up being used to ghostwrite someone else's software by proxy via phone conference, as I was recently.

  29. Morous says:

    Raymend, congratz. No sarcasm here. We all have that kind of day occasionally. When that happens, the smartest thing you can do is to write as little code as possible.

  30. Rick C says:

    A customer joked with me about doing a software upgrade over the weekend and asking my boss for my cell phone #.  I know my boss wouldn't have given it out anyway, but as it happens I had just changed it the week before and the company doesn't have it yet.

    The story about the sales weasel just validates my opinion that they should be kept in a box and jabbed with a stick on general principles every once in a while, a la "poke the Goozim with a stick."  If I worked for a place that gave my personal # out I would hand them my bill and say "since you've turned my personal number into a work number, you get to pay for it."

  31. Silly says:

    Chuck Norris anticipated them and would have implemented a work around, but he realised you would recognise the mistake yourself, and so left things alone as a learning opportunity.

  32. JamesNT says:

    Mr. Chen,

    Consider this comment your official cease and desist demand to never again endanger my god-like opinion of you.


Comments are closed.

Skip to main content