Greg Wilson"Your phone is not a slot machine. It's a to-do list that writes itself." https://www.terrygodier.com/the-last-quiet-thing
Roli on Rails
- 59 Followers
- 64 Following
- 49 Posts
Kasper Timm HansenIt's been 4 years since I left Rails core, and my most impactful work has happened since I left.
Here's a writeup of it all:
https://kaspth.com/posts/i-quit-rails-core-4-years-ago-heres-what-ive-been-up-to
What a weird wold we are living in: https://harpers.org/archive/2026/03/childs-play-sam-kriss-ai-startup-roy-lee/
So much for Anthropic "more moral stance"… https://youtube.com/shorts/jPThSwhJ8CE?is=XCDuGvaXMHoVDQxD
Anthropic’s CEO on his fight with the Pentagon
TIL: you can use different formaction attributes to submit to different endpoints within the same form.
Like "Save as Draft" vs "Save and Publish"
Google Search has become unbearable with the AI overview. It pushes its own summary, then ads, so much scrolling until you get the first proper search result. So now I am giving Kagi Search a real try.
Rémy HannequinMany thanks to @hharen and @crackofdusk for an exceptional edition of @helvetic_ruby, and to all the speakers and attendees. I had a great time and I can relate to the many good things I heard about the conference these last two years!
Helvetic Ruby was a blast! Awesome conference, awesome people!
Collin DonnellNew episode of the Rooftop Ruby podcast out now!
Dave Copeland 
Actually, this is a case study in poor executive communication.
https://discuss.rubyonrails.org/t/a-short-case-study-on-how-to-discourage-documentation-prs/85853
The person in charge of Rails Foundation really did tell the OP to go fuck themselves. No empathy for their experience, or why they perceived it the way they did. No empathy for moving the goal posts, even if there may be good reason/precedent to do so. And, no help in solving the actual issues. End result is that Rails essentially doesn't document this odd behavior and one less person engaged in helping
A short case study on how to discourage documentation PRs
The Rails foundation has been talking about improving docs for a while now [@AmandaPerino ], and that’s partly what encouraged me to make the effort to submit a couple of changes. It started well I hit an issue with some unexpected behaviour. As far as I could see, this wasn’t documented - though I could see where it came from in the code. A helpful core team member pointed out that this was a duplicated issue, and the dupe explains why this is expected behaviour. The same person commented...