I didn't know about this. I enjoy learning something new. Thank you.

We did a total rewrite of our internal software package. We used new technology and the project timeline ended up doubling before we were done simply because of the programmers...

I don't think I'll be using this in my work. But thanks anyway.

I fully agree. Our IT delivers to in-house users. We get them involved prior to release so that we have a user that will make sure we have developed an...

There is no argument for the need of separation of duties. I just find, being an honest person, that all the protection we have to have actually makes my job...

I learned something about unpivoting and nulls.

It just proves the point that we should test our work before submission, and no last second changes without testing.

I agree about the query hints....

I have always taken the position that we should first listen to a request. If we can help quickly then do it. If it is complex then quickly evaluate their...

It seemed obvious but I have to admit I ran it to find out if I overlooked something.

When I was young I helped develop an accounting package that is still used today, decades later. I've also been fortunate to work in the medical industry and have seen...

For documenting before and after works best. I need some documentation before to help keep me on my path. Then as reality sets in I correct the documentation.

Looks like THROW just needs a little prep work ahead of time.

After working at several companies the most common waste of money was believing that you would save money by buying in bulk and getting the items at a smaller per...

It must cost something for the system to prepare for the possibility that this unused parameter may be passed in. Or is it such...