pushedx

The mechanism that they have proposed to make this a non issue is interesting. It reads to me as if they are asking another standards body who measures the angle of the Earth's axis relative to the Sun to adjust by a small amount so that leap seconds wouldn't be needed for a period of 100 years.

"box" he says. "box". as if they could fit into a single "box".

I can't think of a worse first impression for the new owners of a marketplace that relies on buyer and seller loyalty than taking down the entire platform for weeks without any clear timeline or reasoning.

It also gives the impression that they have no idea how to set up a staging environment or seamlessly migrate to a new backend with a double write approach. Just spells trouble all around.

How about "documentation driven development"?

So many times I have found myself writing the end-user documentation (even after writing tests for the code), and realized that the design should change.

This is the kind of post that makes me log in to hn to give a vote.

It's refreshing to read writing which is not AI generated

At the beginning of your comment I was wondering if the "attitude" that was corporate serving was the anti-ECC stance or the pro-ECC stance (based on the full chunk that you quoted). I'm glad that by the end of the comment you were clearly pro ECC.

Any workstation where you are getting serious work done should use ECC

Every so often over the past 15 years I've had this exact thought, "The world needs something which is exactly like flash. Not kind of like flash, exactly like flash."

A whole generation of people learned how to create art, games, music, animations, using flash, and the same kind of tool hasn't existed since then.

I think Minecraft and Roblox replaced flash for the new generations.

As described in the readme of your repo (did you read it?) your agent found the Knuth paper located one directory level above its working directory.

So, you didn't produce a replication in 47 minutes, it just took around 30 minutes for your agent to find that you had the answer in a PDF in a nearby directory.

sorry, needed to edit this comment to ask the same question as the sibling:

have you run these models in an agent mode that allows for executing the tests, the agent views the output, and iterates on its own for a while? up to an hour or so?

you will get vastly different output if you ask the agent to write 200 of its own test cases, and then have it iterate from there

Which agents are you using, and are you using them in an agent mode (Codex, Claude Code etc.)?

The difference in quality of output between Claude Sonnet and Claude Opus is around an order of magnitude.

The results that you can get from agent mode vs using a chat bot are around two orders of magnitude.

Yes, most people (including myself) do not understand how modern LLMs work (especially if we consider the most recent architectural and training improvements).

There's the 3b1b video series which does a pretty good job, but now we are interfacing with models that probably have parameter counts in each layer larger than the first models that we interacted with.

The novel insights that these models can produce is truly shocking, I would guess even for someone who does understand the latest techniques.

I use the iOS app daily, and while it's not the prettiest thing in the world, it has nearly every feature of the desktop client, including full scripting support for card contents, which is amazing for things like collapsable elements and media. And, at the end of the day, it's about what you learn from using it that matters.

One theory that I've had for a while with regards to the no liquid policy is that it was somehow introduced by the food vendors on the other side of security, who want you to buy a drink and some food after you pass through.