More stories

  • in

    My favorite Garmin safety feature is coming to Forerunner models – and I can’t recommend it enough

    Last year’s Garmin Forerunner was one of my favorite smartwatches. Matthew Miller/ZDNETRegular readers know that I always wear a Garmin with an LED flashlight on one of my wrists, and I use it daily. It’s exciting to see, for the first time, that Garmin now has a Forerunner model with this flashlight, which serves as an important safety feature for runners.Garmin’s new Forerunner 570 More

  • in

    I challenge you to find a better pair of budget wireless earbuds than this

    <!–> ZDNET’s key takeaways The CMF Buds 2 Plus are the most premium pair of earbuds from the Nothing sub-brand. At $69, they’re one of the best-sounding and most feature-rich earbuds in the price segment. The way these earbuds are designed makes them not ideal for side sleepers. –> The new Nothing CMF Buds 2 […] More

  • in

    How to move your codebase into GitHub for analysis by ChatGPT Deep Research – and why you should

    David Gewirtz / Elyse Betters Picaro / ZDNETA few days ago, I showed you an amazing new ChatGPT feature available to paying users. Plus, Pro, and Team tier users can now point Deep Research at an entire GitHub repo and get back analysis reports. Also: I test a lot of AI coding tools, and this stunning new OpenAI release just saved me days of workAs I showed, this capability helps speed up the process of coming up to speed on existing codebases. You might need to do this if you acquire a product from another developer or if you’re brought onto a project and need to learn the codebase quickly. It’s also good for reviewing your own codebase and refreshing yourself on how sections work — especially if you’ve moved on to other things for a while and are now coming back to the original code. I promised I’d show you how to bring a codebase into GitHub specifically for analysis by Deep Research. That’s what we’re about to do in this article. Moving my code into GitHub To demonstrate this, I’m moving My Private Site into GitHub. My Private Site is a freemium WordPress plugin with about 20,000 active users I’ve been working on for about a decade. WordPress, for historical reasons, uses SVN instead of GitHub as a code repository, so I haven’t really had a need to put My Private Site into GitHub. Also: I put GitHub Copilot’s AI to the test – its mixed success at coding baffled meBut given the opportunity to perform deep analysis on it, I decided to set it up. I’ll go through that process with you here. Getting started with GitHub Desktop Before we start, let’s clarify some things. Git is a distributed version control system that runs on a programmer’s local computer. GitHub is a cloud-based service that stores an enormous library of open-source and proprietary coding projects. Those projects are moved into GitHub (the cloud service) using Git (the tool). Real programmers only use Git on the command line, where it’s known as git. No real programmer would dare to capitalize git. Real programmers command git via a range of options, creating specialized command lines that do their bidding. Failure to use git on the command line will result in your real-programmer card being revoked by the International Society of Programmers Who Are Smarter Than You. Also: How I used GitHub Spark to build an app with just a one-sentence AI promptI am apparently not a real programmer. I might as well get that out of the way before the comments erupt in disdainful RPs (real programmers) mocking my lack of command-line acuity. I don’t use Git via the command line. I don’t like it. I believe humans left the cave long ago and adopted graphical user interfaces as tools of civilized society. I, therefore, prefer using GitHub Desktop, which is a point-and-click version of Git for those not worthy of the title real programmer. And yes, my official real-programmer card has been revoked. I can live with it.  You can download GitHub Desktop here. More

  • in

    5 ways you can plug the widening AI skills gap at your business

    tolgart / Getty Images Half of global technology leaders believe their organization has an AI skills shortage, and the capability gap has almost doubled in a year. The newly released Nash Squared/Harvey Nash Digital Leadership Report found that almost twice as many technology leaders (51%), compared with last year (28%), said their business has an […] More

  • in

    You may qualify for Apple’s $95 million Siri settlement – how to file a claim today

    Lance Whitney / Elyse Betters Picaro / ZDNETThink that Apple’s Siri snooped on your private conversations in the past? If so, you may be able to snag a slice of the $95 million that Apple is paying out to settle a class action lawsuit.Also: Apple’s big, next-gen CarPlay Ultra upgrade is here – if you drive these carsA settlement page published Friday in the case of Lopez v. Apple Inc. explains the steps and deadlines for people who want to make a claim. The settlement is geared toward current or former users of a Siri device in the US whose conversations with the voice assistant were captured by Apple or shared with third parties due to an “unintended Siri activation.” How to qualifyTo qualify, you must have been using the device between Sept. 17, 2014, and Dec. 31, 2024. How to enter a claimIf you’re in the qualifying group, you should receive an email or postcard with a Claim Identification Code and a Confirmation Code alerting you to the settlement. The email should be sent from an account called info@lopezvoiceassistantsettlement.com with a subject line of “Lopez Voice Assistant Class Action Settlement,” according to The Verge. So, if you receive such an email, don’t delete it. You may also want to check your spam folder to see if the message is trapped there.If you do receive the email, go to the claim submission page, enter both claim codes, and then log in to proceed.Also: 7 ways to lock down your phone’s security – before it’s too lateIf you don’t receive either the email or postcard, you can still try to put together a claim. To do that, enter a new claim at the submission page. You’ll be asked to provide your contact information along with a serial number and model name for the Siri device or proof of purchase. You can add as many as five different devices, including an iPhone, iPad, Mac, Apple Watch, AirPods, HomePod, or any other gadget that uses Siri. Either way, you’ll be asked whether you want to receive your payout by direct deposit to your bank account or by electronic check. Don’t wait too long to file a claim; the deadline is July 2, 2025. You can also opt to do nothing, in which case you simply won’t collect anything.Following the filing deadline, the court still has to approve the settlement before payouts can begin. A final approval hearing is scheduled for Aug. 1 with US District Judge Jeffrey White in the federal court in Oakland, California. More