Back in 2015, I created a set of 5120×2880 deep space desktop images for my then-newish Retina iMac, using images from the Hubble space telescope.
Recently, the Hubble team released the absolutely mind-bogglingly-massive Hubble Legacy Field image…
The snapshot, a combination of nearly 7,500 separate Hubble exposures, represents 16 years’ worth of observations. The ambitious endeavor is called the Hubble Legacy Field. The new view contains about 30 times as many galaxies as in the HUDF. The wavelength range stretches from ultraviolet to near-infrared light, capturing all the features of galaxy assembly over time.
The image mosaic presents a wide portrait of the distant universe and contains roughly 265,000 galaxies. They stretch back through 13.3 billion years of time to just 500 million years after the universe’s birth in the big bang.
Despite those staggering figures, this image still represents only a tiny portion of the sky, covering roughly the area taken up by the Moon in the night sky.
I downloaded the 700MB 25,500×25,500 PNG version of the image, and set to work making some new 5120×2880 desktop images. You can read more about the process in an upcoming post, but for now, here are the resulting images…
If you weren’t reading along this week, I spent the last four days—parts one, two, three, and four—talking about my Tesla Model S and how much I love it.
Today’s surprise ending is this: I sold the car. What I’d replace it with? This…
Obviously that’s another Tesla Model S—a used Model S. It is, in fact, a 2016 Models S 90D—yes, basically the exact car I had, but not really—more on that in a bit. My wife and I call it the unicorn car; read on to understand why, and why I made this trade. (As I was writing this, I learned that others had already used that phrase for this particular vintage of the Model S.)
This is Part Four of a four-part series on our 2016 Tesla Model S. In Part One, I covered why we chose the Model S, the cost of the car, and a bit about Tesla the company. In Part Two, I listed some of the things I love about the car. In Part Three, I listed more of the things I love, plus those things I hate. In today’s Part Four, I’ll discuss what it’s like living with an electric car, cover a somewhat long road trip I took last fall, and offer a few thoughts on the future of auto electrification. Finally, tomorrow’s Part Five will provide an unexpected ending (of sorts) to the series.
Living with an electric car
My two-plus years with an electric car have been basically a non-event. There are many reasons for this, including the fact that I work at home, and that we have non-electric vehicles, so the Tesla doesn’t have to do everything. (But even if I commuted, with the car’s range of 280 miles, I think it’d still be a non-event.)
This is Part Three of a five-part series on our Tesla Model S. In Part One, I covered why we chose the Model S, the cost of the car, and a bit about Tesla the company. In Part Two, I listed some of the things I love about the car; today’s Part Three has more of the loves, as well as the not-so-loves. Part Four will discuss what it’s like living with an electric car, and my thoughts on the future of auto electrification. Finally, Part Five will provide an unexpected ending (of sorts) to the series.
Continuing with the things I love about the car and its infrastructure, and then getting to the not-so-loved things…
This is Part Two of a five-part series on our Tesla Model S. In Part One, I covered why we chose the Model S, the cost of the car, and a bit about Tesla the company. In today’s Part Two, I’ll discuss some of the things I love about the car; Part Three will have more of the loves, as well as the not-so-loves. Part Four will discuss what it’s like living with an electric car, and my thoughts on the future of auto electrification. Finally, Part Five will provide an unexpected ending (of sorts) to the series.
What I love about the car
Everything. OK, that’s not true. But there is a huge list of stuff that—even after nearly three years—helps make any drive in the Tesla an enjoyable experience. The list is generally ranked by order of importance to me, though a lot of these would be ties if I had to absolutely rank them. Most of these things are particular to Tesla’s cars (and some to the Model S in particular), though a couple are generally true of any electric vehicle.
Coming up on three years ago, in June of 2016, I replaced my Subaru Legacy with an electric car. Not just any electric car, but a Tesla. Our Tesla is a 2016 “original nose” Model S 90D, which roughly translates to “a very expensive, quite large four-door sedan with about 290 miles of range, all-wheel drive, propelled by a couple of powerful electric motors.” This is not only the most expensive car—by far—we’ve ever owned, but (spoiler alert) it’s the best car we’ve ever owned.
I’ve been writing this post—off and on—almost since the day we bought the car. So why has it taken so long to publish?
We presently own three Samsung appliances: The 8700 series washer and dryer, and a French door freezer-on-bottom refrigerator. I can say with complete confidence that these are the last three Samsung appliances we will ever own.
Granted, none are brand new—the fridge was bought in 2012, and the washer/dryer pair in 2015. But that’s not old in the world of appliances. And while you might expect a few minor issues as appliances age, we’ve recently had two major things pop up: One in the washer, one in the fridge. What bugs me most is not that these issues occurred, but that they are apparently very well known to Samsung, and yet they’ve done very little in the way of making owners aware of and/or fixing the problems.
2019 update: I’ve uploaded new files (in one zip archive this time) with a few changes and fixes. These files are also set up as “master” files: The idea is you duplicate one, rename it for the current year, then use it. When the next year rolls around, repeat the process. This way, you don’t have to use the macro-enabled version to delete data at each new year. Download the new files.
About two years ago, I created a basic-but-functional run tracking workbook (created in Excel). It worked well, and helped me through my 2,016 mile year in 2016. I didn’t run nearly as much in 2017 (on purpose), but 2018 is upon us, and I’m going to up my mileage this year—probably not to 2,018, though!
In preparing this year’s version of the workbook, I addressed a few things that bugged me about the first one: It was ugly, changing years was difficult, and it was ugly. It was also really ugly. Did I mention it was ugly? Anyway, here’s what I’ve changed with the new version:
- Years are now easily handled; just input the year you wish to track, and the workbook does the rest, including leap years.
- All run data can be deleted with one button click—and yes, there’s a confirmation first. (Requires macro version of workbook.)
- The pace calculator is no longer a separate worksheet; it’s integrated into the Overall worksheet.
- It’s not nearly as ugly as it was before—layout is improved, gridlines are gone, tables are cleaned up, etc.
As noted, there are two versions of the workbook—one contains a macro that can erase the run data from each monthly worksheet, the other does not contain that macro. This is something you’ll only do once a year, but it’s much easier with the macro version.
Growing up, around the holidays my mom would bake something we called Monkey Bread. If you search the net for Monkey Bread recipes, what you’ll find is a number of dessert-like breads, covered in a sticky brown sugar (or other sweet) coating. Those are not the Monkey Bread my mother made—hers was more of a “regular” bread (containing just 1/4 cup of sugar) that you can eat with your meal.
What makes the bread unique—and fun to eat—is that it’s assembled from small pieces, which you then tear off and eat.
Although I bake Christmas cookies and occasional other stuff, I’d never tried her Monkey Bread recipe. But for this year’s New Year’s Eve party/potluck, I thought I’d give it a shot…and after a couple false starts, I managed to get one done…
As noted, that was not my first attempt. I left the egg out of my first batch (whoops), and missed a whole cup of flour (whoops again) on my second try. But in the end, it came out great, and was well liked at the party.
Note: Revised on December 4, 2018 with a much better implementation of the pop-up palette, and some changes in timing and mouse movement.
One of the “problems” with Keyboard Maestro is that it’s so useful I use it a lot, leading to a large collection of macros. Due to the number of macros, sometimes when I want to add a new shortcut, I can’t remember if I’ve used that shortcut before or not. Today’s tip comes in two flavors to address that problem: Simple and Complex.
The Simple solution
Short of just trying the shortcut, there’s a way to check from within Keyboard Maestro itself: Type the macro’s activation keys into the search box, as seen in the box at right.
You can’t do this by pressing the actual shortcut keys—you have to type their character representations. You can do this with the “Show Emoji & Symbols” option under the flag icon in the menu bar, if you’ve enabled it in the Keyboard System Preferences panel. But finding those few special keys (if you even know how to search for them) is a pain.
Technically, you could also use the pop-up character palette macro I wrote, except there’s an issue: When the palette activates, it deactivates the search box, so the characters don’t make it there. It’s also overkill for this task, because there are characters that wouldn’t be part of keyboard shortcuts, and you’d never need the HTML codes, just the characters.
So I wrote what wound up being a set of new macros that make searching for assigned keyboard shortcuts much easier.