It set off the flamewar detector. I've turned that off now.
I only saw this thread by chance and almost didn't look, because the title made the piece sound like a flamebait blog post. Fortunately I saw newyorker.com beside the title and looked more closely.
There is dwindling space for sincere independent accountability reporting on big tech like this to a) be created, since it's incredibly resource-intensive and so many resources flow from Silicon Valley, and b) actually reach people, since more platforms are now owned or otherwise influenced by interested parties.
Thank you for looking. Please do spread this kind of reporting in your communities, and subscribe to investigative outlets when you can.
> OpenAI has closed many of its safety-focussed teams
A paper with "ideas to keep people first" was (coincidentally?) published today:
• Worker perspectives
• AI-first entrepreneurs
• Right to AI
• Accelerate grid expansion
• Accelerate scientific discovery and scale the benefits.
• Modernize the tax base
• Public Wealth Fund
• Efficiency dividends
• Adaptive safety nets that work for everyone
• Portable benefits
• Pathways into human-centered work
You can see the vote history here[1]. It's always hard to know exactly why something gets buried. I was a little sad to see the story down-ranked when I saw that you were here in the comments.
But the discussion is generally pretty low quality with these sort of posts. People react without having read the story, or with whatever was on their mind already, or are insubstantive, or simply low effort. I don't think you'll lose k-factor not having a bigger post here.
Sometimes if you talk to the mods, they'll let you know their perspective. I generally find they're correct that people are much better at contributing/disseminating new knowledge to the world on more technical topics here.
Yes, I was surprised that it was downranked when I saw that too. Then I realized it had set off the flamewar detector and it was a simple matter to turn it off. I'm glad we got to this in time, because sometimes we don't, and this was an important case not to miss.
But isn't that circular? If the ranking algorithm used by the mods tends to devalue articles like this because they don't trust the user base to comment intelligently, doesn't that alter the culture of this site to make that more true?
I'm not sure what big_toast meant, but we do trust the user base to comment intelligently (which sometimes works and sometimes not), and we don't devalue articles like this.
We do tend to devalue titles like this, or more likely change them to something more substantive (preferably using a representative phrase from the article body), but I'm worried that if I did that here we would get howls of protest, since YC is part of the story.
I'm sure you're sick of comments about moderation, but I will say, this makes me more sympathetic to the position you're in.
It's an interesting dilemma. Many very respected publications use provocative titles because of the attention economy. And I'm sure you have good data that provocative titles lead to drive-by comments and flame wars.
But I don't think big_toast was entirely wrong that there is a side effect of sometimes burying articles that are by their nature provocative. And how do you distinguish a flame war over a title from a flame war over content? That's not a leading question. I don't know.
For us the litmus test isn't the title, it's whether the article itself can support a substantive discussion on HN. If yes, then we'll rewrite the provocative title to something else, as I mentioned. Ironically this often gives the author more of a voice because (1) the headline was often written by somebody else, and (2) we're pretty diligent about searching in the article itself for a representative phrase that can serve as a good title.
If, on the other hand, the title is provocative and the article does not seem like it can support a substantive discussion on HN, we downweight the submission. There are other reasons why we might do that too—for example, if HN had a recent thread about the same topic.
How do we tell whether an article can support a substantive discussion on HN? We guess. Moderation is guesswork. We have a lot of experience so our guesses are pretty good, but we still get it wrong sometimes.
In the current case, the title is baity while the article clearly passes the 'substantive' test, so the standard thing would have been to edit the title. I didn't do that because, when the story intersects with YC or a YC-funded startup, we make a point of moderating less than we normally do.
I know I'm repeating myself but it's pretty random which readers see which comments, and redundancy defends against message loss!
I have yet to meet anyone whose problem with AI is that the code is not aesthetically pleasing, but that would actually be an indicator to me that people are using these things responsibly.
My own two cents: there's an inherent tension with assistants and agents as productivity tools. The more you "let them rip", the higher the potential productivity benefits. And the less you will understand the outputs, or even if they built the "correct thing", which in many cases is something you can only crystalize an understanding about by doing the thing.
So I'm happy for all the people who don't care about code quality in terms of its aesthetic properties who are really enjoying the AI-era, that's great. But if your workload is not shifting from write-heavy to read-heavy, you inevitably will be responsible for a major outage or quality issue. And moreso, anyone like this should ask why anyone should feel the need to employ you for your services in the future, since your job amounts to "telling the LLM what to do and accepting it's output uncritically".
>But if your workload is not shifting from write-heavy to read-heavy, you inevitably will be responsible for a major outage or quality issue.
I think that's actually a good way to look at it. I use AI to help produce code in my day to day, but I'm still taking quite a while to produce features and a lot of it is because of that. I'm spending most of my time reading code, adjusting specs, and general design work even if I'm not writing code myself.
There's no free lunch here, the workflow is just different.
There's a reputational filtering that happens when using dependencies. Stars, downloads, last release, who the developer is, etc.
Yeah we get supply chain attacks (like the axios thing today) with dependencies, but on the whole I think this is much safer than YOLO git-push-force-origin-main-ing some vibe-coded trash that nobody has ever run before.
I also think this isn't really true for the FAANGs, who ostensibly vendor and heavily review many of their dependencies because of the potential impacts they face from them being wrong. For us small potatoes I think "reviewing the code in your repository" is a common sense quality check.
I think the unstated (but highly prevalent) view among executives in large swathes of this industry is that they don't really care to spend any time or money on user testing or quality assurance, and if this role exists at companies it is usually under-compensated and straddles both these functions to have some party be accountable. It is sometimes a check on product teams and vision-driven executive teams who don't prototype/test their ideas (or empower their teams to do so), and sometimes a check on engineers and engineering managers who don't want to be accountable to gaps in quality.
The pathfinder algorithm is a great example of why constraints are so important for creativity and creative development.
If AI has any benefit to creative endeavors at all it will be because of the challenges of coaxing a machine defined to produce an averaging of a large corpus of work (producing inherently mediocre slop) provides novel limitations, not because it makes art any more "accessible".
Odious is one of the most reserved words you could use to describe Telegram, which is primarily a host for scams that the influencers and other bottom feeders aren't allowed to monetize on the big social networks.
I'm sorry what? Junior engineers can't learn anything without using AI assistants (or is the implication that having seniors review their code makes them incapable of learning?) and senior engineer would hate their jobs reviewing more code from their teammates? What reality do people live in now?
I thought the implication was that juniors would continue to use AI to stay "productive" (AWS is not a rest and vest job for juniors, from what I've heard) and seniors would no longer have time to do anything but review code from juniors who just spin the AI wheel.
There's a lot of learning opportunity in failing, but if failure just means spam the AI button with a new prompt, there's not much learning to be had.
> senior engineer would hate their jobs reviewing more code from their teammates
Jesus, yes. Maybe I'm an oddball but there's a limit to how much PR reviewing I could do per week and stay sane. It's not terribly high, either. I'd say like 5 hours per week max, and no more than one hour per half-workday, before my eyes glaze over and my reviews become useless.
Reviewing code is important and is part of the job but if you're asking me to spend far more of my time on it, and across (presumably) a wider set of projects or sections of projects so I've got more context-switching to figure out WTF I'm even looking at, yes, I would hate my job by the end of day 1 of that.
If we can't spend that much time reviewing code, what are we exactly doing with this AI stuff?
I don't disagree, I think reviewing is laborious, I just don't see how this causes any unintended consequences that aren't effectively baked into using an AI assistant.
As any president should in that scenario? I'm sorry, we're going to nuke professional class workers and let tech executives keep their 2026 money from the proceeds and let the losers go jobless? Not likely if you don't want a bloodbath. Let me be clear: fuck Trump, but any president who doesn't do that is out of their mind.
It is not at all clear that monetary policy can actually work here, which is what the statement is saying. When your demand side policy doesn't work, it's just pushing rope. It doesn't matter if or how bad you want a certain outcome.
Maybe too late. Trump just walked on stage for the SOTU and Gold either jumped up a bit or the dollar declined in value, whichever way you want to look at it.
The fed was very intentionally set up to be resistant to tampering from political forces, and especially the executive. The entire governance structure is so that they can take actions that may be painful in the short term without being stopped by politicians.
Before Trump it was, for good reason, incredibly taboo to place pressure on the fed or even hint at interfering. Most economists are pretty horrified that particular barrier has been crossed.
The fed has a pretty big stick, and a mandate to try to balance inflation with unemployment. Throwing politics into the mix is a very bad idea since politicians worry about very different things, and adhere to election timelines.
The president has no business getting involved here.
Then what about banking & finance pre central bank era are you nostalgic for?
Because if the current system favors the bankers, the previous system sure as hell favored the bankers. Is it the bank runs?
I guess I should say this is all academic now, since we're about a month an a half away from Weimarizing the dollar lmfao. We've been kicking the institutional legs out from the stool for a while and we will discover the virtue of an independent central bank whether we like it or not.
Bankers have been a problem as long as there have been banks with fractionally reserved deposits. The Fed just stabilized the appropriation of surplus value by the banking system through the issuance of credit. There is nothing independent about it: it will preserve the large banks come hell or high water, and soon enough we'll get both.
I would prefer a social credit system (not the Chinese kind, the other kind) where the money supply is managed for the public good via a citizens dividend tied to the productive capacity of the economy, coupled with making gold buying/selling tax free as a savings (and monetary disciplinary) mechanism.
I have the advantage that this system will never be tried, and therefore I can never be proved wrong.
Ok. We'll see how that shakes out in a year or so. Most folks in the west have never lived in a country where a dictator controls the money supply. It's REAL easy to shit talk the US or even european central banks are when you have no idea what the alternative is.
How do you plan an exit strategy for something that may or may not obsolete a whole field in a matter of months? Not sure there's a real way to do such a thing.
reply