@Ryanbigg Does that work if Your or Your::Namespace haven't been defined, too?

@hschne If you're using RSpec, there's even a metadata version that you can enable that can condense it even more!

https://benoittgt.github.io/vcr/#/test_frameworks/rspec_metadata?id=pass-a-hash-to-set-the-cassette-options

@emma this scanned just a little bit like the william carlos williams poem...

i have deleted
the jquery
that was in
your front-end build

and which
you were probably
abusing
for document.querySelectorAll

Forgive me
that was deprecated
so $
and so old

@james Oh, that's really cool! I recently learned about git worktree, which I found to also be an utter balm for the stash workflow, but npm/yarn don't play well with it.

@matt I'm running blocky on my homelab for much the same reason.

@aibarra I love Ruby's expressiveness! To add one to your list, in the latest version (3.4), in single-arg blocks, you can refer to the arg as it, hence: fruits.each { puts it }!

@Ryanbigg Your browser needs to update. Please close to continue.

The people who are responsible for the recursive flag on chmod being -R and -r on scp are my mortal enemies.

If you’re still masking…thank you

If you’re trying to educate others on the benefits of masks…thank you

If you’re standing in solidarity with disabled & vulnerable people who’ve been cast aside for the last 5 years…thank you

Its not easy being the lone masker in 2025, but we see & appreciate you

@GramrgednAngel Jokes aside and difficulty in remembering what the spelling-du-jour actually is in Canadian English, it's also super cool as a language nerd to see how living the grammar and spelling actually are.

@GramrgednAngel weeps in Canadian English

@raganwald (These days, it also feels a bit like an early warning system in that anyone who would defend its use in hiring is probably not very fun to work with or talk to.)

Maybe I missed it but I haven't seen any of the Rails leaders condemning openly mr Rails.

Now's a really good time, unless you still wanna argue that it's fine to have opinions on the Internet and he's absolutely not a fascist.

@collin I come back to Dynalist over and over again, but it's just an outliner. Accommodates my flows reasonably well.

@MoskitoHero ... I think I'd stick with dry-(struct|initializer|types) because I wouldn't have to type out and read id, role, and name quite so many times, nor define the initialize method. The reduced visual complexity is enough of a win for me, even if I wasn't frequently using complex types with constraints.

It's definitely an intriguing pattern, though, and I enjoy seeing the stuff people come up with pattern matching. On the chance you haven't seen it, @joeldrapper's Literal library does some really interesting and similar things using the === operator.

been trying obsidian for note taking since yesterday and one the biggest pain points is that when i want to launch the app, i type 'obs' and hit return, and OBS starts and i begin a successful career as a streamer and vtuber, until, plagued with unwanted attention and controversy, i settle for a series of misjudged advertising deals and launch a short-lived hair-care and perfume brand

@Scottw Order is an interesting one to consider. I've seen a lot of different approaches to enforcing filtering with multitenant concerns, but ordering isn't one that I've bothered to think much about.

default_scope is pretty noxious, but if you're just specifying an order it might be less of an issue... My own inclination is that I wouldn't trust it without significant tests, though.

@Scottw Depends on how much guarantee you'd like to ensure the query has the default order, I guess:

At the weakest level, just append a scope to your queries and beat your devs with a wrench if they mess up. Write a linting rule if you wind up spending too much time wielding a wrench?

Slightly stronger: you can use a wrapping object; I've seen folks use a Pundit policy or a Gateway/Repository object.

Stronger yet: Make your ActiveRecord models private and do Gateways or something.

Ad infinitum: put your AR models in a different process? Switch to ROM or something similar that discourages direct access? Patch #exec_query or add an instrumentation notifier to raise when a query doesn't have the correct ORDER in it?

@Ryanbigg and yet the focused simplicity has let!(:nothing) { dilute_the_clarity_of_what_you_were_trying_to_say }...

Hot take: coming back around to the idea that Cucumber tests might be better maintenance-wise than writing pure RSpec.