How Claude helped my 65-year-old dad finally ditch his handwritten ledgers


My dad has owned a small business for as long as I can remember, and for just as long, he’s kept his books the old-fashioned way. Every sale gets written down by hand so he can file his taxes later. The problem is that his accountant needs this data in Excel, and my dad, who didn’t grow up around computers, has never learned how to use it.

For years, his workaround was paying someone to manually type his handwritten entries into a spreadsheet. It worked, but it was adding additional cost to his business, which he wanted to avoid, but couldn’t.

What pushed me to create this project

Last week, I was back home and caught my dad hunched over his notebook, writing out yet another day’s worth of sales by hand. I tried to teach him a few Excel basics, and for his credit, he quickly got the hang of it. That said, the data entry itself was still eating up hours of his time. 

Typing out rows and rows of numbers isn’t something you pick up overnight, especially if you didn’t grow up around computers. That’s when I thought about using Claude to take the manual work off his plate entirely.

Turning handwritten bills into a spreadsheet

I got to work. I set up a simple Claude project and gave it instructions to use my dad’s handwritten bills and turn them into properly filled-out Excel data. To show it what I wanted, I built a sample spreadsheet and filled in the first few rows myself. I then uploaded the sample sheet along with photos of his handwritten bills.

Claude filled in the rest of the spreadsheet. Data that would have taken my dad hours to type by hand took only minutes. Yes, Claude made occasional mistakes, but all my dad needed to do was cross-check the data, which is a far easier thing to do than entering hundreds of rows manually. 

The best part is that Claude projects remember the setup. So now all my dad has to do is open the project, create a new chat, upload his spreadsheet and handwritten bills, and Claude handles the data entry from there. No formulas to memorize, no formatting to figure out, and no one else to pay.

Is this worth the bigger picture cost of AI?

I’m not someone who thinks AI is an unquestionable good. The natural resources data centers burn through, and the price increases we’re seeing across consumer electronics are hard to ignore. I don’t think the benefits we’re getting back always match what we’re giving up.

But then I look at my dad. He’s 65, has never been comfortable with computers, and always assumed tools like Excel were simply not for him. Now, with a setup that took me an afternoon to build, he’s using AI to run a part of his business that used to cost him time and money every week.

I don’t think this cancels out the bigger concerns around AI. But it’s hard to dismiss what it’s done for one person who never thought this kind of technology was within his reach. The joy I saw on his face when he completed his first Excel sheet is something I will always hold in my heart. For that one moment, at least, the tradeoffs felt worth it.



Source link

Leave a Reply

Subscribe to Our Newsletter

Get our latest articles delivered straight to your inbox. No spam, we promise.

Recent Reviews


TL;DR

Meta stripped NameTag facial recognition code from its AI app one day after WIRED exposed it on 50 million phones. Meta says no decision has been made.

Meta removed nearly all traces of an unreleased facial recognition system from its smart glasses companion app on Friday, one day after WIRED reported that the software had been quietly embedded in an app installed on more than 50 million phones. The feature, which Meta internally called NameTag, was designed to convert faces captured by the company’s Ray-Ban smart glasses into unique biometric signatures and compare them against a database stored on the user’s device. WIRED also found that faces the system failed to recognise were cropped, indexed, and stored locally for future processing.

Andy Stone, Meta’s vice president of communications, told WIRED on Monday that the feature is “purely exploratory,” adding that no final decision has been made on what to do with it. That characterisation sits uneasily with the evidence WIRED documented. The version of Meta AI published the day of WIRED’s Thursday report contained several code libraries explicitly named for face recognition, a process for running the NameTag recognition pipeline, and a “Person recognised” alert the app would have shown if someone were identified.

Friday’s release stripped all of it out, along with a folder where the app would have stored the cropped images and biometric signatures of unrecognised faces. Meta did not answer WIRED’s questions about why the code was removed or whether the changes were planned before the story was published. A few fragments remain in the latest version, including an internal debug menu label and a dormant link meant to open a recognised person’s profile, pointing to parts of the system that are no longer there.

The 💜 of EU tech

The latest rumblings from the EU tech scene, a story from our wise ol’ founder Boris, and some questionable AI art. It’s free, every week, in your inbox. Sign up now!

The gap between Meta’s public statements and the code WIRED found is the central tension. Before the Thursday report, Stone dismissed the findings by writing that the company could not answer questions about how the system would work because “the feature does not exist.” Andrew Bosworth, Meta’s chief technology officer, called the reporting “incredibly misleading” and “absolutely dishonest.” Yet the code was functional enough to include three AI models, one to detect faces, another to crop them, and a third to encode them as biometric data, all embedded in the companion app for a product already at the centre of a mounting privacy crisis.

Meta declined to answer ten questions WIRED posed before publishing, including whether it had already created the database of face profiles NameTag uses, how long the app retains photographs and biometric data of unrecognised people, and whether that data would ever be sent back to Meta’s servers. The company also did not respond to questions about whether it was building NameTag for blind or low-vision users, or to criticism from privacy advocates who warned the system could let stalkers and abusers identify strangers in public.

NameTag first surfaced in February, when The New York Times, citing internal Meta documents, reported that the company was developing face recognition for its smart glasses and considering a launch as early as this year. One internal memo reportedly described releasing the feature during a “dynamic political environment” when privacy and civil liberties advocates would be distracted by other concerns. WIRED subsequently found that much of NameTag’s machinery had been built into the Meta AI app as early as January, months before any public acknowledgement, adding another layer to the company’s pattern of shipping first and disclosing later when it comes to its smart glasses.

Kade Crockford, director of the technology for liberty programme at the American Civil Liberties Union of Massachusetts, said the removal does not undo the original decision to ship the code and pointed to it as evidence that consumer privacy needs stronger legal protection than Congress has been willing to provide. The Massachusetts House of Representatives last week unanimously passed a consumer privacy bill that, if enacted as written, would impose strong enforcement provisions including a private right of action allowing aggrieved users to sue. “State lawmakers need to do their job and step up to protect consumer privacy,” Crockford said.

Meta’s sneaky tactics in slipping the face-recognition code into its smart glasses show exactly why data privacy bills need the teeth of strong enforcement,” Crockford added. “Companies like Meta prioritise their bottom line, so lawmakers need to speak in the only language its C-suite understands.” Whether a code removal prompted by investigative reporting constitutes a victory or merely a tactical retreat depends on what Meta does next, and on whether the regulatory pressure building on both sides of the Atlantic produces enforceable consequences before the feature quietly returns under a different name.



Source link