cbarrick

The OP is building a blogging platform, with an editor. It's not just a personal blog.

TBF, they could have explained that better in the post.

Look at the incentives. Google makes money from ads. Bad ads cause users to distrust Google ads, causing those users to be less valuable, causing advertisers to spend less with Google.

The goal is maintaining a continuous stream of revenue, not killing the stream for short term gains.

Google has an entire org dedicated to detecting and preventing bad ads.

I have many coworkers who work very hard on this problem.

The claim that Google does not care about ads integrity runs counter to my experience.

Genuinely cool, but the LLM-speak started to wear on me.

An editing pass to make the prose less "punchy" would be great.

OP is describing a distopia.

I _want_ to write code for my job.

Unfortunately, this is exactly the direction the industry is heading.

This is exactly my problem.

I got into this industry because I enjoy programming, and I wanted to get paid for what I enjoy.

It sucks that the fun part of the job is gone.

I agree, except that TAI is off from UTC by 37 seconds.

That's a pretty big smear if you want to convert an existing clock from one to the other.

You have it there.

It's on the blog post by Tejas Kumar [1], when the viewport width is narrow.

https://tej.as/blog/aleph-alpha-kolibri

I got distracted by that scroll-wheel UI component on the page. Neat!

Indeed. Regexes are _regular_, which is non hierarchical by definition.

The two are useful for different layers of abstraction: regex is for lexing and PEG is for parsing.

Speaking of the Chomsky hierarchy, last I checked, it is still unproven whether or not PEGs can parse all context free languages. Intuitively, they're _probably_ weaker than CFGs, but no one has yet provided a counter example.

But they could always do that with regular passwords.

Like, no company should be storing anything but a salted hash of their users' passwords.

I think people are focusing on the training data issue too much. If the data was contaminated, I can still blame that on negligence.

But, at least with the Navier-Stokes solution, it's clear [^1] that they learned that Alpöge and Buckmaster were getting close to a solution and learned of the general approach they were taking. Only after learning the secret to cracking the problem did they send the first prompt.

What makes this worse to me is the intention. They intentionally threw $15 million in compute at the problem in order to scoop the result. They intentionally left Buckmaster and Alpöge out of the citations.

Data contamination should be enough to disqualify them from the prize, but I can believe it to be accidental. On the other hand, someone made an intentional decision to scoop the result by throwing money at the problem. That's so much worse.

[^1]: That's the timeline claimed by Buckmaster, and no one from OAI has disputed it.

> it was a whole team at OpenAI working on the problem

Well, a whole team plus $15 million in compute spend.

(That's what OAI would have charged for the same number of tokens.)

For sure. But I can definitely produce something good enough to get the job done in a much shorter time by bootstrapping myself from an LLM output and editing from there. (I do edit. Raw LLM output is such a drag to read. Too low signal.)

I don't care if anyone else cares that my code has my voice. My voice doesn't add value to the code. But what other people think of my code is entirely beside the point that I'm trying to make.

To me, code is a creative endeavor. I know that this isn't a universal feeling, but to me the act of creating is more personally valuable than the creation. So when I read code that I wrote (with the help of a tool) that doesn't sound like me, I feel like I have robbed myself of something that I find personally important.

My employer, or anyone else, doesn't care and probably shouldn't care about my experience during the act of creating. The creation is what matters to the external world.

But like, I don't think I'm alone in valuing my own creativity and finding that creativity in code.

(And please don't misunderstand. I'm definitely not arguing that code produced should be "clever" or "creative" in the other sense of the word. I'm just talking about the experience of creativity.)

I am using LLMs more and more to help me write docs at work, simply because I do not have time to start these docs from scratch. And it pains me so much that my writing no longer sounds like me.

This is fine at work, I guess. I'm not being asked to sound like myself. I'm being asked to convey an idea to an audience as efficiently as possible, both in terms of my time and theirs.

But I can't shake the feeling that the LLMs are eating my soul.

I still don't use them often to write code. Not that I have issue with those that do, but that sounding like myself in code is a part of my soul that I'm having difficulty giving up.

I know I'm in the minority, but WFO works great for me.

My office is in walking distance of my home. I get great office perks (lunch, coffee, quality meeting rooms, good desk and workspace). And having a second space for work that is not my home is great for my mental health and WLB.

All of my meetings are still video conferences. Doesn't move the needle for me.

I choose to be in office 5 days a week even though only 2 are required, and it's been great for my productivity.

WFO in a shitty office is still a shitty experience, but an actually good office space is a productivity boost IME.

That shell snippet will expand shell variables in double-quote strings. And apparently the entire reason for this fork is to not do that.

Which is dumb. The canonical spec for .env should just be "whatever POSIX sh does."

One of eight color choices. Last one in the list.

If anything, the argument works better as a reason to remove gray from the list.

The use of grayscale is a bit disingenuous.

Gray is not the default color theme on macOS. The default is blue. So the criticism about using right/left to distinguish on/off doesn't really apply. In reality, the use of color disambiguates the on and off states. Just like the physical toggle example it's being compared against.

That's not to say there aren't problems with toggles, but the article's core argument falls apart if you use any color theme other than gray.

TK has the formal title of CEO of Cloud.

CEO of <thing> is a layer above SVP.

Google has many layers of management.

The organicness of the original was really fun. Dunno if coordinating here really fits the HN vibe, but also go where the people are.

Are we coordinating factions here, like the original r/place? The social aspect was such a big part of the original. I'll start:

# PURPLE FRAME #

Our mission is to draw a purple frame around the canvas. 2 rows of blank space between the frame and the top/bottom of the canvas. 4 cols of blank space between the frame and the left/right of the canvas.

I can't see my cursor if it is placed on top of a cell that has already been colored.

There is a separate manual for dashes: https://type.today/en/journal/dash

The Turis Omnia runs a derivative of OpenWrt. They provide a custom UI with an option to switch to LuCI. It's easy to flash it to upstream OpenWRT, which is what I do.

Explain xkcd has links to the Wikipedia articles for each hole.

https://www.explainxkcd.com/wiki/index.php/3266:_Holes

And for those that aren't aware, a PKGBUILD file is just a bash script.

Please adjust the color contrast. I can hardly see the cannon balls.

The journal regularly includes commentaries and editorials on political and economic topics [1][2]. Political talks regularly occur at the conference [3].

In fact, the trigger to all of this was a scheduled talk by Jay Bhattacharya, Director of the NIH and a controversial political figure.

It seems silly to imply that politics are to be excluded from the conference at all costs when the ADA regularly invites political speakers to that same conference.

Do you believe that handing out copies of this editorial constituted inappropriate behavior? If so, why?

[1]: https://diabetesjournals.org/care/article/49/1/5/163166/The-... [2]: https://diabetesjournals.org/care/article/48/8/1309/162954/T... [3]: https://diabetesjournals.org/care/pages/2025_ada_diabetes_ca...