
No really, what were they thinking?
Yet another example of my ongoing frustration with getting Copilot to do anything useful
A personal Blazor blog.
Showing posts tagged Amusements.

Yet another example of my ongoing frustration with getting Copilot to do anything useful

A pointless badge displayed on a GitHub user profile page

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

Just to prove that Windows isn't the only piece of software out there that is capable of amusing me, Thunderbird gave me a laugh today

Another excuse to have a laugh at the expense of some very clever Microsoft engineers!

Just browsing some books on Amazon, and saw this lovely example of what happens when you forget to HTML-encode your text...

Another amazing Microsoft error message

My son just noticed that if you go to google.com and enter "last day of march 2022", then you are given an, erm, interesting result!

I just fired up a virtual PC that I hadn't used for some time, opened File Explorer, and saw this...

I have previously blogged about some of the great error messages I've seen come out of Microsoft.
Here is another one.

Spurred on by my son's amazingly ugly CSS-only background, I decided to go one better and animate it.
Along the way, I rediscovered some of what made the early days of the web the wild, whacky and downright ugly place it was!
Get your sunglasses out before reading this blog post!

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.

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"?

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

Whilst editing a WPF view, the XAML designer claimed it couldn't display a child user control due to a null reference exception. Looking at the stack trace, I noticed a wonderfully named method...

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
Forget all you ever learnt about enterprise design, I'll reveal the truth, and it's not pleasant (but quite funny!)
Following on from my previous posts with great error messages, here are some more
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!
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
Two programming-related jokes that amused me
" I have always wished for my computer to be as easy to use as my telephone; my wish has come true because I can no longer figure out how to use my telephone ."
Danish computer scientist Bjarne Stroustrup
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...
I was underwhelmed at being awarded two separate recognitions for my contribution to the community.
Read on and be as underwhelmed as I was!
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!