If the Kanye West–Donald Trump crazyfest didn't do it for you, there are plenty of other things to take a look at this lunchtime:
That's all for now. Enough crazy for one Friday.
Oh, Sears. You've come to represent much that is wrong with American corporate culture, especially a CEO who embodies the Dunning-Krueger Effect with every syllable he utters.
Crain's Joe Cahill argues that Eddie Lampert, while Sears' proximate cause of death, didn't act alone in its murder:
There's no denying the hedge fund mogul who thought he knew more about retailing than the retailers made critical errors that turned Sears' struggles into an inexorable decline. But Sears started down the wrong path long before Lampert appeared. And its sad fate isn't so much a story of operational missteps as one of missed opportunity. In short, Sears chose to imitate Walmart when it should have tried to pre-empt Amazon.
Like so many established companies threatened by newcomers with innovative business models, Hoffman Estates-based Sears tried to beat the interlopers at their own game, rather than looking ahead to the next big thing. The company that recognized the potential of railroads to support a nationwide retail operation and foresaw that postwar suburban sprawl and shopping malls would redefine retailing for a new generation failed to appreciate the implications of internet technology for the industry it dominated for more than a century.
As for Lampert, he showed no better vision than his predecessors. When he took control of Sears by merging it with Kmart, the combined company still had an opportunity to carve out a strong presence in e-commerce. Amazon had already emerged as the leading internet retailer, but with $8.49 billion in 2005 revenue, it was one-sixth the size of Sears, and barely profitable.
Meanwhile, two other Crain's stories outline the thousands of other victims of this crime: the company's pensioners and all of the malls about to lose their anchor tenants.
Press reports reckon the company has less than 48 hours to live.
I started reading Jessica Powell's online novel The Big Disruption last week. It's hilarious. And it has a lot to say about the archetypes of software development.
The premise is that the monarch of a fictional country has been exiled to California, where he found work first as a janitor at Stanford and then at a hot startup. He applies to a Google-like company and gets hired—but by accident, as a product manager.
Arsyen washed his hands and returned to the cubicle, armed with his new vocabulary.
When Roni asked Arsyen about prioritization, Arsyen asked, “Is this on the roadmap?”
When Sven suggested adding images of attractive women to the car dashboard, Arsyen rubbed his chin.
“Does this align with our strategy?”
When all three looked to him for an opinion in how best to implement Symmetry Enhancement, Arsyen stood and put his hands on his hips.
“Does this align with the strategy on our roadmap?”
No one seemed to notice anything was amiss. If anything, it seemed like product managers just asked questions that other people had to answer.
“Good brainstorm, everyone. Let’s break for lunch,” Roni said. “Oh, and Arsyen, this is still very confidential, so let’s get this whiteboard cleaned off.”
Arsyen jumped up and began to wipe the whiteboard clean as Sven and Jonas scooted their chairs back to their desks. Arsyen was pleased that product managers seemed to have some janitorial tasks in their role. Maybe this wouldn’t be such a stretch after all.
I can't read it at work because I would have to explain why I'm laughing so hard.
As in, "nice work, Dutch military, for unraveling a GRU operation and blowing 300 GRU agents worldwide:"
Dutch authorities have photographs of four Russian military intelligence (GRU) operatives arriving at the Amsterdam airport last April, escorted by a member of the Russian embassy. They have copies of the men’s passports — two of them with serial numbers one digit apart. Because they caught them, red-handed, inside a car parked beside the Organization for the Prohibition of Chemical Weapons in The Hague — the GRU team was trying to hack into the OPCW WiFi system — Dutch authorities also confiscated multiple phones, antennae and laptop computers.
On Thursday, the Dutch defense minister presented this plethora of documents, scans, photographs and screenshots on large slides at a lengthy news conference. Within seconds, the images spread around the world. Within hours, Bellingcat, the independent research group that pioneered the new science of open source investigation, had checked the men’s names against several open Russian databases. Among other things, it emerged that, in 2011, one of them was listed as the owner of a Lada (model number VAZ 21093) registered at 20 Komsomolsky Prospekt, the address of the GRU. While they were at it, Bellingcat also unearthed an additional 305 people — names, birthdates, passport numbers — who had registered cars to that very same address. It may be the largest security breach the GRU has ever experienced.
That's a great way to fight back: exposure. This is an example of the integrity and ingenuity which almost led to the Dutch controlling the world instead of the British way back when.
This week, I got an email from the SEO coordinator at Alaska Airlines:
My name is Shawn with Alaska Airlines. I'm reaching out concerning a specific link on blog.braverman.org. As you may have heard, Alaska Airlines acquired Virgin America last year. We are in the process of updating all Virgin America links to go directly to our website, https://www.alaskaair.com.
We want to make sure your readers are being sent to the correct place!
We would really appreciate it if you could update the link and anchor text, Virgin America, on this page: http://blog.braverman.org/2009/09/default to:https://www.alaskaair.com and Alaska Airlines.
Please let me know if you have any questions.
If you're not the appropriate person to contact about this, can you put me in contact with the right person?
(The actual post he meant me to change is here.)
See, Alaska took over Virgin America, and now they want to scrub the Internet of all references to the old airline. I politely told Shawn that, no, I was not about to change a 9-year-old blog post to send Virgin down the memory hole.
He replied that he understood, but could I just change the URL to point to Alaska Air at least?
No, Shawn. I'm not editing the post, full stop. It reflects the state of the world in 2009, and to me, it's a document that needs to remain unaltered.
I'm sure the SEO coordinator of an airline believes that it's a doubleplusgood thing to help people who may inadvertently discover a blog post from 2009 not get misdirected. But the whole thing really creeped me out. Alaska or one of its vendors had to go through every one of the over 6,500 posts I've written looking for references to Virgin America, and then Shawn had to field my response to his (no doubt automated) email request. That's a lot of effort to pretend Virgin America never existed.
Did I mention Virgin America Airlines? Just making sure.
Lots of stuff crossed my inbox this morning:
Back to my wonderful, happy software debugging adventure.
Via Raymond Chen, Eric Shlaepfer built a 6502 emulator out of full-size components:
The MOnSter 6502
A dis-integrated circuit project to make a complete, working transistor-scale replica of the classic MOS 6502 microprocessor.
How big is it?
It's a four layer circuit board, 12 × 15 inches, 0.1 inches thick, with surface mount components on both sides.
Can you hook it up inside an Apple ][ and run Oregon Trail?
No, not directly. It's neat to think of plugging the MOnSter 6502's in-circuit emulator (ICE) in-circuit replica (ICR) cable directly into a socket inside an Apple ][, but that wouldn't actually work. The Apple ][ design relies on a number of clever tricks that derive timing for video generation and peripheral control from the main clock signal — all of which will fail if you need to run at a slower speed.
Are you going to make one out of vacuum tubes next?
Make sure you watch the 2-minute video.
Before diving back into one of the most abominable wrecks of a software application I've seen in years, I've lined up some stuff to read when I need to take a break:
OK. Firing up Visual Studio, reaching for the Valium...
While trying to debug an ancient application that has been the undoing of just about everyone on my team, I've put these articles aside for later:
Back to the mouldering pile of fetid dingo kidneys that is this application...
Just an historical note: as of today, I've been working with Microsoft .NET for 17 years. The first time I picked it up was 10 September 2001, which, if you think about it, is a very easy date to remember.