watty

for this project, doesn't look like much effort has gone into sharing assets.

I think that's his point as this article reads like that exact prompt. Pure LLM garbage.

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.

This is great insight, I agree with the author! Check out my [INSERT VIBE CODED GITHUB LINK] which follows these patterns!

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?

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.

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.).

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.

I don't think that's fair. I follow politics closely but prefer HN to stay technical. It shouldn't be offensive.

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.

Agree, if they're going to guilt shame companies publicly and be defensive in replies, just dual license it. Not a great look.

you do realize it already comes with a matrix screensaver, right?

> 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.

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.

deep breaths, everything is going to be okay.

I can't speak for the person(s) you're referring to but at lest on HN it's generally always been anti-political.

The guidelines state:

> Please don't use Hacker News for political or ideological battle. It tramples curiosity.

Come on now, security isn't easy but it's not rocket science. If someone is competent enough to be developing applications they're certainly competent enough to do security correctly by researching first.

I admit I haven't read the article but what's disgusting about incentivizing employee efficiency with prizes?

What's weird to me is that these people aren't forced to work there. They're working there because it's their BEST option.

We had to abandon Lambda due to cold starts. Any news if that's resolved?

To be fair he's just pointing out a fact. If we're going to talk about this then let's get the facts straight.

I do not think he was justified in shooting but I also don't think the cop should face jail time or anything. We need to change our process in handling dangerous events due to swatting. It's the reality we live in.

> Blew them away as soon as they opened the door.

Source?

My point was that "as soon as they opened the door" and "seconds later" are not the same thing. Go watch the body cam or do some research. There were 7-10 seconds with commands being issued to Andrew and he did not comply. Absolutely not his fault, I'm sure it was a very confusing situation. I'm simply pointing out that if we are going to talk about it, let's face the facts and not make bullshit up.

There was an investigation. It was concluded that the victim reached for his waist (maybe to pull up pants) after being told not to. Very very difficult situation for sure.

I'm not sure your point. It's extremely harmful as it caused the death of an individual. The investigation concluded the officer was not in the wrong.

The idea is to reduce complexity as developers can simply provide code and let the service handle everything else.

Unfortunately, the technology isn't there yet and serverless is actually more complex than traditional managing servers.

I've got no VR and no problems. Game infrequently, computer off for weeks at a time. Yes, Steam or Battle.NET will need to install updates but that's just like any console.

I don't mean to take away from Shazam (because I too was amazed when I first used it) but the Pixel phones have Shazam-like ability built in which uses minimal battery and without internet... and it's constantly running any time music plays.

Not really "magic" how it works but still pretty amazing that I can pull the phone out of my pocket any time I hear a song I like and immediately see the band/title.

Developing for the browser is leaner but it's the opposite for end-users. I hope PWAs are the future as well but native is still king for the time being.

Looks great for basic websites but it's missing the biggest and most difficult piece of cloud infrastructure. The DATABASE!

Today you'd have to open up your cloud DB provider to the world since Zeit can't provide a list of IPs to whitelist. This is a showstopper for me unfortunately.

Looks awesome and love the focus on plugins. I also like some of the choices made, Redux, React Router, Security, etc. but going with Flow??

Our company has standardized on Typescript, it has practically "won". Unfortunately for me, introducing Flow would get shot down.

That's like saying "electric cars are never happening". Both already are happening.