fidzu : geek

Boris Cherny, the creator of Claude Code at Anthropic, revealed a deceptively simple workflow that uses parallel AI agents, verification loops, and shared memory to let one developer operate with the output of an entire engineering team. "I run 5 Claudes in parallel in my terminal," Cherny wrote. "I number my tabs 1-5, and use system notifications to know when a Claude needs input." He also runs "5-10 Claudes on claude.ai" in his browser, using a "teleport" command to hand off work between the web and his local machine. This validates the "do more with less" strategy Anthropic's President Daniela Amodei recently pitched during an interview with CNBC. VentureBeat reports: For the past week, the engineering community has been dissecting a thread on X from Boris Cherny, the creator and head of Claude Code at Anthropic. What began as a casual sharing of his personal terminal setup has spiraled into a viral manifesto on the future of software development, with industry insiders calling it a watershed moment for the startup. "If you're not reading the Claude Code best practices straight from its creator, you're behind as a programmer," wrote Jeff Tang, a prominent voice in the developer community. Kyle McNease, another industry observer, went further, declaring that with Cherny's "game-changing updates," Anthropic is "on fire," potentially facing "their ChatGPT moment." The excitement stems from a paradox: Cherny's workflow is surprisingly simple, yet it allows a single human to operate with the output capacity of a small engineering department. As one user noted on X after implementing Cherny's setup, the experience "feels more like Starcraft" than traditional coding -- a shift from typing syntax to commanding autonomous units.

Read more of this story at Slashdot.

07 Jan 2026 3:30am GMT

According to Bloomberg, Discord has confidentially filed for a U.S. IPO. Reuters reports: The U.S. IPO market regained momentum in 2025 after nearly three years of sluggish activity, but hopes for a stronger rebound were tempered by tariff-driven volatility, a prolonged government shutdown and a late-year selloff in artificial intelligence stocks. Discord, which was founded in 2015, offers voice, video and text chatting capabilities aimed at gamers and streamers. According to a statement in December, the platform has more than 200 million monthly users.

Read more of this story at Slashdot.

07 Jan 2026 2:02am GMT

schwit1 shares a report from Gothamist: Wegmans in New York City has begun collecting biometric data from anyone who enters its supermarkets, according to new signage posted at the chain's Manhattan and Brooklyn locations earlier this month. Anyone entering the store could have data on their face, eyes and voices collected and stored by the Rochester-headquartered supermarket chain. The information is used to "protect the safety and security of our patrons and employees," according to the signage. The new scanning policy is an expansion of a 2024 pilot. The chain had initially said that the scanning system was only for a small group of employees and promised to delete any biometric data it collected from shoppers during the pilot rollout. The new notice makes no such assurances. Wegmans representatives did not reply to questions about how the data would be stored, why it changed its policy or if it would share the data with law enforcement.

Read more of this story at Slashdot.

07 Jan 2026 1:25am GMT

Motorola is light on details but heavy on hype for its first book-style foldable.

07 Jan 2026 1:00am GMT

The most familiar, full-fledged PC experience you can get from a keyboard.

06 Jan 2026 10:40pm GMT

About half a year ago, I wrote an article about persistent rumours I'd heard from Android ROM projects that Google was intending to discontinue the Android Open Source Project (AOSP). AOSP has been gutted by Google over the years, with the company moving more and more parts of the operating system into closed-source, non-AOSP components, like Google Play Services. While you can technically still run bare AOSP if you're really hardcore, it's simply unusable for 99% of smartphone users out there. Google quickly responded to these widespread rumours, stating that "AOSP is not going away", and a lot of people, clearly having learned nothing from human history, took this at face value and believed Google word-for-word. Since corporations can't be trusted and lying is their favourite activity, I drew a different conclusion at the time: This seems like a solid denial from Google, but it leaves a lot of room for Google to make a wide variety of changes to Android's development and open source status without actually killing off AOSP entirely. Since Android is licensed under the Apache 2.0 license, Google is free to make "Pixel Android" - its own Android variant - closed source, leaving AOSP up until that point available under the Apache 2.0 license. This is reminiscent of what Oracle did with Solaris. Of course, any modifications to the Linux kernel upon which Android is built will remain open source, since the Linux kernel is licensed under the GPLv2. If Google were indeed intending to do this, what could happen is that Google takes Android closed source from here on out, spinning off whatever remains of AOSP up until that point into a separate company or project, as potentially ordered during the antitrust case against Google in the United States. This would leave Google free to continue developing its own "Pixel Android" entirely as proprietary software - save for the Linux kernel - while leaving AOSP in the state it's in right now outside of Google. This technically means "AOSP is not going away", as Chau claims. ↫ Thom Holwerda at OSNews Ever since the claim that "AOSP is not going away", Google has taken numerous steps to further tighten the grip it has on Android, much to the detriment of both the Android Open Source Project and the various ROM makers that depend on it. Device-specific source code for Pixel devices is no longer being released, Google dabbled with developer certification even for developers outside of Google Play, and Google significantly scaled back the release of security patches to AOSP. And now it's early 2026, and Google is about to take the next step in the slow killing of the Android Open Source Project. On the main page of the Android Open Source Project, there's now a new message: Effective in 2026, to align with our trunk stable development model and ensure platform stability for the ecosystem, we will publish source code to AOSP in Q2 and Q4. For building and contributing to AOSP, we recommend utilizing android-latest-release instead of aosp-main. The android-latest-release manifest branch will always reference the most recent release pushed to AOSP. This means that instead of four AOSP code releases every year, Google is now scaling back to just two every year. The gutting and eventual killing of AOSP has now reached the point where the open source nature of AOSP is effectively meaningless, and we're yet a few more big steps closer to what I outlined above: eventually, Google will distance itself from AOSP entirely, focusing all of its efforts on Pixel Android alone - without any code contributions to AOSP at all. If you still think "AOSP is not going away", you're delusional. OASP is already on life support, and with this latest move Google is firmly gripping the plug.

06 Jan 2026 10:39pm GMT

Nvidia's only GeForce announcements this year were about software improvements.

06 Jan 2026 9:56pm GMT

Since we moved to a new year, we also moved to a new month, and that means a new monthly report from Redox, the general purpose operating system written in Rust. The report obviously touches on the news we covered a few weeks ago that Redox now has the first tidbits of a modesetting driver for Intel hardware, but in addition to that, the project has also taken the first steps towards basic read-only APIs from Linux DRM, in order to use Linux graphics drivers. ARM64 now has dynamic linking support, POSIX compliance has been improved, and countless other improvements. Of course, there's also the usual massive list of bug fixes and minor changes to the kernel, relibc, drivers, and so on. I genuinely wish the Redox project another successful year. The team seems to have its head screwed on right, and is making considerable progress basically every month. I don't know what the end goal is, but the way things are looking right now, I wouldn't be surprised to see it come preinstalled on system76 laptops somewhere over the coming five years.

06 Jan 2026 9:16pm GMT

Happy New Year 2026! Once again, a lot has happened in Gentoo over the past months. New developers, more binary packages, GnuPG alternatives support, Gentoo for WSL, improved Rust bootstrap, better NGINX packaging, … As always here we're going to revisit all the exciting news from our favourite Linux distribution. ↫ Gentoo's 2025 retrospective We don't talk about Gentoo very often, and I consider that a good thing. Gentoo is just Gentoo, doing its thing, seemingly unaffected by the shifting sands of any community or world events. Gentoo will always just be Gentoo, and we're all better for it. The past year brought a ton of improvements to both Gentoo as a distribution and as a wider project and community. Because of Github's insistence to shove "AI" into everything, the project is currently moving to Codeberg instead, EAPI 9 has been approved and finalised, there are now weekly Gentoo images for WSL, the project welcomed several new developers, they've got a second build server, and so much more. Sadly, the project did have to drop the hppa and sparc architectures down a peg due to a lack of hardware, which hurts my soul a tiny bit but is entirely understandable, of course. Gentoo is doing great, and I doubt it'll ever not be doing great. Gentoo is just Gentoo.

06 Jan 2026 8:45pm GMT

2025 was a crazy simulation. A lot of glitches, plot twists and fun stuff™.

31 Dec 2025 12:00am GMT

Same as last year, this is a summary of what I've been up to throughout the year. See also the recap/retrospection published by my friends (antiz, jvoisin, orhun).

• Uploaded 467 packages to Arch Linux
  • Most of them being reproducible, meaning I provably didn't abuse my position of compiling the binaries
  • 35 of them are signal-desktop
  • 29 of them are metasploit
• Made 53 uploads to Debian
  • All of them being related to my work in the debian-rust team, that I've been a part of since 2018
  • …

31 Dec 2025 12:00am GMT

With the update to driver version 590, the NVIDIA driver no longer supports Pascal (GTX 10xx) GPUs or older. We will replace the nvidia package with nvidia-open, nvidia-dkms with nvidia-open-dkms, and nvidia-lts with nvidia-lts-open. Impact: Updating the NVIDIA packages on systems with Pascal, Maxwell, or older cards will fail to load the driver, which may result in a broken graphical environment. Intervention required for Pascal/older users: Users with GTX 10xx series and older cards must switch to the legacy proprietary branch to maintain support:

• Uninstall the official nvidia, nvidia-lts, or nvidia-dkms packages.
• Install nvidia-580xx-dkms from the AUR

Users with Turing (20xx and GTX 1650 series) and newer GPUs will automatically transition to the open kernel modules on upgrade and require no manual intervention.

20 Dec 2025 12:00am GMT