Titles and Descriptions in Photos.app

featured-content-sync2-icon_2x.jpg

Adding Captions and Comments to photos in macOS’ Photos.app is easy after you have shared it via iCloud photo sharing. But how to add titles or descriptions to photos you don’t plan on sharing right away, such as just cataloguing old pictures for easier searching?

 

Get Info

The Photos UI is rater limited and no obvious place to add titles is visible. But select one or more photos, hit ⌘+I (or pick Info from the Window menu) and this opens a dialog with information about selected items, among other things, Title, Description, Keywords and Location. This is especially nice if you pick multiple items, you can assign title or description to all of them in group.

photos_info.png

In the above examples I have picked two photos and assigned title, longer description and location to an old photo from 2001. All these fields are now searchable. I have used the description field to list people in the pictures, etc.

 

RubyMine high CPU, no background tasks

RubyMine, being an IDE and not light editor, is expected to hog some CPU. But after each RSpec run, the CPU usage jumps to 300 % for several minutes. If I do fast iteration on specs, then this high CPU usage is constant and heats up my Mac, causing fan noise and of course drains battery.

Screen Shot 2017-08-23 at 17.13.19.png

Googling around for solution did not find anything, especially as there are not background processes running. I even tried profiling the app to see if it gives any  ideas (hint: it did not).

One support ticket for WebStorm though tipped me off and turned out that the culprit are Inspections – those little yellow or red markers around right gutter that tell you when your code smells or is outright broken.

 

Handpick the Inspections

Screen Shot 2017-08-23 at 17.11.58.png

Navigate to Preferences > Editor > Inspections and go through the long list. Unfortunately RubyMine does not tell you which Inspection it currently runs, so it is trial and error to find out what causes the slowness.

In my case there were a lot of “Double quotes” as well as whitespace whitespace warnings, but growing tired of not finding any low hanging fruits, I decided to just disable almost all warnings and left only error-level Inspections.

Now, after running specs, RubyMine CPU usage jumps to around 100 % for only a little while and then returns to normal.

 

A note on tabs

RubyMine has default setting of allowing only a handful of tabs open at the same time. Increasing this limit affects, among other things, the Inspections performance too as these are run for all tabs after every spec run. (Don’t ask me why JetBrains thinks this is necessary.)