jmpeax

Then the probabilities are not calibrated. Jev is basically the LLM version of the "is-even" library.

> A prompt complex enough where it won't get any wrong ideas has to contain as much information as the output would have.. so just write it.

This is only if the output is fully compressed. Writing is not just about encoding the writer's ideas but also about how the reader will ingest those ideas. The writer needs to consider when to put in rests in between complex ideas to help the reader flow through the text. This suggests the LLM could be prompted by a dense complex idea to be presented with the boilerplate needed for the human mind read smoothly and without unnecessary effort.

What a peculiar title. The title suggest parallel dev without using worktrees, but the article is about using worktrees.

> LLMs are also terrible at these new standards.

Skill issue? I mean, I wonder if adding a skill to use these newer standards can push it over the edge from the crappy JS it was trained on.

The types of skills from FPS games and real fighting are much further apart than gaming and ATC. A closer analogy would be a coworker who knows Judo is needed for Greco-Roman wrestling. Very different sports with different rules, but the skills in building and navigating a mental map of the environment carry over.

This whole fiasco could have been prevented had the operator included "Make no mistakes" in the prompt.

> nowhere in the announcement is coding mentioned

It's right there in the middle benchmark bar "LiveCode Bench" 72%.

All unit tests can pass if you don't assert anything. Just have to make sure to read through all 130k lines of code to check.

This post misses that the people selling their "I built" SaaS advertised as a hobby/passion-project are just marketing something as indie that they fully intended to get rich from the beginning. It was never even a hobby worth giving away for free, it was always an attempt at making an easy fortune because they bought into the dream that infra was selling.

it's probably been thrown out the window compared to office and chatgpt

"If you refuse to estimate, you’re forcing someone less technical to estimate for you."

This is the perfect approach, given that estimates are top down and work to fill the estimate is bottom up.

"When I estimate, I extract the range my manager is looking for, and only then do I go through the code and figure out what can be done in that time."

Future icon will just be this: ∠

I like the surface dots like it is. It gives me two points of reference at the poles, and adds intuition for how long it takes to go around the sphere.

From that wikipedia article, delta is the ratio of y variance to x variance. If x variance is tiny compared to y variance (often the case in practice) then will we not get an ill-conditioned model due to the large delta?