hexasquid

The way we do this is to have period "post project" metric checks, looking for

- are the users using the new feature (repeatedly)

- what sentiment is associated with it on customer calls (extracted via call transcripts, but ideally the relevant engineer joins the call)

Cool report

%s/toxic expert/hn commenter/

Can konsole do the fancy shader and inline images? I think that's all that distinguishes the others but I may be overlooking things.

Oh, I was thinking verify what the doc claims to what the code actually does, I misunderstood you.

That's like me with violins!

Seems like an AI could be tasked with verifying the docs. Then a human can double check it's work if it finds anything.

https://webstatus.dev/features/anchor-positioning https://webstatus.dev/features/popover

Probably the place to start

Go back a few years "css isn't a real programming language, there are no functions or control flow"

These arrive

"no! NO!"

3. AGENTS.md tells you not to

For a second I didnt see where it says "made by my own two hands", but it's down the bottom.

Phew!

I gather it goes through an intermediate coercion step where it is "1" + "hello".

What trips us up is having existing expectations for what an operator called + should do.

I suspect all branches of tech have their rite of passage.

For haskellers, it is writing a monad tutorial

For javascripters, it is writing a framework

For make-stuff-with-LLM people, it is producing a diagram explaining your code generation factory

... and so on

It would be subversive if the large corporation doing science in space turned out to be benign

Even a stalker would draw the line there.

I'm curious what people are building with these models

For a moment there this wasn't about LLMs

I would draw the blinds

302 send to reddit

"... and keep your hand up if your ethical, water saving stance means you've become vegan."

"typed error handling, structured concurrency, resource safety, and observability, all from one composable core"

I'm interested to know why tsc (pre-go) would give me near-instant LSP diagnostics on a large typescript project, and rust-analyzer takes ages to produce diagnostics in a small rust project.

It all went wrong when writing was introduced, the lazy kids became addicted to letting the technology take place of their natural human memory.

The AI is getting bad morals from listening to that dreadful rock and roll

Maybe .unwrap()

This got me thinking about what "I made this" means, when we're building on top of zillions of abstractions "made" by others.

I don't make the binaries. The compiler does. I just feed in specification called source code.

I'd be interested to overlay, I don't know, customer satisfaction or anything that can show the follow-on effect of all this output. Linear won't have that information.

My guess is some will jump up (where the team has managed to make themselves move effective and responsive) and many will plummet (doesn't need explaining).

Then there might be something to look at.

// Educational service, not legal advice.

X, not Y

Good instinct. Fair challenge. This corrects my framing. It makes your point sharp. This is a significant finding. Positively confirmed. That settles it, and it flips the picture. Honest verdict - this is not small. Let me wire it in.

"Well, actually, vim doesn't make you faster"