The RubyLA blog offers insights, tutorials, and community updates for Ruby developers in Los Angeles and beyond. Developers can explore Ruby language features, web development frameworks, and best practices for building Ruby applications. Additionally, the blog covers Ruby meetups, events, and job opportunities in the Los Angeles area, fostering collaboration and networking within the local Ruby community.

RUBYLAND

Challenges the common belief that tests should never be deleted, arguing that tests exist primarily to build confidence in code changes. When tests become flaky, overly brittle, too slow to run regularly, or test outdated requirements, they actually decrease confidence and should be removed. The key principle is that any test that harms rather than helps developer confidence in their changes should be deleted rather than maintained.

You should delete tests

<p>I think it should be more like keep tests for the final version rather than the developpement environment therefore debugging happens quicker. but tests are crucial in case you modify expected behaviour</p>
