Amazing Programming!

[Darsithis]

http://www.joelonsoftware.com/articl...000000069.html
As a rule of thumb, you probably shouldn't!

Here is a quote that hits home pretty well with me

The quote is right and wrong. Many times old working code, while probably not developed the way you would write it, is just fine as long as it handles exceptions and executes well. This, on the other hand, isn't something even close to worth saving because it isn't tested by any means, much less working.

What baffles me isn't that a developer was stupid enough to do this in the first place. The world is full of stupid people. But surely whoever was responsible for that shit must have noticed the insane execution time and still they let it go ahead.

It's never been released to production. The previous company has been sued and we're taking over what is left of the project

[ripponesan]

Maybe back then when this was coded joins didt exist? It has to be really OLD then.

[Darsithis]

Maybe back then when this was coded joins didt exist? It has to be really OLD then.

It was written in 2006 for Sql Server 2005

[Hyve]

How would that even be possible? At what point would any developer even consider making those calls, that many times?

What the hell?!

[Darsithis]

How would that even be possible? At what point would any developer even consider making those calls, that many times?

What the hell?!

A developer who doesn't know how to write optimized, complex queries and approached the issue through code instead...always the wrong way to go for any complex operation involving data like this. My stored procedure inserts all 2900 tax transactions in under 1 second.