Recent submissions

Comment · 5 days ago
for this project, doesn't look like much effort has gone into sharing assets.
Comment · 13 days ago
I think that's his point as this article reads like that exact prompt. Pure LLM garbage.
Comment · 1 month ago
Session limits are obnoxious and make Codex much less useful for me. I tend to code in spurts when I find some time and the $20 weekly limit was reasonable for my side projects.

I'm now hitting the session limits which means I can either purchase another plan, upgrade, or move off of Codex.

Comment · 2 months ago
This is great insight, I agree with the author! Check out my [INSERT VIBE CODED GITHUB LINK] which follows these patterns!
Comment · 2 months ago
I'm sorry, maybe I'm out of the loop.

David said he wants an open group no one cares about politics or whatever you support, you are welcome to join.

Seems pretty inclusive?

Comment · 2 months ago
Really? I feel the opposite.

Earlier today our app, used by a handful of actual production customers, went down for 30 minutes due to a GCP migration to a new project and we screwed up a secret in prod. This was an all hands on deck firedrill with 5 whys and incident reports and chaos.

Github has been having major production outages routinely! There are companies who can't release, can't build, can't view issues, basically can't work. I'd imagine most orgs using Github have been forced to move off of them or create an alternate approach to actually get shit done.

Comment · 4 months ago
Just to clarify, and I know you weren't saying they are related, but this has absolutely nothing to do with AI or vibe coding or manager code.

It's a continuation of the Shai Halud worm and the lack of security around developer dependnecy installations, which has existed for a very long time.

Hackers have figured out that developers themselves are an ideal target due to how easy it is to trick them into installing something and how much private information they have on their machines (creds, cloud clis, mcps, etc.).

Comment · 7 months ago
I see the problem everyday and am just playing devil's advocate but it doesn't really do a good job explaining the "why".

They hint at Django being a different level of quality compared to other software, wanting to cultivate community, and go slowly.

It doesn't explain why LLM usage reduces quality or they can't have a strong community with LLM contributions.

The problem is that good developers using LLM is not a problem. They review the code, they implement best practices, they understand the problems and solutions. The problem is bad developers contributing - just as it always has been. The problem is that LLMs enable bad developers to contribute more - thus an influx of crap contributions.

Comment · 9 months ago
I don't think that's fair. I follow politics closely but prefer HN to stay technical. It shouldn't be offensive.
Comment · 11 months ago
I've never had a good experience with individual metrics leaderboards. On one team we had a JIRA story point tracker shown on a tv by a clueless exec. Devs did everything they could to game the system and tasks that required uncertainty (hard tasks) went undone. I believe it contributed to the cog culture that caused an exodus of developers.

However, I love the idea of an occasional team based leaderboard for an event. I've held bug and security hackathons with teams of 3-5 and have had no problem with them.

Comment · 1 year ago
Agree, if they're going to guilt shame companies publicly and be defensive in replies, just dual license it. Not a great look.
Comment · 1 year ago
you do realize it already comes with a matrix screensaver, right?
Comment · 1 year ago
> But Omarchy is a reminder that we live in a world where software isn’t just software, but the people who make it.

I get people are totally within their rights to ban movies/software/sports, etc. for creators whose beliefs they disagree with. However, software is the people who make it? I rarely, if ever, know the authors who create software or what they believe in.

Comment · 1 year ago
Not shocking, a lot of time goes into making Vite and they need to make money.

One approach is to setup consulting services. Looks like Void Zero's approach is to start building value-add tools and features on top of Vite that are no longer free.

The decision that users must make now is whether it's worth the risk investing in Vite, assuming that more and more functionality will move to the paid tier.

Live from the official Hacker News API

A modern reader for Hacker News · SvelteKit + Skeleton