frontpage.
newsnewestaskshowjobs

Made with ♥ by @iamnishanth

Open Source @Github

fp.

They were drawn to Korea with dreams of K-pop stardom – but then let down

https://www.bbc.com/news/articles/cvgnq9rwyqno
1•breve•49s ago•0 comments

Show HN: AI-Powered Merchant Intelligence

https://nodee.co
1•jjkirsch•3m ago•0 comments

Bash parallel tasks and error handling

https://github.com/themattrix/bash-concurrent
1•pastage•3m ago•0 comments

Let's compile Quake like it's 1997

https://fabiensanglard.net/compile_like_1997/index.html
1•billiob•4m ago•0 comments

Reverse Engineering Medium.com's Editor: How Copy, Paste, and Images Work

https://app.writtte.com/read/gP0H6W5
1•birdculture•9m ago•0 comments

Go 1.22, SQLite, and Next.js: The "Boring" Back End

https://mohammedeabdelaziz.github.io/articles/go-next-pt-2
1•mohammede•15m ago•0 comments

Laibach the Whistleblowers [video]

https://www.youtube.com/watch?v=c6Mx2mxpaCY
1•KnuthIsGod•16m ago•1 comments

Slop News - HN front page right now hallucinated as 100% AI SLOP

https://slop-news.pages.dev/slop-news
1•keepamovin•21m ago•1 comments

Economists vs. Technologists on AI

https://ideasindevelopment.substack.com/p/economists-vs-technologists-on-ai
1•econlmics•23m ago•0 comments

Life at the Edge

https://asadk.com/p/edge
2•tosh•29m ago•0 comments

RISC-V Vector Primer

https://github.com/simplex-micro/riscv-vector-primer/blob/main/index.md
3•oxxoxoxooo•32m ago•1 comments

Show HN: Invoxo – Invoicing with automatic EU VAT for cross-border services

2•InvoxoEU•33m ago•0 comments

A Tale of Two Standards, POSIX and Win32 (2005)

https://www.samba.org/samba/news/articles/low_point/tale_two_stds_os2.html
2•goranmoomin•36m ago•0 comments

Ask HN: Is the Downfall of SaaS Started?

3•throwaw12•38m ago•0 comments

Flirt: The Native Backend

https://blog.buenzli.dev/flirt-native-backend/
2•senekor•39m ago•0 comments

OpenAI's Latest Platform Targets Enterprise Customers

https://aibusiness.com/agentic-ai/openai-s-latest-platform-targets-enterprise-customers
1•myk-e•42m ago•0 comments

Goldman Sachs taps Anthropic's Claude to automate accounting, compliance roles

https://www.cnbc.com/2026/02/06/anthropic-goldman-sachs-ai-model-accounting.html
3•myk-e•44m ago•5 comments

Ai.com bought by Crypto.com founder for $70M in biggest-ever website name deal

https://www.ft.com/content/83488628-8dfd-4060-a7b0-71b1bb012785
1•1vuio0pswjnm7•45m ago•1 comments

Big Tech's AI Push Is Costing More Than the Moon Landing

https://www.wsj.com/tech/ai/ai-spending-tech-companies-compared-02b90046
4•1vuio0pswjnm7•47m ago•0 comments

The AI boom is causing shortages everywhere else

https://www.washingtonpost.com/technology/2026/02/07/ai-spending-economy-shortages/
2•1vuio0pswjnm7•49m ago•0 comments

Suno, AI Music, and the Bad Future [video]

https://www.youtube.com/watch?v=U8dcFhF0Dlk
1•askl•51m ago•2 comments

Ask HN: How are researchers using AlphaFold in 2026?

1•jocho12•54m ago•0 comments

Running the "Reflections on Trusting Trust" Compiler

https://spawn-queue.acm.org/doi/10.1145/3786614
1•devooops•59m ago•0 comments

Watermark API – $0.01/image, 10x cheaper than Cloudinary

https://api-production-caa8.up.railway.app/docs
1•lembergs•1h ago•1 comments

Now send your marketing campaigns directly from ChatGPT

https://www.mail-o-mail.com/
1•avallark•1h ago•1 comments

Queueing Theory v2: DORA metrics, queue-of-queues, chi-alpha-beta-sigma notation

https://github.com/joelparkerhenderson/queueing-theory
1•jph•1h ago•0 comments

Show HN: Hibana – choreography-first protocol safety for Rust

https://hibanaworks.dev/
5•o8vm•1h ago•1 comments

Haniri: A live autonomous world where AI agents survive or collapse

https://www.haniri.com
1•donangrey•1h ago•1 comments

GPT-5.3-Codex System Card [pdf]

https://cdn.openai.com/pdf/23eca107-a9b1-4d2c-b156-7deb4fbc697c/GPT-5-3-Codex-System-Card-02.pdf
1•tosh•1h ago•0 comments

Atlas: Manage your database schema as code

https://github.com/ariga/atlas
1•quectophoton•1h ago•0 comments
Open in hackernews

Why Open Source Maintainers Thrive in the LLM Era

https://mikemcquaid.com/why-open-source-maintainers-thrive-in-the-llm-era/
3•mikemcquaid•8mo ago

Comments

mikemcquaid•8mo ago
I've been thinking for a while about what it was about my experience of LLMs that differed so much from some of the naysaying I hear. I feel like my ~16 years experience reviewing PRs on Homebrew makes reviewing LLM output feel easier and similar.

Interested if any other maintainers have a similar experience?

latexr•8mo ago
> Interested if any other maintainers have a similar experience?

Daniel Stenberg definitely hasn’t.

https://www.linkedin.com/posts/danielstenberg_hackerone-curl...

latexr•8mo ago
> All that said, I’d rather hire someone today who overuses LLM tooling over someone who refuses to use any. Ultimately, as technologists in a for-profit company within a capitalist economy, we are hired to generate business value. (…) The LLMs aren’t going to take your software job, but they will let you be better at it.

This is a contender for the most disappointing writing I’ve ever seen from Mike (which isn’t a regular occurrence). It completely misses so many important factors which have been discussed ad nauseam, such that someone abusing LLM tooling today—especially a junior—is crippling their own learning. But all those arguments pale on the face of this blatant embrace for profit above all. I’m profoundly saddened these are the views of someone who is at the helm of one of the most popular open-source projects currently.

The whole article lacks any valuable insight and reeks of the “my business uses AI” hype so many companies are chasing just to be valued and get attention. This is not about “open source maintainers” in general, as the title suggests, but about Mike’s personal experience.

> Let’s build some cool shit (and faster than we could in 2020).

No, let’s not. Let’s go build some stable shit for once. Everything is broken, and you’re partying like breaking everything some more is a good thing.

LLMs are a tool. They can help someone drive a nail through a piece of wood or their own hand. You can use them right or wrong, effectively or ineffectively. But you’re fawning over them like it’s all a panacea and completely ignoring how many people are proudly and ignorantly using them wrong. One day, not too far now, one of those people is going to drive a nail through your hand.

mikemcquaid•8mo ago
> such that someone abusing LLM tooling today—especially a junior—is crippling their own learning

I don't agree with this if they follow the guidelines I've discussed in this post about e.g. actually reviewing and ensuring they understand the output of the LLMs.

> This is not about “open source maintainers” in general, as the title suggests, but about Mike’s personal experience.

You'll be unsurprised to hear I gently disagree here. It's not based just on my experience but the (very mixed) experiences of my peers. Those who are good at code review do seem to be having a better time with LLMs.

> Everything is broken, and you’re partying like breaking everything some more is a good thing.

My experience with LLMs has been that they help me fix broken things more quickly than before LLMs. Again, as I mention in the post, if you're not reviewing the output here: you're doing it wrong.

> You can use them right or wrong, effectively or ineffectively.

Exactly. This post tries to explain how to use them effectively, something I find OSS maintainers find easier.

latexr•8mo ago
All of your answers were already addressed in my previous comment:

> [You are] completely ignoring how many people are proudly and ignorantly using them wrong.

The point is precisely that too many people are never going to verify outputs and will even resist any kind of human review to their LLM-generated code. This is not theoretical, we know this is happening. Which would be fine in a “you do you” manner if what those people did only affected them, but it affects everyone else too. Because we don’t write every software we use, and some day soon we’ll be bitten by one of these idiots who introduced a major security flaw in some system we’re forced to use (e.g. government website).

In other words, what I’m objecting to is precisely the narrow view of this article in unambiguously propping up the good parts and being blind to the bad parts, even criticising those who have a concern for the bad.

mikemcquaid•8mo ago
Yup, that’s fair. Maybe I’m being overly optimistic to think that we can get to established best practises that the vast majority of engineers will follow. Time will tell, I guess.