2 ms·

Also, stack trace should show you everything you need to know to fix this, or am I missing something? (no experience with Ruby) Otherwise, I see the cleanups a

Also, stack trace should show you everything you need to know to fix this, or am I missing something? (no experience with Ruby) Otherwise, I see the cleanups and refactoring as part of normal development process. There is no need to put such tasks in Jira - they must be done as preparation for the regular tasks. I can imagine that some companies take agile too seriously and want to micromanage every little task, but I guess lack of time for refactoring is not the biggest problem.

colechristensen 2y ago
"why don't you just" comments are easy :) (I made one) debugging in codebases with a lot of magic (rails) is hard. it can be very difficult to follow calls around unless you're quite the expert. certain styles of programming really frustrate me, but then again I program like a scientist so the kinds of things I'm prone to do frustrate software engineers (for loops nested 8 deep, preference for single character variables, etc.)
- temporallobe 2y ago
  You’re spot-on with the “magic” of Rails. While it can be very powerful and feature-rich, it can feel like a black box at times and stack traces aren’t always accurate or helpful. To be fair, this happens with a lot of library-heavy frameworks though, Spring Boot being a prime example of this.