I spent some time remodeling the old digs here, adding a fresh coat of paint in the form of a new theme, new hosting, and a shiny new SSL lock.

The new paint comes in the form of the Swiss Jekyll Theme, which I just thought looked like fun while keeping the site readable. The only configuration I did was to switch the theme color to orange, just to brighten things up a bit. And I like orange. I decided a while back that designing my own theme comes at the price of me not writing as much, because I tend to spend too much time tweaking the theme. Now, I search around and browse through twenty or thirty themes till I find a few that I like, then I download each of them and drop my content in them, run the site locally and see how my posts look. Most of the time I just go with my gut… do I feel happy when I look at the site? If not, I move on. For now, I’m happy with how this looks.

I was inspired by Jack Baty’s post on moving to Amazon to migrate my own blog over to S3 and CloudFront. I love that the SSL comes along for the ride. Although I don’t need it for anything here, at least Chrome users won’t be subject to a warning when visiting my site. I remember advocating for doing this back in 2002 in a paper I wrote for college, encrypt everything.

Apart from that, the site is still my outlet for talking about technology, design, and culture. It’s a place for me to own my words, and hopefully say something useful. Maybe, someday years from now, my kids or my grandkids will find this and have some idea of who I was, and what I stood for.

Sometimes it’s a miracle the Internet works at all. For the past week or so I’ve been unable to clone, pull from, or push to private Git repositories from either Bitbucket or Github using the normal git clone git@bitbucket.org:whatever/whatevs.git syntax. The problem had the symptoms of a blocked port or a bad network route; I’d issue the command in Terminal and wait, and wait, and wait, and the command would eventually timeout. After a quick look at the Github documentation I tried ssh -T git@github.com which also timed out and confirmed my suspicions. The ssh protocol was not getting through, but VPN and normal web traffic was.

My first thought was that the issue was probably related to my new Mediacom modem. For my wife’s sake, we recently went back to cable, and when the installer came out to the house he replaced my modem with a newer, fancier one. I don’t think I needed the upgrade, although my speed has been bumped up a bit since the new one was put in, so whatever. Along with the new modem the installer was insisting on setting up “home networking”, which is Mediacom’s way of charging you to use their crappy wireless built into the modem. I explained to the installer that not only do I not need his assistance setting up my network, but that I also have invested in a very nice Eero mesh networking setup that was far better than anything Mediacom could give me.

This resulted in a few phone calls between the installer and his supervisor. The installer informed me that he couldn’t turn off home networking or I’d be charged an additional $40 per month. That seemed ridiculous to me, but again, whatever, I asked the installer to just make sure my wireless worked the way it did before he came out. He obliged, my speed was good, and he finished setting up cable and left.

It wasn’t for a day or two that I noticed the ssh problem. It was easy enough to verify that the issue was isolated to my home network using the Instant Hotspot ability of my iPhone. I verified that ssh to my repositories still worked over cellular, and decided to get in touch with Mediacom. But, knowing what I know of them, I figured I’d better cover all my bases and also get in touch with Eero.

I thought I might need to talk to them because I have “Advanced Security” turned on in Eero Plus. This, among other things, checks outbound traffic for known malicious destinations and blocks it. I wondered if it might mistakenly be blocking my SSH traffic, but after contacting Eero support on Twitter they verified that was not the case. They did however point to what proved to be the problem. Eero advised me to contact Mediacom and make sure that the modem was in bridge mode and that we were not in a double-NAT setup. After checking my Eero’s networking settings I saw that it had a private IP address and knew that had to be the case.

Then I waited a week to get in touch with Mediacom because I figured explaining all this to tech support would be a nightmare.

Turns out, it wasn’t so bad. The first person I talked to had no idea what was going on and sent me over to “Tier 2”. Tier 2 helpfully explained that they do not offer ssh service, which I was fine with because I didn’t want to ssh to Mediacom. Then my call was disconnected while I was on hold, so I called back. The third person I talked to understood exactly what I needed. He was able to turn off the wireless networking on my modem, switch it over to be just a basic modem, reboot it, and just like that outbound ssh worked again. The first two support representatives met my expectations, the third exceeded them. I should probably have higher expectations for Mediacom, but here we are.

I’m glad to have everything working again. Not being able to clone repositories using the standard git+ssh protocol was really cramping my style. Hopefully I won’t have to change anything about this setup I’ve got now for a few more years. I suppose the next thing I look into will probably be ipv6.

Dropbox apparently saved a boatload of money by moving their infrastructure off of AWS and building out their own data centers. Taken at face value this might seem like a strike against AWS, but the way I see it this was the only way Dropbox was going to be able to differentiate themselves as a service. Their job is to provide cloud storage, something AWS can do easily, but if that’s the only thing you are getting from AWS, it’s going to cost an arm and a leg. This news once again got me thinking about the industry as a whole, my place in it, and how I think about cloud services.

If you’ve been in the technology industry for a while it’s easy to think about cloud services like AWS as just another data center. A place where you can spin up a new virtual machine and manage your server instance just like you would if you were racking hardware or using VMWare. AWS will happily let you do that, but you’ll be missing out on the advantages that thinking about the cloud as a development platform offers.

The biggest innovation from AWS is that you only ever pay for what you use. Compare this with managing a data center, where you have to purchase enough hardware to handle peak utilization for the next several years, and then watch as your investment sits mostly underutilized for most of the time. You also have to make an educated guess about expansion for the next few years. Did you buy enough storage? How about memory? Will you need to purchase more in the future? How much of an interruption will that be if you do? Cloud services take care of all of that by only providing what’s needed when you need it, as long as you take advantage of what the platform offers. 

Over the years I’ve noticed a trend towards more simplification in the systems that I build and design. In general, the fewer moving parts in a system the better. It will be more reliable, and easier to troubleshoot when something does go wrong. Unfortunately, I’ve also watched as the industry went in the opposite direction, building card houses out of frameworks and management systems barely out of their infancy. It may be that I’m jaded by my experience, or it may be that I’m just a grumpy old man, but whenever I hear about someone building out a Kubernates infrastructure to run their Docker containers in the cloud I get the suspicion that someone along the way got a case of the clevers¹. Is that necessary? Is it really?

I should specify that the fewer moving parts in my part of the systems I build the better. Amazon, Google, and Microsoft undoubtedly have several layers of gears running their underlying systems, but the trick here is that they use those same layers for thousands of customers running millions of workloads. For example, my favored system uses very small instances in an autoscaling group to automatically add and remove capacity as needed to reflect the ebb and flow of normal business traffic. If sales sends out a big promotional email, the system will recognize the increase in traffic and spin up enough instances behind the load balancer to be able to handle it. When traffic dies back down, the system terminates the additional instances. All transparently behind the scenes. The configuration for the build is simple enough, and the documentation for what each component does is straight-forward. What’s more, Amazon themselves use the same systems to build out higher level services.

Growing your instance size or changing it’s type is also a simple matter. If the base size is too small or too big, a simple adjustment to the CloudFormation template will automatically create a new instance, deploy the latest revision to the application to it, and shut down the old one. Building on the massive scale of AWS, it’s virtually guaranteed that you’ll never run out of resources. Also, unlike hardware in a data center, Amazon’s instances tend to get both faster and less expensive with each new release. Simply upgrading your instance type can save time and money.

For a lot of business out there that aren’t Dropbox, AWS can provide you a path to simplification of your infrastructure where you can build up secure, scaleable, and cost effective environment. If this sounds appealing, but you need someone to handle the complexity for you, get in touch, maybe we should talk.

I’ve heard several people on podcasts or blog posts claim that they’d like to see Apple hold off on new features that nobody wants and just fix the existing bugs in the Mac. This claim is normally followed up with a missive that they can’t imagine what Apple could add to the Mac at this point anyway, since macOS is a stable, mature operating system. Well, I can think of a few things.

Let’s start with the Mac’s management of information. There is, supposedly, artificial intelligence baked into the Mac in the form of Siri, an AI assistant that is supposed to be able to answer questions and perform basic tasks. Basic, as in “far too basic”. I’ve yet to find a way that the AI actually helps me get anything done. Siri has hooks into all of the built-in apps that manage my information: Notes, Contacts, Reminders, Calendar, Mail, Spotlight, and the file system, but doesn’t help me find relevant information unless I specifically ask her for it. What if Siri could suggest additionally relevant information with a simple swipe of the trackpad? The “Today” view in the Mac’s right-hand sidebar would be a perfect place to show relevant files, folders, emails, contacts, notes, or tasks based on textual analysis and AI.

If you have an email selected in Mail, you could swipe over from the right and see a list of other information related to that email. Likewise if you select an event in Calendar, or a Note, etc… Eagle-eyed readers will most likely note the similarities between my suggestion and the fantastic DEVONthink. That’s no accident. I’ve felt for a long time that the AI at the core of DEVONthink would be spectacular if built into macOS. In DEVONthink, selecting a file and clicking on their little top hat icon will show you a list of related documents and suggest an appropriate group, or folder, for the document. I’d like to see the Mac sherlock that bit of functionality and expand it to the entire system.

Speaking of things that should be system-wide, how about tags? I suggest the next version of macOS come with the ability to tag everything. Let’s put tags in notes, todos, calendar events, contacts… the entire suite of productivity apps built into the Mac. The whole shebang, as they say. And, to be clear, let’s make sure they are the same tags, not siloed tags unique per application. That wouldn’t be nearly as useful in the big macOS data soup.

Next, you know how Apple bought the iOS app “Workflow”? How about we stop messing around and ship Hazel as a built-in part of the Mac. It already fits right in, running invisibly in the background and acting on rules set in the preference pane. Of course, if Apple bought it we could put rules for everything in Hazel. We could have Hazel triggering rules not just for files and folders, but for Mail, Calendar, Reminders… are you getting it?

Finally, let’s build in real security into every part of the Mac. I suggest private key encryption for everything before it is sync’d off of the machine. Transmitting files over SSL is fine. Storing files on the server on an encrypted disk is also fine. However, the files themselves are not encrypted, which means (as I understand it) that if the iCloud server is running the files are available. The encryption on the server just means that if someone tried to run off with the hard drive they couldn’t get into it. That’s why you can get to them from the web. Your login to icloud.com does not unencrypt the files, it simply allows you access to them. End-to-end private key encryption would be the next step that Apple could take to ensure that their customer’s information is safe and secure, even when transmitted across the Internet.

The purpose of a computer is to be a bicycle for the mind, a way to not only manage information, but help you make better decisions, cook better meals, make better deals, build better software, write better papers. Whatever you do, a computer should seamlessly help you do it better, and get out of your way to let you do it.

If the Mac is the pickup truck, or SUV, of the computing world, and the heaviness of macOS is what lets iOS stay light, then my suggestion is to lean into that philosophy and make the Mac the absolute best tool for managing information. A professional grade tool for professional daily use. And, obviously, since this is us, do it with style.

The work of systems administration, that is, racking new hardware, running cables, and loading operating systems, is quickly becoming eclipsed by devops. Servers come from the factory ready to rack, and the base operating system has become nearly meaningless in the context of running applications thanks to Docker. All you need is a baseline Linux install, the specifics of what each application needs to run are taken care of inside the Docker container.

If you are running your workloads in the cloud¹, the need for a dedicated sysadmin is even more redundant², since both the hardware and the base operating system are outsourced to AWS, Microsoft, or Google. However, bridging the gap between deploying applications to production and writing the application code sits devops, which for the past several years has been a fantastic opportunity for sysadmins to branch out into new and interesting ways. That opportunity is not going to last forever though. The core tasks of a devops engineer are repeatable, and the current complexity that devops now handles is moving more and more towards simplification.

In devops, there is a starting point, a set of tasks, and a specific end goal to achieve. Primarily, a devops engineer will take code from a repository and build out the systems to test and deploy that code to production in a secure, scaleable environment. That’s what I do anyway. History tells us that any repeatable, programmable task will be automated by a machine sooner or later, and I think we are starting to see what those new machines will look like.

Jason Kottke posted a link to Chess.com earlier today about how Google’s AlphaZero AI became the best chess player in history in four hours. It wasn’t loaded with a chess program, the AI taught itself how to play, and became unbeatable. Putting Skynet theories temporarily aside, how big of a step is it from there to automating devops? An AI could be trained on Github, given AWS or GAE as a deployment ground, and given an end goal of each application up and running.

Programmer friends who I floated this idea to in the past had mixed replies. Some claimed that the AI necessary to do this would be beyond anything currently in our capabilities. Others said that it might be possible. I think the writing on the wall is clear. It is possible, and I imagine it’s only a matter of time before the big three cloud providers each deploy their own version of automatic code deployment. It won’t look like much from outside, the only configuration they’ll need is access to your repository, and the AI will build up everything else necessary.

The models exist, the artificial intelligence exists, and the need for the service exists. DevOps is a career path with an expiration date. If that date is 10, 20, or 30 years down the road, I can’t tell, but it’s closer than any of us working in the industry would care to consider.

I’ve been enjoying watching the new iPad commercial of a kid and her iPad roaming around the city. Two things come to mind. First, is this what it’s like for kids in the city? Having never lived in one myself I find it fascinating that she just roams around, takes the bus, hangs out in an alley, whatever. Second, and more important, is what she’s doing with that iPad.

The first time we see her with the iPad she’s chatting with a friend over FaceTime, snaps a screenshot, and draws on it. She shows the screenshot to her friend, then sends a copy of it over Messages. Next she’s in an alley with a bunch of furniture, sitting in a seat and twisted to her left to type on the iPad keyboard. She notices a praying mantis on a leaf next to her and quickly snaps a photo, dropping that picture into what looks like a Pages document about bugs in the city. We see her typing in a bakery, drawing in a tree, and reading a comic on the bus. Finally, she’s laying in the grass in her backyard typing again, and when her neighbor asks her what she’s doing on her computer, she replies “what’s a computer?”

We’ll put to the side the ridiculousness of that question, as we the viewer are supposed to assume that the next generation is going to grow up using the tablet form factor and will have no idea what a classic desktop computer is. It’s a stretch, but ok. The commercial calls back to a previous iPad video that shows people working in different ways in different occupations using an iPad Pro. In the previous video they use the camera to capture and analyze athletic performance, they type and draw, share building schematics, and use the iPad in place of printed technical manuals. Both commercials point to the type of lifestyle and work-style that Apple believes the iPad is best suited for.

In no video does it show a developer sitting at his desk for eight hours a day starting at the screen and trying his level best to edit code, ssh into servers, and manage his git repositories. All things that are technically possible on an iPad Pro, but not better than they are on a Mac. A few months ago I bought an iPad Pro, Smart Keyboard, and Pencil and attempted to work only using it. The experience was very similar to using a laptop. The screen was small, and I wound up hunched over my desk for several hours a day struggling through tasks that were second nature on the Mac. Before my two-weeks were up, I wound up returning the iPad and getting my money back. I bought a 27” iMac instead, and it’s been fantastic.

However, the experience made me think about what kind of work I do and how I don’t want to get stuck in the past while the world moves on around me. There’s a thin line between waiting for the technology to mature to the point where you can use it without stress, and growing stagnant. There is a fairly good chance that many new developers in the next ten years might not have worked on anything but an iPad, depending on if they got one issued to them in school or not. I want to be able to move to the new technology when it’s ready for me, but judging when it’s ready might not be something I can do objectively, but I think we can lay some ground rules.

The iPad needs to be able to connect to an external monitor and trackpad.

Yes, I can hear the “but it’s a touch interface” objections from here. To answer that I’d like to point at the current iOS feature to 3D press on the keyboard to move the cursor in a text field. Like Jason Snell has argued, they’ve already given us a mouse-like interface, why not take it all the way? It’s probably healthier to move around all day like the kid in the video, but there are a whole lot of us who have a desk they sit at every day, and the iPad is simply poorly ergonomically designed for long periods of work.

The iPad needs to be able to run a full suite of Unix tools.

So much of my development work happens in Terminal.app. For example, in one of our applications we need to run a Django app that uses a ssh tunnel to a MySQL server, and then be able to load the Django site by browsing to localhost on a particular port. One could argue that if that’s the kind of work you are doing, you should just use a Mac. I’d argue that loosening of the iPad restrictions just a bit would open the device up to an entirely new class of user. They don’t need to give full access to the Unix underpinnings of iOS to provide a Unix development environment, they could chroot the user in a sandbox. It’s technically possible, but not currently possible.

The iPad needs a local and remote backup solution.

I worry about my data. Too much, obviously. My Mac runs the classic 3-2-1 backup system (three copies of your data, two local, one remote). iCloud backup could work, but a local Time Machine would be even better. Being able to restore just one file to what it was an hour ago is, at times, priceless. I’d say we are probably closest to having this, depending on the app you are using, but a system-wide, effortless, file-level backup and recovery system would be fantastic.¹

I may be able to switch to an iPad before all these three things happen, but it would be so cumbersome and difficult that my work would suffer as a result.

What I don’t want to do is jump on the “it’s not a real computer” bandwagon. That’s the same argument that was used against Macs for years, back when my Mac was the only one in the company outside of design. The Mac was derided for years as an expensive toy by IT departments and PC enthusiasts. They were wrong then, and those saying it’s impossible to get any real work done on an iPad now are wrong. What I’m saying is that for now, it’s impractical for me to use an iPad for every day work, but I don’t think it’ll stay that way forever. For now, there simply is no alternative to the command line to do what I do. In the future, that might not be the case.

I’ve found it interesting to look at how work was done before computers became commonplace. Writers used typewriters, which served as the models for how computers first evolved, but I think the more interesting occupation to look at is that of an architect working at a drafting table or a drawing board. They might have done some sketching or taken down some ideas in a notebook, but the real work happened with an expansive canvas in an environment that was conducive to long periods of uninterrupted work.

The iPad Pro right now is a professional notebook. I’m waiting for it to be a drafting table, something similar to the Microsoft Surface Studio, but without the suck.

I gave a talk at our school Veterans Day assembly today. I didn’t get everything I wanted to say in, but it seemed to go over well.

So, I thought an awful lot about what I wanted to say to you today. What message I could bring that would be of use to middle schoolers, and I want to talk to you about why you might want to consider joining the Navy after high school. Now, I’m not a recruiter, I’m not here to sell you some schickt or a bunch of meaningless jargon. I want to tell you what the Navy did for me, and what it could do for you too.

I joined the Navy when I was 18 in 1995, which probably seems like absolute ages ago to all of you, but it seem like yesterday to me. I was a rambunctious kid, bit of a troublemaker, you might say. And for me, at the time, college was simply not in the cards. I knew I needed to do something with my life, but I didn’t know what it was. I wanted to travel, and my dad was in the Navy when he was young and he went all over the world, so it sounded like a good idea for me too.

So, I signed up and shipped off to boot camp in Great Lakes, IL in October, graduated in December. After boot camp, I went to engineering common core, then I shipped off to San Diego for “A” school where I learned to be a machinist.

After San Diego I was assigned to the USS Platte, an oiler. We were a floating Caseys, a gas station for all the other Navy ships in the sea. We would pull along side another ship, the gunners mates would fire lines across to them, they’d pull the lines tight, and we’d run big hoses over to the other ship.

Then we’d just steam across the Atlantic pumping millions of gallons of gas over to the other ship. That was our job.

I went on two Mediterranean deployments during the three years I lived on the ship for six months each. During the deployments I visited Portugal, Spain, Gibraltar, France, Italy (spent a lot of time in Italy), Greece, and even went to Israel once. Back stateside we went to the Bahamas and the Virgin Islands once, and north to Nova Scotia once too. That was a blast, you can ask Mrs. Buys about that, she was there for that one!

Back then, and remember this was in the ‘90s, it was peace time, and we were an oilier, so keep that in mind, but we’d go from port to port, spending a week or two underway before pulling into port in another country for a few days. We’d get maybe a day to go explore wherever we were, sometimes go on an MWR trip or something. But, it was a blast, but it was also a lot of hard work. When you’re underway, there’s nothing better to do than to learn everything you can about the ship. And play cards. We played a lot of cards.

I got to travel, I learned that I loved the ocean, I was a firefighter on the ship, and I worked hard and became a radioman. It was an experience I’ll never forget.

After the ship I was transferred to a small joint-services command in rural England, six hours West of London in Cornwall called JMF St. Mawgan. This was a shore command that counted as sea duty for ship-shore rotation because it was so remote, but it was amazing. The Navy shipped our family over, and our Jeep, and we rented a farmhouse right outside a tiny little village. What we did there was… classified, and I was never sure if it was ever unclassified, so, we’ll just move on. I was a radioman and handled communications. The facility itself was underground in a building built to withstand a nuclear bomb. There were armed British guards at a big turnstile, then a long concrete tunnel, then you’d turn and it was another long concrete tunnel, then you’d come to a massive red 50 ton door, then a decontamination station, and then you would be in what was basically an office building.

We loved rural England so much we stayed an extra year. I spent four years there total, and it was another fantastic experience I’ll never forget. I was in England on 9/11. When everything changed. That’s a story for a different day.

Eventually, my tour in the UK came to an end and I had to move once again, this time the Navy shipped me all the way from lush green England to the high desert of Albuquerque, NM, where I was assigned to another special duty command, the Defense Threat Reduction Agency, which used to be the Defense Nuclear Agency. We built bombs, and they sent me every now and then up to the desert in Nevada north of Las Vegas to handle communications for testing these bombs. The base in Las Vegas was an Air Force base sectioned off into different areas that numbered up into the 50s.

After three years at DTRA, the Navy told me it was time for me to go back out to sea again. At this point, I had to stop and take stock of where I was in life.

I had joined the Navy 11 years prior with nothing but the shirt on my back. I was leaving with a family, a home, and the skills and confidence to build a career on. I looked at my young family and thought about all the long months out to sea and being apart from them, and decided that at this point I’d served my time, so I chose not to reenlist, and was honorably discharged in October of ’06.

This was meant to be a really short overview of my time in the Navy, but what I’d like for you to take out of it is that while I did work hard, harder than I ever thought possible for me, I also had some of the best times of my life in the Navy, and had experiences and went places that I never would have been able to otherwise. Navy life is unlike any other military service, or any other job.

Speaking of jobs,

No matter what kind of job you are thinking of going into when you grow up, there’s an equivalent in the Navy. The Navy is a microcosm of the United States, there’s people from all walks of life in the Navy. If you want to be a plumber, there’s a job for that. Computer programmer? There’s a job for that. Doctor? Yep. Mechanic, you bet! Construction? Absolutely, we call them the Seabees.

Don’t get me wrong, when you sign that dotted line to enlist in the Navy you are putting your life on the line. The shipboard environment is hazardous, and our ships are targets for our enemies. I’ve made, and lost, the best friends of my life in the Navy, and I’ve had friends who’ve suffered debilitating injuries. Life on the ocean is for the brave.

Being a sailor is an old service with old traditions. The Navy needs sailors to man the ships, and the ships of the United States Navy make up the most massive display of military power the world has ever known. It was an honor to be part of it. But more than that, more than flag waving and patriotism, if you want to be pragmatic about starting your life out on the right foot, the Navy is unique. You travel and serve, you do what you’re told when you’re told to do it. You learn just how hard you can work, you learn how to deal with emergencies and life-threatening situations. You learn, by pushing yourself further than you think you can go and rising to the occasion, just how deep your strength really goes.

I joined the Navy in 1995 with literally no possessions but the shirt on my back. I left eleven years later with a family, a home, and a profitable career path. Not everything has been roses and unicorns, but thanks be to my savior Jesus, I’m blessed more than I have any right to be. I owe that to the Navy. When I enlisted I signed a dotted line that I was willing to lay down my life for my country, but at the time the only country I was thinking of was a country of one… me. But what I learned in the Navy was that I wasn’t putting my life on the line for myself, I was doing it for my shipmates, for my family, for my kids. I put my life on the line because the country that let a dirt poor troublemaker from a Montana reservation rise up the ranks to be a respectable homeowner is worth defending. Because in America, where you were born does not dictate who you have to be. Your family name, your race, your checking account balance… none of that matters more than how hard you decide to work. You can wallow in your disadvantages, or you can rise above them. In America, you are not born who you were meant to be, you make your own destiny.

Do we have problems? You bet we do. Big ones. But you can’t help solve them until you solve your own. You might find yourself someday in the same position I was at 18. Listless, restless, no direction. In that case I hope you remember this, that I was once like you, and what worked for me, might work for you too.

And along the way you might find the best friends you’ve ever had, you might meet the love of your life, and you just might find a deep sense of patriotism that goes beyond waving a flag or slapping an eagle sticker on your bumper. I joined the Navy for selfish reasons, what I learned was that we did what we did for each other. For the man or woman standing next to me holding the line, fighting the fire. To keep the people we love safe, to maintain our way of life, a veteran put his life on the line.

The 27” iMac 5K is unquestionably the best computer I’ve ever owned. After two months of daily use, for twelve to fourteen hours per day, I can say without reservation that this machine is fantastic. Obviously, I’m late to the bandwagon on this, better reviews than what I would write have already been written, and although those reviews are from 2014, they hold up well enough for the 2017 upgrade too. The screen is beautiful, like a massive glossy magazine. The machine is fast enough so I nearly never have to wait. Basically, it’s everything I need from a computer.

What I Love

Having a desktop computer that is always on has benefits. My mail rules always sort my inbox. I have SuperDuper! setup to automatically clone my internal drive every weekday after Energy Saver wakes it up. The internal SSD is big enough that I’ve got all of my data downloaded and stored locally.

The iMac survived The Great Port Purge so far. So on the back of my screen I’ve got all the connections I need, including four standard USB ports and an SD Card slot for my camera. Three of the USB ports are taken up by my ScanSnap scanner, my time machine backup drive, and the SuperDuper! clone drive. The fourth is open for when I need to charge an accessory.

The two drives are held up by a Twelve South Backpack so they are out of the way and I don’t have to see any cable mess. That keeps my desk clean and my fussy mind focused.

In many ways I feel like the iMac is the last computer that Apple is shipping that’s not compromised to the point of suffering usability, reliability, or both.

The latest Magic Keyboard is great. Like others who’ve become accustomed to the new style of keyboards, every other kind of keyboard now feels like a mushy mess to me. This new one is crisp and precise.

What Could Be Better

Using the Magic Trackpad 2 is not the same as using the trackpad on a MacBook. I’ve had a hard time dragging things from one spot to another, like if I want to drag something from my desktop to a folder. I’ll click with one finger, then start dragging with another, and for some reason sometimes that drag just doesn’t happen. This might be a combination of a new Mac and a new operating system, it might be because I haven’t gotten the feel for it yet, but whatever the problem, it’s been frustrating.

The screen is so big that it takes more than one operation to move a file from one spot to another. That sounds like the firstiest of first-world problems, but it’s a real enough issue that I broke out my old mouse at one point. I’m still getting used to the trackpad, but so far my opinion of it has not been high. Perhaps it will improve with use. The multitouch gestures like five-finger swipe to show the desktop work well on the large trackpad, where the MacBook trackpad was always too small, and swiping from the edge to show the Notification Center works well, as does swiping to go back and forward in Safari. It’s a mixed bag.

This Saturday I’m packing up the iMac and bringing it to the Apple Store for repairs. I found a big, ugly, dead pixel center-right of the screen. When it’s up against a white background, like this text editor, it looks like a speck of dirt and I feel like I should wipe it off. But, it doesn’t go anywhere. So, although I’m loath to have anyone crack the seal on the Mac, I can’t go though the next several years staring at this dot.

Recommendations

If you, like me, spend a significant amount of time in front of a computer, I can’t recommend the iMac highly enough. It’s a beautiful work of art, designed to live in your home or office, and it’s also a powerful workhorse that can keep up with the most demanding tasks. It’s hard for me to recommend any other Mac in the Apple lineup right now to anyone but early adopters or those with enough technical savvy to work around the MacBook and MacBook Pro limitations. I’m hoping in another revision they’ll have some of the issues with the keyboard worked out, and maybe even throw in an extra port or two¹. For me, this iMac is exactly what I need.

Top Four is one of my favorite podcasts. Possibly my number one, although its probably tied with ATP and The Talk Show. It’s a strong contender. Marco and Tif Arment chat about some random group of things, and attempt to rank said things, usually failing because they can’t make up their minds. It’s adorable. It’s clear that the two of them are having a good time, and listening always makes me laugh.

In a recent episode the pair ranked their top four favorite “Fall-tivities”, things to do in the Fall. They named a few things I’d never heard of, like pumpkin blazing, which sounds like a lot of fun, and talked about the corn mazes in the Northeast, which for some reason sound bigger than ours here in Iowa. A travesty if true.

Listening to the podcast put me in the holiday mood early this year, and since it’s good to think about good things that make us happy, here, in no particular order, here are a few of my favorite things about Fall.

• Flannels, sweaters, and jackets
• Getting a chill outside and coming inside to warm up under a blanket with a hot drink
• Apple pie
• The smell of cinnamon and spice in the air when baking said apple pie
• Also pumpkin pie
• Pumpkins on peoples porches
• The leaves changing color and falling
• The holiday season is coming, Halloween, Thanksgiving, Christmas, New Years 🎁🎉🎊
• Getting up before the sun comes up and going outside to look at the stars
• Soups, stews, and chili
• Smores in the backyard over a fire, just because.
• Football and Fall soccer seasons
• The long, hot, miserable summer is over. The seasons change, life goes on.

Fall is by far my favorite time of the year. The grass stops growing, but we don’t have snow yet. The days get shorter, but there’s still plenty of sunshine. Time to break out the gloves and hats and scarves. Time to bake some cookies and carve a pumpkin. Run a little later in the day, and enjoy it more because the temperature is perfect for running in long sleeves. Go for a hayride, have a bonfire, dig the decorations out of storage. Put our petty differences aside and remember that we are all neighbors. Give, laugh, love. Fall is the best.

I’m in St. Louis for the Strange Loop conference, and the conference kicked off last night with a party at the City Museum. I didn’t bother to look into the museum much before I came. A few friends told me a bit about it, but it wasn’t enough for me to really understand what the museum was; the City Museum isn’t a museum, its a mad amusement park.

I heard from another conference attendee who’d been there before that the museum was the product of a single person’s desire to make something out of an abandoned building. A mad genius. I describe exploring the museum like going through someone else’s code… you’re always finding things that make no sense. Why is there an airplane on scaffolding outside? Why are there two? Why is the only way to get to the plane through a maze of metal steps and tunnels? Why is the basement built to look like an underground cave? From the insect display to the collection of Italian movie posters to the human-sized hamster wheel, the City Museum makes no sense. It’s an eclectic collection of amusing things. Five stories of collected randomness.

My friend fulfilled a lifelong dream of falling into a ball pool. There was a live band playing on the first floor, board games on the second, food and drinks on the third, and mazes everywhere. There are two massive bank vault doors connected to a hall of mirrors that leads back to the hamster wheel. There are statues of whales, gorgon heads in a fountain, HO scale model train with flying dragons breathing fire, stairs that don’t lead anywhere and slides that go for several stories.

I’m not sure how “safe” the museum is, or how it manages insurance. The structures I climbed on all seemed sturdy enough, but I did wonder at times how old they were, or when the last time they were inspected was. My original plan was to walk to the museum, grab some food for dinner, and walk back to the hotel, mainly ignoring the festivities and the museum. I’m glad I stayed for a few hours.