Category Archives: Tech

I couldn’t resist trying this $89 lens

TTArtisan 50mm Neo

I was mid-way through a recent four night stay in a 2nd floor hospital room at Queen’s when I spotted an announcement of a new inexpensive Chinese-made lens compatible with my current camera, a Panasonic S9 full-frame that uses Panasonic/Leica L-mount lenses.

The new lens, released under the TTArtisan label, is a 50mm lens, considered to be a “normal” lens on this kind of camera.

A 50mm lens is considered “normal” on a full-frame camera because its field of view and perspective closely mimic how human vision naturally perceives the spatial relationships, distances, and proportions of objects in a scene. While our peripheral vision is much wider, the 46-degree angle-of-view of a 50mm lens aligns perfectly with the area we actively focus on.

Some people salivate over expensive tech. I lean toward seeking out bargain equipment that can produce decent photos.

This lens stands out for several reasons. First, at just $89, it cost just 20% of the comparable lens made by Panasonic itself, which was already part of my camera kit. And then there is its size. This lens is small and light. While the Panasonic lens is by no means considered “large” or “heavy,” the difference in size is dramatic, especially with the lens hoods attached. And, third, the TTArtisan is auto focusing, which distinguishes it from several similar but manual focus lenses already on the market.

There are always questions. How bad can it be? Is its focusing system reasonably fast and relatively accurate? And, at its best, is it capable of producing decent images?

I pulled out my iPhone, logged in to my account at B&H Photo in New York, and placed my order. The package was delivered not long after I arrived home after being discharged from Queen’s.

Initial impression: It seems well made. Basic, without some niceties, but what do you expect for $89?

I haven’t had a chance yet to take this new lens out into the “real” world of color, light, and motion. But I have kept it close to capture cat moments around the house. The conditions aren’t the best, with constantly shifting and often dim light, shallow depth of field, or cats sitting against bright backgrounds, all conditions posing challenges to both exposure and focus.

Two quick conclusions. On the down side, my unverified impression is that it is generally slower to focus than the Panasonic, although that could just reflect the difficult indoor conditions. But despite perhaps a larger share of slightly-out-of-focus images, when it hit the focus, it was capable of nice, sharp images. Not comparable to a top of the line lens costing 50x as much, but pleasant to the eye and nothing to be ashamed of.

It is available in Sony E mount and Nikon Z mount versions, as well as the Leica/Panasonic L mount that I have.

Here are a few photos taken over the past several days that show off what the TTArtisan 50mm is capable of.

New lens: TTArtisan 50mm Neo f/1.8

Houston, we have a problem

Now that we’re here in Redwood City for several weeks of post-surgery rehab, we’ve discovered a new problem.

We are staying in a house on a flag lot with access via a long driveway off of Oakwood Blvd. Boulevard is pretty pretentious for this small street through a quiet neighborhood. It is, admittedly, a LONG driveway for a residential neighborhood.

And we are highly dependent on delivery services for groceries, some meals, and other supplies.

The problem is that Google Maps is simply incorrect.

It directs delivery drivers to the next street. But there is no access to this property from that street.

I now watch the progress of DoorDash drivers on my phone, and most have found themselves at the deadend of the next street wondering how to deliver our stuff. I try to head them off, or send texts explaining that they have to approach on Oakwood Blvd and not on any other street. But we’ve also run into a language gap with Hispanic drivers.

I can see how it happens. Because of the long driveway, this house is physically closer to the next street, but it can’t be accessed from there.

When I checked on how to flag the error with Google’s version of maps, it appears to be difficult or impossible, especially if relying on an iPad.

Apple Maps, on the other hand, provides accurate directions to the house.

But it seems Google has the delivery services pretty much locked up.

I try to tip to cover the “lost” time, but that’s not a good solution.

Just an aside on tiny tech

I brought my five year-old iPad Pro on this trip, but didn’t bring it to the hospital with me. I usually rely on it when traveling, leaving my laptop at home.

So since getting out of surgery, I’ve relied on my iPhone 17 Air which has been much more useful than I expected.

I have been able to post on my blog and on Facebook, Follow threads online, get mail and texts, and even post photos in both places.

I’ve asked me to bring my iPad. The next time she visits, but this phone has been surprisingly effective in this unusual circumstance.

I’ve never relied on my phone so extensively, and it has held up well.

The hospital offers guest wifi, which isn’t speedy but does the job, and T-Mobile has bridged a few gaps.

Just FYI for other iPhone users.

An automated collision avoidance system warned of a close call

A reader writing as Pete808 left the following comment, which appears to provide additional details showing why our United flight to SFO on March 21 abandoned it’s initial landing attempt and powered up, went around, and made another landing attempt (this second one was successful).

Pete808’s findings show how much information can eventually be gleaned from existing public data.

Here are his findings, which initially appeared in a comment but are being elevated here because of their importance.

Here’s what I found by doing some additional internet research. By the way, I have no training or experience as a pilot or air traffic controller, although I’ve flown to SFO quite a few times.

In any event, one can go to LiveATC.net and listen to or download the archived air traffic control recordings for SFO for March 21, 2026. The archives are in half hour segments. After what seems to be a routine clearance to land, the archive for “SFO Tower” has a very cryptic communication from UA 373 a little more than halfway through the recording covering the time period beginning at 2200Z (Zulu or UTC time which is 3 pm SFO time). UA373 indicates that he’s going around although I couldn’t really tell what was being said by listening. In response, the tower controller tells UA373 to fly the runway heading and eventually to contact NorCal Approach.

If you review the archive for NorCal Approach for the period starting again at 2200Z, at around 23:45 into the recording the controller asks UA373 to say the reason for the go around and UA373 replies that they were responding to an RA. An RA is apparently a Resolution Advisory from the ACAS system (Airborne Collision Avoidance System), which is an onboard aviation safety system designed to prevent mid-air collisions by independently detecting nearby aircraft and advising pilots on avoidance maneuvers.

Although two planes landing on parallel runways is pretty routine at SFO with the aircraft required to maintain visual separation, the instructions with respect to ACAS Resolution Advisories is to do what the RA says. So even though UA373 was supposed to maintain visual separation from the other aircraft and even if that visual separation was still being maintained by UA373, when the RA was given by ACAS, the crew of UA373 was obliged to follow it.

Hope your health issues get resolved favorably.