hngrok

Uber Torches 2026 AI Budget on Claude Code in Four Months from briefs.co
81 by lwhsiao 56m ago | | |

Article: 13 min

Uber has spent its entire 2026 AI budget in four months on Claude Code and Cursor, leading to a situation where the tools' success outpaces the company's ability to afford them at scale. Engineers have adopted these AI tools rapidly, with monthly API costs ranging from $500 to $2,000 per person.

Uber's experience highlights the rapid adoption and value of AI tools in software development, potentially influencing other companies' AI budgeting strategies and investment decisions.

95% of Uber engineers now use AI tools monthly, with 70% of committed code originating from AI.
Monthly API costs per engineer ranged between $500 to $2,000 as adoption increased.

Quality:
The article provides factual information without expressing a clear opinion.

Discussion (72): 16 min

The discussion revolves around the integration of AI tools in software development, particularly their impact on performance evaluation and job responsibilities. Opinions vary on the quality and usefulness of AI-generated code, its potential to increase technical debt, and concerns about gaming metrics by developers. There is a debate on the cost-effectiveness and ROI of using AI in software development, with some suggesting that measuring productivity requires considering counterfactual scenarios.

AI tools are becoming integral to performance evaluation
Quality of AI-generated code is questionable
Increased technical debt due to AI use
AI metrics may be gamed by developers

Counterarguments:

AI can lead to increased productivity
AI tools are a part of the business strategy
AI can help in feature acceleration and reduce development time
AI-generated code is useful when properly guided
Measuring AI productivity requires considering counterfactual scenarios

Technology Software Development, Artificial Intelligence

whohas – Command-line utility for cross-distro, cross-repository package search from github.com/whohas
45 by peter_d_sherman 2h ago | |

Article: 34 min

whohas is a command-line utility that enables users and maintainers to search for packages across various distributions, including Arch, Debian, Fedora, Gentoo, Mageia, Mandriva, openSUSE, Slackware, Source Mage, Ubuntu, FreeBSD, NetBSD, OpenBSD, Fink, MacPorts, and Cygwin. It provides URLs for more details about the package and allows users to refine searches using grep commands.

whohas can facilitate knowledge sharing among developers across different distributions, potentially leading to improved package management practices and collaboration within the open-source community.

cross-distro and cross-repository package search capability
written in Perl
helps package maintainers find definitions from other distributions
can be used by normal users to discover available packages on different distributions

Quality:
The article provides clear instructions and examples, making it easy to understand the utility's capabilities.

Discussion (8):

The discussion revolves around an outdated Perl-based package search database, with suggestions for modern alternatives and potential uses in security.

The repository is outdated
Node.js could be a better choice

Software Development Command-line utilities, Package management

Sally McKee, who coined the term "the memory wall", has died from online-tribute.com
46 by deater 2h ago | |

Article: 3 min

Sally McKee, a renowned computer science professor and originator of 'the Memory Wall' term, has passed away.

Her contributions to cybersecurity and mentorship of female computer scientists may inspire future generations.

Received degrees from Yale University, Princeton University, and the University of Virginia.
Worked at Digital Equipment Corporation, Microsoft Corporation, and various universities.
C. Tycho Howle Chair in Collaborative Computing Environments at Clemson University.
Advancements in cybersecurity research.
Pioneering work on 'the Memory Wall' concept.

Discussion (5):

The comment thread discusses the impact of a deceased computer science professor, known for her work on the memory wall, particularly her paper 'Hitting the Memory Wall: Implications of the Obvious'. The commenter shares personal insights about her and highlights discrepancies in academic citation practices.

She wrote a significant paper on computer memory.

Computer Science Academia, Research

Police Have Used License Plate Readers at Least 14x to Stalk Romantic Interests from ij.org
76 by loteck 47m ago | | |

Article:

The article discusses how police have used license plate readers 14 times to surveil romantic interests and suggests steps individuals can take to prevent such surveillance in the future.

14 instances of police surveillance using license plate readers

Quality:
The article provides factual information without expressing a clear opinion.

Discussion (31): 5 min

The comment thread discusses the undercounting of stalking cases, with a focus on evidence for social change and accountability in police misconduct. There is disagreement over the prevalence of stalking cases and the effectiveness of available data.

Stalking cases are undercounted

Counterarguments:

The comment thread lacks substance and is filled with low-effort reactions.

Privacy Cybersecurity, Law Enforcement Surveillance

Running Adobe's 1991 PostScript Interpreter in the Browser from pagetable.com
85 by ingve 5h ago | | |

Discussion (16): 2 min

The comment thread discusses the history of PostScript, its role as a 'Linguistic Motherboard', and its potential for sending programs instead of data structures. Participants share personal experiences with NeWS and discuss related technologies.

PostScript's role as a 'Linguistic Motherboard'

Your Website Is Not for You from websmith.studio
202 by pumbaa 5h ago | | |

Article: 5 min

The article discusses the common misunderstanding about websites being primarily designed for their creators rather than users. It argues that websites should serve as tools to facilitate user actions, not just reflect the creator's preferences or aesthetics.

Websites are tools for users, not reflections of the creator's taste.
Decision-makers often forget that websites serve their customers, not themselves.
Designers should be listened to when they provide evidence-based recommendations.

Quality:
The article presents a clear argument with supporting points, avoiding overly subjective or opinionated language.

Discussion (138): 39 min

The comment thread discusses various opinions on whether websites should be designed for creators or customers, with a focus on UX research and personal websites. There is agreement that websites should prioritize customer experience over creator's personal preferences, but there are differing views on the role of designers in web design.

Personal websites reflect creator's taste and preferences
UX research may not accurately represent user needs

Counterarguments:

Some argue personal websites are for creators and not customers
Others suggest UX research can be a valuable tool when properly utilized
Counterpoint that website aesthetics should align with brand reputation

Web Development Design & Usability

An open letter asking NHS England to keep its code open from keepthingsopen.com
61 by tvararu 1h ago | |

Article: 4 min

An open letter calls on NHS England to maintain its commitment to making new source code open, emphasizing the benefits of transparency and security in software development.

Open source policies can enhance transparency and security in the development of NHS software, potentially leading to better patient care and trust in public services.

Code paid for with public money should be open to the public.
The UK Government Design Principles support this principle.
The NHS Service Standard Principle 12 encourages making new source code open.
Open source requires higher quality, proactive vulnerability management, and risk mitigation processes.

Quality:
The article presents a clear argument for open source in healthcare, supported by relevant references.

Discussion (5):

The comment thread discusses the decision of a healthcare provider to close-source their code in response to a perceived threat. The main arguments are against this action due to its impracticality and lack of effectiveness, while also criticizing the motivations behind such decisions as being driven by optics rather than practical security measures.

Closing all the code would be an overreaction

Counterarguments:

The only exception is if there were significant changes to the code after it was closed given that won't be read by the attackers or the LLMs.

Healthcare Regulations, Software Development

Pro-Iran crew turns DDoS into shakedown as Ubuntu.com stays down from theregister.com
41 by ndsipa_pomu 1h ago | | |

Article: 5 min

A pro-Iranian hacktivist group, The Islamic Cyber Resistance in Iraq (313 Team), is conducting a Distributed Denial of Service (DDoS) attack on Canonical's web infrastructure. This disruption affects the Ubuntu website and its subdomains, preventing users from downloading Ubuntu distros or logging into their Canonical accounts.

Potential for increased awareness of cyber threats and the need for stronger cybersecurity measures, especially in relation to hacktivism.

Sustained, cross-border DDoS attack targeting Canonical's web infrastructure
Users cannot download Ubuntu distros or log into their accounts

Quality:
The article provides factual information without expressing personal opinions.

Discussion (33): 3 min

The comment thread discusses the reasons behind a cyber attack on Ubuntu, with users speculating about motives and potential connections. There is disagreement over whether Iran's actions are politically motivated or driven by other factors.

Counterarguments:

Connection between Linux and US/Israel not clear
Iran might be targeting Canonical due to its open-source involvement

Cybersecurity Hacktivism, DDoS Attacks

New copy of earliest poem in English, written 1,3k years ago, discovered in Rome from tcd.ie
168 by giuliomagnifico 2d ago | | |

Article: 12 min

Researchers from Trinity College Dublin have discovered a new copy of the earliest known poem in English, Caedmon's Hymn, dating back to between 800 and 830 AD. The manuscript was found in Rome's National Central Library and contains the poem in Old English within its main text, making it the third oldest surviving version of the work.

This discovery is significant because it contains Caedmon’s Hymn in Old English within its main body of text, unlike two older copies which have the poem in Latin with the Old English text only added marginally or at the end.
The poem was composed by a cowherd from Whitby, North Yorkshire, after a divine visitation and is said to be the oldest known poem in Old English.

Discussion (101): 24 min

The comment thread discusses the influence of various languages on English, particularly Old English and its relation to Scandinavian and Germanic roots. It also touches upon the evolution of language through borrowing from conquered nations, the standardization of translations like the King James Version, and the potential for unified international communication.

English has been influenced by various nations that conquered England.

Arts Literature, History

Advanced Quantization Algorithm for LLMs from github.com/intel
67 by lastdong 7h ago | | |

Article: 21 min

AutoRound is an advanced quantization toolkit for Large Language Models (LLMs) and Vision-Language Models (VLMs), designed to achieve high accuracy at ultra-low bit widths (2-4 bits) through techniques like sign-gradient descent. It offers broad hardware compatibility, ecosystem integration with tools like Transformers, vLLM, SGLang, and more, and supports multiple formats for maximum compatibility.

This toolkit could significantly impact the AI industry by enabling more efficient and scalable deployment of large language models, potentially leading to reduced costs for hosting and running these models.

Achieves high accuracy with minimal tuning
Leverages sign-gradient descent for optimization
Works seamlessly with various LLMs and VLMs

Discussion (13): 3 min

The comment thread discusses various opinions and concerns regarding quantization methods in AI models. The main points include overstatement of accuracy benefits by quantization papers, degradation in model performance with lower bit depths, lack of transparency, and potential academic misconduct within the field.

Quantization methods often overstate their accuracy benefits
Quantization causes significant degradation in model performance, especially at lower bit depths

Counterarguments:

Most quant papers I've seen usually report non-trivial degradation on standard benchmarks, like 1-10% degradation (compared to FP16/BF16).

Advanced Materials