Slow, steady, progress can appear quick when the alternative is no progress at all. Or, alternatively: avoid "dead air".
I think I generally identify with what the article is saying - but I think it's more about responsiveness and predictability than pure speed. I've always been a pretty quick worker, but more importantly I've been responsive. It's better to reply back in 5 seconds with an "I don't know; you might want to talk to Susan about this instead" than to spend an hour researching on your own and give them the answer yourself. You can even say "If Susie is too busy, I can look into it myself, but it might take an hour or two".
This is one of the things I've seen it be very useful for: putting together one-off tools or visualizations. I'm not going to maintain these, although I might check them into version control for historical reference.
I recently ran across a package in my team's codebase that has a bunch of interrelated DB tables, and we didn't already have a nice doc explaining how everything fits together - so I asked the AI to make me a detailed README.md for the package. I'm currently reviewing that, removing a bunch of nonsense I didn't ask for, and I'm going to run it by my team. It's actually pretty good to start with because the code and DB models are well documented, just piecemeal all over the place, and half of what the AI is doing is just collating all that info and putting it in one doc.
Depends on what you're doing. I've found it extremely useful for creating the boilerplatey scaffolding I'm going to be copying from somewhere else anyway. When I actually get into the important logic and tests I'll definitely write those by hand because the AI doesn't understand what I'm trying to do anyway (since it's usually too novel).
There are already other articles claiming he was shot because he's Jewish and has supported Israel. Seems like the cops haven't arrested anybody yet, so we don't really know anything.
He was working on fusion technology, so you could just as well speculate it was fossil fuel interests involved, but that also seems purely speculative.
First thing that came to mind is that he might have been secretly working for Israel's nuclear program but this is all very speculative. It does feel plausible though given that Israel has already assassinated plenty of Iranian nuclear scientists; so there is some precedent for it.
There are lots of different scenarios you can conjure up. Another could be that Israel assassinated him after he refused to support their nuclear program OR to silence him.
Some students whose work I had to fix (pre AI), was crashing a lot all over the place, due to !'s instead of ?'s followed by guard let … {} and if let … {}
The article says the new style says that you can use either a macron or a doubled letter, but it's not clear if that's supported for keyboard input on various platforms.
But in the case of ō, you can only use a doubled letter if the underlying word is おお. If it is おう then you don't have a doubled letter you can use; you need "ou" and that's not Hepburn any more. It is "wāpuro rōmaji" (word processor romaji).
I've only done a tiny bit of agent-assisted coding, but without the ability to run tests the AI will really go off the rails super quick, and it's kinda hilarious to watch it say "Aha! I know what the problem is!" over and over as it tries different flavors until it gives up.
And the way English generally uses the Roman alphabet (obviously excluding the zillions of irregularities) isn't that far off from how most European languages use the Roman alphabet.
I'd expect that Spanish, German and French speakers would benefit just as much as English speakers from these changes.
> And the way English generally uses the Roman alphabet (obviously excluding the zillions of irregularities) isn't that far off from how most European languages use the Roman alphabet.
Its not far off from the union of how all other European languages use the Roman alphabet, would be closer to accurate.
Sure, but the point is this isn't really making romanized Japanese more English-like. It's making it more similar to how just about every other language already uses the Roman alphabet. This isn't an Anglo-centric thing, it's just good common sense - unless your goal is to make it harder to pronounce your language properly, which seems like an obvious own-goal.
About 30% of people worldwide use a language that's not written in Roman alphabet.
Additionally, being written in Roman alphabet doesn't neccessarily mean it's clear how to pronounce it. Hungarians calls their country "Magyarország", but unless you know Hungarian, you will be surprised with how it's pronounced. Same as "Chenonceaux", "Tekirdağ" or "Crkvina".
Those are especially pathological cases, and not especially relevant to this discussion, as the romanization rules are explicitly designed to be consistent.
We're not talking about words like worcestershire. I'm talking about words like "bat" "monkey" "chimichanga". Those that follow the rules. There can't possibly be irregular spellings using the romanizations we're talking about!
> It's making it more similar to how just about every other language already uses the Roman alphabet.
There is no way "every other language already uses the Roman alphabet."
Many languages are internally consistent in how they use it, but those that are aren't consistent with each other. And then there is English, which does pretty much everything any other language which uses the Roman alphabet does somewhere, and probably a few that none of the other extant languages normally using that alphabet do with it, on top.
A specific example: for some reason, when working on Playwright scripts, Claude really likes to inject
await page.waitForLoadState('networkidle');
But this isn't good, and is not encouraged. So much so that there's an eslint that suggests removing it. This means that by running the linter, if Claude does decide to inject this, it gets taken out, because the linter runs and then tells it so.
I'm assuming this is the case where they are working in an existing codebase written by other humans. I've been in this situation a lot recently, and Copilot is a pretty big help to figure out particularly fiddly bits of syntax - but it's also really stupid suggests a lot of stuff that doesn't work at all.
I think I generally identify with what the article is saying - but I think it's more about responsiveness and predictability than pure speed. I've always been a pretty quick worker, but more importantly I've been responsive. It's better to reply back in 5 seconds with an "I don't know; you might want to talk to Susan about this instead" than to spend an hour researching on your own and give them the answer yourself. You can even say "If Susie is too busy, I can look into it myself, but it might take an hour or two".
Communicate, communicate, communicate.
reply