Rupert Murdoch Takes Over National Geographic, Then Lays Off Award-Winning Staff

ReverbPress, on the National Geographic takeover:

The memo went out, and November 3rd 2015 came to the National Geographic office. This was the day in which Rupert Murdoch’s 21st Century Fox took over National Geographic. The management of National Geographic sent out an email telling its staff, all of its staff, all to report to their headquarters, and wait by their phones. This pulled back every person who was in the field, every photographer, every reporter, even those on vacation had to show up on this fateful day.

As these phones rang, one by one National Geographic let go the award-winning staff, and the venerable institution was no more.

While I’ve never been an avid reader of National Geographic, it has always felt like a staple in the world. I remember flipping through their magazines (in paper!) back in my high school library.

I truly hope that this doesn’t spell the end of the National Geographic as we know it. Like ReverbPress, I can’t help but be worried.

Hyundai will launch Genesis brand in December

Autoblog:

Hyundai is about to go global with a new, high-end sub-brand called Genesis. Rumors of this spinoff have been swirling for years, but an announcement Tuesday confirms that the Genesis brand will launch in December of this year.

It isn’t too often in the automotive world that a new brand is created. It’s particularly impressive to think of how far Hyundai has come: previously cheap and poor quality, now launching their own luxury brand.

While I’ve never driven a Hyundai, many people in my family own one and love it. Since the Genesis model was created, I’ve been impressed by their styling. Congratulations, Hyundai.

Daytime Running Lights

One of the biggest changes on the road for me, after moving from Canada to the US, has been the lack of daytime runing lights (DRL). In Canada and much of Europe, all vehicles are required by law to have functioning daytime running lights, whereas in the US they are merely permitted.

For those who don’t know, daytime running lights are clear or amber lights on a vehicle that are on whenever that vehicle is moving, regardless of time of day.

As a driver, I firmly believe that daytime running lights should be mandated in the US, and all countries around the world. The few possible negative effects are easily avoided, while the benefits are numerous and improve road safety for everyone.

To start, let’s look at headlights, which are better understood. Headlights serve two purposes at night:

  1. Illuminate the road ahead (and to the side to a small degree)
  2. Make your vehicle visible to others

It is the second purpose that is most frequently overlooked, and where DRL shine (pun intended). In any condition where road illumination isn’t necessary but visibility is restricted, DRL are always on, eliminating user error. These situations include rain, dawn, dusk, fog, dust and more.

Daytime running lights also provide guaranteed lighting at night, should someone forget to turn their headlights on. While automatic headlights solve this issue, many vehicles are still sold without. Multiple times since being in the US I have come close to turning in front of a car that didn’t have their headlights on at night, which prevented me from seeing them until they were much closer.

The primary arguments against daytime running lights revolve around them being too bright. If they are too bright they can cause glare and/or obscure a vehicle’s turn signals. These are valid concerns, but are easily remedied: mandate that DRL run at a lower intensity than regular headlights, which is exactly what Canada has done.

The National Highway and Traffice Safety Association (NHTSA) has performed multiple studies over the years showing no or minimal safety benefits from having daytime running lights. As a driver, I know the safety benefits I have seen on the road, as well as the level of comfort daytime running lights provide, knowing that I can see other cars on the road.

Microsoft and Red Hat partner to deliver more flexibility and choice

Scott Guthrie, Executive Vice President of the Cloud and Enterprise Group at Microsoft, on the new partnership with Red Hat:

The partnership we are announcing today with Red Hat extends our commitment to offer unmatched choice and flexibility in an enterprise-grade cloud experience across the hybrid cloud. With more than 80 percent of the Fortune 500 using Microsoft’s cloud, for us to team with the leader in enterprise Linux allows even more businesses to move to the cloud on their terms. By working with Red Hat, we will address common enterprise, ISV and developer needs for building, deploying and managing applications on Red Hat software across private and public clouds...

I like the new, more open Microsoft and its willingness to partner with other technology companies. This cooperation will help make the technology world a better place for all involved by utilizing the strengths of both companies.

Opt Outside with REI

This Black Friday, I’ll be Opting Outside with REI. Where will you be?

On Black Friday I'll be hiking \#optoutside

Social Anxiety

Brent Simmons, on social interactions as an introvert:

If you speak a sentence to me, I hear a paragraph. If you speak a paragraph, I hear your life story.

...But if you raise your hand for a high-five, or hold out a fist for a bump, it won’t even occur to me to wonder why you’re doing those things. You’re just doing those things. Why would there be a reason?

For years I’ve been searching for how to explain why I have social anxiety, why social interactions are so exhausting. Brent’s experiences match mine to a tee.

I wonder if all I’ve done here is to describe why introverts frequently describe being social as tiring.

That you have, Brent. That you have.

Starting Fresh

Moved to a new city.

Started a new job.

Joined a club.

Made new friends.

Rebuilt a website.

We can all use a fresh start sometimes. Welcome to the new Colin C. Williams.

mvim Bash Error — bad interpreter: Operation not permitted

Yesterday I reformatted my computer as it was starting to slow down. RAM and CPU usage was consistently higher than normal. Things just felt sluggish.

When I do a reformat like this, I ensure it is clean. This means that I only copy irreplaceable items from my backup, such as documents and pictures, but all of my applications I re-download and install from either the Mac App Store or their respective websites.

One key application I have been using a lot lately is MacVim. While useful on its own, it also comes with a BASH script for opening files in MacVim from the command line, called mvim.

As usual, I moved mvim to the bin directory in my home folder and ran it to see if it worked, only to receive the following error:

-bash: /Users/colincwilliams/bin/mvim: /bin/sh: bad interpreter: Operation not permitted

This was surprising as, on my previous install, mvim worked just fine from the get-go.

After some searching I noticed similar errors people had from other scripts. One of the common causes was incorrect line endings for the system: Windows is different than Mac OS is different than Unix. I won’t delve into the differences here, but you can read more about them in the Common Problems section of the Wikipedia Article.

On OS X, the simplest fix for this that I could think of was using Bare Bones Software’s TextWrangler1.

To do this, open mvim in TextWrangler and in the menus select Text > Normalize Line Endings. Save the file and try executing mvim again. It should work just fine this time, opening a document in MacVim as expected.


  1. A great text editor to always have on hand. ↩︎

Photos

Some of you may have noticed a new section in my navigation bar. That’s right folks, I’ve officially added a Photos Section!

For a while I’ve had a casual interest in photography, but haven’t been able to invest a proper amount of time into learning. Since I got my iPhone 4, I’ve been trying to take more photos as I always have a camera with me and it’s not half bad!

To help with organizing and sharing my photos, I’ve been using Instagram. So, since all of the photos I take are on my iPhone, and the ones I deem good enough to share on Instagram are the ones I want people to see, I’m simply showing those on this site.

As for the styling, I decided to break the mold of the rest of the site a bit. Everything else has a pure white background and, while I do like it for text, I don’t think it suites photos very well. I find that the photos got lost in the background. On black, however, I find that the photos really “pop”, or stand out.

Satisfactory is Worse Than Not At All

Upon purchasing a product, the user has implicitly placed their trust in you and your company. They trust that you are going to provide them with an excellent, if not outstanding experience — that you made the tough decisions about how that product should look, feel and behave.

This trust can also be found for each feature. The act of including a feature, no matter how small or large, gives the impression that it’s exceptional and something to be proud of.

Herein lies the issue. If including a feature sets the expectations so high, the user is disappointed if the experience is merely satisfactory. In addition, a feature’s existence prompts its use, so users become repeatedly frustrated.

What if you ship a feature only when it meets the expectations of the user, or even exceeds them? While the feature is being refined, the user can only set the same expectations as if it were included, as that is what they are able to imagine. When the feature ships, they will be delighted that the experience is so wonderful. While waiting, they will desire the feature, but not be directly frustrated because of it.

As an example, my Android phone supported copy/paste when I purchased it. However, only some apps supported the functionality and, when I could use it, it was horrible. Text selection was extremely difficult and I usually used a different solution in the end, but I would always try copy/paste first since it was available. This contributed in no small part to my overall frustration with the product and lead to me leaving the platform. Since then this feature on Android has been overhauled to be far easier to use and work consistently across apps.

Contrast that with iOS and when copy/paste was implemented. It received copy/paste later than Android (over two years after the iPhone’s initial release), yet hasn’t been largely modified in the three years since. Every time I utilize copy/paste on my iPhone, I barely notice it as it works so well and it worked in all apps immediately.

Had my Android not had copy/paste in the first place, I would have always resorted to the alternatives and not had the chance to become frustrated. I may have desired for it to be implemented, but frustration is far worse than desire.

As a user of many products in my life I would appreciate if more companies would refrain from releasing features until they are exceptional.