Siri is how I set timers, alarms and reminders on my iPhone. Every once in a while, I'll try to use it to play something on Spotify via my Sonos, then give up and do it manually in the app instead.
Reminds me of this old joke: No ethically trained software engineer would ever write a destroyBaghdad function - they’d write a destroyCity function to which you could pass Baghdad as a parameter.
The intuition I've built is that you can't talk about a false positive rate being high or low on its own - it's always relative to the actual occurrence rate of positives in the tested population. E.g. if there's a 1 in 10000 risk of a false positive, but real positives also are only 1 out of 10000 tested cases, then a positive case will have a 50/50 chance of being a false positive (because for every 10000 tests, you'll have on average one false positive and one real positive). So a false positive rate can only be said to be low if it's significantly lower than the real occurrence rate of positives.
I don't know about the rest of Europe, but in Denmark, universities get a part of their funding based on the number of graduates. So the university has an incentive to help student actually graduate instead of kicking them out. That may or may not matter to the bureaucrat responding to an appeal - but I'd certainly not just assume that "I'm close to graduation, just let me do this one more exam attempt" isn't a good enough reason for them to let you try.
I’m not sure if you’re aware, but Claude Code’s built in remote control feature already lets you respond to permission prompts from the Claude app on your phone.
I feel genuinely conflicted: On the one hand I get the "authoritarian overreach heebie-jeebies", that I think a lot of people on HN probably share. On the other hand I'd also really like the West to harden its election processes from election interference by its adversaries (e.g. Russia) - and shoring up dysinfo on e.g. Facebook by requiring users to prove their identity with a government ID is one of the only ways to truly effectively combat this at its source (fact-checking just can't keep up with a firehose of dysinformation). Ideally I'd want "real id requirements" to be limited " partake in public discourse" (mainly Facebook and Twitter). But the slippery slop argument just feels pretty strong here too - once a mechanism like this is in place, its use will only ever expand, and it's much easier for a new government to commit overreach if it's already there and just needs expanding. And of course all this "think of the children" nonsense needs to stop.
In case anyone is wondering, the quote "Before enlightenment, chop wood, carry water. After enlightenment, chop wood, carry water" is an ancient Zen Buddhist proverb. It speaks to how the life you live, and actions you perform, before and after enlightenment are not materially different. But how and why you do and experience them changes, becoming more mindful and less mired in “attachment” and overthinking.
If I was doing all this ad hoc, it might just be. But I’ve had Claude save this as three “skills” (standard workflows) that chain together (review-branch, triage-findings, apply-fixes) so all I need to do is say “review the branch”, make judgment calls on truly ambiguous decisions, and then “apply the fixes”. It’s effort-full but not for me
I've stumbled on the same workflow. Except for one thing: If I just do as OP does, Claude Code will tend to overengineer. For example it'll build complex solutions to super rare race conditions that have trivial fallout. But I've found that all it takes is a "skeptical pass". Here's how it goes: After having a bunch of specialist subagents review the (plan/implementation), after doing the deduplication/synthesis of their findings, the main agent will bucket them into A) Trivial/obvious fix B) there's multiple possible resolutions, but the LLM had a strong lean, so it went with it on its own C) Genuine ambiguity, where it asks me what to do (and presents its lean) and D) Wontfix. Crucially, after doing this, I have it run a "skeptical pass" where it takes a hard look at these findings and see if maybe some of them deserve to be downgraded. Generally, a lot of things make their way into wontfix this way. I find, I don't need to push back against overengineering, I can have the LLM do so itself, and it'll actually do a decent job of it.
As software engineers we’ve now suddenly become a sort of “god of the gaps” - our existence is only justified in the (fewer and fewer) situations where the AI can’t do the job just as well on its own
I feel like this article leaves out the latest research pointing to acetaminophen having a negative effect on fertility, hindering embrionic development and potentially also also follicular development in baby girls. It's a trade-off for sure, but if you're trying to have a baby, you may want to swing back to ibuprofen.
Not my comment but my guess is they might be referring to the research that shows that intermittent fasting has various health benefits. And one of the most popular ways to do intermittent fasting is 16:8 (16 hours where you fast, 8 hours where you eat), typically where you only ever eat from 12 noon until 8 in the evening, and then fast from 8 pm until noon the next day. Under those conditions, breaking the fast with a breakfast means losing out on the health benefits, and you're better off waiting until lunch.
Remember, having the dot com bubble burst did not prevent the internet from being integrated more and more in society over the next couple decades. What it did was stop the headless investment where money was thrown at anything that tangentially could be called "online". We went from "nobody knows what this is, but everyone wants a piece of it" to "we know what it is, and we sure did pursue a lot of bad ideas when we didn't". Expect something similar to happen with AI - having the bubble burst will not stop it in its tracks, but it will change what gets invested in.
Founder at hrvey.com