I'm not a shadcn user, and so as with any project I'm not familiar with, I'm looking to see if if it's interesting to me. If the post is thoughtful and clear and I like the sense I get of their perspective on programming, then great, tell me more. No guarantees but maybe the writer is someone whose software I'd like to use. Claude doesn't tell me anything except that the writer used Claude.
It's the same as with too marketing-speak, which conceivably this is. Maybe the actual work is good but Sturgeon's law, it's probably crud. If I really needed a UI library or whatever right now then maybe I'd dig deeper but in casual browsing HN mode? No time, catch them later.
So maybe all your maybes but who cares? It's not AI that made me think badly of them: I think badly of all software by default and it takes more than Claude to change my mind.
Usually there's one or two job responsibilities among many, that you can do, but not the way everyone else does them. The ADA requires employers to make reasonable accommodations, and some employers don't want to.
So less, the job requires you to stand all day, and more, once a week or so they ask you make a binder of materials, and the hole puncher they want you to use dislocates your hands (true story). Or, it's a desk job, but you can't get from your desk to the bathroom in your wheelchair unless they widen the aisles between desks (hypothetical).
If the goal to drive the yield on T-notes down, then cut spending and raise taxes. Get the budget into something like balance and the Fed will cut rates, and borrowing costs will fall. You don't need some 3D chess with a manufactured financial crisis.
When your rational explanation involves people shooting themselves in the head to cure a headache, something's off. There's nothing to explain here besides a weak and incompetent leader with a deep need for attention, surrounded by lots of enablers.
> And it’s a healthy wake-up call when someone who knows close to nothing about our fancy stuff designs a system that we would unlikely think of.
I can't tell if the author asked Kasia how she came up with the idea? For all we know she's doing an MBA in the evenings and just wrote a paper on the history of just-in-time manufacturing in the Japanese auto industry.
Not sure why you’re fighting this so hard, but: GW, Triboro, Whitestone, Throgs Neck, Goethals, Outerbridge, Holland Tunnel, Lincoln Tunnel. Only the last two land in the toll zone. So yes, “most,” and it’s not especially close.
I’m not counting the Brooklyn Bridge, etc, because I was replying to your “ways to enter the city.” The topic as I understood it was “will you pay this toll if your final destination isn’t Manhattan,” and the answer is “Not unless you’re coming from certain parts of New Jersey, and even then you’ve got choices.”
You wouldn’t want it in the CI pipeline, because any model clever enough to find real issues is also going to find plenty of false positives. That seems like too much friction for most open source projects.
I’m not one of the downvoters, but you’ve linked to a list of forty or fifty different projects, many of which don’t seem relevant to this use-case. It’s not too surprising people have nothing to say besides “ugh, more AI hype.”
It’s Manhattan below 60th, not all of Manhattan, so maybe half the island, and it doesn’t include the FDR. Most of the ways to get to Queens, Brooklyn or Staten Island by car won’t be affected — same for the Bronx obviously.
Have a goal, and measure your progress towards that goal. If "get stronger" is enough, great; but if not, find some challenging activity you enjoy and want to improve at, and do the resistance training that will help you get better. Personally I find that much more motivating; just knowing there are health benefits never really did it for me.
Really really important to write down what you do. Progress is not always fast, but if you keep records, you'll see it, and that really helps with motivation.
IMO podcasts and such are not so good for strength training specifically, though for endurance work they're fine. You really want to give full intensity to getting through that last rep (with good form). You're training your ability to push through discomfort as much as you are your muscle's theoretical inherent strength.
Counterpoint from someone better informed about bipolar would be interesting and valuable. That said, it’s a discussion of an article asking “why is this guy like this?” One potential partial explanation is a mental health condition. Certainly it crosses my mind any time there’s a consistent and self-destructive pattern of behavior that it’s not clear the person involved can control.
I don’t know what’s served by pretending otherwise. If mental health challenges are real and important, and they are, then they’ll have observable effects outside a doctor’s office, and we should be able to talk about that.
Can't speak for what the person you're replying to meant (lol), but no, of course it's not nearly that stark. There's a continuum. Concrete everyday topic that comes up frequently? Everyone's going to know what they mean by what they say there. But we've all been in business meetings where people were just putting words together in a plausible way; we've probably all been the people speaking at those meetings.
The fact that it's possible to say things that make no sense, without knowing that they make no sense, proves the point. You or I can come up with a phrase like "the barber of Seville shaves all the people who do not shave themselves," and we can come up with paradoxical phrases without realizing that they are nonsensical. Neither of those would be possible if there were always a strict, one-to-one relationship between speech utterances and facts about the world.
Sometimes we have a specific idea of what we mean by what we say, sometimes we're just putting words together, often it's somewhere in between.
I don't know what the response time usually is in urgent cases, do you? There's a quote on pg 16 of the study that makes same-day sound unremarkable. It starts:
> A lot of times the people who have their weapons seized are not having a bad life—they’re having a bad moment.
It's an ex-prosecutor's illustrative hypothetical, so take it for what it's worth. Still the same logic applies if we're talking about bad weeks instead of bad evenings.
Thanks for the link to the paper. But I don't think that 10-20 seizures per prevented suicide estimate you mention can tell us anything about probable cause or the lack thereof. It's a guess at the rate of prevented deaths from suicide attempts, when the subject used a something other than a gun, but would have used a gun if the cops hadn't taken it from them. It's not an estimate of how many suicide attempts were prevented: it's just a measure of how much less deadly the suicide attempts that happened anyway were. A gun seizure is a big dramatic intervention; it's pretty plausible that it sometimes interrupts a bad moment that's essentially a one-off, and sometimes leads to people getting the help they need. Neither of those effects play into the estimate you cited.
Just on the legal standard: it's probable cause that there's a risk, not probable cause that the risky event will happen. If you have 51% certainty that the subject has a 25% chance of harming themselves or someone else, that is likely to be good enough. And while it gives me no joy to defend the US criminal justice system, to me that's appropriate here. Living with someone who's making violent threats towards you or themselves is no fun at all, even if there's only a 1 in 4 chance that they'll follow through.
Nowhere anywhere ever has perfectly and strictly enforced all its laws, or even come particularly close. Prosecutorial discretion isn't something the US invented.
I use nix-shell, and mostly I love it. But it’s important to be aware that the above means “Go get the latest(*) versions of python, pillow and ansicolor and run this code in an environment where they’re available.” It doesn’t do any version-pinning of your dependencies. That might be what you want, but maybe not: it’s frustrating when a script that worked yesterday won’t work today, or will only work after some big download.
My own rule of thumb is that nix-shell is great for quick one-offs and for sharing environments. For local tools and anything else I’m sharing with my future self, it’s usually better to write a nix expression and install it, which gives me access to Nix’s (excellent) rollback system, and lets me upgrade on my schedule, not upstream’s.
* - ‘Latest’ according to whatever Nix channel checkout currently applies. Which you can change, of course, but the point is it’s external to the script.
It’s a great choice for the JS ecosystem for the same reason it’s a terrible choice for the JS ecosystem: JS dependencies are a lot, and they sometimes want to do strange things at install-time that Nix frowns upon. There’s definitely an upfront cost, and a maintenance burden as well. But the flexibility and the control over what code you’re actually running could still be worth it.
It's the same as with too marketing-speak, which conceivably this is. Maybe the actual work is good but Sturgeon's law, it's probably crud. If I really needed a UI library or whatever right now then maybe I'd dig deeper but in casual browsing HN mode? No time, catch them later.
So maybe all your maybes but who cares? It's not AI that made me think badly of them: I think badly of all software by default and it takes more than Claude to change my mind.