frontpage.
newsnewestaskshowjobs

Made with ♥ by @iamnishanth

Open Source @Github

fp.

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•23s ago•0 comments

Atlas: Manage your database schema as code

https://github.com/ariga/atlas
1•quectophoton•3m ago•0 comments

Geist Pixel

https://vercel.com/blog/introducing-geist-pixel
1•helloplanets•5m ago•0 comments

Show HN: MCP to get latest dependency package and tool versions

https://github.com/MShekow/package-version-check-mcp
1•mshekow•13m ago•0 comments

The better you get at something, the harder it becomes to do

https://seekingtrust.substack.com/p/improving-at-writing-made-me-almost
2•FinnLobsien•15m ago•0 comments

Show HN: WP Float – Archive WordPress blogs to free static hosting

https://wpfloat.netlify.app/
1•zizoulegrande•16m ago•0 comments

Show HN: I Hacked My Family's Meal Planning with an App

https://mealjar.app
1•melvinzammit•17m ago•0 comments

Sony BMG copy protection rootkit scandal

https://en.wikipedia.org/wiki/Sony_BMG_copy_protection_rootkit_scandal
1•basilikum•19m ago•0 comments

The Future of Systems

https://novlabs.ai/mission/
2•tekbog•20m ago•1 comments

NASA now allowing astronauts to bring their smartphones on space missions

https://twitter.com/NASAAdmin/status/2019259382962307393
2•gbugniot•24m ago•0 comments

Claude Code Is the Inflection Point

https://newsletter.semianalysis.com/p/claude-code-is-the-inflection-point
3•throwaw12•26m ago•1 comments

Show HN: MicroClaw – Agentic AI Assistant for Telegram, Built in Rust

https://github.com/microclaw/microclaw
1•everettjf•26m ago•2 comments

Show HN: Omni-BLAS – 4x faster matrix multiplication via Monte Carlo sampling

https://github.com/AleatorAI/OMNI-BLAS
1•LowSpecEng•27m ago•1 comments

The AI-Ready Software Developer: Conclusion – Same Game, Different Dice

https://codemanship.wordpress.com/2026/01/05/the-ai-ready-software-developer-conclusion-same-game...
1•lifeisstillgood•29m ago•0 comments

AI Agent Automates Google Stock Analysis from Financial Reports

https://pardusai.org/view/54c6646b9e273bbe103b76256a91a7f30da624062a8a6eeb16febfe403efd078
1•JasonHEIN•32m ago•0 comments

Voxtral Realtime 4B Pure C Implementation

https://github.com/antirez/voxtral.c
2•andreabat•35m ago•1 comments

I Was Trapped in Chinese Mafia Crypto Slavery [video]

https://www.youtube.com/watch?v=zOcNaWmmn0A
2•mgh2•41m ago•0 comments

U.S. CBP Reported Employee Arrests (FY2020 – FYTD)

https://www.cbp.gov/newsroom/stats/reported-employee-arrests
1•ludicrousdispla•42m ago•0 comments

Show HN: I built a free UCP checker – see if AI agents can find your store

https://ucphub.ai/ucp-store-check/
2•vladeta•48m ago•1 comments

Show HN: SVGV – A Real-Time Vector Video Format for Budget Hardware

https://github.com/thealidev/VectorVision-SVGV
1•thealidev•49m ago•0 comments

Study of 150 developers shows AI generated code no harder to maintain long term

https://www.youtube.com/watch?v=b9EbCb5A408
1•lifeisstillgood•50m ago•0 comments

Spotify now requires premium accounts for developer mode API access

https://www.neowin.net/news/spotify-now-requires-premium-accounts-for-developer-mode-api-access/
1•bundie•52m ago•0 comments

When Albert Einstein Moved to Princeton

https://twitter.com/Math_files/status/2020017485815456224
1•keepamovin•54m ago•0 comments

Agents.md as a Dark Signal

https://joshmock.com/post/2026-agents-md-as-a-dark-signal/
2•birdculture•55m ago•0 comments

System time, clocks, and their syncing in macOS

https://eclecticlight.co/2025/05/21/system-time-clocks-and-their-syncing-in-macos/
1•fanf2•57m ago•0 comments

McCLIM and 7GUIs – Part 1: The Counter

https://turtleware.eu/posts/McCLIM-and-7GUIs---Part-1-The-Counter.html
2•ramenbytes•1h ago•0 comments

So whats the next word, then? Almost-no-math intro to transformer models

https://matthias-kainer.de/blog/posts/so-whats-the-next-word-then-/
1•oesimania•1h ago•0 comments

Ed Zitron: The Hater's Guide to Microsoft

https://bsky.app/profile/edzitron.com/post/3me7ibeym2c2n
2•vintagedave•1h ago•1 comments

UK infants ill after drinking contaminated baby formula of Nestle and Danone

https://www.bbc.com/news/articles/c931rxnwn3lo
1•__natty__•1h ago•0 comments

Show HN: Android-based audio player for seniors – Homer Audio Player

https://homeraudioplayer.app
3•cinusek•1h ago•2 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.