Search

Showing posts tagged Amusements.

When developers write documentation

When developers write documentation

One of the nice things about a modern IDE like Visual Studio is the help you get when coding. XML documentation, which shows up as a pop-up below the line of code you're writing helps you check you're using the right method.

Sometimes it tells you a little bit more than that...

Windows 10, built to last

Windows 10, built to last

Whilst I'm getting increasingly frustrated with Windows 10, the number of errors that seem to crop up, and the number of basic features that seem to stop working for no good reason, it has produced more than its fair share of amusements.

Today's suggests that Microsoft have an amazing level of confidence in the staying power of Windows 10.

Erm, how urgent is it?

Erm, how urgent is it?

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...



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

Programmers

Programmers

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

Another great error message!

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!

My computer lies to me

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

My computer just laughed at me

Of course, we professional programmers never make mistakes, ahem. That’s why we never need to use debuggers, ahem.

Well suspend belief for a moment, and assume that I had a bug in the code I was developing. You know the feeling, you stare at it, you write unit tests, you stare at it some more, and still can’t work out why on earth Visual Studio is claiming that there is an error in your code, when it’s so obvious that there isn’t. You even get to the point of talking to your computer, pointing out the error of its ways...

They didn't really mean that did they?

Sadly, whilst building a solution yesterday, my machine started behaving in a very weird manner, with applications not responding, the taskbar disappearing and so on, followed by the dreaded blue screen of death. When I checked the event log after pulling the plug out (I hate doing that!) and rebooting, I found lots of errors, which led me to a Microsoft Connect article (now sadly removed) where someone was reporting a very similar problem.

To my amazement, the very last comment by a Microsoft employee in response to this bus report was “This is known issue, this bug was resolved by mistake, we are already addressing this issue.”

Surely they didn’t mean that did they? Someone tell me I read that wrong!