//
sign in
Profile
by @danabra.mov
Profile
by @dansshadow.bsky.social
Profile
by @jimpick.com
AviHandle
by @danabra.mov
AviHandle
by @dansshadow.bsky.social
AviHandle
by @katherine.computer
EventsList
by @katherine.computer
ProfileHeader
by @dansshadow.bsky.social
ProfileHeader
by @danabra.mov
ProfileMedia
by @danabra.mov
ProfilePlays
by @danabra.mov
ProfilePosts
by @danabra.mov
ProfilePosts
by @dansshadow.bsky.social
ProfileReplies
by @danabra.mov
Record
by @atsui.org
Skircle
by @danabra.mov
StreamPlacePlaylist
by @katherine.computer
+ new component
ProfilePosts









Loading...
Sidekiq has a TUI now: www.mikeperham.com/2026/03/10/s... I've been helping build it!
Bridgetown 2.2 "Verdant River City" is out! It's a springtime bloom of new features: - Wikilinks in Markdown - Support for Falcon, the highly concurrent Ruby web application server - New sponsorship opportunities - Sneak peak at the Bridgetown Center program 👀 www.bridgetownrb.com/release/ever...
If you save them as snippets in a text expander (I use Espanso), then you have near-effortless copying of code from Pry/IRB, and you're one step closer to the Nirvana of REPL-driven development in Ruby.
My world is shattered. For years I've told coworkers who write RSpec blocks with `describe ".some_class_method"` to instead use "`describe "::some_class_method`" (with a double colon instead of a dot).
Or add a REPL method/command: In .pryrc: ``` Pry::Commands.block_command "cp", "Copy last command to clipboard" do IO.popen("pbcopy", "w") { |cb| cb.write(pry_instance.input_array.last) } end ``` In .irbrc: ``` def cp IO.popen("pbcopy", "w") { |cb| cb.write(Reline::HISTORY[-2]) } end ```
But today, I discovered that RSpec itself uses the dot notation for describing class methods: github.com/rspec/rspec/... So here is my public apology to everyone affected by my misguided pedantry.
4mo
3mo
1mo
1mo
4mo
1mo