...

Menu Close

ABA TECHSHOW 2019

ABA TECHSHOW 2019 logo

Whether you’re a tech geek or not, you should consider attending the ABA TECHSHOW if you want to make your practice more efficient. It’s not just for lawyers, but for anyone in the legal field. In addition to the dozens of CLE sessions to choose from, you can also visit the EXPO hall and check out products to improve your practice. We discovered my firm’s case management system in the TECHSHOW EXPO hall a few years ago, which then led to the discovery of our document management system and phone system. All were big improvements over our old systems.

Speaking of sessions, I’ll be back in Chicago this year presenting two sessions:

If neither of those topics are for you, check out the 2019 schedule for a complete listing. I always have a hard time narrowing down the choices, although I plan to hit most all of the sessions in the Mac Track. A few of the sessions I have my eyes on:

In addition to learning from Heidi and Julie, I’m looking forward to seeing other topnotch speakers like Brett Burney of Apps in Law, David Sparks of Mac Power Users and MacSparky, Jeff Richardson of iPhone JD, and many more.

If you attend, please say hello.


Use the Keyboard Maestro Status Menu as a Cheatsheet →

Clark Goble writing for Clark’s Tech Blog:

If you use Keyboard Maestro a good tip is to both create a hotkey and a status menu item. Then you can look at the status menu to remember your keystroke.

Yes, if you click through on the above link, you’ll see I’m linking to a footnote. While I set up the “meta key” mentioned in the post a year or so ago,1 it never entered my mind to use the Keyboard Maestro status menu (in the menu bar) as a cheatsheet. This will be especially handy with new macros, before I commit the hotkey to memory.


  1. It can be done with Karabiner Elements alone these days.


TiVo Coming to the Apple TV and Other Devices →

Jared Newman, writing for TechHive:

As announced during CES, TiVo will release apps for Roku and Amazon Fire TV devices in the second quarter of this year. Apps for Apple TV and Android TV will follow in the third quarter.

If you have a TiVo that supports transcoding (including the Roamio Pro, Roamio Plus, Bolt, Bolt Vox, and Bolt OTA), these apps will let you stream live and recorded video to another TV, either at home or on the road. For other TiVo devices that lack transcoding, such as the entry-level Roamio or Roamio OTA, you’ll need a separate TiVo Stream box to use the apps.

This is huge news. Well, for me at least. I have an Apple TV, but not a TiVo Mini, hooked up to the TV at my treadmill. I get some shows to that TV by running cTiVo on a Mac mini. cTiVo is an app that automatically downloads shows off my TiVo, formats them, and adds them to my Plex library and iTunes library.

The problem for me is that there are frequent glitches in the process, and shows never make it into iTunes or Plex. I hope the app lets me eliminate this whole setup.

One catch is that the apps will only support video at 720p and 30 frames per second. In my current setup, shows come through at 720p, but at 60 frames per second. It remains to be seen how noticeable this will be to my non-discerning eyes.

Even with the resolution and FPS limitations, this is another great benefit of the TiVO ecosystem. I had previously toyed with going to a streaming television service, but this alone will enough to keep with my TiVo, which I love. Of course, let’s see if TiVo delivers the Apple TV app in the third quarter, as the announcement indicates.


Bring Devices into HomeKit with Your Synology →

Casey Liss, at Liss is More:

The final piece that really opened everything up for me was realizing that my Synology has Docker support. Furthermore, after but a moment of digging, I was able to find instructions specifically for setting up Homebridge on a Synology in Docker.

Following those instructions, within about 10 minutes, I had a Docker container on my Synology, running Homebridge, and allowing me to see my not-yet-updated Wemo devices in HomeKit!

Homebridge is a software bridge that allows you to use certain non-HomeKit devices with HomeKit. Two years ago I installed Homebridge on my Mac mini server, which let me add my garage door and my Wemo switches to HomeKit. This process, which required command line dabbling in Terminal, was convoluted enough (for someone of my skill set) that I eventually abandoned it.

A week ago I resurrected Homebridge. This time I installed it on my Synology. As the above post by Casey Liss suggests, this process was MUCH easier than my first go-around. I had planned to publish a complete write-up of the process, but Casey’s post (and the link it contains) should get you on your way.

I followed a slightly different process than Casey followed, as I hadn’t discovered the instructions he referenced. I instead began by installing Docker on my Synology via the Synology’s Package Center, and then used these instructions to upload and install Homebridge.

No matter how you get Homebridge up and running, I encourage you to give it a shot if Homebridge has intrigued you. Aside from pasting text into a configuration file to get plugins working, the entire process was mostly a point-and-click process.


iPad Limitations With Reactive Work →

Riccardo Mori, at morrick.me:

The point that some iPad die‐hard fans seem to miss is that it’s not a matter of people not wanting to adapt to an iOS‐based workflow; it’s not a matter of people lacking mental agility to ditch their computers and switch to iPads for work. It’s that their work imposes different solutions, in the form of dedicated software, company‐issued computers, multitasking requirements (e.g. ability to monitor more than three applications simultaneously on a bigger screen), etc.

Although the “why I can or can’t use the iPad as my only computer” topic has been covered ad nauseam, and although Riccardo’s post focused on the portability and lightness aspect as a draw for iOS, the above quote is what struck me.

While I love the change of pace of working on my iPad when I can, it simply isn’t possibly when things are flying fast and furious at the office. And that has nothing to do with me not being familiar enough with iOS or iOS automation to bend the iPad to my will so I can react quickly. Instead, it has everything to do with the design decisions of the iPad concerning windowing and multi-tasking, as well as the limits of automation on iOS1.

I can’t instantly jump between apps on the iPad as quickly as I can on the Mac, or keep more than a couple windows on screen at once (three, if you count slide over). iOS automation isn’t to where it is on macOS yet, either. For example, with Keyboard Maestro on macOS, I can apply a brute force filter to entries in our firm’s case management system, using Keyboard Maestro’s ability to click on specified images. With the iPad, I have to do this clicking manually. The iPad method takes several seconds longer, and, for me, those seconds count.

For my type of work, the iPad is good when I know what I need to get done, and can control my work environment. When I have to be reactive, though, I need a system with windowed apps, and more advanced multi-tasking and automation (i.e., macOS).

I’m glad Ricardo framed this as “some” iPad users missing the point. I think most of the people in my online circle seem to understand that what works for them doesn’t work for everyone. I certainly understand that my way of doing things is specific to me, and that the iPad is a much better platform for some of you.

(But don’t get me started on the ergonomic and future health issues of working solely on an iPad or laptop.)


  1. This post isn’t meant as a suggestion that there’s something inherently wrong with those design decisions, or that Apple should change them – just that they hold me back in some situations.