Simple yet entertaining
-
Here's one I know we've all seen, but it always give me a chuckle: if ((from i in dc.PRODUCTIONs where i.ACTIVE == true select i.WOID).Contains(getSysId(woid)) == false) If you think this is bad, you should see how the actual software runs! Ever since I started working for this company, I've had to completely strip and rebuild all the code most of it only half works. I'll post more horrors as I find them. Happy coding!
-- Steven
-
Here's one I know we've all seen, but it always give me a chuckle: if ((from i in dc.PRODUCTIONs where i.ACTIVE == true select i.WOID).Contains(getSysId(woid)) == false) If you think this is bad, you should see how the actual software runs! Ever since I started working for this company, I've had to completely strip and rebuild all the code most of it only half works. I'll post more horrors as I find them. Happy coding!
-- Steven
OMG!!
-
Here's one I know we've all seen, but it always give me a chuckle: if ((from i in dc.PRODUCTIONs where i.ACTIVE == true select i.WOID).Contains(getSysId(woid)) == false) If you think this is bad, you should see how the actual software runs! Ever since I started working for this company, I've had to completely strip and rebuild all the code most of it only half works. I'll post more horrors as I find them. Happy coding!
-- Steven
I'm not too familiar with linq yet, what's wrong with this one?
Wout
-
I'm not too familiar with linq yet, what's wrong with this one?
Wout
-
Uuuh... :~ So what's the bug?
Wout
-
Uuuh... :~ So what's the bug?
Wout
-
It's not a bug, but the code is very difficult to understand, even for experienced programmers. The guy should have used variables to store intermediate results.
Aaaah, I thought it was my unfamiliarity with linq, geez!
Wout