@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.
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.
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
@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.
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