Readit News logoReadit News
tuyiown commented on The Geological Sublime   harpers.org/archive/2025/... · Posted by u/prismatic
turnsout · a month ago

  > As for the amber stream pouring into my gas tank as I stand at the self-service pump on my way to Walden, I now take it and all the other plant-based fossil fuels to be an infinity of petrified sunlight, best understood through the compound lens of the Lyell-Darwin eye.
This is the most nihilistic essay I've read in a long time. It contemplates climate change and the extinction of humanity with a lyrical nonchalance that is misanthropic at best. Keep pumping that liquid sunshine, Lewis.

Every single one of us needs to wake the fuck up. The author is right that the planet itself will be fine without us. If we want to survive as a species, we can't bask in decadence and romanticize the decline.

tuyiown · a month ago
> Every single one of us needs to wake the fuck up.

And how do you plan to achieve that ? The denial of reality of human psychology and politics is one of the reasons denial of climate change is still rampant. Yelling at people with urgency only works that much, and it also amplifies resistance.

In the end, everyone needs to wake the fuck up implies a sheer resolution of the need for change, and you won't bring that by schooling people, yelling at them or even violence. The inevitable is there, do what you think is best, tell what you think is best and you'll probably have maximized your contribution already.

Contemplating how things plays out in the end is not nihilistic, it's a form of acceptance of the real hard truth about the grip we have, as individuals, on the mater.

tuyiown commented on Nullable but not null   efe.me/posts/nullable-but... · Posted by u/efeoge
matsemann · a month ago
Problem is you end up other places with the assumption thar it's never null. So in the future when you actually set it to null somewhere it will blow up.
tuyiown · a month ago
People that assume that a (nullable) value is never null because the sample at hand does not contain a null value _will_ learn their lesson the hard way, the one you describe.

But even non-nullable does not always resist to time, I'd argue that use cases where the field _has_ to be null eventually emerges and somehow have to be mitigated. There is no easy solution to safely workaround that without either tons work that duplicates lots of things or taking risks by adapting the code base.

tuyiown commented on What went wrong inside recalled Anker PowerCore 10000 power banks?   lumafield.com/article/wha... · Posted by u/walterbell
jppj · a month ago
Was this last paragraph necessary?
tuyiown · a month ago
We're talking about culture differences about perception of accountability. Not necessary but definitely on topic.
tuyiown commented on I was wrong about robots.txt   evgeniipendragon.com/post... · Posted by u/EPendragon
vintagedave · a month ago
Or a positive belief in human nature.

I admit I'm one of those people. After decades where I should perhaps be a bit more cynical, from time to time I am still shocked or saddened when I see people do things that benefit themselves over others.

But I kinda like having this attitude and expectation. Makes me feel healthier.

tuyiown · a month ago
I deeply agree with you, and I'd like to add:

Trust by default, also by default, never ignoring suspicious signals.

Trust is not being naïve, I find the confusion of both very worrying.

tuyiown commented on LLM Inevitabilism   tomrenner.com/posts/llm-i... · Posted by u/SwoopsFromAbove
mg · a month ago
In the 90s a friend told me about the internet. And that he knows someone who is in a university and has access to it and can show us. An hour later, we were sitting in front of a computer in that university and watched his friend surfing the web. Clicking on links, receiving pages of text. Faster than one could read. In a nice layout. Even with images. And links to other pages. We were shocked. No printing, no shipping, no waiting. This was the future. It was inevitable.

Yesterday I wanted to rewrite a program to use a large library that would have required me to dive deep down into the documentation or read its code to tackle my use case. As a first try, I just copy+pasted the whole library and my whole program into GPT 4.1 and told it to rewrite it using the library. It succeeded at the first attempt. The rewrite itself was small enough that I could read all code changes in 15 minutes and make a few stylistic changes. Done. Hours of time saved. This is the future. It is inevitable.

PS: Most replies seem to compare my experience to experiences that the responders have with agentic coding, where the developer is iteratively changing the code by chatting with an LLM. I am not doing that. I use a "One prompt one file. No code edits." approach, which I describe here:

https://www.gibney.org/prompt_coding

tuyiown · a month ago
Inevitable, but for a very narrow specific use case irrelevant for most the humankind, hardly comparable to internet and the web.

It's pretty clear that there are many specific uses cases where LLMs shine. It's the path from general use (ask it anything) to unidentified specific use case (anything identified and addressed correctly) that is very unproven to happen without some kind of pre-existing expertise.

Dead Comment

tuyiown commented on What do wealthy people buy, that ordinary people know nothing about? (2015)   old.reddit.com/r/AskReddi... · Posted by u/Tomte
socalgal2 · 3 months ago
Worst experience I've ever had was with a Miele dishwashing machine at an AirBnB in the Netherlands. I like my Miele vacuum cleaner though
tuyiown · 3 months ago
The only thing people look up on Miele stuff is to last 20 years minimum. That and maybe the cutlery tray on dishwashers, but the patent expired some time ago. Everything else barely matters if the thing is workable one way or another.
tuyiown commented on Working on complex systems: What I learned working at Google   thecoder.cafe/p/complex-s... · Posted by u/0xKelsey
braza · 3 months ago
I don't think this is adequately addressed by the "complicated vs. complex" framing—especially not when the distinction is made using reductive examples like taxes (structured, bureaucratic, highly formalized) versus climate change (broad, urgent, signaling-heavy).

That doesn’t feel right.

Let me bring a non-trivial, concrete example—something mundane: “ePOD,” which refers to Electronic Proof of Delivery.

ePOD, in terms of technical implementation, can be complex to design for all logistics companies out there like Flexport, Amazon, DHL, UPS, and so on.

The implementation itself—e.g., the box with a signature open-drawing field and a "confirm" button—can be as complex as they want from a pure technical perspective.

Now comes, for me at least, the complex part: in some logistics companies, the ePOD adoption rate is circa 46%. In other words, in 54% of all deliveries, you do not have a real-time (not before 36–48 hours) way to know and track whether the person received the goods or not. Unsurprisingly, most of those are still done on paper. And we have:

- Truck drivers are often independent contractors.

- Rural or low-tech regions lack infrastructure.

- Incentive structures don’t align.

- Digitization workflows involve physical paper handoffs, WhatsApp messages, or third-party scans.

So the real complexity isn't only "technical implementation of ePOD" but; "having the ePOD, how to maximize it's adoption/coverage with a lot uncertainty, fragmentation, and human unpredictability on the ground?".

That’s not just complicated, it’s complex 'cause we have: - Socio-technical constraints,

- Behavioral incentives,

- Operational logistics,

- Fragmented accountability,

- And incomplete or delayed data.

We went off the highly controlled scenario (arbitrarily bounded technical implementation) that could be considered complicated (if we want to be reductionist, as the OP has done), and now we’re navigating uncertainty and N amount of issues that can go wrong.

tuyiown · 3 months ago
I was very centered on the software part of the problem. A complex problem can be solved with a complicated chain of small technical solution. At implementation level, its complicated, not complex, e.g. you mostly need knowledge of the general problem to understand the solution, and many added things make things complicated.

My take is that if your complex problem is only solvable by complex software (e.g. not a combination of simple small parts), and _cannot_ be reduced to simpler things, you are in the complex space.

Maybe it's too reductive, it's just my opinion, but it's a good way for me to determine predictability on ability to solve a problem with many unknown, at the engineering level. The dangerous blockers are in complex space, identifying them early is critical. Complicated stuff can be worked around and solved later.

tuyiown commented on Working on complex systems: What I learned working at Google   thecoder.cafe/p/complex-s... · Posted by u/0xKelsey
braza · 3 months ago
One of my pet peeves with the usage of complex(ity) out of the traditional time/space in computer science is that most of the time the OPs of several articles over the internet do not make the distinction between boundaried/arbitrary complexity, where most of the time the person has most of the control of what is being implemented, and domain/accidental/environmental complexity, which is wide open and carries a lot of intrinsic and most of the time unsolvable constraints.

Yes, they are Google; yes, they have a great pool of talent around; yes, they do a lot of hard stuff; but most of the time when I read those articles, I miss those kinds of distinctions.

Not lowballing the guys at Google, they do amazing stuff, but in some domains of domain/accidental/environmental complexity (e.g. sea logistics, manufacturing, industry, etc.) where most of the time you do not have the data, I believe that they are way more complex/harder than most of the problems that the ones that they deal with.

tuyiown · 3 months ago
I think this is addressed with the complex vs complicated intro. Most problems with uncontrolled / uncontrollable variables will be approached with an incremental solution, e.g. you'll restrict those variables voluntarily or involuntarily and let issues being solved organically / manually, or automatisation will be plain and simple being abandoned.

This qualify as complicated. Delving in complicated problems is mostly driven by business opportunity, always has limited scaling, and tend to be discarded by big players.

tuyiown commented on From: Steve Jobs. "Great idea, thank you."   blog.hayman.net/2025/05/0... · Posted by u/mattl
williamdclt · 4 months ago
I’m confused why cron jobs would be sending emails to root@hpe.com?
tuyiown · 4 months ago
(not an unix sysadmin, just guessing what happened from my shaky knowledge)

cron jobs reports activity by email to the user (UID) they are running, historically UNIX boxes have the ability to handle mail locally (people would leave messages to each other by connecting to the same server via terminal), so that the root cron activity would land into the root (/root) account mbox file.

When email got interconnected more across servers, generally the service that would dispatch mail to the users account on their home folder on the server started to be able to forward to to others servers, if a domain name was provided. Add to it the ability to fallback to a _default_ domain name for sending email into the organization, and voilà, the root email account for the default domain name receives the entirety of the cron jobs running under root of all the servers running with the default configuration and domain fallback.

u/tuyiown

KarmaCake day954July 16, 2015View Original