matt boldt

(Using my highly developed powers of pattern recognition) I have made the same mistake again

@JasonSwett Oh and nested associations that can unexpectedly trigger creation of more records with the default build strategy, leading to invalid factories or hard to diagnose side effects.

@JasonSwett Choosing build/build_stubbed/create, handling deeply nested associations, reusable but flexible traits & sub-factories, keeping factories valid at model level, performance monitoring, global persisted state, testing things like rake tasks where you can’t pass a factory as a dep.

In a book about Rails testing, what would you expect or hope to find in a chapter about Factory Bot?

one time in work slack someone replied to a thread saying “I watched a documentary about this recently!” and someone asked “was it last night’s @iamjohnoliver episode?” to which they enthusiastically replied “yeah!” and I think about this a lot.

@JeromeHardaway instagram.com/reel/C2auKjqvs… a bit different but these tacos are delicious

@tenderlove fyi @getbentsaggy is responsible for my beautiful laptop sticker

in case you’re wondering what living in texas is like

@JasonSwett mom’s gonna fix it all soon

One great big festering neon distraction I have a suggestion to keep you all occupied

@nateberkopec would also be a good alternative to validation contexts, as well as provide a smaller blast radius for callbacks at the repo level

The biggest thing Rails is missing is a repository object. Trying to use ActiveRecord::Relation doesn't work, except in trivial examples. A repository object pattern would make N+1s easier to solve, and would make data loading much more intuitive and yet still extensible.

obvs coming from ruby there's gonna be a ton of differences, but like, needing to dig thru stackoverflow threads to figure out the "right" way to create a string seems wrong

attempting to learn rust. there appear to be 4 different ways to create an owned string -- it's up to your preference 🤔

@mike_mayo they told me to reboot and it worked

excited to announce that today was the first time I took a photo of my computer screen and sent it to IT

@gordysc ruby-focused is great. I'd just like a holistic view of application development (with ruby/rails as the vehicle) without being *too* tied down to a specific framework's features. If that makes sense.

@atmattb I think there are some concepts you could certainly apply elsewhere, but it does feel very Rails/Ruby focused IMO. What tech stack were you thinking of?

This is one of the few books I've sat down and read cover to cover. A ton of great thoughts/insights and references. Highly recommend for folks who've worked on Rails for a while.

@JasonSwett I feel like abstractions are correlated with, but not exactly caused by, de-duplication.

Based on a lot of reading I've come to understand that many programmers hold the belief of: "De-duplicated code = an abstraction" "Duplicated code = not an abstraction" So weird. Why in their minds does the involvement of duplication make the difference?

@thedayisntgray Agreed. I suspect the name fit better when they started as a non-profit.

OR of course you could be solving frustrating problems to make up for a flawed environment or process. I feel like there's a fine line between these two, tho.

starting to realize that the some of the more frustrating and arduous problems you solve become the most valued and appreciated in other words, if you're feeling annoyed, you may be doing the work you're uniquely capable of doing for others

@hopsoft that's how we'll know if we're talking to a human or a bot on the internet: humans on the internet never admit this

ChatGPT just told me, "I stand corrected." after I pointed out that its answer to a question was garbage. 😆