...and also preparing for a fundraiser at which I'm performing tomorrow:
And did I mention Apollo After Hours?
I'm still trying to debug the performance of our principal application, which shouldn't be struggling the way it is.
I did, however, take two minutes out of my life to watch this:
I was here until 7:30 last night and would probably stay that late tonight if I didn't have a prior commitment. At least last night I got to see this:
At least I've isolated the code causing the problem. Unfortunately it's one of the most-called methods in the application. Sigh.
I was going to write a couple of entries today on various topics, but then this happened in production:
That's a production database getting overloaded. I am now going to continue debugging it.
In the reading queue:
Did I mention that DUKE WON?!
With a little more than five days until my next international flight, I'm stocking up my Kindle:
UAT release this afternoon. Back to the galley.
If you have a set of unit tests for a large application, and not every one of them passes, then you don't know whether the application works correctly. In fact, failing unit tests are evidence that it isn't working.
Also, marking them with the [Ignore] attribute doesn't count as fixing them.
Also, deleting the part of the unit test that fails doesn't count either. An empty test method is not a passing test unless the method being tested is also empty. And an empty test method should not ever be committed to the source repository.
</rant>
You may have noticed that the photos I've posted lately have unusual aspect ratios and sizes. This is because I have been lazy.
Usually, I upload photos from my camera or phone to my laptop, process them with Adobe Lightroom, and crop them to a pleasing 2:3 aspect ratio. Lately, though, I've just shot them through Google Hangouts from my phone. I have little understanding of Google's choices but they seem to be around the byte count and not around the dimensions.
Here, for example, is a shot of O'Hare Terminal 3 from this morning:
Google did that one at 1236 x 695, at 249 kB. The original is much larger (4 MB), but the same aspect ratio.
I may re-edit the photos later, after landing.
Update: here's the same photo after going through Lightroom:
After 38 years of publication, Dr. Dobbs is shutting down:
Why would a well-known site, dearly loved by its readers and coming off a year of record page views, be sunset by its owner?
In one word, revenue. Four years ago, when I came to Dr. Dobb's, we had healthy profits and revenue, almost all of it from advertising. Despite our excellent growth on the editorial side, our revenue declined such that today it's barely 30% of what it was when I started. While some of this drop is undoubtedly due to turnover in our sales staff, even if the staff had been stable and executed perfectly, revenue would be much the same and future prospects would surely point to upcoming losses. This is because in the last 18 months, there has been a marked shift in how vendors value website advertising. They've come to realize that website ads tend to be less effective than they once were.
So rather than continue with Dr. Dobb's until it actually loses money, [our owners] decided to sunset the site — a sudden end to remarkably robust and wondrous journey that began 38 years ago.
In the 1980s and 1990s, Dr. Dobb's was the best source of information about C/C++ programming, bar none. I've read the magazine and the website off and on for about 30 years. I'm sad to see it go.
Psy's surreal Gangnam Style video got so many views on YouTube that Google had to change their database schema to count them:
YouTube said the video - its most watched ever - has been viewed more than 2,147,483,647 times.
It has now changed the maximum view limit to 9,223,372,036,854,775,808, or more than nine quintillion.
YouTube's counter previously used a 32-bit integer, which is a unit used to represent data in computer architecture. This means the maximum possible views it could count was 2,147,483,647.
In my programming language, C#, the 32-bit integer is standard, and is called simply "int". The 64-bit integer is called "long". So, basically, Google decided that all their videos needed—wait for it—to get a long.
Ah. Ha, ha. Ha.
Anyway, here's the video in question, which at this writing has 2,160,472,115 views:
Hat tip: Dan DiGangi.