What's the biggest screw up you ever made writing software? Once a team I was on overshot a DCUT for some datacenter automation tools by two weeks, and it still ended up being shitty because the customer kept wanting to add shit.
>>2
You must be confused, I was asking a question to the people who post here. Not saying "Please post a link to a shitty tech blog which exists solely to generate add revenue," not, "help me with this homework cuz I hate school and am lazy and stupid lol," not "hey guys I want to learn <insert newest scripting language here>, what's a good book?" not "I hate jarbur and xml and my manager is retarted and uses buzzwords," not "hey guys, I want to write an <OS, compiler, other huge piece of shit that takes a large team of engineers a long time to do right> how do I do it lol?"
>>3
You, mister, just aged your own thread. That is very rude, and I am now going to sage you, personally.
Name:
Anonymous2006-12-14 15:25
lulz
Name:
Anonymous2006-12-14 15:44
Spent a whole week trying to figure out why my skeletal animation wasn't interpolating properly (flickering, looking like a lot of vertices get sucked into a black hole whose origin strangely didn't move with glTranslatef calls)... only to find out it was due to floating point errors and divide-by-zeros in a couple of my Quaternion member functions.
Whatever happened to programs terminating fatally with an exception when a divide-by-zero happens? God damn, that pissed me off.
Name:
Anonymous2006-12-14 18:12
>>7
DIVIDE BY ZERO!!!! *cums*
Please, you need to tell your story in /sci. We'll all worship you!
Name:
Anonymous2006-12-14 20:17
Forgetting to put the a WHERE clause on a DELETE statement in a rather crucial SQL stored procedure. Lucky I had fairly recent backups ..
Name:
Anonymous2006-12-14 20:42
DELETE considered harmful, Codd scolded
Name:
Anonymous2006-12-14 20:44
Pointers in C.
Every time I try.
Name:
Anonymous2006-12-15 3:51
>>11
The trick is to initialize them and use correct data types
Name:
Anonymous2006-12-15 5:24
The trick is to order extra green onion. But it's not for amateurs; careful if you do, as the employees will notice you're a pro.
Solution: if (0 = i)
Not if you want to set i to some return value from a function who returns a pointer: int *i;
//...
if (i = functionWhoReturnsAPointer()) { //...
I was trying to make a serial generator in C++ in the Dev-Cpp IDE, and my streams were fucking up left and right. If I did something like,
cout << "Enter some shit: ";
gets(SomeString);
it would wait for you to enter stuffs, then print "Enter some shit: ". :|
lol. I also was disassembled a program and realized a problem before reviewing my own source... Sigh.
Name:
Anonymous2006-12-17 11:27
I was writing something in C which required a big complex loop calling a bunch of functions for several different procedures that had to be done. I was perplexed that a certain variable would always get incremented and it shouldn't. I analyzed every function, came to the conclusion that all were right, and then focused on the loop itself. I debugged the program, step-by-step. Every time I was more and more pissed at it, and I ended up reviewing the fucking assembly code. Then I saw how it would clearly get incremented. I got to the point of thinking gcc had to have a bug. When I was about to try rewriting it somehow to prevent it from happening, I noticed:
while (...) {
...big loop...
...lots of stuff...
...function calls...
...etc...
j++;
}
I wasted an evening with that. Fucking stupid. Had my vision checked after it.
Name:
Anonymous2006-12-18 9:44
This is especially dangerous in python since
while (...):
do this1
do this2
do this3
>>34
Yes, and it's a great feature. First, because it forces idiots who don't indent their code properly to do so. Bad indenting = syntax error. Second, because it saves you braces and lines of code, making more code fit in a screen, making code easier to read. Third, because there are no gotchas such as:
if (tl_dr)
if (yoshinoya)
me.lmao();
else
troll();
Because of this gotcha, and more importantly, because of the common debugging printf you add and remove here and there, I got used to always using braces, but it's less nice looking.
>>36
What, optional? Exactly the people who need it forced on them are going to disable it. That was perfectly well thought.