|
Quote:
Originally Posted by raspberryh
1. What kind of programming do you do?
I do mostly web and application design. I also write scripts for our servers here at work :-)
Quote:
Originally Posted by raspberryh
2. How do you ensure that your program/algorithm is correct?
I test the shit out of it, then i hand it to one of the dumber users (read: monkeys) around here and see if they can break it. I usually get them to write down every little thing that they hate/break and hand it to me.
Quote:
Originally Posted by raspberryh
3. To what degree do you ensure that your program/algorithm is correct?
When i am doing the testing, i generally put in input that i know is wrong, just to see if i have my error catching up to par. Then i start inputing correct input, just to see if the functions/objects/whatever are working the way that i want. After that, like i said before is up to the user to break. Then i push a updated version :-)
Quote:
Originally Posted by raspberryh
4. Please give an example (or more than one example!) where a program or algorithm you wrote was not fully correct.
I wrote a inventory program once for our yard (sells railway ties, lumber, fencing etc..), it was designed to have the data input in real time. The user only inputed once a month and then wondered why the transaction dates where wrong (he really should have RTFM). Thus, when he generated reports for the managers all the dates were wrong. I solved it by talking to the user and explaining why there was a need for real time data, and why he should quit being lazy. After that it worked fine.
Quote:
Originally Posted by raspberryh
5. Please give some reasons why program correctness is very important in your field.
Correctness of data is the main reason. If you don't know where you've been, how can you know if your going in the right direction? ie: if you advertise a sale for fencing in winter vs. in the summer. i realize that's a pretty stupid example and it should be just common sense, but you get the picture.
Quote:
Originally Posted by raspberryh
6. What advice do you offer to a student who is thinking about going into your field, as far as program correctness is concerned?
Write code that is easy to read. You should be able to read it like your reading the newspaper. Comment the crap out of it. It makes things much easier in the long run. Think i used the word read enough?
Quote:
Originally Posted by raspberryh
7. How can someone in your field prevent program errors while he/she is still in the process of designing his/her algorithm?
Like i said above, make your code readable and lots of comments. Also, always assume the user that your giving the software to, is as smart as a rock and that his/her computer is the most broken chunk of crap out there. Cover all angles of input, even if you know said input is hard to screw up.
Quote:
Originally Posted by raspberryh
8. Do you do any collaboration in writing software or algorithms?
Not at the moment, i used to be part of the IM project here on PFO, but i didn't have the time to donate. Also i no longer have the Internet at home (something i am changing in the near future).
Quote:
Originally Posted by raspberryh
9. Any other comments/case studies/stories you may have are greatly appreciated!
N/A
Welcome to the forums! I suggest that you stick around we have a great community here :-)
The reason that i say that is because from time to time we get people coming here asking questions like this one and leave after they get enough answers. Kinda pisses me off.
Ether way, enjoy your stay :-)
BTW i like your binary clock on your site :-)
__________________
Profanity is the one language that all programmers understand.
Check out my Blog <---updated Nov 30 2007!
|