sfink

Joined 14 years ago

Karma
4,375
Submissions
1,554
Member since
Jun 15
I work for Mozilla, read books, and trim my toenails once in a while. If you cut me, I bleed. (But there are much more preferable ways of verifying my identity, thank you.)
View on Hacker News

Recent submissions

Comment · 6 days ago
I lost a friend who died from complications caused by chemotherapy. That's a true statement. It's also true that she would most likely have died at least a decade earlier, maybe two decades, had she not done chemotherapy. (She was on her 3rd or 4th relapse.)

I don't mind the above wording at all, because there's another thing that happens: people seem to have this impression that if you get cancer, follow the recommended treatment, and are in remission... that you're "done", and you "won". It isn't like that. First, the treatments have serious side effects, both short and long term. Second, cancer is never gone from your life, even if it never comes back. That doesn't mean you should not do the recommended and available treatments. Your odds of survival are almost always much much higher if you do, and imo is the right thing to do for the vast majority of people. But go into it with your eyes open. You're past the point where you get to have a conventional happy ending. You'll need to figure out how to be ok with the ending that you can still have. (Which may be a happy one! But not in the way that you imagined when you were younger.)

Comment · 8 days ago
You can also brag to people about how great you are because you returned a wallet and expected and/or received nothing in return. With the expectation of receiving social approval.
Comment · 11 days ago
You're talking only about legal responsibility. That is about negligence and recklessness, and is tangled up with legal interpretation and things, and is separate from moral responsibility. If your kid breaks something, it's your responsibility (whether or not it was your fault). Same with your bot.

> Normally, I would say you don't want to be patient zero, but with the attitudes shown by frontier labs, I guess YOLO is the way.

In practice, yes. That's exactly how it's playing out.

Comment · 11 days ago
Yes, I fully agree, and it's why I wrote the comment! I'm bothered by all the "oopsie woopsie, we let our experimental bot run wild on the internet and told it to do things with no regard for the consequences and it went and did things with no regard for the consequences! silly bot."
Comment · 11 days ago
Huh. I thought I was pretty explicit in drawing the distinction between them.
Comment · 11 days ago
> As an investor a company's duty is towards shareholders.

I think you left out some part of that sentence, it sort of has two subjects? Companies are not investors.

"As an investor, I only care about a company's duty towards shareholders" maybe?

But no, companies are not obligated -- legally or morally -- to be extractive or abusive in pursuit of shareholder's interests. A company can do whatever it wants, can be formed for whatever reason it wants, and shareholders can vote or divest if they don't like it. The whole "a company's only duty is to its shareholders" is a myth that was widely propagated in the 1980s. There's a kernel of truth to it, but it means much less than is commonly understood.

Comment · 11 days ago
Heh, such pushback here. The writeup seems to have gotten under people's skin.

It's refreshing to read human prose about something like this. There's so much you can get about the author's state of mind -- pride at what they've accomplished and how they like to conceptualize it, traces of how they learned things and what those things mean to them... for me, it's a reminder of what we've lost in giving over so much of our writing to AI.

But it's understandable that the writeup would trigger defensiveness. It claims a lot of originality and novelty that seem overreaching. AIUI, it's an optimizing JIT with a superoptimizer and a shared cache, with the search procedure guided by AI. And the equivalence model that the superoptimizer is based on includes all of Python and can handle both CPU and GPU code. It's quite impressive, really.

It's hard to tell what of it is new. Superoptimizers are not, JITs are not, caching JIT code is not, using machine learning to speculate or search is not. Constraining an LLM to produce correct output is no newer than forcing semantically valid JSON output. (You could think them as different type systems.) Different JITs have handled different kinds and amounts of runtime information -- tracing JITs, runtime type inference like SpiderMonkey used to use, speculative compilation and invalidation (global or just in time like inline caches)....

But none of that takes away from Maxwell. There isn't really enough information to compare it to other systems. Random example: many JITs work really hard to balance compilation time with execution time, and the post doesn't talk about that. Is it only for long-running code? Does it reach a steady state, and if so how much overhead is there at that time? What does it make slower or bigger?

At any rate, it seems like there's a lot of interesting work in Maxwell, and it's worth checking out.

Comment · 12 days ago
You can set it to 1h. The analysis script Claude wrote for me says I'm saving 11% over the 5m window by doing that on my API account.

It's something, at least.

Comment · 13 days ago
I've found that telling agents to not do something mostly just gives them a suggestion of a way to do that thing, and the part about not doing it that way gets lost. Well, it's nicely accessible for when it apologizes for doing it.

I now try to only give examples of how I want it to do things, and hooks that complain when they do the bad thing (but still don't mention the bad thing in the complaint.)

Comment · 13 days ago
Since this seems to get lost, I'd just like to point out: if you ask your agent to do something like this (or pretty much anytime you give it internet access and say "do whatever it takes"), you are responsible for what it does. Even if you couldn't have predicted the lengths to which it would go.
Comment · 13 days ago
It's the latest iteration of "a little X is good, a lot of X is bad".

Email was awesome when it first became widespread. I could cold-email random professors at other universities (I was in school at the time) and get meaningful responses back. Then lots of people (and companies) started cold-emailing, and it stopped working.

Social media is broken if there's nobody there, is great with a medium-sized community, and is broken if everyone is there.

Ad-supported websites can offer all kinds of valuable free services. Up until either (1) they become so ad-infested that they're no longer useful, or (2) all the users block ads.

There was a wave of websites providing APIs for programmatic access a while back. You could script together whatever flow you wanted. If no API was offered, you could scrape the HTML. That triggered a wave of alternate interfaces to sites, skipping their ads, skipping their engagement funnels, separating the value from the cost. So everything got locked up behind captchas and accounts and API keys with limited access.

This outcome was always inevitable. Humans don't understand social contracts, or they do and both sides abuse the hell out of it. We feel entitled to have just the loss leaders without ever buying anything else. When running businesses, we feel entitled to keep adding more and more adds and generally enshittifying the experience. People can take it or leave it, after all.

Agents don't change the underlying structure at all. They just magnify and accelerate parts of the system, and will therefore magnify and accelerate the reactive and defensive responses.

Comment · 15 days ago
Because individual investors, and especially individual investors lumped together via a fund, have all the incentives for profit maximization and no incentives for quality of work or quality of workers' lives, except insofar as it is reflected in profits.

"Anybody who wants to" is precisely the problem -- there's no correlation between a rando's wishes and the health of a project or working environment. You need people with skin in the game, and in the right game.

Comment · 15 days ago
It's fine for them to exist, and probably better -- you can land incomplete things behind a feature flag and avoid some amount of rebase/merge hell.

But they should be marked experimental in that case, not optional. Optional flags ought to work together, or at least it should be considered a bug worth quickly fixing if they don't. Combining experimental flags otoh is Buyer Beware.

Comment · 18 days ago
That just sounds like generic marketing-speak to me. That stuff never did mean anything.
Comment · 18 days ago
No. Are you thinking that was a feature intended to appeal to corporate use or something? I'm pretty sure it was all about AI backlash. It's still a popular setting to have available. (I have no idea how many people actually use it.)

Live from the official Hacker News API

A modern reader for Hacker News · SvelteKit + Skeleton