** UnhandledExceptionEventHandler :: OFFICIAL LC / CHATTER THREAD **

[diebitter]

wow you guys have to deal with some real retards. I was going to tell some stories about dealing with 3rd parties, but they're nowhere near as bad as, say, the nazi DBA.


Is it me, or do nazi DBAs always have faces that remind you of a well-slapped arse? (red and blotchy)

[diebitter]

Originally Posted by Zurvan

Reasonable code review is nice, it often spots issues that you can't see because yourself. Insane code review like that is somebody power tripping like a douche.

The DBA at my old job hadn't learned new technology since 2001. He refused to let us use Subversion, because it was a security risk ("OMG ANYBODY CAN CHANGE YOUR CODE"). He didn't upgrade to MySQL 5 because it was too much work. He refused to allow us to use Stored Procedures because - wait for it - they were a security risk. He much preferred that we hand code all SQL and apply our in-house data sanitization routine - which amounted to mysql_real_escape_string, but done recursively so we could pass arrays.

jesus christ get that guy a time-machine set for the early 90s.

[ShermanTank]

Evil DBA sounds like he came from a company like where I work. DB performance is so important we have a standards doc that reads like a lawyer wrote it. I would be pissed if someone was standing over me all day doing that though especially the SET/SELECT crap there's no difference. If I deploy something and it times out its one me I'd rather take responsibility for my own screwups that be micromanaged.

Is there any interest in a C# or MS SQL Server thread?

[jalexand42]

Originally Posted by ShermanTank

Is there any interest in a C# or MS SQL Server thread?

If you haven't already done this, definitely go right ahead. We could start off with a general Microsoft .Net platform development thread and then if it gets bonkers split it up.

My company is 100% .net based, so I'm sure I'll chime in there.

[greg nice]

this new programming forum should be removed

its just another thing to waste my time on instead of actual coding and getting stuff done

[jukofyork]

Originally Posted by greg nice

this new programming forum should be removed

its just another thing to waste my time on instead of actual coding and getting stuff done

Same could be said for the whole of 2+2

"If only I could have all those hours of random browsing back..."

Juk

[e i pi]

sweetness a new forum. maybe this forum will motivate me to get back into programming. i saw so much potential for solving poker problems.

[diebitter]

Can we rename this thread to make out more clearly the programming low content thread please?

how about the hackers trycatch?

Or the exception handler thread?

[TheIrishThug]

Along the same lines, UnhandledExceptionEventHandler thread. Anything that does get covered by the other threads goes in here.

It is also ans awesome name because it is there to handle exceptions that are not handled. But if there is an exception that is handled by this handler, it would not be an unhandled exception.

[_dave_]

Originally Posted by TheIrishThug

Along the same lines, UnhandledExceptionEventHandler thread. Anything that does get covered by the other threads goes in here.

lol awesome

[jalexand42]

Originally Posted by diebitter

Can we rename this thread to make out more clearly the programming low content thread please?

how about the hackers trycatch?

Or the exception handler thread?

haha, I was just changing it to something like: catch("LOW CONTENT" > /dev/null)

Saw _dave_ already changed it based on the above suggestion, so I'll leave it, I like the UnhandledException idea better, maybe we can rotate it between ideas.

[diebitter]

Ahhh thata much easier to spot, ta

[diebitter]

Originally Posted by ShermanTank

Is there any interest in a C# or MS SQL Server thread?

both imo. I think the ms sql server one would be particularly good for me, I know quite a few tricks about writing ****-off-a-shovel-fast sprocs.

[kyleb]

Originally Posted by Spottswoode

I agree with this, and I was actually quite happy to have someone reviewing my code when I started here, as it's probably the first job I have had where someone does this.

But when it comes to things like the following examples, it gets really annoying.

{t-sql}
Declare @tempVariable int
select @tempvariable = (Select count(0) from some table)

"WHY YOU USE SELECT, USE SET!!!!!!!!!!!!!!!!!!!!!!!!!"

or
Declare @GroupingType nvarchar(64) --SMK:16 is enough

These lines of code have passed 6 code reviews, but suddenly they are an issue since my last check-in.

LOL. This reminds me of my last dev job. They eventually implemented a style guide that blacklisted certain types of variable declarations and/or loops. It was unbelievable.

[diebitter]

I have to get this out of my system. Every time I read that 'select/set' thing, I have to resist the urge to say 'but there's a good reason to use SET instead of SELECT...'


I'll get my coat...