diatone

Hey HN, six years ago I submitted a toy to render terrain:

https://news.ycombinator.com/item?id=23660898

Since then I've ended up with a new account, but I still have the underlying Netlify app running. I didn't have the original repo, but these days with AI you can unminify code, so I ended up porting it to Vite and a different state management stack, and then rigorously profiling it so the original comments (eg: about it being able to run instantaneously on a Pentium) are honoured.

AIUI: my intuition is Alex and Alice are points in the distribution. They don’t think about their experience in terms of population statistics. They see their individual latency times, and use that as their sample. If t is low in their experience, great the distribution is low.

But for any t that goes high that they observe (which tends to be the case in a skewed distribution such as service latencies), it drags their impression of the distribution up, dominating the shape of that impression.

First word of second sentence:

> Stability

ie: lack of volatility, ie: integrity, ie: I know it does what it says and don’t have to second guess that.

If we can just simulate the business accurately enough we can solve having to interact with the market… which is also trying to solve interacting with us… We just need to do it more accurately…

Something tells me people will still be in the mix here.

A cursory glance does make it appear like either a prolific individual, or a bot. The fact that the novel bears little relation to the analytics posts, which seem to bear the style of LLM prose, makes the whole thing fishy. Ironic given the subject matter of TFA

Revenue recognition for private companies generally is less precise than for public companies, which in the US are obligated to report under GAAP, which uses a different indicator than annualised revenue so public companies are comparable.

It makes sense to scrutinise Anthropic’s revenue in the lead up to IPO on those grounds; their AR figure simply isn’t comparable to revenue numbers from other firms.

However it doesn’t make sense to be sensational about this - iirc reporting GAAP revenue is a necessary condition of going public so the chickens will come home to roost one way or another.

So if the benefits haven’t accrued to you, it must have gone to your customers right?

If your students were growing up to subvert your line of work, sure. Pretty sure that’s not the case though!

Yep agree it looks like it’s taking the existing generated artefact, parameterising it within an inch of its life, exposing a pseudo WYSIWYG for the parameters and calling it a day with a few export options. Not a huge leap from what they’ve got already but it’s a clever adjacent step for sure. Same product new chrome.

You’re illustrating one of the points of TFA - a team that is equipped with the right tools to measure feature usage (or reliably correlate it to overall userbase growth, or retention) and hold that against sane guardrail metrics (product and technical) is going to outperform the team that relies on a wizardly individual PM or analyst over the long term making promises over the wall to engineering.

Until they’re using consistent methods of reporting those figures, they’re not comparable. Same as any other company pre vs post IPO

Without commenting about the frequency of negligence myself, I suspect at least that you and GP are in agreement.

I doubt GP is suggesting ‘go ahead and be negligent to feedback and guardrails that let you course correct early.’

Plugging the Cynefin framework as a useful technique for practitioners here. It doesn’t have to be hard to choose whether or not rigorous planning is appropriate for the task at hand, versus probe-test-backtrack with tight iteration loops.

If 9 of those solutions are crummy and reviewing them takes longer than just doing it right once…

Chiming in as Australian with no context on European situation. AFAICT the key drivers of cost inflation are to do with reconfiguring the electric grid to transfer power efficiently and reliably from plants that produce renewable energy. However, the grid is set up to do so from non-renewable sources. And you want to do it while smoothly operating the network. This is extremely hard. Doing so quickly therefore elevates prices. That’s the rationale I could imagine being the case in EU markets.

That’s not real math though, that’s a quirk of floating point math.

That’s possible, I suppose. I think @btbuildem was expressing a personal distaste for other uses of power, and an avulsion to the technology because of that. For example: labor camps.

Iiuc it wasn’t a comment about what the perfect lifespan is. It’s expressing a concern about how people in power might apply life extending technologies, like they do many other technologies, to exercise and entrench that power.

Or put differently: it’s a request, given limited resources let’s expend effort on a fairer society, not one with longer lived people.

Probably worth clarifying with GP what responsibility and accountability they’re referring to.

Where I live, if an engineer signs off on a bridge design and the bridge personally collapses, they are personally liable for harm done to folks on the bridge. As far as I’m aware software engineering does not have something like that.

For one - I’d say scoped API tokens that prevent messing with resources across logical domains (eg prod vs nonprod, distinct github repos, etc) is best practice in general. Blowing up a resource with a broadly scoped token isn’t a failure mode unique to LLMs.

edit: I don’t have personal experience around spending limits but I vaguely recall them being useful for folks who want to set up AWS resources and swing for the fences, in startups without thinking too deeply about the infra. Again this isn’t a failure mode unique to LLMs although I can appreciate it not mapping perfectly to your scenario above

edit #2: fwict the LLM specific context of your scenario above is: providing examples, setting up API access somehow (eg maybe invoking a CLI?). The rest to me seems like good old software engineering

FTA

> That’s exactly what it means to hit a wall, and exactly the particular set of obstacles I described in my most notorious (and prescient) paper, in 2022. Real progress on some dimensions, but stuck in place on others.

The author includes their personal experience — recommend reading to the end.

I’ve read some blog posts by Geoff and there’s a useful idea here but it’s surrounded by so much storytelling.

To dig up the lede: LLMs are proving useful in some instances, consider staying abreast of developments here to find ways to do a better job as time goes by. The exact nature of “better job” and the timeframe along which that reveals itself are left as exercises for the reader

Take a photo on your phone, OS recognises the link in the image, makes it clickable, done. Or, use a QR code instead

Same as it’s always been.

https://7powers.com/

Deep fakes have always been horrible. The idea that someone - anyone - can take your image and represent you in ways that can ruin your reputation, is appalling. For example, revenge porn.

Having your likeness used to express an opinion that is the opposite of your own is nasty too. You can produce the kind of thing that has no courtesy, no grace, no kindness or care for the people around you.

The mass extraction and substitution of art has also caused a lot of unnecessary grief. Instead of AI enabling us to pursue creative work… it’s producing slop and making it harder for newbies to develop their craft. And making a lot of people anxious, fearful, and angry.

And finally of course astroturfing, phishing, that kind of thing has in principle become a lot more sophisticated.

It unnerves me that people can pull this capital lever against each other in ways that don’t obviously advance the common good.