Log in

No account? Create an account
current entries friends' entries archives about me Previous Previous Next Next
Software Changes - cellophane — LiveJournal
the story of an invisible girl
Software Changes
Can I "squeeze this in" at the last minute? Yes.
Will it be properly tested? No.
Do I write good code that usually works? Yes.
Does my code always work the first time? No.
Am I human, and therefore capable of making mistakes? Yes, that's what testing is for.
Will it break? I don't know. No promises.....
read 4 comments | talk to me!
jkling From: jkling Date: May 8th, 2003 07:46 pm (UTC) (Link)
Code poetry!
From: nicegeek Date: May 9th, 2003 11:09 am (UTC) (Link)

Eww...let me guess...someone just did a last minute requirements change on you?

I think we need to write a standard disclaimer to hand to anyone who tries that.
bjorng From: bjorng Date: May 9th, 2003 02:05 pm (UTC) (Link)
I was at a talk last month, and the speaker (Bruce Eckel, if you know who he is) had a mantra for production code. It was: "if it's not tested, it's broken". He had a couple of really vivid examples from his own experience. His talk was about unit testing and something called Design By Contract, both of which have to do with using a test-first development philosophy, so you could argue that his assertion was overemphasized. But I tend to agree with it.
renniekins From: renniekins Date: May 12th, 2003 09:27 am (UTC) (Link)


Yeah, I totally agree -- you can't trust untested code. Simple mistakes are way too easy to make!
read 4 comments | talk to me!