Pinned Tweet
Really excited and grateful for the opportunity!
@realntl will introduce us to Test Bench at wroclove.rb 2023🚀
Test Bench was built with one simple goal in mind - to reward the diligent developer with a modest testing tool that stays out of their way. For over seven years now, Test Bench has been getting simpler and simpler!
Claude just unironically and confidently dropped the term "duck-probing" in a sentence about some Ruby code it was working on (Ruby being known for it's "duck typing").
You're alright, Claude. Don't ever change.
Sad that @TheLibPatriot is shutting it's doors. It's getting harder to stave off the feeling of political homelessness. They were one of the few making the case for the Dems to take position where Americans are actually at, rather than where the pressure groups want us to be.
I'm so excited, thanks @tuple !
Nathan Ladd retweeted
The paradox of civilization is that the more one is anxious to survive, the less survival is worth the trouble.
Nathan Ladd retweeted
📻 Tune in and join @Robbyussell and @realntl as they discuss why “perfectly maintained software” might be a platonic ideal rather than a realistic target. 🎯
🎧 Listen here: buff.ly/TelcgXB
Nathan Ladd retweeted
Honestly it's pretty incredible that the winners of a super-darwinian multi-million person tournament sorted in large part by how devotedly you followed instructions from authority figures as a child are as progressive as they are.
Nathan Ladd retweeted
Russians are using donkeys to transport arms to the frontlines. Their old stock of Soviet weaponry is almost depleted.
Why are Trump and Vance so desperate to snatch defeat from the jaws of victory for the West?
Behind the tough guy language, there is no argument here. What's the firepower advantage of the respective parties to the conflict? Manpower? How might that change with further NATO action, and how are you proposing to change it?
As it turns out, I'm right and Joshi is wrong, though maybe he believes the underlying dynamics *could* change in the future. He's welcome to make that argument.
Nathan Ladd retweeted
The risk of World War III is entirely in what war crimes a fascist regime may freely choose to commit against innocent people for no reason other than its demented ideology.
Just like World War II.
In my experience, the most significant indicator of team health is how infrequently a team repeats the same mistake.
A team that rarely repeats the same mistakes twice:
- Engages in technical communication constantly, and is therefore tapping its collective intellect
- Takes problems seriously and cares about its users
- Consistently shines sunlight on mistakes without a culture of shame or fear
- Is striving for continuous improvement
This quoted post is unavailable.
For anyone seeking an explanation for the outcome, Starr County seems like a good place to begin.
Nerd spaces are oversocialized, exhibit no. 54354325: stallman-report.org
Just admit you can't stand the guy's views on proprietary software because they would mean less access to high paying jobs! Nothing wrong with that.
The accusation that the Kind Communication Guidelines he wrote are "transphobic" is an absurdity to end all absurdities. gnu.org/philosophy/kind-comm…
Nathan Ladd retweeted
There are three basic genres of fantasy in America:
1) High fantasy, which means imagining we had cities that look like Europe
2) Science fiction, which means imagining we had cities that look like Asia
3) YIMBY, which is a mix of both
The chief problem I see with many of the techniques common in the DDD/ES community is an attraction to solutions that attempt to obviate domain modeling (!).
Nathan Ladd retweeted
I really don't get Go developers who use Docker. You have a language that has amazing cross platform support and builds fully self-contained binaries. You could easily target every platform with single binary downloads and you use a system that repackages it again?
"With FP, you don't need all those GoF patterns" is one of the more ridiculous claims I hear semi-regularly.
You can "just wing it" and ignore design patterns in OO, too.
You might end up with code that's good. If you do, though, you'll find GoF patterns reflected in your code.
Really enjoyed @zverok 's proposal for improving Ruby's pattern matching:
bugs.ruby-lang.org/issues/18…
It inspired an additional elaboration that I added to the comments section:
bugs.ruby-lang.org/issues/18…
Nathan Ladd retweeted
I agree. There's a lot that is messy about this. And there's plenty of room for discomfort about this chain of events. But willfully sacrificing tens of billions of dollars suggests that there are more that purely business motives at work here.
