Recent submissions

Comment · 6 months ago
Why does the commit editor hide the coauthored message? Why not pre-populate the text field and users take or leave it when committing?
Comment · 6 months ago
I agree with the sentiment on many of these comments. Understanding something is work and that can’t be offloaded to others or even LLMs.
Comment · 6 months ago
OpenClaw can just rebrand again, problem solved!
Comment · 6 months ago
Isn’t this still true for the large language models and math is detected and handled by an external tool? Anything you can give as a source for the latest state of the art?
Comment · 7 months ago
One reason is that AI can create PRs at a scale that can just overwhelm maintainers not to mention drowning out non-AI PRs.
Comment · 7 months ago
Why can’t people add a disclaimer when their text was written or edited with AI? That is my completely unrealistic wish for the world today…
Comment · 7 months ago
Definitely goes back earlier for software. See the Mythical Man Month… Growing a team imposes a communication cost.
Comment · 10 months ago
This account seems like LLM slop looking at the post history. Who starts every post ‘from Japan’?

I don’t want to interact with hidden chat bots on HN. The irony of this comment about accountability is also frustrating.

Comment · 10 months ago
Merry Christmas hackers!
Comment · 10 months ago
Sending power outage context to the vehicles does not seem like enough of a response. I hope at least they have internal plans for more. For large, complex systems, you want multiple layers of protections. The response feels way too reactive when they could use this incident to guide improvements across the board.
Comment · 1 year ago
Maybe I’m just a skeptic, but it seems like a software engineer or SRE familiar with the application should be able to come to the conclusion of load testing fairly easily. For sure not as fast like 80 seconds though which is impressive. As noted you still need an engineer to review the data and complete those proposed action items.
Comment · 2 years ago
I think the idea is you could still have a page in the UI that shows archived data but you wouldn’t do that normally with a soft delete. The lifecycle thing makes it up front with the user instead of hiding soft delete as an implementation detail.
Comment · 3 years ago
What was the password length? How many iterations were used?
Comment · 4 years ago
In Visual Studio if you drag the execution arrow up, it will rewind to that point. It works really well. It’s okay especially useful when you step over a line you wanted to step into instead.

Live from the official Hacker News API

A modern reader for Hacker News · SvelteKit + Skeleton