frontpage.
newsnewestaskshowjobs

Made with ♥ by @iamnishanth

Open Source @Github

Benchmarking Is Hard Sometimes (postgresql)

https://vondra.me/posts/benchmarking-is-hard-sometimes/
1•biehl•1m ago•0 comments

Passkey Deployment Checklist

https://web.dev/articles/passkey-checklist
1•vdelitz•2m ago•0 comments

Save Millions on Your Cloud Bill: 11 Strategies for Kubernetes Cost Optimization

https://blog.cleancompute.net/p/kubernetes-cost-optimization
2•nibir•4m ago•0 comments

Show HN: TypeBridge – Compile-time RPC for client/server

https://github.com/uptownhr/TypeBridge
1•uptownhr•7m ago•0 comments

Tackling performance issues caused by load from bots

https://progress.opensuse.org/news/125
3•fionera•8m ago•0 comments

Show HN: Bulktopus – Generate All Your Ad and Social Media Images 10x Faster

https://www.bulktopus.com/
1•fer_momento•9m ago•0 comments

Contrastive Flow Matching

https://arxiv.org/abs/2506.05350
1•badmonster•12m ago•1 comments

Show HN: Posture Correction Using AirPods Motion Sensors

https://github.com/wizenheimer/workwell
2•tinylm•12m ago•0 comments

Show HN: Restore Per-App Keyboard Input Language on macOS

https://gitlab.com/spacest/InputLanguageKeeper
1•rado•14m ago•0 comments

Twilio – Intentionally Clever or Accidentally Genius?

https://ramansharma.substack.com/p/twilio-intentionally-clever-or-accidentally
1•intrepidsoldier•15m ago•0 comments

Russian billionaire: SAP replacement is expensive but essential

https://energynews.oedigital.com/energy-markets/2025/06/03/russian-billionaire-sap-replacement-is-expensive-but-essential
1•teleforce•16m ago•0 comments

Ruby Newsletter 472

https://ruby.libhunt.com/newsletter/472
1•amalinovic•16m ago•0 comments

We Built Cline to Never Hold You Hostage

https://cline.bot/blog/why-we-built-cline-to-never-hold-you-hostage
3•howtofly•18m ago•0 comments

Photoshop Arrives on Android

https://blog.adobe.com/en/publish/2025/06/03/photoshop-arrives-on-android
1•teleforce•19m ago•0 comments

Musk tweets that Trump is named in Epstein files

https://www.cnn.com/2025/06/06/politics/trump-musk-epstein-files-accusation
2•strogonoff•21m ago•0 comments

Silicon Valley Is Starting to Pick Sides in Musk and Trump's Breakup

https://www.wired.com/story/musk-trump-feud-venture-capitalists-pick-sides/
2•beardyw•23m ago•0 comments

Maker of 'Most Complex Machine Humans Ever Created' Is Navigating Trade Fights

https://www.nytimes.com/2025/06/05/technology/asml-chips-tariffs-trade.html
1•doener•28m ago•0 comments

This is Water by David Foster Wallace (Full Transcript and Audio)

https://fs.blog/david-foster-wallace-this-is-water/
1•rendx•33m ago•0 comments

Obsidian 1.9.2 brings breaking changes

https://www.neowin.net/news/obsidian-192-brings-breaking-changes-ui-improvements-and-several-bug-fixes/
1•bundie•33m ago•0 comments

People Keep Inventing Prolly Trees

https://www.dolthub.com/blog/2025-06-03-people-keep-inventing-prolly-trees/
2•thunderbong•35m ago•0 comments

Tesla share plunge amid Trump feud wipes $152B off Elon Musk's company

https://www.theguardian.com/technology/2025/jun/05/tesla-share-drop-trump-musk-feud
1•beardyw•38m ago•0 comments

Australian Navy ship accidentally blocks WiFi across parts of New Zealand

https://www.theguardian.com/australia-news/2025/jun/06/australian-navy-ship-accidentally-blocks-wifi-across-parts-of-new-zealand
1•defrost•45m ago•0 comments

OpenBSD Hackathon Japan 2025

https://rsadowski.de/posts/2025/j2k25-japan-openbsd-hackathon/
1•damir•45m ago•0 comments

MLX-based LLM inference engine for macOS with native Swift implementation

https://github.com/Trans-N-ai/swama
1•jovezhong•50m ago•1 comments

Second ispace craft has probably crash-landed on Moon

https://www.nature.com/articles/d41586-025-01751-3
1•politelemon•52m ago•1 comments

The Automaker Wars No One Talks About

https://www.carsandhorsepower.com/featured/the-automaker-wars-no-one-talks-about-niche-competitions-in-weird-segments
1•Anumbia•53m ago•0 comments

How Anthropic teams use Claude Code [pdf]

https://www-cdn.anthropic.com/58284b19e702b49db9302d5b6f135ad8871e7658.pdf
1•ChrisArchitect•56m ago•0 comments

I Learned Rust in 24 Hours to Eat Free Pizza Morally

https://medium.com/@sebastiancarlos/i-learned-rust-in-24-hours-to-eat-free-pizza-morally-28ea8312e523
1•todsacerdoti•57m ago•0 comments

OpenAI CEO Sam Altman says AI is ready for entry-level jobs

https://fortune.com/2025/06/05/openai-ceo-sam-altman-ai-as-good-as-interns-entry-level-workers-gen-z-embrace-technology/
3•01-_-•1h ago•3 comments

Google confirms more ads on your paid YouTube Premium Lite soon

https://www.neowin.net/news/google-confirms-more-ads-on-your-paid-youtube-premium-lite-soon/
2•01-_-•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•1d ago

Comments

mikemcquaid•1d 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•1d ago
> Interested if any other maintainers have a similar experience?

Daniel Stenberg definitely hasn’t.

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

latexr•1d 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•1d 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•1d 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•1d 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.