0. Don't be a meat proxy (gruhn.me)
1841 points · 740 comments · by ngruhn
The author urges people not to pass AI-generated responses directly to others, arguing that they should understand, verify, and restate the output themselves—especially in code reviews, where uncritical AI use shifts implementation work onto reviewers. [src]
Commenters broadly condemned using AI as a “meat proxy”—forwarding long Claude outputs to colleagues and making them validate or interpret the work, including one enterprise effort that generated thousands of documentation lines for hundreds of employees to review [0][1]. Some saw this as evidence of laziness, insecurity, and declining engineering competence, while others framed AI as a legitimate productivity tool and wrestled with whether to disclose using it when answering questions [2][3][8]. Suggested responses ranged from bluntly telling senders to ask Claude themselves [4] to treating persistent behavior as grounds for dismissal [5].
1. LLMs reward expertise (seangoedecke.com)
1411 points · 572 comments · by MaxMussio
LLMs broaden access to generalist skills, but the author argues domain expertise remains crucial for steering models, spotting errors, and extracting high-quality solutions, making human judgment—not model capability—the bottleneck in many tasks. [src]
The discussion largely agrees that LLMs amplify existing expertise: technical vocabulary, domain knowledge, and familiarity with a codebase help users give precise instructions, evaluate results, and avoid getting stuck, while novices can spiral into vague feature discussions [2][6][7]. Others argue that LLMs dramatically shorten the old trial-and-error loop and may eliminate the need to learn low-level skills such as CSS or assembly [1][5], though critics counter that the slower process was also how people learned [3][9]. There is disagreement over whether experts or generalists benefit most, with some suggesting the decisive advantage belongs simply to people who actively experiment and keep the model in the loop rather than blindly delegating [4].
2. Qwen3.8-Max: A New Bar for Coding and Cowork (qwen.ai)
1121 points · 614 comments · by ai2027
Qwen has released Qwen3.8-Max, a 2.4-trillion-parameter model available through QwenCloud, touting advances in coding, workplace automation, research, multimodal agents, and long-horizon tasks, with open weights promised next week. [src]
The discussion is broadly enthusiastic about Qwen’s local models, with users calling the 3.6 line their daily drivers and citing practical success running coding agents on laptops, Macs, and consumer GPUs [1][3][7]. There is some disagreement over model tradeoffs: 35B MoE is praised for speed, while the 27B dense version is considered smarter by at least one user [6]. Commenters also question whether hosted AI companies have a durable moat when users can easily switch models, while others worry that increasingly capable agents will displace freelance programming work [2][8].
3. Ten advances in mathematics and theoretical computer science (openai.com)
627 points · 938 comments · by milkshakes
OpenAI says its Astra model generated and Lean-formalized solutions or substantial advances on ten long-standing problems spanning mathematics and theoretical computer science, including sphere packing, group theory, quantum complexity, lattice cryptography and Ramsey theory. [src]
The discussion treats AI’s progress in mathematics and theoretical computer science as increasingly undeniable and no longer especially surprising, though commenters disagree on whether this reflects genuine intelligence or powerful tool-assisted search and verification [0][4][5][6]. Major concerns focus on opaque evaluation methods—such as undisclosed problem selection, retries, and computing resources—and whether the reported cost is meaningful [2]. Beyond mathematics, commenters debate how AI will affect writing, biology, politics, employment, economic distribution, and personal meaning, with particular alarm over scalable, individualized manipulation [1][7][9].
4. More German than many Germans (mertbulan.com)
647 points · 500 comments · by mertbio
A Turkish software engineer recounts his welcoming experiences in Hamburg, admiration for Germany’s rules, social democracy and historical reckoning, and eventual citizenship after eight years, while acknowledging his privileged start and that others face greater integration challenges. [src]
The discussion largely agrees that Germany offers exceptional stability, fairness, and quality of life, even as immigrants may struggle to feel culturally integrated or find local cultural life compelling [1][2][3]. Commenters contrast this appreciation with concerns about Germany’s political drift toward the far right, economic stagnation, and the risk of alienating immigrants who could strengthen society [3][9]. A humorous bus anecdote illustrates the culture of strict rule-following, which some defend as necessary for safety, liability, and orderly schedules [0][4].
5. SQLite Critical CVEs or LLM Slop? (research.jfrog.com)
726 points · 374 comments · by ymir_e
JFrog researchers found that six supposedly critical SQLite CVEs were likely fabricated or AI-generated, citing nonexistent code and failing PoCs, and warned that weak vulnerability-reporting validation can pollute security databases and misdirect remediation efforts. [src]
Commenters largely agreed that LLM-generated vulnerability reports require rigorous human verification, citing cases where models mistook a code comment for vulnerable code and created substantial wasted effort [0]. They warned that this increases CVE noise and makes legitimate issues harder to identify, even though LLMs may also uncover real vulnerabilities that attackers can exploit [1][5]. The discussion also criticized blanket CVE-patching policies and the CVE system’s tendency to flag vulnerabilities in rarely used components, with zlib’s MiniZip issue offered as an example of costly, largely irrelevant remediation [2][9].
6. Prevent cognitive debt by manually retyping LLM-generated code (ankursethi.com)
539 points · 444 comments · by mpweiher
Developer Ankur Sethi manually retypes LLM-generated code instead of accepting automated edits, sacrificing speed to preserve comprehension, detect mistakes, and maintain a detailed mental map of his projects. [src]
The consensus is that simply retyping LLM-generated code is a poor learning strategy: it encourages memorization rather than intuition, while writing code first and using an LLM for critique or alternatives is seen as more valuable [2][8]. Commenters disagree over whether manual coding remains viable professionally—some emphasize creativity, skill retention, and maintainability risks [0][4], while others argue employers will prioritize the productivity of LLMs regardless of cognitive costs [1][6]. A minority view is that LLMs substantially amplify programmers’ capabilities, making the loss of hands-on coding a worthwhile tradeoff [5].
7. Devtools must be open source (blog.exe.dev)
728 points · 233 comments · by bryanmikaelian
AI agents make open-source developer tools more valuable by letting users directly personalize and maintain their software, reducing the need for traditional configuration and plugin systems. [src]
Commenters broadly agree that open-source devtools enable inspection, fixes, and customization, with LLMs potentially making code exploration and small personal modifications far easier than before [0][3]. However, many dispute replacing conventional configuration and plugin systems with bespoke AI edits, citing wasted compute, fragile behavior, ongoing fork maintenance, and the risk of unreviewed “AI slop” [1][2][7]. Others question whether personalization is useful for most users, warn that the economics of open-source devtools are already difficult, and note that AI could make it even harder for companies to monetize or sustain them [5][6][8].
8. Wind and solar overtake fossil fuels in Germany for the first time (intellinews.com)
378 points · 332 comments · by just_some_user
Germany’s wind and solar power generation surpassed fossil fuels for the first time, marking a milestone for the country’s renewable-energy transition. [src]
Commenters note that wind and solar surpassed fossil fuels over all of 2025, while total electricity generation changed much less and Germany’s industrial output and energy consumption remain important context [0][1]. The main disagreement centers on nuclear: some argue shutting it down increased emissions and costs, while others attribute high prices primarily to the loss of Russian gas and say renewables are now the alternative [3][4][5][8]. Several comments broaden the discussion to reducing meat-related emissions and to thermal storage using sand or bricks for industrial heat and grid stability [2][9].
9. Taylor Farms has rewritten its cyclospora statement four times in sixteen days (marlerblog.com)
304 points · 263 comments · by speckx
We couldn't summarize this story. [src]
Discussion centered on the difficulty of tracing cyclospora when symptoms appear weeks after exposure, with some commenters defending Taylor Farms’ repeated updates as a reasonable response to changing evidence [3], while others viewed the revisions and alleged institutional cuts as signs of poor accountability [1][4]. Commenters broadly criticized weak restaurant transparency—not only for ingredient sourcing, but also for allergen disclosure—sharing personal experiences of being unable to identify food origins or safely order meals [0][2][6]. Others cautioned that small restaurants may lack the resources to meet extensive disclosure requirements and noted that evidence linking CDC cuts to the outbreak response remains unproven [5][8].
10. Bonsai: Janestreet's UI Library (github.com)
390 points · 155 comments · by KolmogorovComp
Bonsai is Jane Street’s OCaml framework for building performant, reactive web and terminal applications with composable state machines, incremental computation, shared types, and expressive automated UI testing. [src]
Commenters welcomed Bonsai’s promise of sharing OCaml types and code between frontend and backend, but noted that compiled-to-JS approaches such as Scala.js, Kotlin/JS, and ClojureScript still face friction integrating with the broader JavaScript ecosystem, often requiring wrappers or bespoke tooling [0][1][6][7]. Some criticized the demo UI’s tight, inconsistent margins, while others argued this likely reflects the samples rather than the library itself [2][3][4]. A related point was that Jane Street’s trader-focused UX deliberately does not follow many conventional software design rules, supported by dedicated UX designers and specialized user needs [9].
11. I stopped trusting USB-C cable labels and started testing them (makeuseof.com)
258 points · 262 comments · by baranul
We couldn't summarize this story. [src]
The consensus is that USB-C’s single connector hides major differences in charging, data speed, and protocol support, forcing buyers to research, label, or test cables themselves [0][9]. Commenters disagree on whether this is an unavoidable tradeoff for keeping one connector—since making every cable support top speeds would mean thick, short, expensive cables [1][8]—or a labeling/specification failure that leaves nontechnical buyers vulnerable [2]. Affordable testers can check continuity and chip reports but not certify high-speed performance, which requires very expensive lab equipment [4][7].
12. Twenty Years of Pandoc (pandoc.org)
420 points · 53 comments · by fiddlosopher
Pandoc creator John MacFarlane commemorates the project’s 20th anniversary by recounting its evolution from a 3,000-line Haskell Markdown converter into a widely used tool supporting 51 input and 76 output formats. [src]
The discussion celebrates Pandoc’s durable design, especially its carefully chosen intermediate representation, which enables extensive reader/writer interoperability [1][4]. Commenters emphasize that Pandoc remains more efficient and reliable than LLM-based conversion for deterministic, large-scale work, while praising its usefulness in daily workflows, static-site generation, and email conversion [1][5][8]. They also highlight its welcoming contributor experience and the remarkable impact of a tool created by a philosophy professor, while acknowledging the ongoing difficulty of maintaining many parsers and renderers [6][7][9].
13. Show HN: Run an 80B Qwen in 4.3 GB of RAM on a Mac, and a 35B on an iPhone (github.com)
311 points · 142 comments · by leonickson
Swiftlet is an open-source Swift and Metal runtime that streams Qwen MoE expert weights from storage, enabling 35B and 80B models to run locally on Apple devices—including an iPhone 17—with as little as 2.5GB and 4.3GB of RAM, respectively. [src]
Commenters split between optimism that experimental local inference will drive hardware and efficiency breakthroughs, and skepticism that SSD-swapped models are practical or representative of real progress. Supporters envision dramatically cheaper consumer hardware enabling very large models, potentially on phones and Macs [0][2][3], while critics highlight drive wear, extremely slow decoding, and prefill bottlenecks [5][7], arguing centralized servers will remain more efficient for most use cases because they can batch parallel requests [6]. Some also question whether scaling to trillion-parameter models on inexpensive SSDs is realistic at all [1][8].
14. Show HN: Isopolis – Isometric pixel map of SF (sf.isopolis.city)
348 points · 81 comments · by nuwandavek
Isopolis is an interactive isometric pixel map of San Francisco featuring 583 mapped areas and places, guided tours, startup and landmark listings, community submissions, and a Silicon Valley-themed radio player. [src]
The project was widely praised as charming, beautiful, and easy to browse, with comparisons to the labor-intensive Floor796 [3][7]. Discussion also highlighted shortcomings: AI-generated imagery can feel soulless on closer inspection [1], contains geographic errors such as roads rendered as lakes and nonexistent ponds [8][9], and flattens San Francisco’s famously hilly terrain while omitting useful details like street names and transit [2]. The creator explained that it uses Google Photorealistic 3D Tiles and AI-generated training imagery, with substantial manual curation to achieve a consistent pixel-art style [0].
15. MiniMax H3 Day-0 Support in ComfyUI: Open Weights, Native Audio, and 2K Video (blog.comfy.org)
334 points · 94 comments · by vblanco
ComfyUI now natively supports MiniMax H3, an open-weights multimodal video model that generates up to 2K, 15-second clips with native stereo audio and can run locally on an RTX 3060 through memory optimizations. [src]
Commenters were impressed by the mouse and other clips, calling the quality a major leap, though some found the output aesthetically bland or noted lingering “AI smoothening” artifacts likely best handled with traditional close-up rendering [5][7]. Performance varies widely by hardware: 10 seconds of 480p video took about 10 minutes on a 4070 Ti Super, three minutes on a 5080, and 68 seconds on a 6000 Pro, with 2K output taking over five minutes even before optimization [0][3][4]. Discussion also focused on whether the model supports genuine technical reasoning beyond art, while contributors explained that replacing timestep-dependent diffusion modulation weights with lookup tables is a
16. Andy Pavlo joins ClickHouse to establish ClickHouse Labs (clickhouse.com)
340 points · 76 comments · by nikolay_sivko
Carnegie Mellon professor Andy Pavlo is joining ClickHouse to lead ClickHouse Labs, a research group focused on advancing database technology, collaborating with engineers and PostgreSQL teams, and exploring how databases can support and benefit from emerging AI and agentic systems. [src]
Discussion centers on whether ClickHouse Labs represents meaningful database research or simply engineering within a database company. Some argue databases qualify as “deep tech” because major theoretical and scalability challenges remain, while others reserve the term for fields like fusion or quantum computing and question the practical value of academic algorithms [1][2][4][7][9]. Pavlo confirmed that his CMU seminar series will continue under ClickHouse sponsorship, while a former student shared how his open-source course helped him secure a database interview despite ultimately not being hired [3][5][8].
17. Branchless Rust: Making a Filter 4x Faster by Removing an If (greyblake.com)
291 points · 111 comments · by greyblake
A Rust benchmark shows replacing an unpredictable filter branch with branchless arithmetic makes the 50%-selectivity case nearly four times faster, though it slows predictable cases and sacrifices some readability. [src]
The discussion largely agreed that removing unpredictable branches can substantially speed up filtering, while noting performance depends on CPU architecture and branch-prediction behavior [4][8]. A more advanced AVX-512 compress implementation reportedly improved throughput by another 25–60%, especially on smaller inputs where memory bandwidth matters less [1], with compiler auto-vectorization and `target-cpu=native` suggested as further avenues [9]. Much of the thread, however, focused on suspicions that the article was AI-generated, driven by its overly dramatic, “Claude-like” prose [0][2][3][5].
18. ICE Collected Nearly 1M People's DNA Last Year–Including Young Children (wired.com)
242 points · 103 comments · by BlueBerry2001
ICE may have submitted nearly 920,000 DNA profiles to the FBI’s criminal database in 2025, including samples from children, despite most detainees having no criminal convictions. [src]
The discussion largely focused on the tension between DNA databases’ potential benefits—identifying missing people, validating family relationships, and aiding investigations—and the risks of government misuse, weak safeguards, and mission creep [0][3][5]. Commenters questioned DNA-match reliability, false positives, and the need for corroborating evidence, noting that a genetic match alone does not prove a crime [1][7]. Some compared national DNA collection favorably to practices in Europe, while others invoked Germany’s privacy protections and apartheid-era record-keeping as warnings about trusting authorities with highly identifying data [2][4][6].
19. Smaller, faster, safer: running Kimi and GLM at scale (blog.cloudflare.com)
267 points · 66 comments · by ascorbic
Cloudflare outlines its approach to deploying smaller, faster, and safer Kimi and GLM AI models at scale through Workers AI, inference optimization, and quantization. [src]
Discussion centered less on the technical content than on the article’s apparently AI-generated, “sloppy” prose, with several commenters wishing HN offered filtering or flagging for AI-written submissions [0][1][2][9]. Technical feedback was mixed: readers appreciated transparency about KV-cache quantization, but wanted broader model testing and coding/tool-use benchmarks, where small errors may compound [4]. Others criticized the missing or hard-to-find Cloudflare pricing [3][5], questioned the lack of K3 support [7], and called the LLM-serving discussion too shallow [8].
Brought to you by ALCAZAR. Protect what matters.