This was one of the last photos I took of Norway, just as we were leaving Flam.
I would have to say that Norway was one of the most stunning places I have ever visited. The landscapes were truly amazing.
I came across this video highlighting a very large scale infrastructure project to connect the coastal communities of Norway.
If implemented successfully, this would be an impressive achievement.
Most will credit Grace Hopper with establishing the use of the word “bug” to describe a problem with computers. A dead moth had been found in Harvard’s Mark II computer and Hopper used the term to identify the issue. Literally, a bug was found inside the computer.
However, the use of the word “bug” goes back over 140 years to Thomas Edison. He used that phrase when working on telegraph systems back in the late 1800s.
You can read all about it here.
I received an email earlier this week asking for some help on a website that was exhibiting very slow page loads, in excess of 2 minutes or more. Very few people have the patience to wait a couple of minutes for a page to load.
When I was teaching computer science many years ago, I remember telling my students that the process of debugging required three fundamental steps:
Step 1: identify the problem
Step 2: isolate the problem
Step 3: resolve the problem
The steps are not often easy as some bugs can be very difficult to track down. There is also the tendency to repeat the same approach to problem resolution. Expecting a different outcome from the same approach can lead to lengthy debugging sessions.
My first reaction, upon taking a closer look at the website, was to attribute the issue to outdated themes and plugins, this being a WordPress site.
I was careful to make a full backup of the site and the WordPress database, create a local instance on my desktop, and ensure that all components of the site were using current versions.
Although all good actions to take, that did not resolve the issue. I had yet to identify the problem.
Debugging on the web is fairly good relative to the old days when I was debugging C and Assembler code.
Browsers provide pretty good tools to step through a website and find the issue.
I am quite used to working through complex websites with the development view.
Bringing up my friend’s website allowed me to identify the problem almost immediately with the console trace. Upon loading certain areas of the site, the code failed when attempting to load a resource.
The reason? A bad link to an image file.
It happens with WordPress.
The code was unable to load the resource with the following snippet: <img src=”http://123.45.678.910/~userid/domain.com/wp-content/uploads/2018/08/image.jpg”…
It would eventually timeout and recover without loading the resource hence the lengthy page loads.
I had successfully completed step 1. I had identified the error. I then jumped right to step 3. After all, the problem was pretty obvious to me. And it was obvious. I just forgot to isolate it in the code.
These snippets with bad links were everywhere in the code. And the code was literally just a glob of unformatted text. Thousands of lines of dense code. Very hard to isolate in the WordPress admin panel as most of the pages were created using a visual composer plugin. Fixing the bad links in the WordPress admin panel is not the most fun way to spend your time. Tedious to go in and bring up isolated sections of the code.
After a few hours though, I had found them all and promoted the changes back up to the server.
I asked my friend to walk through the site to make sure I hadn’t missed anything. So far, so good.
Loading images from a hard-coded IP address instead of a domain name is not typically a good thing to do. Fortunately I did not have to go into the WordPress database to update link details. The issue was limited to bad links in the code itself.
I don’t know why it happened. Very few people have changelogs for their websites. I suspect someone was doing something on localhost and uploaded the code through FTP with client-side references. I was just happy to be able to resolve the problem in a timely fashion.
Not too bad for an old, retired CIO.
The end of the DSLR?
Nikon finally revealed two mirrorless cameras today. A necessary response to the market demand for sophisticated mirrorless cameras.
Thom Hogan offers a thoughtful post on the re-entry of Nikon into the mirrorless world.
Finally, here’s the dirt simple truth. The three primary sources of camera purchase are:
- New users (e.g. the young getting their first dedicated camera)
- Updaters/Upgraders (e.g. existing DSLR/mirrorless users getting a better camera)
- Replacers (e.g. someone who dropped, damaged, lost, or had stolen their gear and is buying again)
Nikon’s problem is the first group, particularly recently with lame entry DSLR upgrades and marketing, plus no real entry cameras to speak of (compact or mirrorless). Sony’s problem is more the second group (because people in one brand tend to stay in that brand, and Sony started in a deep third place position). So it’s going to be interesting to watch as the two battle it out for second place in the ILC business.
I’d still say it’s Nikon’s ball to fumble.
Be prepared to fork over several thousand Canadian dollars for one of these cameras. Vistek has the pre-order pages up and the Nikon Z7 is $4,400 before tax body only and the Nikon Z6 is $2,600 before tax body only.
Three lenses to start. A 24-70mm f4 at $1,300, a 35mm f1.8 at $1,100 and a 50mm f1.8 at $800.
Be prepared for some Nikon shooters selling off their DSLR gear for the new mirrorless offerings. Should be some great deals on D750s, D850s, and assorted Nikon F-mount lenses in the used marketplace.
And, apparently it is Zee. Everywhere. Even in Canada.
When we were wandering around Hamburg, Germany a few weeks back, I came across a number of tour buses operated by Hansa Rundfahrt. I took this shot just outside one of the churches in Hamburg.
This is what they have to say about themselves on their website:
Die Hansa Rundfahrt GmbH ist ein erfahrenes und modernes Busunternehmen in Hamburg. Wir bieten seit über hundert Jahren die Anmietung von Omnibussen inklusive Fahrer an. In der schönen Hansestadt Hamburg haben wir uns auf Bustransfers für Gruppen, Schulen, Firmen und Vereine spezialisiert. Buchen Sie uns für Flughafentransfers, Incoming Transfers und Shuttle Transfers.
I’m not sure what it means but I do like the design of the bus. Very sharp.
I have done FTP tests numerous times over the years. It comes with the territory if you are interested in improving your performance on a bike. FTP gives you a number and you base your training effort against that number.
I hate FTP tests. They are really awful. You ramp up through a progressive warm-up and then you go as hard as you can for twenty minutes.
Twenty minutes, full out on a trainer, pushing hard watts, can seem like an eternity.
The Sufferfest, my preferred service provider of pain and agony, introduced a different fitness test called Full Frontal.
I did the test on Sunday.
Makes sense that I am a “pursuiter” rider type. I do chase other cyclists when I am out on the road.
The Full Frontal test exceeded my expectations for pain and suffering. It was the hardest thing I have done on a trainer. Ever.
I’ll now start a new 12-week training program based on the four dimensional power profile — as if training by FTP alone wasn’t hard enough.
Here are the gory details about the fitness test in case you are interested.
It was innocent enough really. The App Store was telling me that I had an update for Fantastical 2. And what should you do when you have an update from the App Store?
Well, in this case, I probably should have left the update alone.
The story begins with me applying the update. I have many apps that I have purchased from the App Store. And they are frequently updated.
This one, though, decided to give me trouble.
It began with this dialog box. One that I would see several hundred times over the next few days as tech support from Flexibits and Apple attempted, in vain, to resolve the issue.
I followed the direction, entered my password and, voila: the same dialog box reappeared.
I repeated the same steps a few dozen times expecting, perhaps, that my one and only Apple ID and password would eventually be accepted. But all that happened?
And then it dawned on me. A crushing conclusion. I would have to contact technical support.
I am, by nature, a very self reliant person. I prefer to manage my own affairs especially my own tech stuff. It is very rare that I deal with technical support especially with software companies.
But I use Fantastical 2 on all my devices: laptop, smartphone, tablets and desktop. Even though I am retired, I still have important meetings to manage gosh darn it!
Here was my first note out to technical support at Flexibits.
The latest update from the App Store broke my desktop app. I am stuck in an infinite loop with the following dialog:
“Fantastical 2” was purchased using the App Store on another computer. To use “Fantastical 2” on this computer, sign in using the Apple ID and password used to purchase it.
I sign in using the only Apple ID and password I have ever had, and all that happens is the same dialog box comes back up.
The reply was actually pretty fast. And it led to the following set of emails:
Funny how the technical support folks continued to focus on the obvious: you must be using a different Apple ID and password so go back and check!
I sent them a copy of my receipt.
I purchased Fantastical 2 on the very iMac which the App Store rejected.
At this point, Flexibits gave up and told me to contact Apple. The problem, they said, must be with the App Store.
So I reached out to Apple.
Well, of course this had absolutely NOTHING to do with the problem. And I told them that. Their response? Well, you will have to contact a different support group at Apple.
And I did.
I have Apple Care which I guess gives me a bit of an advantage in terms of getting technical support in a timely manner. I called Apple Support, provided them my AppleID and my device and within just a few minutes I was online with first-level support.
We spent about an hour or two making all sorts of changes to my machine. We did a safe start with the iMac — at which point Fantastical 2 from the App Store did launch properly — and then moved on to removing login items, trashing all sorts of files and, well, eventually being assigned to second-level support as we kept getting the same dialog box over and over.
I spent several hours on the phone attempting to resolve this issue with second-level support. We tried killing processes in sequence, multiple safe starts as well reinstalling the OS. I must admit I was a bit nervous about doing that step.
Anyway, after spending about four or five hours chasing down the issue, I launched Fantastical 2 from my now very clean iMac and what did I get?
Apple gave up and told me to go back to Flexibits.
Which I did. At this point, I thought it would be easier just to buy the desktop version off the Flexibits website and abandon the App Store upgrade altogether. But, now that I am retired, I have to think about expenses. Why should I have to pay twice for the same product?
So I started with a request for a discount.
Their first response was to try and make the website version authenticate with a hidden file that the App Store deposits on the computer. Using the terminal app, I punched in a Unix copy command, optimistic that I would finally have my app back and working.
Clicked on the Fantastical 2 app icon and…
We tried a bunch of other technical stuff and it became apparent to Flexibits that this problem was not going to get resolved.
The other way out of this pickle was a link to a coupon for a zero-cost license to Fantastical 2 from the Flexibits website.
I clicked on the Fantastical 2 app icon and…
I retired on July 20th, 2018. But really, the first few weeks of my retirement consisted of travelling through places like Geiranger, Norway, pictured above.
In other words, I was on vacation for the first few weeks.
Now that I am back home, I can look at this week as being my first week of retirement. I did not go back to work after taking a vacation, which is what I would have done for the past 35 years or so.
How did the first week of retirement go?
In a word, terrific. Every night a Friday night. Every day a Saturday.
I did set out a calendar which included the following activities for this first week:
- 1-2 hours of cycling each day.
- 1-2 hours of content creation each day for rvcastaways and this blog.
- 1-2 hours of guitar practice each day.
- 1-2 hours post processing photos from our Norwegian cruise and creating videos from our Norwegian cruise each day.
I had several lunches with different friends. I took my son out to Mission Impossible. I walked the dog. Lorraine and I went out to a few lunches. I’ve been reading a couple of books. I managed the investment portfolio. We started packing for our winter trip south.
I’m having a great time so far. And I am not worrying about much of anything at the moment.
I decided that for the first few weeks (months? years?) of retirement, that I can loosen up a bit although with enough structure and challenge to the day that I have a sense of accomplishment.
So far, so good.
Morgan AC 20 Deluxe. Sold.
Clark Beaufort. Sold.
Fender Super Champ. Sold.
Mesa Boogie Road King Dual Rectifier with 4×12 Cab. Sold.
Hughes & Kettner TubeMeister 18. Sold.
Fender Hot Rod Deluxe. Sold.
Mesa Boogie Lonestar Special. For Sale.
Fender ’64 Deluxe Reissue. For Sale.
Fender ’57 Tweed Deluxe Reissue. For Sale.
That leaves me with two amps: the Swart STR Tremolo and the Swart AST Mk II head and 1×12 cab.
With retirement, downsizing and a focus on travel for the next few years, carrying all of these amps really made no sense which is why I sold most of them.
Getting older comes with its own set of challenges. Hauling around heavy amps and heavy pedalboards being one of them.
I have always been a tone snob. As far as I was concerned, tube amps were the only way to get a great guitar sound. I found the early digital modellers, like the Line 6, to be less than satisfactory. Some players I knew were able to get some great results from that class of technology but it wasn’t for me.
And then the community of guitarists that I hang around with started jumping into modeling. Specifically the Kemper platform.
I’ll be south during the winter months travelling in a 40-foot diesel coach. Although the coach offers a lot of living space, given the form factor, I have to travel light.
Guitar amps are bulky.
Modellers like the Kemper promised great sounds and portability.
I bought one.
I struggled to get “the sound” I was looking for from the Kemper rig.
I purchased thousands of profiles trying to find a few gems in what appeared to be a large pool of mediocre tones. I ditched my pedalboards and went all in with the Kemper for about a year.
I gave it a chance.
The Kemper just didn’t work for me.
It also grew in size and weight.
By the time I added the rack case, the Kemper remote, and a bunch of external pedals, I had a rig that was pretty much the same bulk as my smaller amp rigs.
I sold the Kemper and bought the Fractal AX8.
Very portable. Very affordable (relative to the Kemper). Really great sounding models out of the box. And great sounding effects.
The software side of the Fractal was significantly ahead of the Kemper.
I came across this post: Why I Bought a Modeling Rig and Why I Didn’t Go Kemper.
Having made the move to in-ear monitors, I don’t miss the “amp in the room” sound. The tones from the Fractal are consistent stage-to-stage relative to an amp, the amp models and effects are pretty easy to tweak and even with some limitations on the CPU, I find that I am so close in tone to what I had been using before with my amps that the few drawbacks are pretty insignificant.
Plus I can carry a guitar, the Fractal and a small gig bag without breaking my back. Setup and teardown is a snap. I don’t worry about tubes going microphonic and I don’t worry about being too loud on stage. I rarely play gigs where I am not being mic’d through a system. And, whenever that does happen, I pull out one of my Swart amps.
I use the Fractal for everything now, even my jazz playing.
It sounds great to my ear and I can take it with me wherever I go.
But I will still keep a couple of tube amps.
Just in case.