HN user

verve_rat

1,524 karma
Posts2
Comments602
View on HN

We have difficulty defining “actual understanding”.

Indeed. C.f philosophical zombies and the Chinese room problem.

The idea that some “actual understanding” (or more precisely, the outward appearance of it) needs a mechanism that includes free will is a bold claim.

GPT-5.6 13 days ago

Using remote control I will choose a model but Claude will always revert to Haiku for the first turn.

Basic stuff about features that are more than a week old just get no attention at all. From the outside Athropic seems to be a clear feature factory.

And maybe they just wrote a sentence like that because that's how they write. LLMs learned their style from humans, we were here first.

Yes, compare Czech Republic-> Czechia. No problem typing that out, no problem updating my mental map of the world.

Frankly I dispute that Türkiye can be the English name given it contains a non-English letter.

But in any case you cannot go back to a GUI and not have that problem of GUIs being too restrictive: invariably there shall be a need to chain several simple commands that do one thing and that excel at that one thing and that only become powerful when chained with other commands. GUIs cannot solve that.

But TUIs can't solve that either? The ability to pipe CLI commands together when using a tool non-interactively is orthogonal to what UI is used interactively.

Just because they weren't paid doesn't mean women were not doing economically valued labour. The washing machine is probably the greatest productivity unlock since the steam engine.

Changing the tax system to tax capital rather than labour would probably get you 90% of the way there without great societal upheaval (capital would fight back though).

There is a basic problem with framing though. Why does the labour need to find somewhere to go, but capital doesn't? Why can't the increase in productivity be captured by labour and denied to capital?

Agreed. I'm actually excited to hope for a cambrian explosion of IDE experiments.

LLM powered visual diagramming of the code as you work? The ability to edit the diagrams and have tje LLM apply that back to the code? Visualisation of test coverage over the UI you are working on? Allowing you to attach user submitted videos of bugs directly to tests in the code?

I don't know if any of that is a good idea, but I really hope a bunch of people try.

They (Stripe) don't have to be a arbitrator of every edge case, just use the information they have that merchants want to give them and surface a risk signal back to merchants, then it can be up to the merchant what level of risk they are happy with for each customer.

It doesn't seem like an unreasonable ask frankly.

Maybe, instead of trying to scare (scar?) children you should just teach them to make eye contact with the driver so you are sure they have seen you before you put yourself in the path of their car?

How much of our "safety" culture around kids is because people don't have basic life skills and aren't passing them on to kids?

My theory is we will end up in a similar spot to hiring people. You can look at a CV (benchmarks) but you won't know for sure until you've worked with them for six months.

We as an industry cannot determine if one software engineer is objectively better than another, on practically any dimension, so why do we think we can come to an objective ranking of models?