HN user

l1ng0

18 karma
Posts0
Comments34
View on HN
No posts found.
Will It Mythos? 29 days ago

Lots of interesting answers here, but I'm particularly intrigued people feel this would affect how they talk to humans.

I guess I see AI the same way I see a compiler. I've never worried that I'll end up using code syntax in human conversations.

I tend to write to the AI using language I'd use in technical documentation: concise, detailed, unambiguous as possible.

Will It Mythos? 30 days ago

You write to the AI as if it were a person. From my point of view it looks like a fair bit of extra typing and extra tokens. Is there a reason you include things like your emotional response and use a very chatty tone? Do you find this seems to alter responses?

A friend uses chatGpt for self diagnosis. I warned him it was less accurate than a human doctor. He said "I know, but it has a better bedside manner!" :)

Sad but frequently true.

(He also takes its advice with large grains of salt.... metaphorically)

It's part of the culture where I live, but the heat keeps increasing. 45 in dry heat (unless you work outside) is fine if you get cooler nights to recover, but when you don't get a break, it's lethal. Also aircon helps you but adds significantly to the heat outside in urban areas, causing what feels like a vicious circle. Anyway, where I live aircon is not common and electricity costs are high.

iNaturalist 4 months ago

honestly I can never remember which of these words means which

I expect it makes a big difference what kind of work one does. For me, working with a legacy codebase for firmware, with 1000s of lines of C in each module, AI is very slow (~5-10s response time) and almost none of the code is acceptable.

I do however find it useful for getting an overview of dense chunks of confusing code.

I came across an old graphics project I'd made for Windows/DOS around 20 years ago. Within about a half hour I was able to compile and run it on a Linux machine with Wine, installing the latest version of the compiler and dependencies.

I can rarely get a 6-month-old JavaScript web project to compile and run this easily. Churn in node versions, npm/yarn versions, dependencies being abandoned, superseded, dropping backwards compatibility.

I agree that the churn is constant.