Lyle retweeted
I'm saying the world could be a more tranquil place if people like you were boiled, that's all
Lyle retweeted
You're in the hospitality business, not the paying-off-my-mortgage-without-consequences-or-inconvenience business.
Lyle retweeted
Hello @nickshirley @libsoftiktok @ScottPresler you guys were right voter fraud is real! Please report on this!!!!!
Lyle retweeted
Lex Fridman interviews a PHP security researcher
Lex: My guest today discovered a critical vulnerability in PHP. What is a vulnerability.
Researcher: A weakness that allows an attacker to compromise a system.
Lex: But aren't we all vulnerable.
Researcher: Yes, but
Lex: Is love a vulnerability.
Researcher: We're talking about remote code execution.
Lex: Could an attacker remotely execute love.
Researcher: No.
Lex: Stalin executed millions.
Researcher: What does that have to do with
Lex: Do you think Stalin was happy.
Researcher: I have absolutely no idea.
Lex: Fascinating. We're 3 hours in. Let's talk about consciousness.
The unhinged AI psychosis posts I see these days has me realizing that most of you apparently didn't know what the fuck you were doing before you gave up your brains to LLMs, and so your opinions now are even less trustworthy.
Lyle retweeted
My top advice to junior software engineers:
Eat more eggs.
When I was a junior engineer, my boss asked me, "Hillel, how many eggs have you eaten today?"
I told him, "three."
He said, "that's not enough eggs." And then he gave me four more eggs.
I ate the eggs and eggshells and immediately got promoted to regular engineer.
To become a senior engineer, I had to eat twelve eggs. To become a staff engineer, I had to eat twenty seven.
Nowadays I won't even *consider* jobs where the engineering director can't eat sixty eggs at once.
Got any more #tips for Junior engineers? Please share in the comments!
Lyle retweeted
The Campfire ports and benchmarks are invalid. Nothing published is of credibility.
Yes we will be reading code less or none in the future. But that’s not today.
The Campfire ports proved absolutely nothing except one individual got bamboozled by AI’s benchmarks.
Lyle retweeted
This is exactly what happens when nobody reads or writes the code. The Rust port got hand-tuned fragment splicing, cached digests and compiled templates. The Go port re-hashes and re-copies the whole page every request. You're not benchmarking languages, you're benchmarking how much attention each port got.
I've had agents implement and optimize the Campfire web app in Elixir, Go, and Rust. Yes, Ruby is the slowest. I didn't care about that when the pay-off was huge in terms of productivity and developer joy. But if you're no longer reading the code? github.com/basecamp/once-cam…
Readers added context they thought people might want to know
The shown benchmarks use non-equivalent implementations: Elixir routes all DB queries through a single GenServer with Redis for jobs (retained from Rails), while Rust uses in-process queues, omits CSRF tags/fields, and applies other caching changes.
github.com/basecamp/once-…
raw.githubusercontent.com/basecamp/once-…
github.com/basecamp/once-…
github.com/basecamp/once-…
x.com/zachsdaniel1/s…
Lyle retweeted
But you compared the performance to a build you iterated on - with a model presumably - dozens of times.
Do you not see how this is terrible experiment?
Rust may yet be the best choice here but you didn't show that in any way and now just look really silly and are driving the narrative that you are not a real software engineer.
Lyle retweeted
Disasters avoided this week by reviewing Opus 5.5's work:
- allowing anyone to elevate to admin privileges
- every message sent to every mobile device in the fleet
- crashing the OTel collector from stupidity
- reusing a UI for a nearly identical purpose doubles the app code
Found one, lol. Guy does a drive-by shitpost and blocks me so I can't respond.
I can explain, though: twitter is extremely dumb and curating a herd of dipshit followers doesn't even register as something worthy of effort.
Open invitation for somebody to set me straight...
Lyle retweeted
I installed omarchy to see what the hype's about and still don't get it. Feels like the Arch dotfiles of a guy with a big following who just discovered linux and r/unixporn. The community seems unaware that none of this is new and is rediscovering footguns from first principles.
Lyle retweeted
Let me do one serious post chat, and I'll resume shitposting. This is important to make explicitly clear.
Two weeks ago, fellow Dane, David Heinemeier Hansson (@dhh) went on a public tirade about Nix and the Linux ecosystem.
"Goddamn maniacs." "Clowns." "Goblins." "Cancer."
In the same conversation, he called Nix “amazing technology.”
Two days ago, it became clear that he is planning to build his "distribution" on NixOS.
That is worth dwelling on.
NixOS can be criticized. Of course it can. We criticize ourselves constantly.
What I find deeply gross is arriving as a tourist to an ecosystem, using an enormous platform to ridicule the people who built it, then deciding their work is good enough to become the foundation of your own project.
Much of his indictment is not even about NixOS. Land acknowledgements? That is not some defining debate here. It is Twitter culture-war material imported into a caricature of a community he barely knows.
For someone so insistent that technology should be "apolitical", David spends a lot of time talking about politics, culture, codes of conduct, and community governance.
He rails against codes of conduct, then writes rules for how people in his own community should behave while insisting that somehow does not count.
Call it whatever you want. Communities require governance.
And governance, packaging, security, infrastructure, release engineering, review and maintenance are not distractions from building a distribution.
They are the work.
So far, what he has is a configuration and installer layer on top of years of work by Arch, Linux, Rust, and soon NixOS and Nixpkgs contributors.
Using Claude to produce that glue does not make the work underneath disappear.
Packages, infrastructure, security and technical knowledge exist because people did the difficult, boring work required to make this ecosystem function.
You are not replacing those people. You are depending on them.
Which makes the rhetoric about creating a home for the "competent" people obnoxious.
David, the competent people are already here.
They are the people your project depends on — including people and communities you have been calling clowns.
You do not get to praise the "amazing technology", dismiss the people who sustain it as politically deranged, put a layer on top, and cast yourself as the serious technical adult in the room.
That is not escaping dysfunction. It is standing on other people's work while sneering downward.
People mock NixOS. They declare it insane. They explain why nobody should want it.
And then they use it anyway. So who's competent here?
You can hate us. You can mock us. You can call us clowns.
But when the answer to your own technical problems is to build on our work, that tells its own story.
So, David: welcome to NixOS.
But understand what you are standing on.
If you intend to build on years of work from this community, the attitude adjustment is overdue: less culture-war posturing, more respect and humility toward the people doing the work you now depend on.
