If Wikipedia is ti be believed, Article 67 of the DPRK (North Korea) constitution gives citizens "freedom of speech, the press, assembly, demonstration and association" so I guess that's all we need to know about that.

I'm familiar with the expression but if an American said that to me, I'd probably think it meant "rethink what you just said".

It depends a lot on their tone. Most of the time I've heard it, it's a quick "begpardon?", sometimes with their ear cocked towards you.

When I see it in writing, I too for some reason picture an angry posh British man who is about to demand satisfaction.

As a learner it feels like Japanese is full of this kind of formalized, preemptory apologizing in all kinds of situations. You go to the supermarket and ask if they sell stamps (the answer is no) and they say the formal apology "申し訳ありません" (literally: I have no excuse).

There's also ごめん下さい "gomen kudasai" (literally "please forgive me") which is used as a greeting when visiting someone's house unexpectedly. And どうもすみません "domo sumimasen" (literally "thanks excuse me/I'm sorry") when accepting someone's offer to help with something.

None of these necessarily imply the speaker has actually done something wrong or wouldn't do the same again.

> None of these necessarily imply the speaker has actually done something wrong

You’d be surprised. The culture of kidzukai has two core tenets: (1) You must anticipate and cater to the other person’s every need and whim. If you fail you must apologize. (2) You must not allow the other person to do (1) for you instead of you doing it for them. If you fail you must apologize.

This means that every interaction between people who are even slightly close to each other in the social hierarchy is 3D chess which always ends in one or both of you apologizing to the other.

p.s. Gomen kudasai is “please permit me” to enter your house, not really an apology like gomen nasai.

Not the parent but I've had this happen when debugging for sure. Sometimes I ask Claude Code to help me debug something and it makes a wrong assumption and just churns in circles burning tokens. While it's doing that I realize the problem and fix it.

Sometimes debuggind is faster indeed, and making small very focused changes too.

But during feature development? Not possible. And I consider myself a very fast developer

Don't you find that debugging takes place as part of feature development though?

What I meant is that only sometimes I am faster than Claude with debugging. When it's a standalone problem, a report in Sentry, and I just know immediately where I need to go to fix it. Then it's faster to do myself, than telling Claude what's the problem and where to look and wait.

Bugs happen during feature development, as you say, but then Claude is in the context, and I don't need to tell it where to go, it sees the bug with failing tests, or smth similar.

BTW. One thing that helps my Claude with debugging harder problems is that I tell it to apply scientific method to debugging. Generate hypotheses, gather pros/cons evidence, write to a journal file debug-<problem>.md, design minimal experiments to debunk hypotheses.

You can add that as a skill, and sometimes it will pick it up automatically, but it works wonders just as a single sentence in the input.

..but then you ignore all other times CC got it right, and statistically I would put my bets CC does it right (or Codex (or PI)) than you would, and more often is right than tis not.

besides it is a system that you query, it responds. I'm sure your dbs are not always 'right' and particularly when you as the wrong questions.

Democratic leadership are also all Zionists who not-so-secretly approved of the war, which is why they stalled the war powers vote until after he attacked.

https://capitalandempire.com/p/top-democrats-try-to-stop-vot...

But if Republicans are Zionists, and Democrats are too, what hope is there for peace in the Middle East?

I can understand that Israel's long-time strategy is to keep all their neighborhood in a state of permanent mess so that nobody is strong enough to be an existential threat. But after almost a century, it's clear this is not working.

The strategy is to do what the US did to native Americans.

"Make a desert, and call it peace"?

Freedom House. But then again, most of their funding comes from the US state department.

> People making cooking websites, websites for their garden, etc usually have nowhere to go.

They've had WYSIWYG website builders since the late 1990s.

They don't have anymore. At least not since Artisteer shut down.

What about SquareSpace and the like?

It's certainly a great and useful tool. But it's a website maker somewhat in the same way that a Facebook page or Instagram account is a website maker.

AFAIK you can't make a website on SquareSpace and download it to your computer, edit it locally and move it to a different host, etc.

In the past there were actual WYSIWYG editors which let you design your website or CMS theme and then do whatever you wished with it. Artisteer was the pinnacle of this. Then nerds took over with their command lines and Kubernetes.

Imagine if one day people decided that making and editing documents in Word was no longer possible, that they had to be hand coded and command line compiled and linted, and not mix tabs and spaces. That's what happened to website publishing. For no reason at all.

2 minutes on Google showed me that DreamWeaver is still around and getting updates, so those desktop tools still exist as well.

I think that's the real gap. Non-technical people don't want to learn DreamWeaver or SquareSpace's backend. They want to describe what they need and have it just work.

Now that I think of it, the last decade has just been wave after wave of techwashing the same old gambling. First it was sports betting, then cryptocurrency, then NFTs, then "prediction markets".

In the 70 and 80s ppl kept their lifestyle by having their spouse starting to work. In the 90s and 2000s it was with credit cards. In the 2010s it was apps offering artificially deflated prices to corner markets. And now it’s gambling and buying burritos w Klara.

People on LinkedIn who are trying to build their "personal brand" seem to favor it. In fact, that's basically all the platform is these days.

Actually this more or less describes how accessibility APIs work.

Not really. For the most part, accessibility APIs provide programmatic interfaces to user interfaces, application APIs provide semantically meaningful interfaces to application functionality.

A closer analogue would be AppleScript, or rather, the underlying Apple Event and Open Scripting Architecture functionality supplied by the OS to support AppleScript, that allowed applications to expose these interfaces along with metadata documenting them, and for external tools to record manually performed tasks across applications as programs expressed in terms of these interfaces to make them easier to use (this last bit, while not strictly required, is convenient, and especially useful for less technical users).

If you're familiar with VBA in Microsoft Office applications, sort of like that, except with support provided by OS APIs that could be used by any application that chose to implement scripting support, official guidance from Apple suggesting that all well-designed applications should be scriptable and recordable, and application design patterns and frameworks designed with scriptability and recordability in mind.

Note that I use the past tense here, despite AppleScript still being available in macOS, because it is not well-supported by modern applications.

https://dl.acm.org/doi/epdf/10.1145/1238844.1238845