Tag: Amusements

I just lurve clients sometimes!

Our main client has the (probably not uncommon) habit of labelling every ticket as urgent. The problem with this is that when something really urgent comes along, they have no way of making it stand out above the other urgent jobs. This predictably led to the creation of a “Very urgent” rating.

Today they outdid themselves…

How urgent is it?

This led to a lively debate as to what would come next. How about “-1. Life threatening”?

I blogged a couple of months ago about how MailTrap had achieved precognition. Well, it seems that they aren’t the only ones to manage this. We use Freshdesk for our support ticket system, and they have done the same! Amazing what they can do with these new-fangled rubber-band-and-string-driven computer type things nowadays eh?

We use the rather excellent mailTrap for testing code that sends emails. Whilst this site is very well done, I didn’t realise quite how clever the developers were until I noticed this…

Just saw this comment on Stack Overflow, and thought it too good not to repost…

A programmer’s wife sends him to the supermarket. She tells him, “Buy a loaf of bread, and if you see some eggs, grab a dozen.”

The programmer later returns with a dozen loaves of bread under his arm

Having blogged recently about some great error messages, I came across another one! Microsoft much employ people to craft these, they just couldn’t be there by accident. I reckon they are put there to amuse developers, and distract them from the fact that the software is misbehaving!

Anyway, I was using the SQL Server Import and Export Wizard, and it threw up the following error message:

Error 0xc004706b: Data Flow Task 3: “Destination 14 – EntityHistory” failed validation and returned validation status “VS_ISBROKEN”

I just love that last bit!

And I’ve seen a few! I was just trying to back up an SQL database, and got this truly wonderful error message… Not much you can say to that is there?

Bored of the usual methods of inflicting torture upon myself, I thought I would upgrade SQL Server 2008 R2 to SQL Server 2014 (stop laughing at the back!), because, erm, well it seemed like a good idea at the time.

Read more to hear the whole sorry story