In case you didn’t know, there’s a lightspreader mod for the backlight which makes it a lot less terrible. I did it on my f91, the backlight still looks a bit odd but it’s much more readable
Thinking about it, even a lot of fancy fashion watch brands seem to do this, “Quartz”, “water resist 20m”, however many jewels. The old Casio watches are a bit worse for it though.
But check out the Casio MQ-24, it’s cheap and cheerful but has a much plainer face.
As someone who is usually on the other side of this interaction (software engineer at a company receiving bug reports), it's much easier when people write in their own words (even if they sometimes use the wrong terms or say something which can't be true) than when they use an LLM to make things clear and correct. I want to know what you're trying to do, what you expected to happen, and what actually happened - that doesn't benefit from having an LLM rewrite it.
Sure, I use precise and technical language, but I'm still a human and I can understand what people are getting at when they use imprecise terms. But if the text passes through an LLM I can't tell whether the result actually matches the original problem or whether the LLM has made guesses or filled in blanks.
Bug reports aren't so high-stakes (although poorly written bug reports can often be useless). I've got something to sell, and I want this expert to confirm that what I've built is better than what's currently available. That's a much harder approach. You want people to send bug reports. You don't want everybody to try to sell something to you. But I really think that I've solved the problem that she identified, so I want her to take a look at it instead of dismissing it as most people would probably do when a random nobody claims to have solved something. It doesn't help that this entire issue is way out of my comfort zone.
Generally the claude jargon is valid jargon I’ve seen real people use, it just uses jargon so much more often than a human would. And because it has particular jargon it likes, and claude is widely used, you see so much of that particular jargon that you get sick of it.
It’s like having one coworker with a very particular writing style which is mildly annoying, but then it suddenly feels like half the internet was written by that one person and it becomes a lot more annoying.
I think by "dangerous" they include things like "makes an edit to a config file outside the current project", not just "wipes the production database". So "dangerous" commands just means things we should ask the user for confirmation, not commands which definitely cause irreversible damage.
Even if that's what they mean it would still be disturbing if commands that should have explicit user confirmation were being waved through - whether by users or the auto mode - and being run when they shouldn't. The statistics appear to suggest that this is not only possible but actually quite likely given the number of commands an agent running all day might propose to run. But if that failure mode is a possibility at all then IMHO the whole system is playing with fire.
I changed from cursor to claude code a couple of weeks ago and this is the biggest difference I've noticed. cursor very rarely had to ask for permission for a command because it almost always used builtin find/read/edit tools. Whereas claude code makes extensive use of unix tools with mysterious flags which are basically impossible to whitelist and pretty impractical to manually review.
Overall claude code seems better at "just get things done" if you blindly trust it, but cursor was much better at keeping the human in the loop.
sed can be used to edit files (with the -i option). Not sure how this interacts with piping to its STDIN, but I wouldn't automatically assume `grep | sed` is safe.
I was thinking about this the other day, standard UNIX utilities seem poorly suited for this because they have so many weird options/flags with "unsafe" side effects. I have no idea if grep, for example, has some niche option to make it write/edit/delete files, so I wouldn't be comfortable blanket whitelisting it.
reply