As I mentioned in this post, I have finally thrown my Jekyll markdown footnote id plugin up on Github. It’s not much, and I need to package it into a real plugin, but at least it’s there for other folks to use (assuming it’s not just for an audience of 1).
That lead me to find this delightful subreddit that’s all about videos of happy crowds (singing along, going crazy over something). A few hours later I came out of the vortex. 1
It was nice to see a handful of my favorite Virginia Tech moments show up … VT crowds get pretty riled up. And there’s enough English football in there to make it clear to me I need to see a Premier League (or Championship) match sometime soon.
In any event, this brightened up a dreary Monday/2017.
Don’t love linking to reddit, as I find that for every good subreddit, there are 10 that are just mindblowingly awful. But there’s this Happy Crowd one, and this Isolated Vocals one that are really pure joy. ↩
Really great article by Brian Nemhauser on the topic of spending a long time at at tech company. Having just finished up my ~12 year run at a tech company, so much of this resonated with me. In the handful of times I took an interview/phone call in the past 4-5 years, I had to develop an answer to why I had stayed at the same place. My answer was similar to Brian’s—it wasn’t really the same place, nor the same job. I worked at a small startup, a mid-size company, a pre-public company, a public company, and a host of transitions in between.
Change was not something I embraced when my career started, but adaptation and anticipation quickly became second nature. My appetite for change did not come from lack of attachment to Adobe history. To the contrary, it was fueled by a deep loyalty and dedication to our mission built over many years.
One of the things I had to adapt to was that change wasn’t bad. Early on, I had a hammer, and everything was a nail. As a company changes, the logical thing for lots of folks is just to do it the way you’ve always done it. Eventually you realize that you can bring your existing ways with you, but can learn from the changing company (and changing world around you) and embrace that change.
Now I was learning about sales, marketing, finance, human resources, and corporate strategy. It was an MBA-in-a-box.
This is often how I’ve described my time. By being open to change and taking on new things, I worked with so many groups that I might not have had a chance to in a normal tech path. I used to refer to it as my MBA-on-the-job.
Longevity, however, need not equal stagnation. It can mean wisdom, passion, dedication, and sustained peak performance. That is what I see when crossing paths with most of the other marathon runners at Adobe.
Longevity, in and of itself, is not a bad thing. There are certainly employees who find their comfort level and will push back against any changes. Those employees can be toxic, and you need to find a way to help them see the value in growth and change, or find a way to minimize their toxicity. Those long-timers who are adaptable and embrace change, they are your keystones, bridging the past to the present.
It’s a long read, probably about 30 minutes, which is somewhat amusing when you read the first line …
Thirty minutes. That’s about how long it would take a nuclear-tipped intercontinental ballistic missile (ICBM) launched from North Korea to reach Los Angeles. With the powers in Pyongyang working doggedly toward making this possible—building an ICBM and shrinking a nuke to fit on it—analysts now predict that Kim Jong Un will have the capability before Donald Trump completes one four-year term.
For all these reasons, acceptance is how the current crisis should and will most likely play out. No one is going to announce this policy. No president is going to openly acquiesce to Kim’s ownership of a nuclear-tipped ICBM, but just as George W. Bush quietly swallowed Pyongyang’s successful explosion of an atom bomb, and just as Barack Obama met North Korea’s subsequent nuclear tests and missile launches with strategic patience, Trump may well find himself living with something similar. If there were a tolerable alternative, it would long ago have been tried. Sabotage may continue to stall progress, but cannot stop it altogether. Draconian economic pressure, even with China’s help, is also unlikely to curb Pyongyang’s quest.
This is the scenario I have feared with a Trump presidency. Does the President (and his administration) have the stomach to not look “strong” and to continue to sabotage and stall North Korea’s progress until an economic and diplomatic solution are reached? Or will they roll the dice on a riskier alternative?
Those alternatives, as the article lays out, all have high likelihoods of significantly worse outcomes for the Korean peninsula, the US West Coast, and the US at large.
Does the President have the patience to make the right decision, even if it’s the one that is the least flattering personally?
One of the nice things about moving my site to Jekyll is how extensible it is. Everything related to Jekyll (and it’s ecosystem) is open source, so as I’ve come across things that don’t work the way I want, I can change them.
Recently, I noticed that when I used footnotes, they would work on the first post on the home page, and they would work on the individual post pages, but when multiple posts with footnotes were on the home page, the nice footnote popup 1 didn’t work.
The second issue was that, on the home page (or any collection page), the Littlefoot plugin would find all the footnotes, but only hide the first set of plugins. That was something I could actually fix in the plugin. Again, what’s nice about the Ruby/Jekyll ecosystem is that I could fix it, put it up on Github, and then use my fixed version until the fix is taken into the mainline. The code change was pretty simple:
That loops over all the footnote divs, rather than just hiding the first one.
After this was done, it stuck in my craw that I was going to have to remember to be smart about naming my footnote references. I spent a bit of time looking at how to build a jekyll plugin—I figured I could write some code that would loop through the page, find the footnotes, rename them (using some seed data; I chose the filename), and then write them out.
It took me a couple of hours, but I got it working (well, I think). When this post goes up, we’ll see if it all went swimmingly.
Assuming it works as expected, I’ll likely put the plugin up on Github and maybe make it a gem (just for the practice).
If you happened to have caught this post a bit ago, you would have seen some generic content. I was testing how well I could post from the iPad to my Jekyll site. Since I’m using a git deploy mechanism, that means using an app called Working Copy, and some automation via an Editorial workflow.
I based my workflow off the work of Kirby Turner, adopting it to meet my needs. The big difference I have is that I started with an Editorial Document Template1 which creates the framework of the post. I can then write the post, click a button to trigger the workflow, and it’s committed to the git repo locally. Then I pop into Working Copy, double check things, and push the changes to my git repo to trigger the post.
That’s an extra step or two, but it’s actually not bad. It forces me to make sure I’m reviewing things before they go live. Besides, I don’t tend to post a lot of just quick posts, so this isn’t really any different than doing it at my desk.
I probably will start to poke around with another version of this, triggered from the Workflow app (not to be confused with Editorial’s workflows), that maybe will take the most recent photo, create a post, commit it, and ship it up to the site without too much interaction.
I like my iPad being a nearly full fledged computer. If I didn’t use my iPad so much, I’d update to the iOS 11 beta to take advantage of all the new iPad goodness.
The only downside to this is that I don’t think Editorial document templates are sync’d between devices (the way you can sync workflows), which meant I had to rebuild it on my phone. Not the end of the world, but a bit more work than I’d wanted. ↩
There are at least two stories12on major tech sites covering playing old console games.
Nintendo has the rights to many, many of these games (as they’ve released them on various iterations of the Virtual Console). Plus an even bigger backlog of games from various other consoles they’ve licensed (or already own, i.e. the N64).
Nintendo has a major hit with the Switch. It’s portable and a home console. They’ll likely have sold upwards of 10 million Switches by the end of the year.
Just charge us $5-10 a month for an on-demand virtual console service. Even at $50 a year, I would expect that, even very conservatively, 10% of Switch owners would pay. That’s $50,000,000, or about a 1% increase in Nintendo’s revenue.
(Now, assume a more likely 25-50% attach rate, and you’re talking potentially a 5% increase.)
I’m sure there’s digital licensing issues, i.e. the deals they have with the various game companies covers certain types of digital distribution, but not others. Maybe Konami is going to want a slice of the pie for every subscription. But then there’s the Spotify/Apple Music model here; give the producers a tiny cut of each subscription (since they’re used to help the marketing), and then slice them off royalties when games are played.
There’s free money sitting on the table, and the sooner the game companies realize it’s from the streaming(-ish) model, and not from the “let’s package up Sonic for the 10th time and sell another full game”, the sooner they get to make money off of all of their legacy IP.
Nintendo (and, probably Sony and Microsoft, but Nintendo more than most because of their classic IP) literally has a mint sitting in front of them, waiting to start filling their pockets with new money as soon as they are willing to. Striking now, while they have a system that is still hot, would let them capitalize and make the Switch into an evergreen system.
Alfred 3.4 was just released and the snippets functionality is improved enough that I can retire TextExpander from daily use. There are still a handful of snippet features that TextExpander does better than Alfred, but when I looked through the snippets I used, I was more than covered with Alfred’s functionality. Alfred also seemed to handle the replacements faster than TextExpander did.
While I’m transitioning between roles, I’m spending a little bit of time paying attention to how I use my computer, where things can be optimized, what I need/don’t need. Moving to Jekyll was one of those things. I’m now looking at the various workflows I can simplify with Alfred.
If you don’t use Alfred, it’s worth picking it up.
“I am going to take care of everybody. I don’t care if it costs me votes or not. Everybody’s going to be taken care of much better than they’re taken care of now”
— Donald Trump 1
Both the House and Senate Health Care bills destroy health care for the poor and elderly.
More moderate Republican senators, such as Dean Heller of Nevada, expressed their own qualms, as did the American Hospital Association, the American Cancer Society Cancer Action Network and the Association of American Medical Colleges.
“We are extremely disappointed by the Senate bill released today,” the medical school association wrote. “Despite promises to the contrary, it will leave millions of people without health coverage, and others with only bare bones plans that will be insufficient to properly address their needs.”
Make it difficult for millions of people to get affordable health care. That’s definitely better that what we have today.
Some senators have concerns based on other issues specific to their states, including the opioid epidemic that has battered states like West Virginia and Ohio.
You know which single health care insurer covers the most opioid treatments? Medicaid.
State with the largest number of opioid deaths? West Virginia.
Percentage of population on Medicaid? 30%.
State with the third largest number of opioid deaths? Kentucky. Percentage of population on Medicaid? 28%.
State with the next largest number of opioid deaths? Ohio. Percentage of population on Medicaid? 25%.
Once again, this is clearly better than what we have now.
It would also repeal most of the tax increases imposed by the Affordable Care Act — a capital gains tax cut for the affluent would be retroactive for this year — to pay for expanded coverage, in effect handing a broad tax cut to the affluent in a measure that would also slice billions of dollars from Medicaid, a health care program that serves one in five Americans, not only the poor but almost two-thirds of people in nursing homes.
The poor and elderly getting kicked so that the rich can have a tax break. All negotiated in secret by a small committee of 13 white men and lobbyists.
Better for everybody is what that group has in mind.
Who benefits? It’s all about the tax cuts, almost half of which will go to people with incomes over $1 million, the great bulk to people with incomes over 200K.
So, is this bill good for you? Yes, if you meet the following criteria:
1.Your income is more than $200,000 a year
2.You have a job that comes with good health insurance
3.You can’t imagine any circumstances under which you lose that > job or income
4.You don’t have any family members or friends who don’t meet those criteria
5.You have zero empathy for anyone else
— Paul Krugman, June 23, 2017 2
Think what you want about Krugman, but he’s not wrong. This isn’t about health care. It’s about tax cuts for the wealthy. It’s perfectly fine if, as a citizen or representative, you want to argue that this is the right thing.
But don’t try to package it up in fixing health care.
And don’t try to sell it as taking better care of everybody.
It’s been a couple of weeks since WWDC
wrapped up and there’s a couple of things that stuck out
that I found interesting.
All the iPad Stuff
I’ve written a bunch about the iPad.
I really love and get a ton of use out of my iPad, to
the point that it’s my travel machine. The limitation
has always been that you can’t get “real” work done
without jumping through hoops. Real(er) multitasking, drag
and drop, and the new iPad Pro are all steps towards
the iPad’s ultimate destiny: a daily computer for the
vast majority of people. I could probably do 90% of my
work off of an iPad at this point, but it’s a bit
painful. With iOS 11, it looks like it will be a lot
iOS 11 and High Sierra (and Siri)
Setting aside the dumb name of High Sierra, both new
OSes seem like reasonable advances. There’s a few
little things in each (new Control Center, APFS, all
the machine learning libraries) are really nice
evolutions from iOS 10.
The small improvements to Siri (although the Omnifocus
integrations are going to be awesome) are worrying.
I actually think Siri is decent (and has gotten
considerably better in the past 18 months), but there’s
still far too much that can’t be done with Siri.
Apple needs to find a way to advance the ball faster.1
Once again, setting aside the dumb name2 I’m
cautiously optimistic about the HomePod. We have a
handful of Sonos speakers in our living room, and
we love them. I use them all the time. However,
the lack of voice control and native Airplay3means they take a bit more thinking to use. So,
even though we have these big, powerful speakers
sitting there, my wife uses her phone to listen to
It drives me batty.
So, a HomePod, with Airplay (well, Airplay 2), that
my wife can tell to play whatever music she wants,
plus HomeKit integration (we’ve got a bunch of HomeKit
devices), and some Siri integration, works for us.
We have an Echo Dot, which is handy for things like
checking the weather and random facts, but we don’t
use it to do much more than that. The HomePod should
easily be able to replace that, plus native integrations
with calendars, reminders, etc., probably fit in our
life better than the Alexa device does.
The downside: it’s expensive. Like more expensive than
getting another Sonos speaker expensive. Won’t have more
than one in the house expensive.
The price will probably come down over time, and it’s
capabilities will get better (presumably), so I’m hopeful
this is the smart speaker that will fit best into our home.