Yes, this is why I generally still use "ask for permission" prompts.
As tedious as it is a lot of the time ( And I wish there was an in-between "allow this session" not just allow once or "allow all" ), it's invaluable to catch when the model has tried to fix the problem in entirely the wrong project.
Working on a monolithic code-base with several hundred library projects, it's essential that it doesn't start digging in the wrong place.
It's better than it used to be, but the failure mode for going wrong can be extreme, I've come back to 20+ minutes of it going around in circles frustrating itself because of a wrong meaning ascribed to an instruction.
oh man the going-in-circles thing - that's the worst because you don't even know how long to let it run before you realize it's stuck. I've had similar issues where it misunderstands scope and starts making changes that cascade in ways it can't track. the 'allow this session' idea is actually really good - would be useful to have more granular control like that. honestly this is why I end up breaking work into smaller chunks and doing more prompt-response cycles rather than letting it run autonomously, but that obviously defeats the purpose of having an agent do the work
I can't speak for the status quo, but for at least the first ~5 years (so until 3 years ago when I last attempted to use it), the JS implementation of Fluent was a mess. Constant issues with incomplete API, wrong TS typings (which at that point were external) and build/bundling issues to the point where we opted for a homebrew solution.
I imagine that I probably wasn't the only one driven away by that (and I gave it many attempts!).
The standard is, for better or worse, gettext; it's good enough that any attempt to replace it runs into the problem that people can't agree on how much better an alternative needs to be to be worth migrating to; so you get a constant churn that so far hasn't seen any clear winner.
Feels like it's That XKCD page; there were standards like gettext, then web development came along and a load of people (...present company included) rediscovered localization and pluralization through trial, error, half-building one's own localization library, then the JS world reinvented it, etc etc etc.
As much as I used to love Sublime, the version switching caught me out which burned me a bit, even if admittedly my v2 key lasted an unreasonable time through the version 3 beta, but I don't want to risk buying a v4 key without a clear roadmap of when they might switch to version 5.
Oh wow, yes I remember now, I used to type `Alt+F` and then `S` immediately because Notepad didn't support `Ctrl+S` back then. Thanks for giving me nostalgia!
I've still got the very fast muscle memory of "Alt-F S", I used to do it habitually in Word and Excel. Still do it occasionally, then having to then undo whatever it does now (luckily it's usually nothing), but sometimes it leaves the Alt press 'open' so the next letter I press does something unpredictable.
And funnily enough, Office for Mac doesn’t allow you to do this, or at least it didn’t used to. I think I may’ve just noticed that it’s started working.
Doesn’t work for me. The absolute most infuriating thing is that copying text out of OneNote pastes as AN IMAGE. The only way around this is sanitizing the text in a notepad on the host machine itself.
It's worth noting that technically London uses GMT for 5 months and BST for 7 months.
The GMT offset is zero, but it's important to note the difference especially when configuring servers to avoid nasty daylight savings surprises kicking in at at end of March.
There has been talk of moving to a +1 offset all year round for lighter evenings in winter, albeit at the cost of some very dark morning, but given we couldn't even manage Metrication without people still complaining 20 years later, I can't see it ever happening.
I was specifically thinking of the "Metric Martyrs" who were jailed over refusing to display weights and measures in metric.
The law requiring metric didn't actually come into force until 2000, these cases were early 2000s. Note that the law to this day still allows for imperial measurements to also be displayed, but they wanted to display in solely imperial.
If you're going through the hassle of dropping DST, why not settle on BST as the permanent timezone if that's what the preference is for hours of daylight?
Asking an entire culture to change from 09:00-17:30 to 08:00-16:30 seems awkward and doomed to failure in comparison to simply landing on BST instead.
Only one participant can stream in a call. An arbitrary restriction that I just dont understand.
You also can't properly full screen when you're viewing a screen share, for whatever reason....
It's also a UI that makes covert (bot) advertising basically useless. Any form of communication that is not one-on-one-real-time has a bad UI and is heavily deprioritized.
Unironically the biggest flame-wars I ever saw on forums back in the day was on whether or not mandatory bike helmets made cycling safer or more dangerous.
I can understand, I’ve had some awful bicycle accidents while not wearing a helmet and the helmet would have made no difference. My knees, hands and elbows have been through a lot but I have never hit my head. Even while skateboarding the one time I hit my head a helmet would not have helped. In hindsight I should have worn knee pads a lot more often but then I wouldn’t be able to tell if it’s gonna rain or not from the feeling in one of my knees :)
However if I had to ride on a public road with cars zooming pass me recklessly I would absolutely wear a helmet on a bicycle.
And there are countries where everyone rides a bike, and they are not usually the ones with mandatory helmets. When you hit someone with a bike you are less likely to kill them than when you hit them with a car, so more bike riding means less deaths, without even considering the effects of air pollution.
Helmets are fine for sport riding, but inconvenient if you want to ride 5 minutes to the shops on a whim. And that kind of riding is usually less intense and safer, I presume, anyway. Football has helmets, walking doesn't.
Those countries also have a higher number of brain injury cases vs countries where people wear helmets.
If you are hit by a car a helmet will do approximately nothing. However there are a lot of accidents that happen where you are not hit by a car where a helmet will help. (and even more when knee and elbow pads are what you need)
A helmet can make a big difference in saving your brain if you are hit by a bike. Or if you hit a slippery spot and fall off your bike. Or - hundreds of other things that happen.
cars are too big and heavy for a helmet to make a difference - but they are not all that can go wrong. Even in car heavy US there is more than a car that can harm you.
Well unironically you would be safer if you did that! Although it's a trade off between looking ridiculous and being safe. I personally don't think bike helmets should be mandatory because it puts people off riding a bike (including me), but do acknowledge that they do make an individual safer.
Can't resist taking this bait, but I feel like the consensus is pretty much that as an individual, choosing to wear a helmet will make you safer, and as a society, mandating bike helmets (and other measures that will cause people to use transportation methods that are more dangerous to others) will make everyone less safe.
Of course, it's hard to prove. But I think you'll generally find that, if you compare the number of injuries/deaths while cycling in countries with mandatory helmets per km will be higher than it is in the Netherlands, where they are not mandatory.
Comparing the Netherlands with some of the best, if not the best bike infrastructure to other countries without said infrastructure seems very reductionist. To get anywhere near an interesting number you would have to compare the number of injuries to the total number of accidents including cyclists in countries with comparable bike infrastructure and differing helmet policies.
Yeah that's why it's hard to prove. However, it does show that infrastructure experts who actually care about safety (and have achieved the safety numbers to support it) reach for a lot of other measures before they do helmet mandates.
Sure, the tank rolling at the bottom looks a bit like a model, but it isn't nearly as jarring as the part where the shot of the guy in the tank looks like it came from another world entirely and has been badly edited in on top.
As tedious as it is a lot of the time ( And I wish there was an in-between "allow this session" not just allow once or "allow all" ), it's invaluable to catch when the model has tried to fix the problem in entirely the wrong project.
Working on a monolithic code-base with several hundred library projects, it's essential that it doesn't start digging in the wrong place.
It's better than it used to be, but the failure mode for going wrong can be extreme, I've come back to 20+ minutes of it going around in circles frustrating itself because of a wrong meaning ascribed to an instruction.
reply