frontpage.
newsnewestaskshowjobs

Made with ♥ by @iamnishanth

Open Source @Github

fp.

Replacing Obsidian with Neovim

https://linkarzu.com/posts/neovim/markdown-setup-2025/
1•feel-ix-343•29s ago•0 comments

Velocity of Money

https://en.wikipedia.org/wiki/Velocity_of_money
1•gurjeet•2m ago•0 comments

Stop building automations. Start running your business

https://www.fluxtopus.com/automate-your-business
1•valboa•6m ago•1 comments

You can't QA your way to the frontier

https://www.scorecard.io/blog/you-cant-qa-your-way-to-the-frontier
1•gk1•7m ago•0 comments

Show HN: PalettePoint – AI color palette generator from text or images

https://palettepoint.com
1•latentio•8m ago•0 comments

Robust and Interactable World Models in Computer Vision [video]

https://www.youtube.com/watch?v=9B4kkaGOozA
1•Anon84•12m ago•0 comments

Nestlé couldn't crack Japan's coffee market.Then they hired a child psychologist

https://twitter.com/BigBrainMkting/status/2019792335509541220
1•rmason•13m ago•0 comments

Notes for February 2-7

https://taoofmac.com/space/notes/2026/02/07/2000
2•rcarmo•14m ago•0 comments

Study confirms experience beats youthful enthusiasm

https://www.theregister.com/2026/02/07/boomers_vs_zoomers_workplace/
2•Willingham•21m ago•0 comments

The Big Hunger by Walter J Miller, Jr. (1952)

https://lauriepenny.substack.com/p/the-big-hunger
2•shervinafshar•23m ago•0 comments

The Genus Amanita

https://www.mushroomexpert.com/amanita.html
1•rolph•27m ago•0 comments

We have broken SHA-1 in practice

https://shattered.io/
9•mooreds•28m ago•2 comments

Ask HN: Was my first management job bad, or is this what management is like?

1•Buttons840•29m ago•0 comments

Ask HN: How to Reduce Time Spent Crimping?

2•pinkmuffinere•30m ago•0 comments

KV Cache Transform Coding for Compact Storage in LLM Inference

https://arxiv.org/abs/2511.01815
1•walterbell•35m ago•0 comments

A quantitative, multimodal wearable bioelectronic device for stress assessment

https://www.nature.com/articles/s41467-025-67747-9
1•PaulHoule•37m ago•0 comments

Why Big Tech Is Throwing Cash into India in Quest for AI Supremacy

https://www.wsj.com/world/india/why-big-tech-is-throwing-cash-into-india-in-quest-for-ai-supremac...
1•saikatsg•37m ago•0 comments

How to shoot yourself in the foot – 2026 edition

https://github.com/aweussom/HowToShootYourselfInTheFoot
1•aweussom•37m ago•0 comments

Eight More Months of Agents

https://crawshaw.io/blog/eight-more-months-of-agents
4•archb•39m ago•0 comments

From Human Thought to Machine Coordination

https://www.psychologytoday.com/us/blog/the-digital-self/202602/from-human-thought-to-machine-coo...
1•walterbell•40m ago•0 comments

The new X API pricing must be a joke

https://developer.x.com/
1•danver0•41m ago•0 comments

Show HN: RMA Dashboard fast SAST results for monorepos (SARIF and triage)

https://rma-dashboard.bukhari-kibuka7.workers.dev/
1•bumahkib7•41m ago•0 comments

Show HN: Source code graphRAG for Java/Kotlin development based on jQAssistant

https://github.com/2015xli/jqassistant-graph-rag
1•artigent•46m ago•0 comments

Python Only Has One Real Competitor

https://mccue.dev/pages/2-6-26-python-competitor
4•dragandj•47m ago•0 comments

Tmux to Zellij (and Back)

https://www.mauriciopoppe.com/notes/tmux-to-zellij/
1•maurizzzio•48m ago•1 comments

Ask HN: How are you using specialized agents to accelerate your work?

1•otterley•50m ago•0 comments

Passing user_id through 6 services? OTel Baggage fixes this

https://signoz.io/blog/otel-baggage/
1•pranay01•50m ago•0 comments

DavMail Pop/IMAP/SMTP/Caldav/Carddav/LDAP Exchange Gateway

https://davmail.sourceforge.net/
1•todsacerdoti•51m ago•0 comments

Visual data modelling in the browser (open source)

https://github.com/sqlmodel/sqlmodel
1•Sean766•53m ago•0 comments

Show HN: Tharos – CLI to find and autofix security bugs using local LLMs

https://github.com/chinonsochikelue/tharos
1•fluantix•54m 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.